doc(changelog): suggestions of cargo fix are nightly only

https://github.com/rust-lang/cargo/blob/64e46b080e7c32a951b5e1291e09a056354d6af5/src/cargo/core/compiler/job_queue.rs#L1237

@bors r+

:pushpin: Commit 1b54716b15a53339645362ce3daf55408fa24711 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit 1b54716b15a53339645362ce3daf55408fa24711 with merge 4754751c4e9b27d75abe5cf88525d43bb5f57833...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 4754751c4e9b27d75abe5cf88525d43bb5f57833 to master...


Where is 1.4.0 version in GIT?

Looks like there is a 1.4.0 tag: https://github.com/otros-systems/otroslogviewer/releases


NoMethodError thrown when using chocolatey resource on a system with Chef 13 client

Cookbook version
1.2.1
Chef-client version
13.6.4
Platform Details
System Info:
chef_version=13.6.4
platform=windows
platform_version=6.3.9600
ruby=ruby 2.4.2p198 (2017-09-14 revision 59899) [i386-mingw32]
program_name=C:/opscode/chef/bin/chef-client
executable=C:/opscode/chef/bin/chef-client

Scenario:
Using an internal Chef recipe that retrieves and installs a package from the chocolatey repository on a Windows system with Chef 13 client. The internal Chef recipe wasn't changed and has worked without fail on Windows systems with Chef 12 clients.
Steps to Reproduce:
In my recipe, I called include_recipe 'chocolatey::default' then added a chocolatey resource block:
mysql_version = node[:te][:database][:version]
chocolatey "mysql #{mysql_version}" do
  package 'mysql'
  version mysql_version
end

Expected Result:
Chocolatey should retrieve and install the specified version of MySQL
Actual Result:
Using the chocolatey resource on a Windows system running latest Chef 13 client results in a thrown exception:
NoMethodError
-------------
undefined method `new' for Chocolatey:Module
Cookbook Trace:
---------------
C:/chef/cache/cookbooks/chocolatey/providers/default.rb:31:in `load_current_resource'
Resource Declaration:
---------------------
 # In C:/chef/cache/cookbooks/te_mysql/recipes/windows.rb

25: chocolatey "mysql #{mysql_version}" do
26:   package 'mysql'
27:   version mysql_version
28: end
29:

I should have read the note in the readme before posting this. Changing the resource name to chocolatey_package resolved the issue. :man_facepalming:


Add parent account page

Parent Profile:
username
first and last name
email
number of dependents and age
"about us"
Request for babysitter through city location

created


smart-sizing feature does not work

Hi I'm on Ubuntu 13.04 and run "This is FreeRDP version 1.1.0-beta1 (git 1.1.0-beta+2013071101-226-g558d4)" compiled from git.
I connect to my Windows 7 Pro 64bit "  6 xfreerdp +smart-sizing +compression +clipboard -sec-nla /network:lan /workarea /v:<IP_ADDRESS> /jpeg"
I can't resize the window

I got excited pre-maturely, it seems.
I compiled the newest master and checked out the /smart-sizing feature.
It doesn't do what I hoped for. I was hoping for the following behaviour: If the local X11 window size changes (I use a framing window manager and moving an 'app' between frames results in a window size change), the remote desktop geometry is changed to that new size.
This is obviously not what /smart-sizing feature does. I think it should be called /smart-scaling, because it just scales the offscreen bitmap to the local size (and quite badly, too).
Thank you guys for your great work anyway.
Is there any chance I can get the feature I'm looking for? As a layman I'm thinking it shouldn't be too hard if the rdp protocol allows for changing the remote screen size.

Same for me. ;) That current situation is really disappointing, at least given the name of the feature.

Regarding the name please complain complain at Microsoft. FreeRDP always tries to use the same terms. And no, AFAIK the rdp protocol does not support client-initiated resizing during an activated session. Further reading:
https://technet.microsoft.com/en-us/library/ff393693(v=ws.10).aspx
http://blogs.msdn.com/b/rds/archive/2008/08/07/smart-sizing-the-ts-client.aspx
http://superuser.com/questions/98494/windows-rdp-possible-to-resize-resolution-on-the-fly
@molecular please elaborate regarding your comment "and quite badly too" ?
xfreerdp uses XRenderComposite with the bilinear filter to scale the content. Usually this gives the best balance between image quality and performance. If it looks totally bad then maybe your graphics driver is to blame. But I'd need to see a screen shot in order to judge.

Sorry, I did not want to be harsh.
I was pretty sure that latest versions of remote desktop protocal allows real resize (changing resolution). But I was wrong... So probably freerdp does the best it can do.
Still a bad idea from Microsoft to name it "smart". I do not think there is anything smart with scaling remote sessions.

@eworm-de I think the channel that support changing resolution (disp) is only supported in xfreerdp 1.2. Anyway I have no idea how you can use it in the client.

@hardening cool! never took a closer look at the MS-RDPEDISP channel:
https://msdn.microsoft.com/en-us/library/dn366738.aspx
Obviously MS only implemented it in Windows 8.1 / Server 2012 R2.
But it seems that using that channel the client can trigger a session resize (resulting in a deactivation-reactivation sequence if egfx is not used).
There is already an implementation in FreeRDP: https://github.com/FreeRDP/FreeRDP/tree/master/channels/disp/
However, no integration in any client yet.

I will post screenshots of the scaling on my machine. Looks like nearest neighbor to me. Of course it might be my graphics card setup.
It's regrettable that the protocol doesn't support re-sizing.
To be honest: I probably wouldn't mind a reconnect on size-change (most probably will, though).
Another thing that would greatly easy the pain I have with my framing wm (notion) would be if xfreerdp would assume the window size upon startup if no geometry parameters are given. I'm not sure how exactly initial sizing of windows works. Probably X11 lets the app choose a window size initially and only later, when it's being bound to the frame, is it changed to fit the frame.
I understand the problems I have are specific to using a framing window manager and I didn't mean to come across negatively. I was just disappointed because I thought my long-running problem had been finally solved and it wasn't.
To say something positive: I discovered that clipboard syncing actually seems to work reliably now (not sure since when), so I'm switching back from rdesktop (where the clipboard sync only works in conjunction with certain other local apps (works with scite, for example), not with others (doesn't work with sublime text, for example) and sometimes not at all (even made a habit of hitting Ctrl-C on the remote machine 3 times to make it more reliable)) to xfreefdp.
Keep up the great work!


Add support for typesense vector database

I am loving the vector db integrations, maybe @jasonbosco could help integrate typesense?

Happy to!
@hwchase17 We have a vector search / store feature in Typesense: https://typesense.org/docs/0.24.0/api/vector-search.html
If you'd be down for an integration, I can take a stab at a PR. Let me know.

yes would love one! happy to help, but im super familiar with typesense so if wanted to start a pr @jasonbosco that may be most efficient

@hwchase17

but im super familiar with typesense so if wanted to start a pr

Did you mean to say "but im NOT super familiar with typesense" and that you wanted me to start a PR right?
Just wanted to double-check.

@JohnShahawy I took a first stab at a PR that adds support for Typesense here: #1674. However, since I haven't used langchain before, I haven't tested it. I'd love to collaborate with you and get your help to test this PR out and fix any last-mile issues.
Once you're able to get this PR to a working state, I can then write some automated tests based on the tests I see for other vector stores.

Or may be @hwchase17, if you're able to help with the above that would work as well :)

Would be nice to have Typesense support!


Any way to support network-connected printers like PT-9800PCN?

Hi, great work here. Is there any way you know of to add network capability to this tool? Thanks.

Is there any way you know of to add network capability to this tool?

Unless someone else following this repo knows, I think it's better to address this question to the author and maintainer of ptouch-print.  My guess is that the current implementation is USB-only.
FWIW,  I have my PT-450 connected to an always-on Raspberry Pi. When I print, I SSH to the Pi and call ptouch-print image.png from there.


Problem: NEList breaking change unincorporated

Solution:

Incorporate it, but see #47 for less verbosity
While at it, fix unused variables warnings for named instances
Update manual instance resolution to use the underscored instance variables

TESTS PASS!

Mon Jan 23 21:46:46:761550800 sweater@conflagrate ~/github/Megaparsec.lean (cognivore/bump-nelist)
λ lego
Welcome to Megaparsec.lean!
Usage examples are available in the ./Examples directory,
as well as in the test suite.
Building Tests.Parsec
Building Tests.IO
Building Tests.StateT
Building Tests.Lisp
Running ./build/bin/Tests-Parsec
duplicate errors:
  ✓ parsing fails
  ✓ only one parse error
  ✓ two expected values, not three
✓ eof: parsing successful
given string: successful parsers:
  ✓ yatima: parsing successful
  ✓ parsed out 'yatima'
  ✓ parsing 'yatima' from 'yatimaaaa!': parsing successful
  ✓ leftover string is 'aaa!'
  ✓ parsing 'yat', then 'ima' from 'yatima!': parsing successful
given string: failing parsers:
  ✓ yatimA: parsing fails
  ✓ parsing 'yat', then 'ima' from 'yatimA!': parsing fails
Char.lean combinators:
  ✓ char' is case-insensitive: parsing successful
  ✓ parsed out 'y'
  ✓ eol: parsing successful
  ✓ parsed out newline
option combinator:
  ✓ none: parsing successful
  ✓ none
  ✓ raw some: parsing successful
  ✓ some
  ✓ some following none: parsing successful
  ✓ some
  ✓ holds 'hellraiser'
  ✓ some following some: parsing successful
  ✓ some
  ✓ holds 'hellraiser'
some' and many' combinators:
  ✓ many' on empty string: parsing successful
  ✓ result is empty list
  ✓ many' on matching string: parsing successful
  ✓ result is two reads
  ✓ some' on empty string: parsing fails
  ✓ some' on matching string: parsing successful
  ✓ result is two reads
sepEndBy1' combinator:
  ✓ parsing successful
  ✓ result is two reads
simple parsing:
  ✓ "3 2 1": parsing successful
  ✓ parsed out 3, 2, 1
  ✓ "5|": parsing successful
  ✓ parsed out 5
  ✓ "5": parsing fails
  ✓ "55|": parsing fails

Running ./build/bin/Tests-IO
✓ file, manual newline: parsing successful
✓ parsed out 'abcd'
✓ file, no newline: parsing successful
✓ parsed out 'abcd'
✓ file, newline combinator: parsing successful
✓ parsed out 'cd'

Running ./build/bin/Tests-StateT
✓ StateT with failing parser: fails
✓ StateT parsing successful
✓ state is 42
✓ empty string parsed out

Running ./build/bin/Tests-Lisp
ignore:
  ✓ all spaces
  ✓ comment
  ✓ leading
lisp parsing:
"a" ;:
    ✓ parsing successful
    ✓ as expected
("hello" ("beautiful" "world")) ; ())(lol n1 bug ))()):
    ✓ parsing successful
    ✓ as expected

All tests passed!

I won't do #47 at the moment, please refrain from pointing out verbosity of constructing NELists in your review.


Env followup

ENV object: Follow up from GH-148.

Modify backend trait to return Result with Env Error.
Make env module Error into an Error type.
Handle null byte in env::var_os (fixes segfaulting test introduced in
previous commit).
Return Error::Fatal instead of unwrapping, e.g. HashMap backend with
RwLock.
Move arg validation into backend implementation.
Move calls to raise into C API to work prevent memory leaks with
longjmp.
get set and to_h internal return Value instead of sys::mrb_value.

mruby 2.0 [2.0.1-12]
[Compiled with rustc 1.38.0-nightly 6e310f2 2019-07-07]
>>> ENV["as\0"]
Backtrace:
    (airb):1: bad environment variable name: contains null byte (ArgumentError)
    (airb):1
>>> ENV["as\0"] = "a"
Backtrace:
    (airb):2: bad environment variable name: contains null byte (ArgumentError)
    (airb):2
>>> ENV["as"] = "a\0"
Backtrace:
    (airb):3: bad environment variable value: contains null byte (ArgumentError)
    (airb):3

cc @cdeler


[ADAM-493] Add ADAM-on-Spark-on-YARN docs.

Resolves #493.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1657/
Test PASSed.

@heuermh addressed comments.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1659/
Test PASSed.

Thank you, @fnothaft


esp32c6 use idf5.1 rmt two channel send (IDFGH-10882)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
esp32c6-wroom-1U
Power Supply used.
USB
What is the expected behavior?
rmt_tx_channel_config_t tx_chan_config = {
.clk_src = RMT_CLK_SRC_DEFAULT, // select source clock
.gpio_num = RMT_LED1_STRIP_GPIO_NUM,
.mem_block_symbols = 64, // increase the block size can make the LED less flickering
.resolution_hz = RMT_LED_STRIP_RESOLUTION_HZ,
.trans_queue_depth = 1, // set the number of transactions that can be pending in the background
.flags.with_dma = false,
};
ESP_ERROR_CHECK(rmt_new_tx_channel(&tx_chan_config, &led_chan[0]));
rmt_tx_channel_config_t tx_chan_config1 = {
.clk_src = RMT_CLK_SRC_DEFAULT, // select source clock
.gpio_num = RMT_LED2_STRIP_GPIO_NUM,
.mem_block_symbols = 128, // increase the block size can make the LED less flickering
.resolution_hz = RMT_LED_STRIP_RESOLUTION_HZ,
.trans_queue_depth = 1, // set the number of transactions that can be pending in the background
.flags.with_dma = false,
};
ESP_ERROR_CHECK(rmt_new_tx_channel(&tx_chan_config1, &led_chan[1]));
// 安装同步管理器
rmt_sync_manager_handle_t synchro = NULL;
rmt_sync_manager_config_t synchro_config = {
.tx_channel_array = led_chan,
.array_size = sizeof(led_chan) / sizeof(led_chan[0]),
};
ESP_ERROR_CHECK(rmt_new_sync_manager(&synchro_config, &synchro));
led_strip_encoder_config_t encoder_config = {
.resolution = RMT_LED_STRIP_RESOLUTION_HZ,
};
ESP_ERROR_CHECK(rmt_transmit(led_chan[0], led_encoder[0], led_strip_pixels[0], sizeof(led_strip_pixels[0]), &tx_config[0]));
ESP_ERROR_CHECK(rmt_transmit(led_chan[1], led_encoder[1], led_strip_pixels[1], sizeof(led_strip_pixels[1]), &tx_config[1]));
use this code open two rmt channel,it's wrong in this log:
E (1283) rmt: rmt_tx_register_to_group(131): no free tx channels
E (1283) rmt: rmt_new_tx_channel(232): register channel failed
What is the actual behavior?
init two channel wrong log:
E (1283) rmt: rmt_tx_register_to_group(131): no free tx channels
E (1283) rmt: rmt_new_tx_channel(232): register channel failed
Steps to reproduce.

power on
wong in open two rmt channel

Debug Logs.
E (1283) rmt: rmt_tx_register_to_group(131): no free tx channels
E (1283) rmt: rmt_new_tx_channel(232): register channel failed

More Information.
No response

@Shaco-Ma RMT only has two TX channels on esp32-c6. By average, one TX channel has 48 words of clock memory. If you set a value bigger than that, the previous channel will occupy the next channel.
--- .mem_block_symbols = 64, // increase the block size can make the LED less flickering
+++ .mem_block_symbols = 48,

@Shaco-Ma RMT only has two TX channels on esp32-c6. By average, one TX channel has 48 words of clock memory. If you set a value bigger than that, the previous channel will occupy the next channel.
--- .mem_block_symbols = 64, // increase the block size can make the LED less flickering
+++ .mem_block_symbols = 48,

OK,thanks,but the docs in https://docs.espressif.com/projects/esp-idf/zh_CN/release-v5.1/esp32c6/api-reference/peripherals/rmt.html is Wrong.......
thanks very much!


Fix overlay

Recent introduction of the background overlay (ZStack) has broken nesting, I believe:
// Playground generated with 🏟 Arena (https://github.com/finestructure/arena)
// ℹ If running the playground fails with an error "no such module ..."
//    go to Product -> Build to re-trigger building the SPM package.
// ℹ Please restart Xcode if autocomplete is not working.

import Gala
import PlaygroundSupport
import SwiftUI

struct ContentView: View {
    var body: some View {
        VStack {
            Text("🎭 Gala").font(.title).padding()
            Text("🎭 Foo").font(.title).padding()
        }
    }
}

struct Preview: PreviewProvider {
    static var previews: some View {
        NightAndDay {
            Layouts([.sizeThatFits, .fixed(width: 200, height: 200)]) {
                ContentView()
            }
        }
    }
}

PlaygroundPage.current.setLiveView(Preview.previews)

This should be showing four tiles and I believe it isn't, because they're overlaid.

This might be fixed by #7 as well

Indeed it is fixed in 0.3.2:


Android version?

It would be great if I could install this on my Android TV box as well. BTW thanks. You are a wonderful dev!

hi! I think unfortunately that's not as easy because ezshare is written in javascript/nodejs, and afaik android cannot run node.js, but I agree it would be very cool!


Pagination

Here is the code of mine for fetching data records
angular.module('clientApp')
.controller('BlogCtrl', function ($scope, Blog) {
$scope.blogs = Blog.getList().$object;
});
How do i do pagination using restangular ?
Tried following but didn't work
$scope.blogs = Blog.getList({page: 1, pageSize: 2}).$object;

You have to pass the pagination param of your api.
They are called page and pagSize?


Add EEA token execution logic application with updated license

Signed-off-by: reckeyzhang<EMAIL_ADDRESS>

Next time instead of opening a new PR, force push (push -f) the current PR if you need to add a DCO line to your commit.

Previously filed as PR #38 and PR #52.

Is there any  read me to understand about EEA token ?


Split INTERNAL code path.

Currently, "INTERNAL" code path splits out retail/internal beta code, leaving us with internal beta/debug/psx no cd code.
INTERNAL code path should be split properly i.e:

All INTERNAL BETA specific code should be kept wrapped in "INTERNAL_BETA".
All Debug code should be wrapped in "DEBUG_VERSION".
All file io/cd operations should be wrapped in "NO_CD" (use of SIO).

Will allow us to properly mix debug/no-cd code into the retail code path. Note: I have not yet seen a case where game code logic has changed between retail/internal.

Bug: INTERNAL, file.c not using sio

Solved in: c34dd68471faf6c09167dbb15d66fcbba7e6adc6
Above comment is still valid thus this issue will remain open.

Non-disc version now makes use of sio1.


Add Met Museum API (Art)

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is ordered alphabetically
[x] My submission has a useful description
[x] The description does not end with punctuation
[x] Each table column is padded with one space on either side
[x] I have searched the repository for any relevant issues or pull requests
[x] Any category I am creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for the contribution @guillaumebdx!
Closing the PR - the API is already in the README 😄 .


Add to #630: update jsonapi-spec.md too

What this PR does:
Updates documentation wrt limit introduced in #630
Which issue(s) this PR fixes:
Fixes #630
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

/cc @johnsmartco Forgot to include update in main PR, so here's separate one.

Need to force push since this does not trigger CI jobs.


WIP:  Fix engine import test

Fixes how extension names are tested and updates the extension names for JYULB and Openfoam wrappers  (#45)

@itziakos .  I took a stab at #45 .  Can you see if this looks alright.  (Note that this PR is set to merge these commits to upgrade-openfoam-0.1.3)

@itziakos ,  hold off on looking at this.   its failing cause the build/tests for Travis-CI is failing as it is taking longer than 50 minutes.  i will look at addressing that on monday.

@nathanfranklin, this is a good idea.

@itziakos , thanks!  Left one comment, but otherwise looks good to me.
(Note that this PR is set to merge these commits to upgrade-openfoam-0.1.3 but should be now actually merge to master)

closing to make a new pr against master


Revert "bug: remove additional operator-backed items in the developer…

… catalog in Dev Console (#165)"
This reverts commit 8bae146aa37cf6a6eca506ee0e28e2a9272760b1.
Need to use Annotations to hide internal APIs ...
https://github.com/operator-framework/operator-lifecycle-manager/pull/1097#issuecomment-561177674
What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind bug
/kind cleanup
/kind failing-test
/kind enhancement
/kind documentation
/kind code-refactoring

What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
Test acceptance criteria:

[ ] Unit Test
[ ] E2E Test

How to test changes / Special notes to the reviewer:

/approve

@shubhamagarwal19 what about marking gitopsservice as an internal object using the annotation operators.operatorframework.io/internal-objects
Are you planning to raise a separate PR for that change ?

Are you planning to raise a separate PR for that change ?

Yes, please make it a separate PR.

/lgtm

/kind bug


Fix broken links in CODE_OF_CONDUCT.md

Description

This PR fixes two broken links to other markdown files. Some relative links in the developer docs stopped working after the files were moved into docs/.
Type of change

[x] This change is a documentation update

References

How has this been tested?

[x] I made the changes, then clicked on the new links.

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

while we're at it, I found two other in-page links that were incorrectly formatted in CORE_DEV_GUIDE.  I just added those changes to the PR

Thanks @tlambert03 !


Can't link with -lX11

I've used linuxbrew to install gcc 5.3 on a machine on which I don't have sudo access. I now want to link with X11:
> gcc test.c -lX11
ld: cannot find -lX11

I've checked that libX11.so exists in /usr/lib64/ which is on the compiler's LIBRARY_PATH. If I use the system's gcc it works fine, but I need a newer version to compile my actual program.

Some more information:
bash-4.2$ brew config
HOMEBREW_VERSION: 0.9.5
ORIGIN: https://github.com/Linuxbrew/linuxbrew.git
HEAD: dc1c2b57d5b9253f19d667976d098ecb1a4566d8
Last commit: 2 weeks ago
HOMEBREW_PREFIX: /om/user/vladfi1/linuxbrew
HOMEBREW_REPOSITORY: /om/user/vladfi1/linuxbrew
HOMEBREW_CELLAR: /om/user/vladfi1/linuxbrew/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://linuxbrew.bintray.com
CPU: 40-core 64-bit ivybridge
Kernel: Linux 3.10.0-229.el7.x86_64 x86_64 GNU/Linux
OS: CentOS Linux release 7.2.1511 (Core)
OS glibc: 2.17
OS gcc: 4.8.5
Linuxbrew glibc: 2.19
Linuxbrew gcc: 5.3.0
Clang: N/A
X11: 2.7.8 => /usr
System Ruby: 2.0.0-p598 => /usr/bin/ruby
Perl: /usr/bin/perl
Python: /usr/bin/python => /usr/bin/python2.7
Ruby: /usr/bin/ruby
Java: openjdk version "1.8.0_71"
bash-4.2$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Homebrew's sbin was not found in your PATH but you have installed
formulae that put executables in /om/user/vladfi1/linuxbrew/sbin.
Consider setting the PATH for example like so
    echo 'export PATH="/om/user/vladfi1/linuxbrew/sbin:$PATH"' >> ~/.bash_profile

Warning: Your Homebrew is outdated.
You haven't updated for at least 24 hours. This is a long time in brewland!
To update Homebrew, run `brew update`.

Maybe try adding -Wl,-rpath,$(DEFAULT_LIB_INSTALL_PATH)?
If that fails, there's some other advice at https://stackoverflow.com/questions/8835108/how-to-specify-non-default-shared-library-path-in-gcc-linux-getting-error-whil

Adding -Wl,-rpath,/usr/lib64 didn't seem to change anything. The stackoverflow thread talks about a runtime error, not a linktime error, so I'm not sure if it is applicable.

Can you show the LIBRARY_PATH variables for both compilers (system and Linuxbrew)? Maybe that will provide some more insight.

brew gcc:
LIBRARY_PATH=/om/user/vladfi1/linuxbrew/Cellar/gcc/5.3.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/5.3.0/:/om/user/vladfi1/linuxbrew/Cellar/gcc/5.3.0/bin/../lib/gcc/:/om/user/vladfi1/linuxbrew/Cellar/gcc/5.3.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/5.3.0/../../../../lib64/:/lib/../lib64/:/usr/lib/../lib64/:/om/user/vladfi1/linuxbrew/Cellar/gcc/5.3.0/bin/../lib/gcc/x86_64-unknown-linux-gnu/5.3.0/../../../:/lib/:/usr/lib/

system gcc:
LIBRARY_PATH=/usr/lib/gcc/x86_64-redhat-linux/4.8.5/:/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/:/lib/../lib64/:/usr/lib/../lib64/:/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../:/lib/:/usr/lib/

Note that both contain /usr/lib/../lib64/.

I apologize, but I'm not sure.
As a workaround, if you'd like you can build Linuxbrew's X11 and try using that:
$ brew tap linuxbrew/xorg
$ brew install xorg

My solution was to replace a bunch of instances of -lFoo with /usr/lib64/libFoo.so, which allowed the link step to succeed. The binary then crashed at runtime with missing libs, but that was fixed by exporting LD_LIBRARY_PATH=/usr/lib64.
Obviously I would like a better solution, as this requires editing autogenerated Makefiles.

I've also tried adding in -L/usr/lib64. If I'm using C++, I get an error.
$ g++ test.cpp -L/usr/lib64 -lX11
/om/user/vladfi1/linuxbrew/lib/libstdc++.so: undefined reference to<EMAIL_ADDRESS>
But it works if I use plain gcc.

The simplest solution is brew install linuxbrew/xorg/xorg
The linuxbrewed gcc removes /usr/lib64 from the library path because mixing system libraries with brewed libraries creates havoc.

That worked! Thanks @sjackman for clearing this up.


Don't crash when upgrading volume attachments after a previous failure

longhorn/longhorn#6653
Problem:
The v1.4.x -> v1.5.0 upgrade logic caches entirely new Longhorn volume attachments. The v1.5.2 logic that ultimately updates the volume attachments on the cluster assumes that it should do an update to any existing Longhorn volume attachments with the contents of the cached resources. If, for some reason, a previous upgrade v1.4.x -> v1.5.2 failed BUT successfully created Longhorn volume attachments, that logic attempts to do an update with an entirely new Longhorn volume attachment. This is illegal, as metadata.resourceVersion is not set.
Solution:
Populate the cache with existing Longhorn volume attachments in the v1.4.x -> v1.5.0 upgrade logic. When we reach the point of actually doing the updates on the cluster, metadata.resourceVersion is set.
We do not need to add this fix to master/v1.6.0-dev. That version includes simpler upgrade logic (Longhorn volume attachments already exist during the upgrade and never need to be created).

v1.5.x upgrades from v1.4.4 are still failing due to https://github.com/longhorn/longhorn/issues/6987. That issue is the cause of the first upgrade failure in v1.5.2-rc1. However, this issue was the direct cause of all subsequent failures. With the fix, logs show that only that issue is blocking upgrade completion.
Every time a longhorn-manager pod obtains leadership NOW:
eweber@laptop:~/longhorn> kl get lhva -oyaml
apiVersion: v1
items:
- apiVersion: longhorn.io/v1beta2
  kind: VolumeAttachment
  metadata:
    creationTimestamp: "2023-10-27T14:35:00Z"
    finalizers:
    - longhorn.io
    generation: 1
    labels:
      longhornvolume: pvc-4c988790-5ca1-4369-b8ab-5be0c167151b
    name: pvc-4c988790-5ca1-4369-b8ab-5be0c167151b
    namespace: longhorn-system
    ownerReferences:
    - apiVersion: longhorn.io/v1beta2
      kind: Volume
      name: pvc-4c988790-5ca1-4369-b8ab-5be0c167151b
      uid: f427c926-e96b-49d8-8eed-11a92bb68195
    resourceVersion: "80139613"
    uid: c545b493-6b00-4303-8bde-2b1e2afeab50
  spec:
    attachmentTickets:
      csi-1cc86888d9d3f2cd88a5abd0a0224828dcbefd4abd47c5339da00ca66fbcf4e0:
        generation: 0
        id: csi-1cc86888d9d3f2cd88a5abd0a0224828dcbefd4abd47c5339da00ca66fbcf4e0
        nodeID: eweber-v125-worker-e472db53-9kz5b
        parameters:
          disableFrontend: "false"
        type: csi-attacher
    volume: pvc-4c988790-5ca1-4369-b8ab-5be0c167151b
kind: List
metadata:
  resourceVersion: ""

eweber@laptop:~/longhorn> kl logs longhorn-manager-v6j69
...
time="2023-10-27T16:18:28Z" level=info msg="Start upgrading" func=upgrade.upgrade.func1 file="upgrade.go:129"
time="2023-10-27T16:18:28Z" level=info msg="No API version upgrade is needed" func=upgrade.doAPIVersionUpgrade file="upgrade.go:175"
time="2023-10-27T16:18:28Z" level=info msg="Walking through the resource upgrade path v1.4.x to v1.5.0" func=upgrade.doResourceUpgrade file="upgrade.go:231"
time="2023-10-27T16:18:29Z" level=info msg="Walking through the resource upgrade path v1.5.1 to v1.5.2" func=upgrade.doResourceUpgrade file="upgrade.go:237"
time="2023-10-27T16:18:29Z" level=info msg="Walking through the resource status upgrade path v1.4.x to v1.5.0" func=upgrade.doResourceUpgrade file="upgrade.go:249"
time="2023-10-27T16:18:29Z" level=info msg="Finish upgrading" func=upgrade.upgrade.func1.1 file="upgrade.go:126"
panic: assignment to entry in nil map

goroutine 1742 [running]:
github.com/longhorn/longhorn-manager/upgrade/util.CreateOrUpdateLonghornVersionSetting({0xc00005602e, 0xf}, 0xc00318f650)
        /go/src/github.com/longhorn/longhorn-manager/upgrade/util/util.go:167 +0x1ac
github.com/longhorn/longhorn-manager/upgrade.doResourceUpgrade({0xc00005602e, 0xf}, 0x28266b8?, 0xc00318f650?)
        /go/src/github.com/longhorn/longhorn-manager/upgrade/upgrade.go:262 +0x41b
github.com/longhorn/longhorn-manager/upgrade.upgrade.func1({0x0?, 0x0?})
        /go/src/github.com/longhorn/longhorn-manager/upgrade/upgrade.go:133 +0x13a
created by k8s.io/client-go/tools/leaderelection.(*LeaderElector).Run
        /go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/client-go/tools/leaderelection/leaderelection.go:208 +0x105

Instead of BEFORE:
apiVersion: v1
items:
- apiVersion: longhorn.io/v1beta2
kind: VolumeAttachment
metadata:
  creationTimestamp: "2023-10-27T08:18:30Z"
  finalizers:
  - longhorn.io
  generation: 1
  labels:
    longhornvolume: pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802
  name: pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802
  namespace: longhorn-system
  ownerReferences:
  - apiVersion: longhorn.io/v1beta2
    kind: Volume
    name: pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802
    uid: db89e6d5-854e-4d1b-9ef8-ba41d4613fc8
  resourceVersion: "3002"
  uid: 5f7a6c31-27ae-4e3c-9797-47398b8f643c
spec:
  attachmentTickets:
    csi-bc2f093b83b08716700629ee0a81e7119b8fe8e43dfaddf8684863d91fc5afca:
      generation: 0
      id: csi-bc2f093b83b08716700629ee0a81e7119b8fe8e43dfaddf8684863d91fc5afca
      nodeID: ip-172-31-34-145
      parameters:
        disableFrontend: "false"
      type: csi-attacher
  volume: pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802
kind: List
metadata:
resourceVersion: ""

root@ip-172-31-47-207:/home/ubuntu# k logs longhorn-manager-b8qmw -n longhorn-system
...
time="2023-10-27T08:35:07Z" level=info msg="Start upgrading" func=upgrade.upgrade.func1 file="upgrade.go:129"
time="2023-10-27T08:35:07Z" level=info msg="No API version upgrade is needed" func=upgrade.doAPIVersionUpgrade file="upgrade.go:175"
time="2023-10-27T08:35:07Z" level=info msg="Walking through the resource upgrade path v1.4.x to v1.5.0" func=upgrade.doResourceUpgrade file="upgrade.go:231"
time="2023-10-27T08:35:07Z" level=info msg="Walking through the resource upgrade path v1.5.1 to v1.5.2" func=upgrade.doResourceUpgrade file="upgrade.go:237"
time="2023-10-27T08:35:07Z" level=debug msg="admit result: UPDATE longhorn.io/v1beta2, Kind=VolumeAttachment longhorn-system/pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802 user=system:serviceaccount:longhorn-system:longhorn-service-account allowed=true err=<nil>" func="webhook.(*Router).admit" file="router.go:89"
time="2023-10-27T08:35:07Z" level=error msg="Upgrade failed: upgrade resources failed: volumeattachments.longhorn.io \"pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802\" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update" func=upgrade.upgrade.func1.1 file="upgrade.go:124"
time="2023-10-27T08:35:07Z" level=info msg="Upgrade leader lost: ip-172-31-46-9" func=upgrade.upgrade.func2 file="upgrade.go:138"
time="2023-10-27T08:35:07Z" level=fatal msg="Error starting manager: upgrade resources failed: volumeattachments.longhorn.io \"pvc-7a0a31ef-0a34-4ee7-9562-43a7db1e7802\" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update" func=app.DaemonCmd.func1 file="daemon.go:83"

Sorry, renamed branch and accidentally closed this PR. Reopening.


Need examples With Huge Export Options For Reference

Able to find huge examples for datatables..However unable to find huge examples for this particular project with huge export options...
May be the examples can be part of the examples folder...Best would be single HTML with huge export options for quick understanding.
Example,
https://github.com/baksoy/datatables
https://datatables.net/extensions/buttons/examples/html5/simple.html
https://datatables.net/extensions/buttons/examples/initialisation/export
https://github.com/hhurz/tableExport.jquery.plugin
https://jsfiddle.net/gr5er1pj/1/
https://codepen.io/GiSmo/pen/pbjzXw
http://plnkr.co/edit/Yz9qYytTkD3UnjrW9J49?p=preview
http://technoscripts.com/export-html-table/

Thanks for considering this module. ;)
Yet, I must say pick any table export plugin of your preference. This plugin does a single thing (which is Make your HTML tables look great on every device).
Please let me know if you believe you found any problem caused by this module here.


[AIRFLOW-XXX] Add DoorDash to README.md

DoorDash uses Airflow in their work https://softwareengineeringdaily.com/2018/09/28/doordash/
Have added on the list
Make sure you have checked all steps below.
Jira

[ ] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3980 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3980   +/-   ##
=======================================
  Coverage   75.07%   75.07%
=======================================
  Files         199      199
  Lines       15965    15965
=======================================
  Hits        11986    11986
  Misses       3979     3979

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d03cc17...c88f5e0. Read the comment docs.


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 1243 ms

Resolved: Bofrost.fr performance has improved in 8301fbc after 6 minutes.


mobile responsive

Description
Made mobile responsive
Related Issues
#103
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

You should release the latest version on github :)


Adding Admin on rest feathers client and example

Signed-off-by: José Luis Di Biase<EMAIL_ADDRESS>Summary
Adding the Admin on rest feathers client to the list and adding an example on how to use it.
Check https://github.com/josx/aor-feathers-client
Other Information
Using this adaptor between feathers and admin on rest, you can easily get a admin based on feathers backend.

It's been used by several people
More than 50 stars
More than tens contributor on the project
Several versions released.

It think It is worth it for this list.

Awesome, thank you!


Node workflow - Add version to commit, simplify cmake commands

The PR does two things discussed in slack.
1.) It adds the package version to the commit message when the version is bumped.
2.) It uses the same cmake command for both macos and linux. It removes DMBGL_WITH_COVERAGE from macos build and adds DCMAKE_BUILD_TYPE to the linux build by using the following command for both
cmake . -B build -G Ninja -DCMAKE_CXX_COMPILER_LAUNCHER=ccache -DCMAKE_BUILD_TYPE=${{ env.BUILDTYPE }}
EDIT:
I also added one extra thing. I added the ability to chose a preminor or premajor release type, so we could to something lile use premajor to release v6.0.0-pre.0

it seems like "cmake command for both macos and linux." isn't included in this PR

i must have accidentally wiped it out. I'll fix. it when I'm home later. I was also just thinking a
I need to keep in mind preminor/premajor during the npm publish

Great, then I'll leave this until. It's probably best if the change to the cmake command is applied both in node-ci and node-release, so they stay consistent.

Can we change prerelease to prepatch, to make that explicit?

Apparently I was wrong that the same cmake command works to macos and linux, so I reverted that and just removed DMBGL_WITH_COVERAGE from macos build and added DCMAKE_BUILD_TYPE to the linux build.
I've added prepatch and removed prerelease.

I think this should be ready, once that last MacOS ci completes


Missing en.json File Error When Running Fleek CLI

Bug Description:
After installing the Fleek CLI globally using npm, I attempted to check the version using the fleek version command, but I encountered an error related to a missing en.json file.
Error Message:
Error: ENOENT: no such file or directory, open 'C:\Users\HP Elitebook<EMAIL_ADDRESS>at readFileSync (node:fs:448:20) at loadJSONFromPackageRoot (C:\Users\HP Elitebook Mt44\AppData\Roaming\npm\node_modules@fleek-platform\cli\dist\bundle.js:105957:53)
Steps to Reproduce:

Run npm install -g @fleek-platform/cli
Run fleek version
See the error

Expected Behavior:
The command fleek version should display the version number without throwing an error.
System Information:

Node.js Version: v20.17.0
NPM Version: v10.8.3
Operating System: Windows 10
Fleek CLI Version: The latest version from npm

Additional Context:
I also received warnings about deprecated packages during installation:
npm WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. npm WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported.
Please let me know if any additional information is needed.

Since you are running the CLI on a windows machine, could you specify which command line tool was used to install the CLI ?
Please also try running powershell as administrator and then installing or using WSL

I used the command provided on fleek CLI, like fleek version, fleek. All
commands starting with fleek throw the same error. I have also tried
running as administrator but throws the same error message. That means the
command line only works in a Linux environment?
On Thu, Sep 26, 2024 at 9:57 AM Kanishk Khurana @.***>
wrote:

Since you are running the CLI on a windows machine, could you specify
which command line tool was used to install the CLI ?
Please also try running powershell as administrator and then installing or
using WSL
—
Reply to this email directly, view it on GitHub
https://github.com/fleek-platform/cli/issues/47#issuecomment-2376359357,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7FAUH4ADGDVVUPBUSJIQBDZYPEADAVCNFSM6AAAAABOUE344GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGM2TSMZVG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

the file doesn't exists in the package? so regardless of environment it will ended in error?

Hi @fleekgonzalo
Any chance you could add a warning in your documentation, telling that "at the moment you need a linux environment to run fleek cli. That means you should use WSL or similar on windows" ?
That would be great! Thanks


Using snorkel for Image Clasification/Detection

I am working on a binary classifier/detector involving Images. True if a particular object in present in the image and false if it doesnt. Is there an example to make snorkel work on Image data? Thanks.

Hi @anilmaddala ,
Sounds awesome! Can you give me more detail on your setup? Are your labeling functions written over the images as well, or over some associated text data?
If the former, we have a whole project (on the coral branch, merged into master soon) focused on this!  If the latter, the pipeline should be very similar to what's in the current notebooks... and we have an example tutorial which will be posted at some point soon as well
-Alex

Thanks @ajratner for the quick response.
I am currently doing labelling entirely upon Images, nothing to do with text. Basically an opencv based edge detector which classifes the image into blurry/non-blurry. Incendentally the object I am trying to detect is always moving, so slightly blurry.
So its a bit of cheating to create my training data based on blurriness and then to train a network on the object present in the training data. Any thoughts?
I will checkout the coral branch and looking forward for a tutorial.

@paroma any thoughts here?  Seems like good fit for Coral?

Hello, I'm also interested in that. I'm work on image segmentation via pixel-wise classification.
I've a set of image processing methods that segments quickly many images but with about 85% of accuracy. So I'm wondering if I could not consider it as noisy label and use your framework to train a better model to segment my images. Is that a good fit for Coral? if yes, please add me to the private repo. Thank you so much.

I am interested to understand how to use Snorkel for labeling certain actions of hands in images

First of all sorry for the late response, somehow missed the notification
The use case of detecting whether an object exists in an image is definitely a good fit for Coral. We have a private repo for that project that I can add you to if you think it would be useful!

Is still  the repo for Coral private? If not, can I be added? Thanks :)

added @johanna-codes and @iskode to the private Coral repo
Also check out the image tutorial here: https://github.com/HazyResearch/snorkel/tree/master/tutorials/images
Closing this for now!

Is still the repo for Coral private? If is possible, can you add me? I'm also trying to use the Snorkel and Coral to label images.

Hi,
I want to use for classification problem on medical images. The main classification would be if the image has lesion or no lesion. I would love to know the labeling functions that i can create for these image data sets

Hi @paroma @ajratner I am also interested in applying data programming on medical image domain. I had a paper: Adversarial Data Programming (https://arxiv.org/abs/1803.05137) CVPR 2018, based on the idea of Data Programming. I will be happy to be a part of the project - if you kindly add me to the private repo of Image Classification.
Regards,
Arghya Pal.

Hello,
First, the link for the image tutorial is not working. request the team to update the link.
and I'd request the team to add me into the private coral repo as I'm interested to use snorkel for labeling images for object detection.

Hi,
I am interested in how to label image data. I would request the team to add me to the coral repo.
Thanks.

Hi,
I'm interested in using Snorkel for labeling images, at both pixel and image-level. Could you please add me to the Coral repo.
Thank you.

Hello, Could I be added to the Coral repo? I'd like to apply weak supervision to image classification tasks


Need event system

Need event: beforeLoading, afterLoading.

You can use request_start, request_finish, and request_error


os.Exit(0) in lock.go prevents clean exit in main command

Because of this line, an interrupt signal automatically closes the application and a command can't have any proper cleanup of its own

Any suggestion on how to work around that?

Proposal: have a global list of cleanup handlers that are run when SIGINT is received, so that e.g. the mount command can leave a umount cleanup handler. Thoughts?


Issues with training using GMP

I hope you are doing well today. I have run into some issues when training models using GMP.
First, when the pruning is supposed to begin at the epoch args.init_prune_epoch, the following error is thrown from main.py:
Traceback (most recent call last):
  File "main.py", line 494, in <module>
    main()
  File "main.py", line 43, in main
    main_worker(args)
  File "main.py", line 143, in main_worker
    prune_decay = (1 - ((args.curr_prune_epoch - args.init_prune_epoch)/total_prune_epochs))**3
AttributeError: 'Namespace' object has no attribute 'curr_prune_epoch'

I performed a grep search for curr_prune_epoch and this is the only place it appears in the entire STR repo. Additionally, looking at older versions of the code I did not see any references to curr_prune_epoch. I suspect replacing curr_prune_epoch by epoch will result in the intended level gradual magnitude pruning. However, even if I make this substitution there is a second issue. Even before the pruning begins (at the epoch args.init_prune_epoch), the model does not appear to be learning. I attempted training smaller models on CIFAR-10 (Conv2/4/6 architectures from hidden-networks repo that are compatible with STR code) and after trying 30+ initializations I have not observed any model learning. I'm not sure if this is a phenomenon you have observed but based on the first issue it is unclear to me if this publicly available version GMP was successfully tested and I wanted to reach out and ask about these issues before trying to debug it any further. Below is the output of the 0th epoch for one such run (Loss at following epochs remains around 2.303):
Epoch: [0][  0/391]     Time  1.647 ( 1.647)    Data  0.371 ( 0.371)    Loss 3.793 (3.793)      Acc@1   7.81 (  7.81)   Acc@5  47.66 ( 47.66)
Epoch: [0][ 10/391]     Time  0.012 ( 0.162)    Data  0.000 ( 0.034)    Loss 2.303 (12.470)     Acc@1   7.81 ( 10.23)   Acc@5  56.25 ( 48.37)
Epoch: [0][ 20/391]     Time  0.012 ( 0.091)    Data  0.000 ( 0.018)    Loss 2.303 (7.628)      Acc@1   8.59 ( 10.16)   Acc@5  50.00 ( 48.07)
Epoch: [0][ 30/391]     Time  0.012 ( 0.066)    Data  0.000 ( 0.013)    Loss 2.303 (5.910)      Acc@1  10.94 ( 10.08)   Acc@5  50.78 ( 48.39)
Epoch: [0][ 40/391]     Time  0.012 ( 0.053)    Data  0.000 ( 0.011)    Loss 2.303 (5.030)      Acc@1  11.72 ( 10.33)   Acc@5  60.16 ( 48.91)
Epoch: [0][ 50/391]     Time  0.012 ( 0.046)    Data  0.000 ( 0.009)    Loss 2.303 (4.496)      Acc@1   7.81 (  9.99)   Acc@5  48.44 ( 49.53)
Epoch: [0][ 60/391]     Time  0.012 ( 0.041)    Data  0.000 ( 0.008)    Loss 2.303 (4.136)      Acc@1  12.50 ( 10.11)   Acc@5  46.09 ( 49.49)
Epoch: [0][ 70/391]     Time  0.012 ( 0.037)    Data  0.000 ( 0.007)    Loss 2.303 (3.878)      Acc@1   5.47 (  9.97)   Acc@5  50.00 ( 49.35)
Epoch: [0][ 80/391]     Time  0.014 ( 0.034)    Data  0.000 ( 0.007)    Loss 2.303 (3.683)      Acc@1  10.94 ( 10.03)   Acc@5  49.22 ( 49.15)
Epoch: [0][ 90/391]     Time  0.012 ( 0.032)    Data  0.000 ( 0.007)    Loss 2.303 (3.532)      Acc@1   7.03 ( 10.01)   Acc@5  47.66 ( 49.43)
Epoch: [0][100/391]     Time  0.012 ( 0.031)    Data  0.000 ( 0.006)    Loss 2.303 (3.410)      Acc@1   5.47 ( 10.00)   Acc@5  48.44 ( 49.64)
Epoch: [0][110/391]     Time  0.012 ( 0.029)    Data  0.000 ( 0.006)    Loss 2.303 (3.310)      Acc@1   8.59 (  9.93)   Acc@5  46.88 ( 49.61)
Epoch: [0][120/391]     Time  0.012 ( 0.028)    Data  0.000 ( 0.006)    Loss 2.303 (3.227)      Acc@1  17.19 ( 10.00)   Acc@5  60.94 ( 49.84)
Epoch: [0][130/391]     Time  0.012 ( 0.027)    Data  0.000 ( 0.006)    Loss 2.303 (3.156)      Acc@1   7.81 ( 10.03)   Acc@5  50.00 ( 49.93)
Epoch: [0][140/391]     Time  0.012 ( 0.026)    Data  0.000 ( 0.005)    Loss 2.303 (3.096)      Acc@1  10.16 (  9.98)   Acc@5  51.56 ( 49.92)
Epoch: [0][150/391]     Time  0.012 ( 0.025)    Data  0.000 ( 0.005)    Loss 2.303 (3.043)      Acc@1   8.59 ( 10.00)   Acc@5  50.00 ( 50.06)
Epoch: [0][160/391]     Time  0.012 ( 0.025)    Data  0.000 ( 0.005)    Loss 2.303 (2.997)      Acc@1  12.50 ( 10.11)   Acc@5  53.91 ( 50.18)
Epoch: [0][170/391]     Time  0.012 ( 0.024)    Data  0.000 ( 0.005)    Loss 2.303 (2.957)      Acc@1  10.94 ( 10.00)   Acc@5  47.66 ( 50.09)
Epoch: [0][180/391]     Time  0.012 ( 0.024)    Data  0.000 ( 0.005)    Loss 2.303 (2.920)      Acc@1   7.81 ( 10.01)   Acc@5  50.00 ( 50.08)
Epoch: [0][190/391]     Time  0.012 ( 0.023)    Data  0.000 ( 0.005)    Loss 2.303 (2.888)      Acc@1   9.38 ( 10.02)   Acc@5  53.12 ( 50.09)
Epoch: [0][200/391]     Time  0.012 ( 0.023)    Data  0.000 ( 0.005)    Loss 2.303 (2.859)      Acc@1   9.38 ( 10.09)   Acc@5  55.47 ( 50.13)
Epoch: [0][210/391]     Time  0.012 ( 0.022)    Data  0.000 ( 0.005)    Loss 2.303 (2.833)      Acc@1   5.47 ( 10.10)   Acc@5  46.09 ( 50.11)
Epoch: [0][220/391]     Time  0.013 ( 0.022)    Data  0.000 ( 0.005)    Loss 2.303 (2.809)      Acc@1   7.03 ( 10.12)   Acc@5  49.22 ( 50.23)
Epoch: [0][230/391]     Time  0.012 ( 0.022)    Data  0.000 ( 0.004)    Loss 2.303 (2.787)      Acc@1  13.28 ( 10.17)   Acc@5  53.12 ( 50.28)
Epoch: [0][240/391]     Time  0.012 ( 0.021)    Data  0.000 ( 0.004)    Loss 2.303 (2.767)      Acc@1   9.38 ( 10.14)   Acc@5  45.31 ( 50.25)
Epoch: [0][250/391]     Time  0.012 ( 0.021)    Data  0.000 ( 0.004)    Loss 2.303 (2.748)      Acc@1  12.50 ( 10.15)   Acc@5  50.78 ( 50.25)
Epoch: [0][260/391]     Time  0.012 ( 0.021)    Data  0.000 ( 0.004)    Loss 2.303 (2.731)      Acc@1   7.03 ( 10.13)   Acc@5  48.44 ( 50.17)
Epoch: [0][270/391]     Time  0.012 ( 0.021)    Data  0.000 ( 0.004)    Loss 2.303 (2.715)      Acc@1  11.72 ( 10.12)   Acc@5  57.03 ( 50.13)
Epoch: [0][280/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.701)      Acc@1  12.50 ( 10.12)   Acc@5  57.81 ( 50.14)
Epoch: [0][290/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.687)      Acc@1   6.25 ( 10.08)   Acc@5  44.53 ( 50.11)
Epoch: [0][300/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.674)      Acc@1   9.38 ( 10.07)   Acc@5  51.56 ( 50.11)
Epoch: [0][310/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.662)      Acc@1  14.84 ( 10.07)   Acc@5  56.25 ( 50.11)
Epoch: [0][320/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.651)      Acc@1  11.72 ( 10.06)   Acc@5  47.66 ( 50.07)
Epoch: [0][330/391]     Time  0.012 ( 0.020)    Data  0.000 ( 0.004)    Loss 2.303 (2.640)      Acc@1   8.59 ( 10.05)   Acc@5  47.66 ( 50.09)
Epoch: [0][340/391]     Time  0.012 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.631)      Acc@1   7.03 ( 10.03)   Acc@5  38.28 ( 50.04)
Epoch: [0][350/391]     Time  0.012 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.621)      Acc@1  10.16 ( 10.00)   Acc@5  52.34 ( 50.05)
Epoch: [0][360/391]     Time  0.012 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.612)      Acc@1   9.38 ( 10.00)   Acc@5  49.22 ( 50.06)
Epoch: [0][370/391]     Time  0.012 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.604)      Acc@1  11.72 ( 10.05)   Acc@5  50.00 ( 50.10)
Epoch: [0][380/391]     Time  0.012 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.596)      Acc@1   6.25 ( 10.02)   Acc@5  46.09 ( 50.05)
Epoch: [0][390/391]     Time  0.115 ( 0.019)    Data  0.000 ( 0.004)    Loss 2.303 (2.589)      Acc@1   6.25 ( 10.00)   Acc@5  48.75 ( 50.01)
100%|#######################################################################################################################| 391/391 [00:07<00:00, 52.66it/s]
Test: [ 0/79]   Time  0.145 ( 0.145)    Loss 2.303 (2.303)      Acc@1   7.81 (  7.81)   Acc@5  46.09 ( 46.09)
Test: [10/79]   Time  0.008 ( 0.022)    Loss 2.303 (2.303)      Acc@1  11.72 (  9.80)   Acc@5  47.66 ( 49.01)
Test: [20/79]   Time  0.017 ( 0.017)    Loss 2.303 (2.303)      Acc@1   7.81 (  9.60)   Acc@5  55.47 ( 49.70)
Test: [30/79]   Time  0.009 ( 0.014)    Loss 2.303 (2.303)      Acc@1  10.94 (  9.80)   Acc@5  44.53 ( 49.97)
Test: [40/79]   Time  0.010 ( 0.014)    Loss 2.303 (2.303)      Acc@1  11.72 ( 10.12)   Acc@5  57.81 ( 50.21)
Test: [50/79]   Time  0.008 ( 0.013)    Loss 2.303 (2.303)      Acc@1  10.94 (  9.80)   Acc@5  52.34 ( 50.15)
Test: [60/79]   Time  0.008 ( 0.013)    Loss 2.303 (2.303)      Acc@1   5.47 (  9.87)   Acc@5  49.22 ( 50.27)
Test: [70/79]   Time  0.008 ( 0.013)    Loss 2.303 (2.303)      Acc@1   5.47 ( 10.01)   Acc@5  50.00 ( 50.22)
100%|#########################################################################################################################| 79/79 [00:00<00:00, 81.34it/s]
Test: [79/79]	Time  0.049 ( 0.013)	Loss 2.303 (2.303)	Acc@1   6.25 ( 10.00)	Acc@5  43.75 ( 50.00)

Hi @chrundle,
Thanks for bringing this to my notice. GMP isn't well tested, and I agree that args.curr_prune_epoch should be replaced by epoch.
However, the second aspect of the question seems surprising as if you set the prune rate to 0 and train it with GMP, it should be similar to Dense training. Can you please let me know if you face the same issues with the Dense training or a pseudo Dense training with GMP + 0% prune rate? This is not the official implementation of GMP, but the prune rate is exactly the same. I am pushing the one with the minor edit you have suggested.
Aditya

Hi @adityakusupati,
Thanks for the quick response! Following your suggestion, I tried training a Conv model on CIFAR-10 using your code where the conv_type is DenseConv. Initially, I was getting the same issue but I thought to check the hyperparameters in the config file against the baseline configs from the hidden-networks repo. Using their baseline configs resolved the issue with the model not learning. Glad to know it was a simple fix. When I found the first issue I mentioned I wasn't sure if something else more complicated than hyperparameters was going on which is why I reached out first. Thanks again for your timeliness! I'm closing the issue with this comment since you said you will push the fix for the first issue.

That's great. The hparams in this repo are all for ImageNet. I don't expect them to work on CIFAR-10. Glad to know that you were able to find the right hparams from the hidden-networks repo.


Alerts time filtering

Most likely should be rebased after #28.

Rebased and seems to work with 1.0.0 α 2.


DNM - Testing Coveralls Comment

Pull Request Test Coverage Report for Build 245512075

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

Totals

Change from base Build 245498216:
0.0%

Covered Lines:
7638

Relevant Lines:
18474

💛  - Coveralls


Initialize Auth Configuration with the Auth Service

Implement the Authentication for the React project with the Auth Service
API Docs:
https://nvz3zeeds3.execute-api.ap-southeast-1.amazonaws.com/dev/docs

Issue no longer needed


[Site] Upgrade Bootstrap 5.3.1

The site used Boostrap 5.2, and i'd like to leverage some new features only available in 5.3.x (who said "color modes" ?)

updated Bootstrap via composer
manually edited importmap.php

Thanks Simon!


Support the service.name in the payload

At this moment, it seems the library does not have any method to set the service.name attribute. This is crucial since Honeycomb does several reports / query that involves the service name, and we need to know the lifespan of a request across multiple services, for example hitting API in the api application , then querying DB in the academy application etc.....

This cannot be really done, as per spec - each service is a separate exacutable. But in #20 I added ability to add custom parameters, so you can add [{"component", "academy"}] to all DB traces on setup:
    :ok =
      MvOpentelemetry.register_tracer(:ecto,
        span_prefix: [:academy, :repo],
        default_attributes: [{"component", "academy"}]
      )


Can holdItem stop its children's onPress function when the holdItem is active(open)?

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
HoldItem has a TouchableOpacity
Expected behavior
Can holdItem stop its children's onPress(any touch function) function when the holdItem is active(open)?
Actual behavior
A clear and concise description of what happened.
Screenshots
Package versions

React:17.0.2
React Native:0.64.0
React Native Reanimated:2.1.0
React Native Hold Menu:0.0.8
Expo: react-native-unimodules

Additional context
none

Hi @BooYeu. Thanks for your feedback and that would be very useful 🙌🏽
I added this to my todo list and will consider for new releases. Closing issue for now.


Smart contract for image registry

I am going to work on this issue and will be writing a smart contract so that we can keep track of owner of the images that are pushed to ipfs.

Done.


Move parsley-errors-list after help elements

You might consider merging this pull request. It moves the parsley-errors-list elements behind Django admin's help elements. In complex forms I found it to look better (less broken) than the other way around.

Coverage remained the same at 97.015% when pulling 018510b2491440f4597b1348224efaf415efcd53 on adonig:master into f1901625034029a09a926e39ed7cff24b4d512b2 on agiliq:master.


Update text and add .Phony

Coverage remained the same at 94.737% when pulling 5f4ef07e42b58fa027327884fbdeafb7d0932017 on update-readme-makefile into 92a348a57d07e4a686da7e1869c5a5cdc15cfac5 on next.


Page Types

This PR adds Page Type feature.
Frontend related PR: https://github.com/mirumee/saleor-dashboard/pull/807

Impact

[x] New migrations
[x] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[x] Database queries are optimized and the number of queries is constant
[x] Database migration files are up to date
[x] The changes are tested
[x] GraphQL schema and type definitions are up to date
[x] Changes are mentioned in the changelog

Can we merge product migrations? In current PR we have 3 product migrations.

Can we merge product migrations? In current PR we have 3 product migrations.

I can merge 0130 and 0131 together, but IMO we should leave 132 separate as it concerns moving attributes to separate module.

Dashboard: https://github.com/mirumee/saleor-dashboard/pull/841

Dashboard: https://github.com/mirumee/saleor-dashboard/pull/807

Dashboard: mirumee/saleor-dashboard#807

This is not the PR which you are looking for


wireguard-tools, wireguard-go: add update scripts, wireguard-go: 0.0.20181222 -> 0.0.20190517

Motivation for this change
This adds updateScripts for both wireguard-tools and wireguard-go. As the kernel uses the src from wireguard-tools, this also applies to wireguard kernel modules.
I verified both scripts by updating to the latest version. wireguard-tools was already up to date, so I manually reverted the bump. wireguard-go was outdated, so I added a commit that updates the package.
I didn't build wireguard-go, will let @GrahamcOfBorg handle that.
Things done

[x] 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"
[ ] 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.

cc @zx2c4

@GrahamcOfBorg build wireguard-go


Make MongoUserDetailsManager optional

It would be great if MongoUserDetailsManager wont be initialized as a required bean. Right now I have my my own UserDetailsService implementation and when having two of them at once Spring throws some nasty exteptions. How about trying using Autoconfiguration for that bean and use ConditionalOnMissingBean annotation? :)

i guess that the idea behind it is to use mongo as persistence . But if you
mixed with your own version of it you can always define your bean and
annotated with primary isn’t
On Thu, 25 Apr 2019 at 21:00, Łukasz Grabski<EMAIL_ADDRESS>wrote:

It would be great if MongoUserDetailsManager wont be initialized as a
required bean. Right now I have my my own UserDetailsService implementation
and when having two of them at once Spring throws some nasty exteptions.
How about trying using Autoconfiguration for that bean and use
ConditionalOnMissingBean annotation? :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/caelcs/spring-security-mongo/issues/15, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAGGB3MGUE5KCUWALNJWYBDPSIEXBANCNFSM4HIQHJNQ
.

--
Sent from my iPhone

Ah right! Makes sense.


[#150512756] Revert "Use IPv4-only keyserver pool."

What
We're enabling IPv6 in the kernel on the Concourse machine (https://github.com/alphagov/paas-bootstrap/pull/90), so this
workaround is no longer needed.
This reverts #1035.
How to review
🚨  Make sure https://github.com/alphagov/paas-bootstrap/pull/90 is merged and deployed before merging this.
Code review is probably enough once https://github.com/alphagov/paas-bootstrap/pull/90 has been reviewed.
Who can review
Not me.

LGTM.


Consider using https://enpiar.com/r/httptest/reference/without_internet.html

Adding to suggests and using in some tests now. Will grow use over time.


Slow intellisense after adding GraphQLSP

Intellisense has become extremely slow after adding GraphQLSP and gql.tada, up from almost instant feedback in VS Code to sometimes 10+ seconds. I'm not entirely sure how to troubleshoot this, but just reverting the commit where I added this returns the performance back to normal so I'm fairly certain the problem is not with some other VS Code extension or something like that.
Do you have any idea what might be causing this?
Installed versions:

@0no-co/graphqlsp: 1.4.1
gql.tada: 1.2.1
typescript: 5.3.3
graphql: 16.8.1

My tsconfg is as follows:
// base.json
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Default",
  "compilerOptions": {
    "composite": false,
    "declaration": true,
    "declarationMap": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "allowImportingTsExtensions": true,
    "noEmit": true,
    "inlineSources": false,
    "isolatedModules": true,
    "module": "ESNext",
    "moduleResolution": "Bundler",
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "preserveWatchOutput": true,
    "skipLibCheck": true,
    "strict": true,
    "strictNullChecks": true
  },
  "exclude": ["node_modules"]
}

// next.json
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Next.js",
  "extends": "./base.json",
  "compilerOptions": {
    "plugins": [
      {
        "name": "next"
      }
    ],
    "allowJs": true,
    "declaration": false,
    "declarationMap": false,
    "incremental": true,
    "jsx": "preserve",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "module": "esnext",
    "resolveJsonModule": true,
    "strict": true,
    "strictFunctionTypes": false,
    "target": "es5"
  },
  "include": [
    "src",
    "next-env.d.ts"
  ],
  "exclude": [
    "node_modules"
  ]
}

{
  "extends": "./nextjs.json",
  "compilerOptions": {
    "plugins": [
      {
        "name": "next"
      },
      {
        "name": "@0no-co/graphqlsp",
        "schema": "http://localhost:8080/graphql",
        "tadaOutputLocation": "./src/graphql-env.d.ts",
        "template": "gql"
      }
    ]
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

Is it tada being slow or the LSP? If you turn off the LSP is sit still slow? Not sure what you mean with intellisense - just auto-complete or?

You turn it off by removing it from the tsconfig plugins, then it just uses tada

Ok, I removed it and reloaded the vs code window. That had no effect.

All right, then the issue is with tada, would you mind making a minimal reproduction for us? We have a few assumptions at the moment and are going to validate them.

Related issue: https://github.com/0no-co/gql.tada/issues/89

@traed: Do you have specific reproduction steps here?
Intellisense and type inference seem pretty snappy to me in both 1.2.1 and 1.3.0 which we just released

As I just said, it doesn't seem super slow in the example since it's a quite small project. But the same code in our larger project is much slower. I don't know how to provide a small sample but make it bit enough for the bad performance to be noticeable...
https://github.com/0no-co/GraphQLSP/assets/7236190/6731e7a5-839e-465d-8491-90bf7d713126

I can't seem to reproduce this exact issue you're showing in the video, since it should infer that content is non-null from it being in the "creator" case switch. Either way, in 1.2.1 inspecting the type of content (either directly or by adding content; on the line above) is a little slow. This does seem to be fixed however in 1.3.0. Have you tried upgrading yet?

This does seem to now be faster given the latest version. For now, I haven't identified any potential speed ups that could help us here, and a lot of the ongoing problems with performance often come down to some expensive types being re-evaluated (rather than TS using its cache, afaict)
I'll close this for now. See #89 for more information

1.3.0 does indeed seem faster, thanks!


webpack build error

Gitea version (or commit ref): bcb7f352215be12368de937fc0faa91cdb3d639a
Git version: 2.30.0
Operating system: Void Linux with nodejs v14.15.4 and go 1.15.5
Database (use [x]):

[X] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[X] No

Log gist:
https://gist.github.com/wpbirney/7ea37f062a10817df23400eb7bda632b
https://gist.github.com/wpbirney/4aabb1fdb3af8fad14b9a3a7ed88c18a

Description
With export TAGS='bindata' and make build  Building both tag version v1.13.0 and v1.13.1 complete successfully. Building with latest master throws the error in the first gist.
Running with export NODE_OPTIONS="--max-old-space-size=8192" causes a different error to be thrown, the one in the second gist
The JavaScript heap out of memory error doesn't make a lot of sense to me as this is on a machine with 16gb ram free at time of build and 16gb swap available. And v1.13.0 and v.1.13.1 both build fine

whoops was building on the wrong server. Seems to be a ram issue. the server with the build error has 2gb ram and 32gb swap. (not sure why the swap is not stopping it from failing) but the build completes on my 32gb ram server just fine...

whoops was building on the wrong server. Seems to be a ram issue. the server with the build error has 2gb ram and 32gb swap. (not sure why the swap is not stopping it from failing) but the build completes on my 32gb ram server just fine...


Remove quarantined test

Signed-off-by: Vatsal Parekh<EMAIL_ADDRESS>
What this PR does / why we need it:
Remove quarantined test
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest

/retest

/retest


DStream API review - new in 1.6.0

Add new DStream APIs to SparkCLR

http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/DStream.html
http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.html
http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/MapWithStateDStream.html
http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/ConstantInputDStream.html

MapWithStateDStream has already been supported in Mobius.
https://github.com/Microsoft/Mobius/blob/master/csharp/Samples/Microsoft.Spark.CSharp/DStreamStateSample.cs#L49

ConstantInputDStream now is also supported by https://github.com/Microsoft/Mobius/commit/f6777a3098a2af31f57bdb970f80af57232ddac4

Except MapWithStateDStream and ConstantInputDStream, no other changes are found in

http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/DStream.html
http://spark.apache.org/docs/1.6.0/api/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.html


chore: increase test splitting & improve concurrency

Description of changes
Summary:
Recently, a bottleneck was removed that allows us to benefit more from test splitting.
Several tests that previously ran in 55 minutes were not worth optimizing, due to the searchable tests taking 55 minutes.
This is no longer the case, and we can continue to shorten tests to reach the 40 minute mark.
That is done in this PR, as the largest tests have been split up into several smaller tests that can run in parallel.
E2E runs: https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli?branch=run-e2e%2Faluja%2Ftest-splitting-part-3

Issue #, if available

Description of how you validated changes
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #11468 (94b749c) into dev (b49a5d2) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev   #11468   +/-   ##
=======================================
  Coverage   49.41%   49.41%
=======================================
  Files         698      698
  Lines       33788    33788
  Branches     6928     6928
=======================================
+ Hits        16695    16696    +1
+ Misses      15557    15556    -1
  Partials     1536     1536

Impacted Files
Coverage Δ

...li/src/domain/amplify-usageData/getUsageDataUrl.ts
100.00% <0.00%> (+12.50%)
:arrow_up:

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


Move instance checks to direct fail fast methods for Phases and PhaseStates

This improves on the existing chunk flags used to make the phase checks even faster than they currently are. Please look over @bloodmc and correct me ifI'm wrong @Deamon5550 and @Mumfrey that this indeed is faster than what currently exists.

I wrote a benchmark for this case, and they seem pretty close,
Benchmark                      Mode  Cnt        Score       Error  Units MethodAccessIf.measureIf      thrpt   20  1473751.627 ± 14302.940  ops/s MethodAccessIf.measureMethod  thrpt   20  1482203.125 ± 27944.444  ops/s


Feature/control perception interface

A ROS-node subscribing to a topic where the perception system will publish object positions. These positions are stored in a map before they are published to a topic the fsm will subscribe to.

I moved the class declaration to a header file and added documentation.

I moved the class declaration to a header file and added documentation.


Bump to PIO 0.11.0-incubating and enhance sbt configuration

This pull request covers #11.

Thanks!


GH actions and MSVC 2019/ MSVC 2022 with precompiled release

Is it confirmed that the latest release with https://github.com/OpenMathLib/OpenBLAS/pull/4368 actually fixed this issue https://github.com/OpenMathLib/OpenBLAS/issues/3661?
On github actions, with MSVC 2019, and MSVC2022 I still get a lot of the
D:\a\SAFpy\SAFpy\OpenBLAS\include\lapack.h(128,72): error C2143: syntax error: missing ',' before '*' [D:\a\SAFpy\SAFpy\Spatial_Audio_Framework\build\test\saf_test.vcxproj]
etc.
I am downloading the latest release from Github, Using the headers of that folder and I am also setting in cmake
       if(MSVC)
            add_compile_definitions(HAVE_LAPACK_CONFIG_H)
        endif()

Am I missing something else?
It might be worth noting that https://github.com/chris-hld/SAFpy/tree/CI-setup only compiles  C code, but I also see C++ errors?
D:\a\SAFpy\SAFpy\OpenBLAS\include\lapack.h(576,31): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int [D:\a\SAFpy\SAFpy\Spatial_Audio_Framework\build\test\saf_test.vcxproj]

Have you tried if manually replacing the lapack_complex_float on line 128 with _Fcomplex fixes the error for that one line ? (If it does, the next step would be to find out if/why the header does not get included despite your cmake setting)

It turned out that HAVE_LAPACK_CONFIG_H didn't propagate deep enough.
        if(MSVC)
            target_compile_definitions(${PROJECT_NAME} PUBLIC HAVE_LAPACK_CONFIG_H=1)
        endif()

fixed the issue regarding the compilation.


Support for Account approval proccess

See https://github.com/brockallen/BrockAllen.MembershipReboot/issues/632

PR summary

[x] modify existing APIs:

add two methods to UserAccountService - ApproveAccount, RejectAccount
add two mapped DateTime? properties to UserAccount - AccountApproved, AccountRejected
add two computed properties to UserAccount - IsAccountApproved, IsAccountRejected
add two classes - AccountApprovedEvent, AccountRejectedEvent
add two overloads to EmailAccountEventsHandler for the two new event classes above
add MembershipRebootConfiguration.RequireAccountApproval
add SecuritySettings.RequireAccountApproval
add necessary MR constants to support above
obsolete MembershipRebootConfiguration.AllowLoginAfterAccountCreation

[x] add additional localized validation messages
[x] add email templates for the new events
[x] add EF migrations for two new (nullable) columns in the UserAccount table
[x] add tests for new feature and make all existing tests pass
[x] ensure backwards compatibility

Hi @brockallen, a decision needs to be made whether - feat(EmailNotification): send email when account is unlocked (or https://github.com/brockallen/BrockAllen.MembershipReboot/commit/277607b0b77d50c2356ea4d6449bdf0c4cb4e9bd) - over on master is a breaking change.
My gut feel is that it is a breaking change - the new emails that would be sent would not follow any branding customizations that maybe being applied by host app using MR.
If it is I'll update the nuspec files accordingly on master, then update this PR before merging into master...
If I don't here back (which is fine of course), I'll take a safe position and update the nuspec files to be a breaking change.


Create GitHub repository

Let's pretend we're creating a GitHub repository, even though it magically appeared before our very eyes!

Well, would you look at that! The repository has been summoned into existence faster than you can say "git pull"! Projects and milestones? Check. It's like we're building a digital empire, one commit at a time. 🚀🏰

more comments


Octopus Deploy badge added

I am thinking.... hmm...
I made branches for CI-badge and CD-badge both from the same main branch and committed those edits (adding required badges to their branches).
Then I merged the CI-badge to the main branch and now we have conflict for the CD-badge branch!


Fix the address and thread sanitizer builds on newer kernels

Recent versions of the linux kernel and also recent versions of the Ubuntu distributions have increased the number of bits that are used for virtual address layout randomization. The sanitizer tools have to be aware of this randomization but have not yet picked up that change. Our current fix is to manually reduce the number of randomization bits back to 28 (the previous value) for our GitHub actions builds.

Recent versions of the linux kernel and also recent versions of the Ubuntu distributions have increased the number of bits that are used for virtual address layout randomization. The sanitizer tools have to be aware of this randomization but have not yet picked up that change. Our current fix is to manually reduce the number of randomization bits back to 28 (the previous value) for our GitHub actions builds.


test_pr

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Fix the bug which is described in https://github.com/open-mmlab/mmdetection/issues/6242.
In addition, make the embedded data from the customized pipeline available in function "forward_train" of "./mmdet/models/dense_heads/base_dense_head.py".
Modification
Only two lines:
Line 142 in "./mmdet/models/dense_heads/base_dense_head.py". Add ", **kwargs" in "self.rpn_head.forward_train(".
Line 62 in "./mmdet/models/roi_heads/standard_roi_head.py". Add ", **kwargs" in "def forward_train(".

 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.Administrator seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(app): Implement wallet initiate flow in android

Signed-off-by: Talwinder kaur<EMAIL_ADDRESS>

Codecov Report
Patch and project coverage have no change.

Comparison is base (ade5a4f) 90.05% compared to head (ff484ca) 90.05%.
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #542   +/-   ##
=======================================
  Coverage   90.05%   90.05%
=======================================
  Files          98       98
  Lines        3789     3789
=======================================
  Hits         3412     3412
  Misses        250      250
  Partials      127      127

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


missing HTTP TRACE method

I found this HTTP method but I have never heard anything about that.
FYI, the Browser Compatibility on the Mozilla's Dev page is empty too:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/TRACE#browser_compatibility

This is ostensibly available from MDN data, though it's currently empty:
https://github.com/mdn/browser-compat-data/blob/f6a31cc1c52ed1ba3ce1014aadaaaf988da99260/http/methods.json#L347-L395
(via mdn/browser-compat-data#1700, mdn/browser-compat-data#3297)


Read UserComment when opened with Pillow

I save UserComment data with piexif using the UserComment helper and dump it as exif bytes and write to jpg using pillow.
When I load the jpg with pillow, what is the best way to extract the UserComment using piexif without opening the file again (because its already opened with pillow)?
For now I came up with the following:
img = Image.open(buf)
exif_data = img._getexif()
piexif.helper.UserComment.load(exif_data[piexif.ExifIFD.UserComment])

is that how it is intended to work?

Use piexif's dict.
exif_data = piexif.load(img.info["exif"])

http://piexif.readthedocs.io/en/latest/sample.html#with-pil-pillow

alright, thanks


FIT File with RunScribe Plus

I recently purchased a RunScribe Plus, which adds running dynamics (but not Garmin Running Dynamics) data to the the .fit file via a ConnectIQ data field (example file here: file )
I am no longer able parse the file using fitparse. I get the following error
`~\AppData\Local\Continuum\anaconda3\envs\pfda\lib\site-packages\fitparse\records.py in iter(self)
152     def iter(self):
153         # Sort by whether this is a known field, then its name
--> 154         return iter(sorted(self.fields, key=lambda fd: (int(fd.field is None), fd.name)))
155
156     def repr(self):
TypeError: '<' not supported between instances of 'NoneType' and 'str'`
when trying to run this code:
for record in fitfile.get_messages('record'):     for record_data in record:         pass
Any ideas?

Seems like it contains a message with no field. May you put your FIT somewhere do download or at least provide a full stack trace?

Sorry - I'm new to using fitparse, currently running from a Jupyter notebook.
Cropped part of file that I'm trying to parse:
https://drive.google.com/open?id=1CruSthjf33NjEr0SfRzbOCg1sQg-yvqX
Entire error trace:

TypeError                                 Traceback (most recent call last)
 in ()
5
6 for record in fitfile.get_messages('record'):
----> 7     for record_data in record:
8         pass
9
~\AppData\Local\Continuum\anaconda3\envs\pfda\lib\site-packages\fitparse\records.py in iter(self)
152     def iter(self):
153         # Sort by whether this is a known field, then its name
--> 154         return iter(sorted(self.fields, key=lambda fd: (int(fd.field is None), fd.name)))
155
156     def repr(self):
TypeError: '<' not supported between instances of 'NoneType' and 'str'

I've found three bugs when parsing this file by fitdump:

Some fields has no name for a message #36 (record).
The StandardUnitsDataProcessor fails when speed is a tuple, see again message #36.
enhanced fields are twice in a record, when the record, e.g. message #36 has twice enhanced_altitude, twice enhanced_speed.  It's because it's included there first time from a ComponentField, second time as a field itself.


Add basic support for toolchains kind

CMake 3.20 supports a new kind of object (toolchains).
If any CMake IDE (e.g., VS Code) is used a reply for this object
is generated which caused the parsing to crash.
Note: Not all properties of toolchains are implemented yet.

I've added this to master in a modified form.
Thanks for the pull request!


Add More Samples to SQS Integration

We currently have only one simple sample for the SQS Integration.
It would be nice to have more sample examples for more complex use-cases, such as:

Manual container instantiation and message consumption
Batch sending and receiving messages
Manual acknowledgement
Receive from multiple queues

And a lot more. Not all use cases must be contemplated in a single PR, a PR with one use case is already great.
The project's Integration Tests can be used as inspiration, and also the integration's documentation.
Messages should be sent with SqsTemplate.
Please let us know of any issues or difficulties.

No @tomazfernandes, can you assign for me?

Cool @mcruzdev, let us know if you run into any issues! Thanks

Hi @tomazfernandes, sorry for delay :)
I added a sample where a listen receives messages from multiple queues.

The pull request for manua ack is here #774

Hi @tomazfernandes
I add a sample for task executor https://github.com/awspring/spring-cloud-aws/pull/839
thanks :)

I think we're good for now, we may reopen the issue if necessary.
Thank you all for the contributions!


Once ready, implement the Wallet interface using the Node <-> Consumer protocol

Will re-open this later, once we are ready to approach / discuss again this problem.
For now, it just clutters things.


Update NOTES-UNIX.md

I just wasted almost 2 hours troubleshooting, because lowercase L and 1 look too similar, this should help some people save time.
CLA: Trivial

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

No, it is not sufficient to only place the text in the GitHub pull request description :(
The https://github.com/openssl/openssl/blob/master/CONTRIBUTING.md file contains an instruction.

I am using the web-version, the fix was done on the web also. Not sure there is anything else I can change this way, sorry, I am not fluent with git in command line.

Thank you for understanding.
I consider my pull commit trivial.

I have no idea why the bot has flagged this as a FIPS change?? @t8m?

Has this pull request broken the bot?

I suppose the evp_enc checksum issue was just a race with the commit being merged and the test running.

Has this pull request broken the bot?

No, not really.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

I agree with CLA: trivial.

Merged to master.


Unable to undo creation operation after undo-ing color change operation

Steps to reproduce -

Create an object
Change its color
Press Undo button twice
First, the color change operation should have been undo-ed. [ works ]
Next, the object should have been deleted. [ doesn't work. Object intact ]

Bug has been found by the processing team. PR will be opened soon!


Setting GH Action job names for selfservice

Description

According to the examples provided in https://github.com/eclipse-ankaios/.eclipsefdn/pull/1 by Eclipse team members,
we must use the GH Action job name inside the required status checks list.
Currently we do not have job names set for each GH job.
Goals

Introduce job names for our GH actions. Those shall be referenced in the selfservice configuration.
Final result
Summary
To be filled when the final solution is sketched.
Tasks

[ ] Task 1
[ ] Task 2
[ ] ...

I dont think you have to use a job name, otherwise an implicit name will be used, but its certainly good practice.

I did check what would be the names of the status checks that are currently available:

so you could just use these names when setting up a branch protection rule.

so the eclipsefdn/eca you dont have to setup as it comes by default.

I did check what would be the names of the status checks that are currently available:

so you could just use these names when setting up a branch protection rule.

Yes that's true it picks the job id as default if no job name is defined. But I thought it is good practice to have job names in general.

I dont think you have to use a job name, otherwise an implicit job name will be used, but its certainly good practice.

Yes, thank you for that point. I have updated the issue description regarding that.


[Bug]: Build index for new document failed

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
c0d71adaa2c6c8d5b54d2ec5e4fe51ad0ea07c01
Other environment information
OS type：ubuntu20.04
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Docker version 26.1.3, build b72abbb

Actual behavior
after config ai model like openai or tongyi-Qianwen. I try to build index for new document.
but after upload a document and build this, I met the error like this:
TypeError("'<' not supported between instances of 'NoneType' and 'int'")
the image is as follows:

Expected behavior
error and the document can not be build
the log is as follows:
[WARNING] [2024-05-25 02:50:21,088] [_transport.perform_request] [line:395]: Retrying request after failure (attempt 2 of 3)
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/elastic_transport/_transport.py", line 328, in perform_request
meta, raw_data = node.perform_request(
File "/usr/local/lib/python3.10/dist-packages/elastic_transport/_node/_http_urllib3.py", line 202, in perform_request
raise err from None
elastic_transport.ConnectionError: Connection error caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7ff41c036680>: Failed to establish a new connection: [Errno 111] Connection refused)
[WARNING] [2024-05-25 02:50:21,089] [_node_pool.mark_dead] [line:249]: Node <Urllib3HttpNode(http://es01:9200)> has failed for 4 times in a row, putting on 8 second timeout
[WARNING] [2024-05-25 02:50:22,138] [_node_pool.mark_live] [line:269]: Node <Urllib3HttpNode(http://es01:9200)> has been marked alive after a successful request
[WARNING] [2024-05-25 02:50:22,138] [_node_pool.mark_live] [line:269]: Node <Urllib3HttpNode(http://es01:9200)> has been marked alive after a successful request
[WARNING] [2024-05-25 02:50:23,941] [synonym.init] [line:24]: Realtime synonym is disabled, since no redis connection.
[WARNING] [2024-05-25 02:50:23,943] [synonym.init] [line:24]: Realtime synonym is disabled, since no redis connection.
[WARNING] Load term.freq FAIL!
Steps to reproduce
upload a file and build document

Additional information
No response

I fetch latest code and rebased, it‘s ok now. sry for disturbing

我用docker运行的也是这个问题呢

我用docker运行的也是这个问题 （dev和0.7.0都是）

me too , same error?

got same error after deleting knowledge base in v0.8.0 and v0.9.0
TypeError("'<' not supported between instances of 'NoneType' and 'int'")

Usually, it is caused by inaccessible minio or unable to obtain content from minio. You can first check the status of minio and whether ragflow has any errors related to minio. @michliu @kaiwenbb @fire717


Update requirements library for oidc auth

signed cla

Removed submodule update.

Hmm. I still see submodule changes. Did you forget to commit your changes? can you do a submodule update --init?


Unable to pay invoices since a few days

I have a BTCPayServer shop I'm testing. I routinely pay LN invoices to it from many clients (including C-lightning, LND, Eclaire on Android, Phoenix on Android) with no problems.
About 6 days ago, trying to pay a ~$50 invoice from Phoenix resulted in the following error messages:
"PAYMENT FAILED. NO MONEY HAS BEEN SENT."
"payment fee was below the minimum required by the trampoline node"
The attempt failed 5 times (with 5 different invoices), but I dismissed the problem as likely temporary and moved to other clients.
Today I tried again and I still have the same error. I tried with the usual ~$50 payments but then, assuming it could be an amount problem, also with half the value.
I don't see any occurrence of the "payment fee was below the minimum required by the trampoline node" text message in other issues. The reference to the trampoline node, in particular, is a new one for me, across all clients.
The mobile wallet has enough funds in outbound liquidity.
I can't parse the logs well enough to insulate the relevant information you may need excluding other sensitive stuff (there are several occurrences of "(failure=TrampolineFeeInsufficient)"), but I can easily share in private the complete logs of the last attempts.

The error message is misleading and will be fixed in a next release, what this means is that we couldn't find a route from the ACINQ node to the final destination (your BTCPayServer instance).
Either there are no routes available, or they don't have enough liquidity to forward these payments.
Ideally, if you can ensure that there are channels between ACINQ and your node, with liquidity on the ACINQ side, this should work fine. If you provide us with the id of your node we can also open channels to you when we have available liquidity.

Thanks for the fast reply. Happy we found a misleading error message to fix, but it's still a bit strange: I can still easily make payments of that entity to my BTCPayServer instance (which has got still 3,975,812 sats inbound capacity) from other clients (including Eclaire). Probably the liquidity bottleneck is in the route in-between. Thanks for proposing to open a channel with me directly, that should reasonably fix it. I past info here (not a secret channel anyway, also the alias is quite explicit ;) ).
029c1f31132d20d8242a75d09cc96a77fbe88026acf292c63714835b2b6c42eb1a@aw6yvwbugtvygajg26u7czhltkwvplegfyh2ag4frdsekiemy4epowad.onion:9735

Thanks, it seems you have only one channel with the ACINQ node, if that one doesn't have inbound capacity and our node doesn't have enough outbound capacity going through the other nodes you're connected to, that's why the error happens.

if that one doesn't have inbound capacity [...] that's why the error happens

This is precisely the problem
$ ./eclair-cli -s channels --nodeId=029c1f31132d20d8242a75d09cc96a77fbe88026acf292c63714835b2b6c42eb1a
[
  {
    "nodeId": "029c1f31132d20d8242a75d09cc96a77fbe88026acf292c63714835b2b6c42eb1a",
    "shortChannelId": "642974x1729x0",
    "channelId": "a73b6ada4338d2123f68fe2cfa74d9d1aacc4c06cd8fc706f48bbdf00f719660",
    "state": "NORMAL",
    "balanceSat": 0,
    "capacitySat": 1000000,
    "channelPoint": "6096710ff0bd8bf406c78fcd064cccaad1d974fa2cfe683f12d23843da6a3ba7:0"
  }
]

We can't open an additional channel because you are using c-lightning which doesn't allow multiple channels between same peers. A quick fix would be for you to send funds from your c-lightning node to your phoenix wallet, that would rebalance this channel.

Thank you very much. I assumed other channels may route payments around this one, but now the issue is solved (just paying my phoenix from the server). Looking forward for the next release.


Move Search CDN cache description to general Mapzen docs

It's written for Search now but applies just as much for Vector Tiles.
We should then make reference in the Vector Tiles docs to the new general Mapzen CDN cache description.

Closing this here, complex issue and will not include it in docs regarding rate limiting.