Added Power Of Two in Kotlin

Have you read the Contributing Guidelines on Pull Requests?
YES
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Closes: #6792

@ankitaggarwal23 @HarshCasper @bhav09 Please review this

@ankitaggarwal23 I have already added all the changes that you requested

@ankitaggarwal23 I have done it. Please check it again


Use web-time instead of unmaintained instant crate.

Fixes #538.
The changes are mostly trivial, mainly replacing instant::Duration with web_time::Duration.
I also made some small changes in the relevant doctests, using e.g. Duration::ZERO instead of Duration::new(0, 0) or Duration::from_nanos(x) instead of Duration::new(0, x).
My understanding is that the equivalent of the instant's wasm-bindgen feature is always enabled for web-time, though I didn't check what the CI checks on wasm targets.

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

Project coverage is 91.91%. Comparing base (c7673ef) to head (56c94a1).

Files with missing lines
Patch %
Lines

crates/argmin/src/core/executor.rs
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #539      +/-   ##
==========================================
- Coverage   91.92%   91.91%   -0.02%
==========================================
  Files         177      177
  Lines       23724    23727       +3
==========================================
  Hits        21808    21808
- Misses       1916     1919       +3

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

The cargo-deny CI job failure here (multiple occurences) doesn't seem to be directly related to the addition of the web-time dependency (the offending packages are transitively pulled-in by the eframe dependency in the spectator crate).
Would 2bb66df still be ok? The Unicode-3.0 license is OSI-approved and allowed e.g. in the cargo-deny repository.


Added CreateJobTemplate with pretty output for tests

Could you change the other test cases as well?

I'm not sure if i have addressed:

Could you change the other test cases as well?
But i think the pr could be ready.

Please correct the final typo, thanks.


Cannot preview the app demo

https://expo.io/@fromtexas/budgety  states that
'This project needs an update
This project uses Expo SDK v24.0.0. If you want to open this project, the author will need to update the project's SDK version.'
Could you update it. Would love to see the app working

Thanks its working now


[CARBONDATA-1935]fix the backword compatibility issue for tableInfo deserialization

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?

[x] Any backward compatibility impacted?

[x] Document update required?

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2274/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2278/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1053/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2280/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2526/

retest this please

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2528/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2529/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2282/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1065/

retest sdv please

retest this please

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1085/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2301/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2317/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1101/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2380/

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1164/

retest this please

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1204/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2430/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2620/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2441/

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/1220/


[Windows] 404 for MudBlazor on Production mode

The MudBlazor Files could not be fetched from the aspnet backend 404:

Steps to reproduce:

Have Windows (10)
Install dotnet 6 rc1 sdk x64
dotnet new blazorserver
Follow the tutorial: https://mudblazor.com/getting-started/installation#manual-install
dotnet run --environment Production

After this easy steps i get this strange behavior (see Screenshot). It seems MudBlazor could not be served from the virtual _content folder.
Edit: When i'm running  dotnet run --environment Development everthing is fine.

I have the same problem. have you already resolved it?
I wonder If the authors are maintaining the issues.


Make a copy so nodes can't mutate each others environment variables

LGTM. Passing curiosity if there's anything else we're assigning to a ref that could later be mutated, but looks like it'd just be the cluster object which... yeah. If we're changing that outside we have bigger problems.
👍


Very Appreciate for your work and looking foward for the 32k token and llama supported

@gumplus, Thank you. Next on the roadmap for me are

Cleanup the README
Scaling up experiments to fit 16/32k window fine-tuned models.


Navigation Timing 2

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming2/Overview.html
At first glance getEntriesByType seems ... weird.

Discussed in NYC; alex to review.

Question: does the group want our feedback? We need to reach out and schedule a discussion with them on a future telcon.

/cc @igrigorik

@torgo re, feedback: yes. FWIW, we're doing a lot of shuffling and spec cleanup work at the moment, so (a) make sure you're looking at the latest draft, and (b) check the open issues as we have a bunch of work in flight.

Discussed on call 5-Aug – we want to be involved when they need us but we need to be able to respond to a concrete request for feedback. Issue to be reassigned to Boston f2f.

Picked up in Boston.

@slightlyoff : "strange that it's not possible to query the navigation timing api with reference to a resource."

Editor's draft is now at https://w3c.github.io/navigation-timing/

@slightlyoff to write up some comments in advance of a joint discussion. We could discuss with @igrigorik at TPAC or beforehand if it can be arranged.

Per the TPAC discussion, I need to update the draft review to also discuss the Performance Observer API designs that are coming down the pike.

Need to check-in with current status of Performance Observer spec and implementation progress. Should revisit at next TAG f2f meeting.

Firefox has it implemented behind a flag: https://bugzilla.mozilla.org/show_bug.cgi?id=1165796
Chrome has it implemented behind a flag: https://plus.google.com/+IlyaGrigorik/posts/c4xiQ9fxCpf
Edge lists is as "under consideration": https://dev.windows.com/en-us/microsoft-edge/platform/status/performanceobserver

Can we prioritize this? Are there are any particular questions we can address to resolve this?

@igrigorik What subset of performance timeline features have Firefox and Chrome implemented on Performance Observer? (Nav Timing/Resource Timing/User Timing/Frame Timing/Server Timing/other?)
Are all open spec issues from TPAC 2015 on when a Nav Timing is delivered to the Performance Observer resolved?

As far as I can tell, Mozilla's implementation is feature complete (including new getEntries filtering) and integration with all the shipped perf APIs (user, nav, and resource timing).
The implementation in Chrome enables PerfObserver interface and integrates with User + Resource Timing. Nav Timing support is missing because we need to update our NT implementation to v2 -- once that's done the observer support will be there.

Apologies for the delay in getting back to everyone. Overall Performance Timeline 2 looks good!
A few things stand out (some of them are editorial, sorry!):

It'd be great for there to be a separate explainer doc that goes into more detail about the problems that NT2 solves and the sample code you might write to use it to address those issues.
In section 3, step 3.1, where is new entry allocated?
In step 3, are you really meaning to get the list of registered performance observer objects from the global environment? Could it be a more standard data structure like a list or map hidden away using a symbol?
The "low priority queue" language is interesting...are there other specs that use similar priority statements that you're aware of?
Where is the list of types that you can listen for via a PerformanceObserver listed? E.g., frame seems to relate to Frame Timing, but I'm not sure what's definitive.
Can Performance Observers be used to observe page load that may have already happened? How does that work?

Thanks!

Thanks for the review Alex!

It'd be great for there to be a separate explainer doc that goes into more detail about the problems that NT2 solves and the sample code you might write to use it to address those issues.

I assume you meant Perf Timeline 2, not Nav Timing 2.
I think we can address this in the intro section. We already provide a PerfObserver code sample and I think we can just: (a) clarify that this is a v2 feature, (b) explain why it should be a preferred way to access the timeline.

In section 3, step 3.1, where is new entry allocated?

That algorithm defines the steps that are invoked by other specifications when they need to queue a "new entry" - e.g. Frame Timing allocates new entry and invokes the algorithm.

In step 3, are you really meaning to get the list of registered performance observer objects from the global environment? Could it be a more standard data structure like a list or map hidden away using a symbol?

What would that symbol be associated with?

We started with "unit of related similar-origin browsing contexts's" - same as MutationObserver.
Boris and Anne suggested that we should be using "global environment" - commit.

The "low priority queue" language is interesting...are there other specs that use similar priority statements that you're aware of?

I think IntersectionObserver is attempting to do something similar by leveraging requestIdleCallback - open bug to cleanup interop. PerfObserver came about before we had rIC. It might make sense to go back and define PerfObserver to fire via rIC.

Where is the list of types that you can listen for via a PerformanceObserver listed? E.g., frame seems to relate to Frame Timing, but I'm not sure what's definitive.

There is a note in 3.1 that lists all valid entryType values, with links to each spec: https://www.w3.org/TR/performance-timeline-2/#the-performanceentry-interface

Can Performance Observers be used to observe page load that may have already happened? How does that work?

No. If you register an observer after an event has already happened, you won't get a notification for it. If you want to get notifications for resource timing / nav timing entries when the page is loading, you should register the PerfObserver as a first thing in your doc -- e.g. inline the registration snippet in the head of the doc, before any resource declarations.

Taken up on 20-07-2016. We agreed to close the issue.


fix #166

Branch is rebased. PR is updated.

make queue size configurable
block timer when queue is full


Admin Repo Checks - UI

Added styling.
Added final copy.
Repo Checks logic
Still Missing Unit tests implementation

LGTM +1


LinearTransformationSceneExample does not work in Colab

Description of bug / unexpected behavior
I'm trying to change the base configurations for LinearTransformationScene, but I get an error. This was not the case when I was using the previous version of Manim a few days ago
Expected behavior
I was hoping to change the configs without getting an error
How to reproduce the issue
Following is some example code taken from the docs. The first line was to get it to run in Google Colab (as described in the tutorials section)
 %%manim LinearTransformationSceneExample

 class LinearTransformationSceneExample(LinearTransformationScene):
            def __init__(self):
                LinearTransformationScene.__init__(
                    self,
                    show_coordinates=True,
                    leave_ghost_vectors=True,
                )

            def construct(self):
                matrix = [[1, 1], [0, 1]]
                self.apply_matrix(matrix)
                self.wait()

Logs
Terminal output

TypeError: __init__() got an unexpected keyword argument 'renderer'

System specifications
System Details
Google Colab's settings
Python version
python3

FFMPEG
Output of ffmpeg -version:
ffmpeg version 3.4.8-0ubuntu0.2

Additional comments

Can you try to change the code to
class LinearTransformationSceneExample(LinearTransformationScene):
    def __init__(self, **kwargs):
        LinearTransformationScene.__init__(
            self,
            show_coordinates=True,
            leave_ghost_vectors=True,
            **kwargs,
        )

    def construct(self):
        matrix = [[1, 1], [0, 1]]
        self.apply_matrix(matrix)
        self.wait()

and see whether this helps?

Yes! That fixed it. Could you briefly explain why?
Thanks!

Yes! That fixed it. Could you briefly explain why?
Thanks!

Of course! Apologies for the delay: When rendering a scene in Colab (or generally in Jupyter Notebooks), the renderer gets passed to the scene as an additional keyword argument; this is part of the %%manim IPython magic.
The way the example in the documentation is currently written does not allow for additional keyword arguments; by adding **kwargs to both the custom __init__ of your scene, as well as to the corresponding LinearTransformationScene.__init__ call, the keyword is propagated properly.
The issue should remain open (and I've also renamed it a bit) until the example in the documentation is changed accordingly.

Thank you for your clear explanation!

I could write about it in the docs, but let me check if I understand correctly what is going on: By default, the cell magic %%manim feeds the constructor with the appropriate renderer to display the output in the IPython cell. So basically only the example needs to be changed or should also contain a note pointing out to this detail?

@Tsukalos @behackl Do you need any help with this issue? I can work on it


Which version support redis 6.0.9??

Thanks for wanting to report an issue you've found in redis-py. Please delete this text and fill in the template below.
It is of course not always possible to reduce your code to a small test case, but it's highly appreciated to have as much data as possible. Thank you!
Version: What redis-py and what redis version is the issue happening on?
Platform: What platform / version? (For example Python 3.5.1 on Windows 7 / Ubuntu 15.10 / Azure)
Description: Description of your issue, stack traces from errors and code that reproduces the issue

Any version of redis-py should support 6.0.9. I would suggest using the latest version.


Cannot validate certificate hostname without SNI

I get the following error message (example.com replaced with actual website) and can't figure out why and what to do about it:
<< Cannot establish TLS with webmail.chalmers.se:443 (sni: None): TlsException('Cannot validate certificate hostname without SNI',)
Steps to reproduce the problem:

mitmdump -vw filename
Connect (add as proxy) with android phone and install certificate (using mitmproxy.it)
Connect to some server

Any other comments? What have you tried so far?
It seems to work for some https-sites but not others. Examples that cause the errors are webmail.chalmers.se and m.handelsbanken.se.
System information
Mitmproxy version: 0.18.2
Python version: 3.5.2
Platform: Linux-4.7.2-1-ARCH-x86_64-with-arch
SSL version: OpenSSL 1.0.2h  3 May 2016
Linux distro: arch

Which client are your using? I suspect an old version of Android?
The problem is as follows: When mitmproxy connects upstream, it verifies the certificate the server presents. One part of the verification is to check if the certificate matches the hostname the client is expecting. Modern versions of TLS mandate the client to send a Server Name Indication (SNI) extension during the TLS handshake which names the expected site. However, if your client does not send a SNI extension, there's no way for us to verify the authenticity of the server's certificate as we don't know which site the client is expecting and we fail the connection in the way you described. You can work around this by disabling certificate verification with mitmproxy --insecure - be warned that you are subject to man-in-the-middle attacks then.

Yeah, that was probably the issue. Thanks!

However, if your client does not send a SNI extension, there's no way for us to verify the authenticity of the server's certificate as we don't know which site the client is expecting

@mhils  I get your point on SNI yet, if a Fully Qualified Domain Name is provided with the CONNECT, can't you use this piece of data instead of the SNI ?

yet, if a Fully Qualified Domain Name is provided with the CONNECT, can't you use this piece of data instead of the SNI ?

Yes, that would be possible, but I feel the complexity of supporting that outweighs the potential benefit.

I'm not sure I understand why mitmproxy tries to validate the name of certificate.
IMO, the following should work and avoid upstream man-in-the-middle attacks:

Connect to the remote server, transmitting any SNI, ALPN, etc. received from the clienty (basically copies the Client Hello info).
When server sends Certificate, validate the chain but ignore the subject. (completely bypass verification if --insecure)
Generate MITM cert based on Cert received from server (CN, other fields). Basically the only difference should be the public/private key and of course the signature (and possibly the Issuer if not replicating the cert tree)
Client verifies the MITM Cert, including the subject against its expectations.

That way, it would work for protocols/client that don't use SNI, in transparent / SOCKS mode, or if the client tries to validate the subject using something else than a host name (happens with TCP over TLS streams).

I have another idea to work-around this problem: a reverse-dns table in the mitmproxy config.
So, if there are a couple of IP addresses which I know ahead of time will receive requests for a particular domain name, I could put that in the mitmproxy config, like:
assume_hostname:
    "<IP_ADDRESS>": "foo.example.com"
    "<IP_ADDRESS>": "bar.test.net"

Then, when mitmproxy intercepts a TLS connection to <IP_ADDRESS>, it uses the hostname foo.example.com to check the certificate, if the client did not include TLS-SNI, and it otherwise does not yet know the hostname.
Just an idea, which would help with my use case at least.

@ploxiln
when I run with the config provided by you I get in console:

Ignored options: {'assume_hostname': CommentedMap([('my.ip.address.here', 'my.hostname')])}
and mitmproxy is started

Mitmproxy: 3.0.3 binary
Python:    3.5.2
OpenSSL:   OpenSSL 1.1.0g  2 Nov 2017
Platform:  Linux-3.13.0-79-generic-x86_64-with-debian-jessie-sid
Any clues why the option is ignored?

It does not exist. It was an idea for a feature to be added.

I have a similar issue as @ploxiln where the very dumb client device I am working with doesn't include the SNI but the domain came through in the previous DNS request. I can map it to an IP address so having the concept of assume_hostname would solve my problem.

Starting mitmproxy with the -k (--ssl-insecure) option will disable certificate checking so this will work (though obviously it will open all of your traffic up to invalid certificates).

Starting mitmproxy with the -k (--ssl-insecure) option will disable certificate checking so this will work (though obviously it will open all of your traffic up to invalid certificates).

The disable certificate checking doesn't fix the problem with no SNI in the header. If for example you had a machine with multiple interfaces or secondary IP addresses such as:
<IP_ADDRESS> sitea.com
<IP_ADDRESS> siteb.com
If you could add in a "assume hostname" configuration element as mentioned above into MITM proxy then if your client is connecting to sitea.com on <IP_ADDRESS> but the client didn't include the SNI as part of the client hello request to the proxy server and only validated the subject but didn't care about the certificate chain (or you could load your own CA into the client) then this would work.

Starting mitmproxy with the -k (--ssl-insecure) option will disable certificate checking so this will work (though obviously it will open all of your traffic up to invalid certificates).

The disable certificate checking doesn't fix the problem with no SNI in the header. If for example you had a machine with multiple interfaces or secondary IP addresses such as:
<IP_ADDRESS> sitea.com
<IP_ADDRESS> siteb.com
If you could add in a "assume hostname" configuration element as mentioned above into MITM proxy then if your client is connecting to sitea.com on <IP_ADDRESS> but the client didn't include the SNI as part of the client hello request to the proxy server and only validated the subject but didn't care about the certificate chain (or you could load your own CA into the client) then this would work.

The disable certificate checking doesn't fix the problem with no SNI in the header.

I can't claim to understand SNI but I got the error listed above, and adding --ssl-insecure fixed it for me. I think in my case the client was connecting by IP address, like https://<IP_ADDRESS>/` or whatever, and it also ignores certificate validation errors.
Also, I found that the mitmweb has an option to turn on --ssl-insecure temporarily in the web interface which is nice. There's a slight bug in that if you pass --ssl-insecure on the command line, the "Don't validate certificates" checkbox is initially unchecked.


Remove SMT.AST.nameFromSExpr

See #1702
Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock

I added from the K repository the test ite-bug's passing-spec.k and it's not working

The proof doesn't pass for me. The implication check at the end is sent to the solver, but it is not completely translated.

@andreiburdusa I fixed the test by using minInt instead of #if_#then_#else. Please add tests for Kore.Attribute.Smtlib.applySExpr, because I had to fix a bug there, see #1755.


Return invalid amount from get_address_abstracts API if a transaction has network fee

e.g. for the transaction ee6f489503137bc80f81502be6d0ec8558df59797b7279aa873624e9e96b5587 from the address APdjiDV4EmJjRHV1pTQT6fFN3iPVswb7RP to address AKNywXYJMKpoEgbfG8wij2Tae5uQ78pg7n:

actual amount: 0.00215951
expected amount:  0.0021595

I believe the amount are correct, the 0.00000001 missing is actually the network fee. Maybe we should have a visual to make it part of the transaction, right now it is just written under, maybe it is not that clear.

Maybe I mentioned it's not clear from previously, I mean the amount from the get_address_abstracts API (https://api.neoscan.io/api/main_net/v1/get_address_abstracts/APdjiDV4EmJjRHV1pTQT6fFN3iPVswb7RP/1) is 0.00215951.
But actually, the address APdjiDV4EmJjRHV1pTQT6fFN3iPVswb7RP transferred 0.0021595 to AKNywXYJMKpoEgbfG8wij2Tae5uQ78pg7n (https://neoscan.io/transaction/EE6F489503137BC80F81502BE6D0EC8558DF59797B7279AA873624E9E96B5587)
Is the amount should be 0.0021595 from get_address_abstracts?

yes indeed, I will investigate

right now an intermediate solution is to remove the network fee from the gas transfer (special case for gas transfers) only one abstract will be shown and the transaction for the network fee will be omitted from the list.
this a temporary solution, a better solution will be to list the gas transfer and the network fee. Similar of what we have when we do a neo transfer with network fee.

I agree with you as it shows difference between UI and database.


Merge Exploration/lidar

Example of loading and visualizing lidar data

Hi @NicolasDenier ,
thank you very much for this PR. You can just add a few lines in the readme to explain what you're doing here and how to run the code. For example, you need to download the data. Maybe you can add a script to do it easily

I added explanations on the readme


[BUG] Deploy doesn't work out of the box

Overview

Downloaded the CLI
Created hello world blueprint
Built it successfully
Deployed using the script

Error:
   0: data did not match any variant of untagged enum GadgetSourceFlat at line 47 column 7

Location:
   cli/src/deploy.rs:134

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

I will take a look at it today.
cc @Serial-ATA we may need to add integration tests with the CLI on CI

It looks like you are using an older version of the CLI, please update to the latest version and try again.
To update, try:
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/tangle-network/gadget/releases/download/cargo-tangle-v0.1.2/cargo-tangle-installer.sh | sh

Or from crates.io
cargo install cargo-tangle


A wired problem I found when testing the VOC dataset 2007

def get_conv_image_descriptor_for_image(image, model):
    im = cv2.resize(image, (224, 224)).astype(np.float32)
    print('resized: {}'.format(im.shape))
    dim_ordering = K.image_dim_ordering()
    if dim_ordering == 'th':
        # 'RGB'->'BGR'
        im = im[::-1, :, :]
        # Zero-center by mean pixel
        im[0, :, :] -= 103.939
        im[1, :, :] -= 116.779
        im[2, :, :] -= 123.68
    else:
        # 'RGB'->'BGR'
        im = im[:, :, ::-1]
        # Zero-center by mean pixel
        im[:, :, 0] -= 103.939
        im[:, :, 1] -= 116.779
        im[:, :, 2] -= 123.68

    im = im.transpose((2, 0, 1))
    print('transposed: {}'.format(im.shape))
    im = np.expand_dims(im, axis=0)
    print('expanded: {}'.format(im.shape))
    inputs = [K.learning_phase()] + model.inputs
    _convout1_f = K.function(inputs, [model.layers[31].output])
    return _convout1_f([0] + [im])

def get_state(image, history_vector, model_vgg):
    print('--------b4: {}'.format(image.shape))
    descriptor_image = get_conv_image_descriptor_for_image(image, model_vgg)
    print('--------aft: {}'.format(np.array(descriptor_image).shape))
    descriptor_image = np.reshape(descriptor_image, (visual_descriptor_size, 1))
    history_vector = np.reshape(history_vector, (number_of_actions*actions_of_history, 1))
    state = np.vstack((descriptor_image, history_vector))
    return state

when deploying the function above, the output I got on screen were as follows:
--------b4: (272, 500, 3)
resized: (224, 224, 3)
transposed: (3, 224, 224)
expanded: (1, 3, 224, 224)
--------aft: (1, 1, 5376)
the final output from the 31th layers of VGG16 should be 25088 (size of length), but in my code the size is 5376. Therefore the inference cannot be continued because of this dismatch between two vectors, one should be 25088, but is 5376 instead.

Have you made any changes to the data set voc2012?Why does this error occur when I run the program?
xml.etree.ElementTree.parseError:not well-formed(invalid token):line1,column 0。Could you tell me how to solve this problem?


Glyph vertical alignment different than some FontAwesome icons in Firefox.

I noticed the difference in vertical alignment on the angle-right and angle-left icons ('\f105' and '\f104') in Firefox. I haven't seen this problem in other browsers I've tested in.  I can adjust the alignment in the stylesheet on a case by case basis, but it would much better if Fontello could be dropped in as a replacement for Font Awesome without needing fine-tuning like that.
Changing the "Units per em" and "Ascent" font metrics to match Font Awesome (1792 and 1536, respectively) didn't seem to make a difference.
Anyway, thanks for providing this great tool/resource.

I'd suggest 2 things:

vary baseline in advanced settings, FA uses 14.2857143%
disable or enable hinting (don't know if FA use it)

If that does not help, then metrics compare with ttx utility required.

Strange, the only way I had nearly similar results across browsers was to set baseline to 0...
(Font with 5 social media icons from FA)

I'm seeing differing vertical alignment in all browsers compared to FontAwesome.

Not sure if related, but i had issues with some vertically subaligned FA icons (fa-download, fa-cogs, fa-power-off) in Windows browsers only (tested with Chrome, Firefox, Edge).
After disable hinting as suggested, vertical align is ok:

seems to be exactly the problem I am having, have not yet figured out what hinting is or how to disable it.


does compiling on linux work?

What is your question?
i just need to know if compilling in linux works?

yes it does(

yes, work.
but becareful window code if you edit source


[Snyk] Upgrade firebase from 9.10.0 to 9.12.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade firebase from 9.10.0 to 9.12.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 39 versions ahead of your current version.
The recommended version was released a month ago, on 2022-10-12.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Base: 81.05% // Head: 81.05% // No change to project coverage :thumbsup:

Coverage data is based on head (5c939d1) compared to base (bef07b7).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #402   +/-   ##
=======================================
  Coverage   81.05%   81.05%
=======================================
  Files          31       31
  Lines         417      417
  Branches       61       61
=======================================
  Hits          338      338
  Misses         73       73
  Partials        6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Object literal properties color

It would be nice to have different colors for JavaScript object literal attributes and values to make them easier to distinguish.

Hi, can you provide more details?

Sure,
let value1 = 1;
let value2 = 2;
let obj = {
  property1: value1,
  property2: value2,
};

In a case like this, it would be nice if the properties had a different color to clearly distinguish them from the values.

Do you se something different?

This is what I see, using the default Material Theme

We can't replicate this issue. Are you using a javascript syntax extension?

I'm seeing the same as @tobdub, with no other theme extensions installed other than this one.

That's the point guys :) The basic vscode highlights aren't good since they don't cover all the syntax scopes.

Changed language to typescript, and now obj : key looks ok.

I too am seeing the same issue as @tobdub. Changing language to Typescript did nothing for me. Anyone able get this to work?


Png's with alpha overlayed within a viewport render with a black outline.

Just built godot on windows and the problem still persists. Here is a detailed description:

Solved (use trasparent bg setting for the viewport).

@PLyczkowski Using that option is what gives me black outlines on sprites with transparencies.   Have things changed since you first posted this?

@PLyczkowski Using that option is what gives me black outlines on sprites with transparencies.   Have things changed since you first posted this?

I can see all of you.
On Thursday, 14 January 2021, avencherus<EMAIL_ADDRESS>wrote:

@PLyczkowski https://github.com/PLyczkowski Using that option is what
gives me black outlines on sprites with transparencies. Have things changed
since you first posted this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/1499#issuecomment-760160501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMZECTXQVJB5OEQTWEBZUDSZ3OJ5ANCNFSM4A5SQ7TA
.

--
nicole.gmail.org

I can see all of you.
On Thursday, 14 January 2021, avencherus<EMAIL_ADDRESS>wrote:

@PLyczkowski https://github.com/PLyczkowski Using that option is what
gives me black outlines on sprites with transparencies. Have things changed
since you first posted this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/1499#issuecomment-760160501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALMZECTXQVJB5OEQTWEBZUDSZ3OJ5ANCNFSM4A5SQ7TA
.

--
nicole.gmail.org

Look into using premultiplied alpha textures and viewport. You may have to tweak the CanvasItemMaterial used to display the ViewportTexture.

Look into using premultiplied alpha textures and viewport. You may have to tweak the CanvasItemMaterial used to display the ViewportTexture.

@Calinou Thanks.  Yeah, that solved it.  Not able to follow the reference, I'm not sure what the source and destination textures are in the equation.  Looked at GL_ONE_MINUS_SRC_ALPHA, and maybe I could reason about it if I were blending two textures.

@Calinou Thanks.  Yeah, that solved it.  Not able to follow the reference, I'm not sure what the source and destination textures are in the equation.  Looked at GL_ONE_MINUS_SRC_ALPHA, and maybe I could reason about it if I were blending two textures.

@Calinou Doesn't work when lowering the alpha when trying to modulate.  Was aiming to be able to fade the whole VP texture.  Any suggestions on how to combine the modulate alpha and premult alpha?

@Calinou Doesn't work when lowering the alpha when trying to modulate.  Was aiming to be able to fade the whole VP texture.  Any suggestions on how to combine the modulate alpha and premult alpha?


Reactivity from array children ?

I wonder if I did something wrong here, could you explain why it does not work as I expect it ?
The router sends data to the template :
Router.map(function () {
    this.route("/index", {
        data: function () {
            return {
                items: Items.find().fetch()
            }
        }
    });
});

*Items look like : *
{
    _id: 123123,
    name: "Apple"
}

Template :
<template name="index">

{{selected.name}}

{{#each items}}

    {{name}}

{{/each}}
</template>

Javascript :
Template.index.viewmodel({
    selected: undefined,
    select: function (id) {
        this.selected(_.find(this.items(), {_id: id}));
    }
});

I am using Lodash here. Then when I click on the div with the binding, the item is correctly selected and its name is displayed above.
Problem : When I change one of the item in the database, the items list updates reactively, but not the selected one. If I click again on the previously selected item, it updates on the selected. If it was really reactive, the selected item should update when the items list updates, should it not ?

You're doing a couple of things wrong here.

You should use IR just for routing and not subscriptions and data fetching.
You're going through all items to find one, use minimongo instead (collections are hashed by _id).
You're pushing data into the selected property. It should be a function that returns the item based on the selection.

Here's how it can look:
Router.map(function () {
    this.route("/index");
});

Template.index.viewmodel({
  items: function() {
    return Items.find();
  },
  selectedId: '',
  selectedItem: function() {
    return Items.findOne(this.selectedId());
  }
});

<template name="index">

    {{selectedItem.name}}

  {{#each items}}

  {{/each}}
</template>

That's the usual case, but if you're not going to use the selectedId for anything else, you can simplify it even further:
Template.index.viewmodel({
  items: function() {
    return Items.find();
  },
  selected: null
});

<template name="index">

    {{selected.name}}

  {{#each items}}

  {{/each}}
</template>

You are right ! I have still some trouble using viewmodel logic. Until now, I used a lot of route data (especially since I was using the router progressbar) and worked as much as I could with that (not much minimongo though). Thank you :)


Placeholder in partial application method

Placeholder value R.__ is not working with R.partial. In the example below it should leave "b" free to be applied, but never applies it. It should apply 4 to "b" in my opinion.
function add(a, b, c) {
  console.log('a', a, 'b', b, 'c', c);
  return a+b+c;
}
var add2_5 = R.partial(add, 2, R.__, 5);
add2_5(4);
// prints "a 2 b {ramda: "placeholder"} c 5"
// output 2[object Object]5

thanks, that looks like a :beetle: alright

I agree that R.partial and R.partialRight should respect the R.__ placeholder. The implementation could be similar to jashkenas/underscore#1382.

that sounds like you are volunteering @davidchambers :smiling_imp:

We definitely should do this.  And that Underscore implementation looks useful.

Anyone want to create a PR for this?
Anyone?  Anyone?  @bahmutov?

I was initially excited by this idea, but I now wonder whether it's something we should support. One can use R.curry instead. For example,
var add2_5 = R.partial(add, 2, R.__, 5);

could be written
var add2_5 = R.curry(add)(2, R.__, 5);

I'd like to hear from users who actually use partial/Right on this.
We have partial because of all the discussions about the difference between currying and partial application.  (I do understand the technical differences, and realize that what we call currying in Ramda is something in between the two.)  It seemed that there were people who really wanted to just use partial application of their functions.
I am -- ahem -- partial to currying, and never use our partial-application, so I don't have a real sense if there are reasons that users who wanted the placeholder couldn't simply use curry instead.
Can anyone answer this?

I've only used R.partial when fully applying a function but not wanting to invoke it yet. I.e. to apply n arguments to a n-ary function in order to get back a zero-arity function.

I never use R.partial, but I occasionally use R.partialRight to avoid using the placeholder:
var readFile = R.partialRight(fs.readFileSync, {encoding: 'utf8'});

Rather than:
var readFile = R.curry(fs.readFileSync)(R.__, {encoding: 'utf8'});

Closing without prejudice

I just tried to use placeholders in partial() instinctively, but as you noticed it's no-go.
I believe this functionality has its place just as compose / pipe functions do.
I'm not opening a new ticket as i'm still quite fresh in ramda, and i don't feel competent reasoning more, than i just said.

@shdpl, would you mind sharing the code snippet? I'm interested to see whether it could be written naturally in terms of R.curry or R.partialRight, or whether R.partial with placeholders really is the most natural expression of the idea.

I guess that situation will happen anytime you want to inject something in a middle, so more arguments your functions take, more chances for that. I'm not used to "classical" functional style where you need to care about parameter ordering that much. I also like to define variables only if something needs to be used at least twice, so it's quite possible that people who program in "classical way" do not have such needs.
var f = R.curry( GoogleMaps.on )( 'overlaycomplete', R., this.drawingDisable )
var f = R.partial( GoogleMaps.on, 'overlaycomplete', R., this.drawingDisable )
I'm not saying it's hell of a difference, but second definition just feels more natural ( to me ).

I'm not saying it's hell of a difference, but second definition just feels more natural ( to me ).

I find the R.partial definition more natural too. The question is whether slightly more natural definitions in these cases justify the documentation complexity and implementation complexity of overloading R.__. My current view is that they do not, since the alternative definitions are almost as nice.
Perhaps the solution is to explain in the documentation of R.partial how R.curry can be used to mimic _.partial with placeholders.
I'm open to changing my mind on this matter. Feel free to post more examples here as you encounter situations where placeholder support in R.partial would be useful.


Environmentment variable for cluster access

Accessing a remote cluster requires that I have an environment variable set. Is there a way to accomplish this, or could a configuration option be added?

Can you clarify?  If the cluster is in your kubeconfig then it should accessible through the extension. What do you mean by 'remote'?  (E.g. we use it for clusters in Azure all the time.)  What is the environment variable you find you need to set?


sort array with 0,1,2

Related Issue

Mention issue for which this pull request is a part of (please mention issue number # )

Proposed Changes

Change 1
Chnage 2

Additional Info

Any additional information or context

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the documentation.
[x] 🎀 I have updated the documentation accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Output Screenshots

Screenshot #1
Screenshot #2

Title goes here
Title goes here

Image goes here
Image goes here

Duplicate  #165

Few things to keep in mind while contributing next time

ScreenShots of your code and working output in pR
Make your PR descriptive
No README Changes
Faulty checks in checklist things are not actually done but checked in checklist i.e. README

Short Description or CheckLists

Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Descriptoin -----------------------///
For contribution and more guidelines i would recommend you to go through this
tutorial video of the project here, thanks.
///-----------------CheckList-------------------------///
Make sure your Pull Request is descriptive and complete the checklist .
I would recommend you to go through this tutorial video of the project here ,thanks.
///------------------Description -----------------------///
Let me show you how to check the check list , there should be no space inside brackets like [x]
[x]

[x] Checklist
[ ] Or you can just check them from outside without doing any of these
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[ ] 🌟 ed the repo

Starr the repo if you haven't !
Have you watched this video ?

///----------------------PR README --------------------///
You need to follow particular guidelines for your README , please follow
these guidelines click here
also you can see how your README should look like see here
for more please go through these here


Sb 16295 feat: upload Component - Buttons disable/Modal display is corrected

https://project-sunbird.atlassian.net/browse/SB-16295

@venkanagouda-k Follow git commit standards
** Issue #SB-xxxxx feat: 'message'**


Inventory

From #797. Added missing mission.xml changes. Adjusted the default amount(s) attributes in MissionHandlers.xsd. Currently failing PythonIntegrationTests_inventory_test.

I think the reward needs updating with something like:
int dimension = params.getDimension();
float adjusted_reward = this.adjustAndDistributeReward(
((BlockOrItemSpecWithReward) matcher.matchSpec).getReward().floatValue(),
params.getDimension(),
((BlockOrItemSpecWithReward) matcher.matchSpec).getDistribution());
addCachedReward(dimension, adjusted_reward);
in all the RewardFor*.getMatch() methods.
But the test assumes that the reward is given each time the number of items are collected.

Now restored backwards compatibility. Need more testing of new functionality.


Pr/update serverless

Update serverless to v1.28.0

Ah so we forked https://github.com/serverless/serverless & update it regularly.
@mt-yucheng What are the changes/differences between the version we have & update? If we have any major updates we should be careful.

@mt-sukeshni Here are some details: https://github.com/moneytree/serverless/wiki

@mt-yucheng Thanks for the details link it's a bit more clear, checked the files that were changed by us https://github.com/moneytree/serverless/compare/v1.26.0...v1.26.0-mt , they look good after the update.
To me it looks OK but better to get someone else's review :)


About Target JKS/PKCS12 password - Not in the generated target configMap/Secret

I have recently discovered trust-manager and started experimenting with it.
To me, the part about JKS/PKCS12 password lacks some clarity:

In https://cert-manager.io/docs/trust/trust-manager/#targets, spec.target.additionalFormats.jks.password and spec.target.additionalFormats.pkcs12.password are introduced as a mean to overwrite the default 'changeit' password.
In https://cert-manager.io/docs/trust/trust-manager/api-reference/#bundlespectargetadditionalformats, no mention of the password parameter or their purposes (=> documentation needs to be updated)

Looking to use the bundle outcome (as a secret) with Jenkins for the HTTPS keystore (see https://github.com/jenkinsci/helm-charts/blob/e60a42b6e11f41328f73c4a90bcbcce14f535165/charts/jenkins/values.yaml#L836-L846), I was under the impression that the JKS/PKCS12 password would be included into the generated secret.
Unfortunately, tests showed that it is not the case...

Would it possible to set spec.target.additionalFormats.jks.password/spec.target.additionalFormats.pkcs12.password from a secret reference and key?
Would it be possible to have that password included in to the generated secret, or a separate one?

Hi @Ceddaerrix, this seems to be a multi-purpose issue. 😉
It seems like the trust-manager API documentation is out-of-date. Thanks for letting us know! I will look into what's happened here.

Would it possible to set spec.target.additionalFormats.jks.password/spec.target.additionalFormats.pkcs12.password from a secret reference and key?

Why do you need this? It would make the controller mechanics considerably more complex. Passwords on JKS/PKCS#12 keystores/truststores do not make things more secure and should be considered legacy. There is a note about them in our FAQ: https://cert-manager.io/docs/faq/#why-are-passwords-on-jks-or-pkcs12-files-not-helpful

Would it be possible to have that password included in to the generated secret, or a separate one?

Why? If you think the keystore/truststore password represent anything useful, you should keep it separate from the keystore/password and manage it independently. 😸


Flash via LAN port

I'm trying to set up a station to test a EASY92080 DSL router from Intel. The DSL router has a DSL for the  WAN port and four LAN ports. In this case, I'd need to flash the router via the LAN port. This is a problem in Boardfarm as all of the TFTP flashing support assumes that the WAN device will be the TFTP server. In this case, we have no WAN device and we need to flash for the LAN device.
I've been thinking of ways to address them and some of themseem to imply that we'll have to significantly modify how TFTP is setup on devices. For example, we could make TFTP a capability of sorts and allow any device to be setup as a TFTP server. This means pulling some of the code out of debian.setup_as_wan_gateway.
Another way we could do it as allow the LAN configure as a WAN right before the flash happens and then reconfigure back after the flash is complete. I'm unsure on the consequences of this though.
What do folks think?

I've added some code to my master branch to do just this, can you test it out?
mattsm./boardfarm

This code is merged


Requests for clarifications on fsc and snips

We are a group of NYU MS in Data Science students who are working on developing an end-to-end speech-to-intent model. We have read your paper and replicated your code and would love to ask you some questions.
Paper vs. Github Results Discrepancy
We notice that the final test accuracies for both FSC and SNIPS are different in your paper (ie. 97.65% for FSC, 73.49% for SNIPS) and the github repo (ie. 95.65% for FSC, 69.88% for SNIPS). Can you share some thoughts on the difference between the number in the paper and git repo?
SNIPS Data Partition Ambiguity
In prepare_snips.py, we notice that you split complete.csv into train-val-test. However, since we don’t have this complete.csv that you used, we can’t replicate the exact same partitions. Our results from running your code on our SNIPS dataset using our own splits are significantly higher on average: we ran 4 times (each time using our own splits of shuffled complete.csv), and average accuracy is 81.17%  though we use the same environment mentioned in your git repo. We’d love to double check with you on these points.

Which subsets of the SNIPS dataset did you use to create the complete.csv? Our guess is that you used smartLight close-field and far-field (3320 observations) for your experiments (ie. are these the data listed in your complete.csv). Please let us know if that’s incorrect.

Would you mind sharing your complete.csv and intents.json for SNIPS with us? We believe having the input data in the same format/split is important to draw a fair comparison between yours and our future work.

BERT Embeddings Fine-tuned or Not.
Section 2.1 of your paper says “we back-propagate the embedding and SLU task losses only to the acoustic branch” because you think fine-tuning BERT will lead to overfitting. From this line, our understanding was that the BERT embeddings would be frozen. However, we’ve noticed this piece in the code where the parameters were passed into the Adam optimizer with the learning rate 2e-5 (line 63 in experiment_triplet.py), implying that BERT embeddings would be fine-tuned.
       self.optimizer = torch.optim.Adam([             {'params': self.model.bert.parameters(), 'lr':args.learning_rate_bert},             {'params': self.model.speech_encoder.parameters()},             {'params': self.model.classifier.parameters()}         ], lr=args.learning_rate)
We would appreciate it if you can give us clarification on whether BERT is fine-tuned and, if so, the reason you chose to fine-tune BERT. Furthermore, in the case where BERT’s parameters are not frozen, could you share some thoughts on fine-tuning BERT for 20 epochs (default in the code), which may lead to overfitting and hurting the text embeddings? As mentioned in other papers about BERT, the typical number of epochs for fine-tuning BERT is 5 at max.

great!

Hi Cora, I'm on a team from CMU and we're also trying to reproduce the results from the Tie Your Embeddings Down paper. Were you able to get the FSC model trained, matching the results reported in the README?
My teammate @ostapen tried this but found the model isn't learning, even after hours and hours of training. To avoid hijacking your thread, you can alternatively email me at the email address listed on my website, and then I can start a thread with my other teammates.

great!
你好，你下载的snips数据集里有。.csv文件吗？


Desktop

Made corrections to my css design.
Added a link to my live site

Thank you
On Monday, December 19, 2022 at 11:16:44 AM GMT+1, Jerry Owusu<EMAIL_ADDRESS>wrote:

@jerryowusu approved this pull request.
Hi @Divinity-dev ,
Your project is complete! There is nothing else to say other than... it's time to merge it
Congratulations! 🎉
Highlights
Project deployed successfully ✔
All linters are passing ✔
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding! 👏 👏 👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


How to change needle color

Hi,
I need to change the needle color and value text because I would like to use a black background in may app.
Is it Possible?
Thank you

Hi,
@afacchin73 if u find way to change needle color and value text, can u write here?

Hi,
I need to change the needle color and value text because I would like to use a black background in may app.
Is it Possible?
Thank you

Hi Sorry for late response
if it still relevant
you can change color of needle like this example
 HalfGauge.setNeedleColor(Color.MAGENTA)

Hi,
@afacchin73 if u find way to change needle color and value text, can u write here?

Hi Sorry for late response
if it still relevant
you can change color of needle like this example
HalfGauge.setNeedleColor(Color.MAGENTA)


Quadratic programming Lasso formulation

You state in <IP_ADDRESS>: "There are several applications of quadratic programming in ML. In Section 11.4, we show how to use
it for sparse linear regression."
Then I looked at 11.4.
I was expecting some reference to GPSR paper, [FNW07] or some formulation like the one in <IP_ADDRESS>.
I.e., showing how to reformulate lasso as a quadratic-programming problem which can then be fed into generic cvx or cvxpy packages. I am guessing that this is not efficient computationally, but would fit your statement "show how to use
it for sparse linear regression."

I can see it in <IP_ADDRESS>. Anyway, was not easy to find with so many subsections. Perhaps it would help to guide a bit more precisely.

Yes I should cite eqn 11.103 for how to formulate Lasso as a QP. Fixed.


fix: not print secret in the log

fix #3

For testing, I pull a test docker image: chengqingsu/cert-manager-webhook-dnspod:latest

thanks for your pr, I found that your commit contains that set request domain name, which is required parameter of the dnspod api now, I already fixed it , just forgot commit, and your hiding secret suggestion is accepted, commit together and pushed, thank your again.


Issue with Cookies module for angular 1.4+

The cookies aren't stored in the browser when we use angular 1.4+ simply by using $cookies.var = value
https://docs.angularjs.org/api/ngCookies/service/$cookies
We have to use $cookies.get(name) and $cookies.put(name, value, [options])

@adimux This issue is not directly related to django-rest-auth. Closing.

Which trouble with cookie you have, maybe I can help you. We use angular too with django-rest-auth

It is related, because the key is not stored in the cookies. And thus, django-rest-auth is not aware that the user is already connected if the page is reloaded.

@adimux feel free do with this key what you like. If you want save key from default auth serializer to cookie and then reuse it in angular app, you must integrate key more closely to angular.
Actually you can use default auth by cookie for this case.


Correct XML docs for DataModel Attributes

Description

This change corrects XML doc references to "local" indexes for "global" index attributes, "range" keys for "hash" key attributes, and fixes some small typos.
Motivation and Context

I'm new to DynamoDB, while exploring the available attributes in my IDE's autocomplete I noticed that the descriptions for some attributes seemed to mismatch what the attribute actually represented. This change corrects the documentation, and removes confusion for those using the SDK. I noticed a few other typos while making the change and fixed them up as well.
Testing

Since this change only touches documentation, I haven't tested very thoroughly. I need to get my home environment running with older versions of .NET, but after unloading the 3.5 and 4.5 projects I managed to run all unit tests (except 3..5 and 4.5 specific ones) successfully.
Screenshots (if appropriate)
N/A
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have read the README document
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

Thanks for the contribution, your PR will be included in the next release of the AWS SDK for .NET.


fix: implement native_iceberg_drop

… dev and testing
Description

resolve #285
resolve #291

Remove need for direct access to S3 & Glue to drop an Iceberg table. I figured that there needs to be a way for me and others to test the solution works with the restricted permissions so I have the start of that here.
Models used to test - Optional

Checklist

[/] You followed contributing section
[/] You kept your Pull Request small and focused on a single feature or bug fix.
[ ] You added unit testing when necessary
[ ] You added functional testing when necessary

:thinking: when I committed the restrictive role contained in the CloudFormation template for convenience) my thinking was to document a specific set of permissions in a role that can be used by anyone (or automation) for testing that the base functionality works without direct access to restricted APIs - obvs. could loosen the restrictions eg. to allow direct access to certain Glue APis.

Maybe it's a separate thread/issue, but having a way to explicitly test that basic dbt functionality works under a more restrictive set of permissions than the one currently used seems like the only way to really say that dbt-athena can be used under those permissions?
that's indeed the right thought.
What do we need to achieve this in a more scalable way:

a IAM role that can be assumed by github action with resticted permissions - I would add it here: https://github.com/dbt-athena/dbt-athena-infra (CDK based setup) - see here
another section in functional-tests that assume the role with restricted mode and we the flag native_drop=True

IMHO, in this specific case you are not really blocked, as you can prepare the feature without all the testing setup - to see if it works we can check if drops query hits athena, and you can turn debug mode on to see if the s3 cleanup path is called.

It might make sense to combine this and the native seed thing - they are a bit coupled together which makes me a bit unsure whether it's good as a whole
Evidence
21:37:10.808696 [debug] [Thread-1  ]: Began executing node seed.ephemeral.base
21:37:10.881750 [debug] [Thread-1  ]: Opening a new connection, currently in state closed
21:37:11.224528 [debug] [Thread-1  ]: Dropping relation via SQL only
21:37:11.226145 [debug] [Thread-1  ]: Using athena connection "seed.ephemeral.base"
21:37:11.227143 [debug] [Thread-1  ]: On seed.ephemeral.base: drop table if exists `awsdatacatalog`.`test16843558268112747602_test_basic_iceberg_native_drop`.`base__dbt_tmp`

21:37:12.694506 [debug] [Thread-1  ]: SQL status: OK -1 in 1.0 seconds
21:37:12.714119 [debug] [Thread-1  ]: Using athena connection "seed.ephemeral.base"
21:37:12.715985 [debug] [Thread-1  ]: On seed.ephemeral.base:
    create external table `awsdatacatalog`.`test16843558268112747602_test_basic_iceberg_native_drop`.`base__dbt_tmp` (id string, name string, some_date string)
    row format serde 'org.apache.hadoop.hive.serde2.OpenCSVSerde'
    location 's3://843328850426-athena-results/staging/tables/test16843558268112747602_test_basic_iceberg_native_drop/base__dbt_tmp/afd3b34c-0d4c-4581-82d4-da916d517f73'
    tblproperties (
      'skip.header.line.count'='1'
    )

21:37:14.046299 [debug] [Thread-1  ]: SQL status: OK -1 in 1.0 seconds
21:37:14.362476 [debug] [Thread-1  ]: Config native_drop enabled, skipping direct S3 delete
21:37:14.363567 [debug] [Thread-1  ]: Using athena connection "seed.ephemeral.base"

Test run output, unit_tests all passing too
pytest -n auto tests/functional
====================================================================================== test session starts ======================================================================================
platform linux -- Python 3.8.13, pytest-7.3.1, pluggy-1.0.0
rootdir: /home/paul/projects/brabster/dbt-athena
configfile: pytest.ini
plugins: cov-4.0.0, dotenv-0.5.2, xdist-3.3.0
8 workers [57 items]
ssssss....ssss.ss.s.....ss........s......................                                                                                [100%]
======================================================================================= warnings summary ========================================================================================
tests/functional/adapter/test_basic_hive.py: 31 warnings
tests/functional/adapter/test_basic_hive_native_drop.py: 15 warnings
tests/functional/adapter/test_basic_iceberg.py: 15 warnings
tests/functional/adapter/test_basic_iceberg_native_drop.py: 6 warnings
tests/functional/adapter/utils/test_utils.py: 60 warnings
tests/functional/adapter/test_snapshot.py: 36 warnings
  /home/paul/projects/brabster/dbt-athena/venv/lib/python3.8/site-packages/jinja2/lexer.py:650: DeprecationWarning: invalid escape sequence '\('

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=================================================================== 41 passed, 16 skipped, 163 warnings in 593.48s (0:09:53) ====================================================================

please, fix the CI with required type import GetTableResponseTypeDef

Not sure how to close off the 2x requested changes - they have been implemented

I've been trying out these changes in my real project and looking at the logs I've got a suspicion that native_drop might be taking effect when it shouldn't... super difficult to be confident without tests and it's unclear how to write/augment tests that ensure the correct behaviour in on/off cases.
I did wonder about asserting the logs do or do not contain specific text (this is how I'm checking by hand) but I'm not sure how to assert against the caplog for the existing test cases that are extending dbt base tests, any ideas?

There was a bug, the way I was trying to get the value of 'native_drop' as a boolean was always true and that meant that any iceberg table would get the native drop behaviour regardless of the flag.
{%- set native_drop = config.get('native_drop', default='False') | as_bool -%}

Swapped to
{%- set native_drop = config.get('native_drop', 'False') == 'True' -%}

Which seems to work correctly based on log inspection. Also removed a few messy log messages that I'd left in there.

@svdimchenko my adjustments are based on several trials of different ways of expressing a boolean such that it worked in the iceberg test cases and in my actual model dbt config. I was really struggling to work out what the heck type was actually coming out in the Jinja template until I found that sqlserver example and this SO post which refers to Jinja docs saying and suggests that the bool types are lowercased in Jinja:

The special constants true, false, and none are indeed lowercase. Because that caused confusion in the past, (True used to expand to an undefined variable that was considered false), all three can now also be written in title case (True, False, and None). However, for consistency, (all Jinja identifiers are lowercase) you should use the lowercase versions.

So i'm confused now - especially as config.get('foo', default='bar') form is used everywhere else in the templates? Maybe I'm misunderstanding?


[BUG] Incomplete Display of Lists

I can only see a few pages of my favorites/tags. For example, I want to view a comic that I added to favorites a long time ago, but I can only see about 50 galleries, then I hit the bottom.
Just scroll down any of the lists then the problem appears.
Maybe the normal behavior is showing all of the favorites when scrolling down?
Additionally, I don't know if newer releases fixed this problem because they all need IOS 16. I would suggest that maybe you fix this on IOS 15? I'm not able to upgrade to IOS 16, thanks.

Thanks for your feedback.

I don't know if newer releases fixed this problem

Yes, that should have been fixed in v2.5.1.

I would suggest that maybe you fix this on IOS 15?

I'll answer that in #311.
cc @chihchy


Change setupLog.V(1) to setupLog.info to log some missing messages

Change setupLog.V(1) to setupLog.info to log some missing messages
To contribute to this ticket: #395

I actually made these debug messages because they aren't really relevant for end users. If more verbose log messages are required, you can always increase the verbosity with the -l flag.

This is why you are using setupLog.V(1) ? Why don't we then use then (like for java language) a debug mode and that we log such messages using setupLog.debug() ?

Ok. I will close this PR as such a change is not needed


Update Set-SnipeitAccessoryOwner.md

Just a minor documentation typo, nothing much =)

Hi, thanks for finding this typo.
All documentation in /docs is generated from modules powershell files. So all changes should be done there.
I'll update /docs  before merging develop to master.
If you are willing to make change, edit powershell files.  There's two things to add:
Use feature branch on your repo and when when making PR assign it against develop-branch here.

Hello Petri!
Thank you for the answer and the tips and sorry for the troubles, I had to idea that the /docs is generated from the powershell files. I will see what I can do about it!


Ionic2 solution

Do you plan to do a ionic2 solution?

Sure, it's possible! I'll give it a look.

+1

+1


improve correctness by using identity more broadly throughout the code

motivation: improve correctness by using identity more broadly throughout the code
changes:

remove name from package-reference, replace with alternate-identity for secondary (manifest driven) identity
use identity to lookup managed-dependencies and pins instead of urls
adjust tests

❗ this the the first part in a series of PRs, once this is merged and "baked" will continue with the next steps

@swift-ci please smoke test

@swift-ci please smoke test

cc @mattt

For your consideration, I have some follow-up changes here: https://github.com/mattt/swift-package-manager/pull/1/files

this is great, thanks for putting together. should we wait for this to be merged and you can follow on with a PR? I am also working on the next PR in this series but that work does not conflict with yours

For your consideration, I have some follow-up changes here: https://github.com/mattt/swift-package-manager/pull/1/files

this is great, thanks for putting together. should we wait for this to be merged and you can follow on with a PR? I am also working on the next PR in this series but that work does not conflict with yours

This is great!  I had left a question in the follow-on PR https://github.com/apple/swift-package-manager/pull/3155 about the change to the pins store, which I think is the internal name for the Package.resolved?  If so, I wonder if there is something we can do to make the experience better for old toolchains (e.g. 5.4) encountering the new keys.  I agree with the change, just thinking about the ergonomics of the change.

This is great!  I had left a question in the follow-on PR https://github.com/apple/swift-package-manager/pull/3155 about the change to the pins store, which I think is the internal name for the Package.resolved?  If so, I wonder if there is something we can do to make the experience better for old toolchains (e.g. 5.4) encountering the new keys.  I agree with the change, just thinking about the ergonomics of the change.

should we wait for this to be merged and you can follow on with a PR? I am also working on the next PR in this series but that work does not conflict with yours

@tomerd It's as you like it. I'm happy to submit a follow-up PR if that makes things easier for you.

should we wait for this to be merged and you can follow on with a PR? I am also working on the next PR in this series but that work does not conflict with yours

@tomerd It's as you like it. I'm happy to submit a follow-up PR if that makes things easier for you.

@swift-ci please smoke test macOS Platform

@swift-ci please smoke test macOS Platform

closing in favor of #3244


Missing directories/files are not created if needed

On a whim, and to see if I could keep things on my host machine, instead of creating a Docker volume with -v shotshare_data:/app/storage I created a directory under my host machine's ShotShare stuff, chown'd to 82:82 and mounted it with --mount type=bind,source=/shotshare/data,target=/app/storage.  This threw a 500 error (from caddy, not from nginx) so I went digging. It looks like the logger will create /app/storage/logs/  if needed, but if the empty directories already present in the Docker image aren't there as expected then ShotShare won't create them. Namely:

/app/storage/app/
/app/storage/app/public/
/app/storage/framework/
/app/storage/framework/cache/
/app/storage/framework/cache/data/
/app/storage/framework/testing/
/app/storage/framework/views/

Interestingly, an exception to this is /app/storage/app/uploads/, which gets created on first upload just fine.

Hey @EmberHeartshine, for this pattern, I would actually just mount the /app/storage/app/uploads folder, that way you don't interfere with any of the framework native directories, while still being able to mount your shots to a directory. For ex. -v /shotshare/uploads:/app/storage/app/uploads.

In this instance I specifically made a bind mount because I wanted the files to be on the host filesystem instead of obfuscated away in Docker's volume tree.

In this instance I specifically made a bind mount because I wanted the files to be on the host filesystem instead of obfuscated away in Docker's volume tree.

So you should be able to use -v to accomplish this, if you specify a path before the colon it will use a path from your host file system, if you just use a string it will be a named volume.
-v /shotshare/uploads:/app/storage/app/uploads should mount /shotshare/uploads on your host to /app/storage/app/uploads in your container.

Regardless of the syntax, I feel like the directories should be created if they're missing for whatever reason to avoid 500 errors.

Updated the docs to point to the correct directory (app/storage/app/uploads), I plan to revisit setup process for further simplifications. Additionally, this change will not be backwards compatible (it will only work for new installations where their shotshare_data volume is empty), to fix this you will need to

Create a new mount at the new path (not shotshare_data)
Move the old mount elsewhere (ex. /tmp/shotshare_data)
Manually copy the files from tmp to new volume (cp /tmp/shotshare_data/* /app/storage/app/uploads)
Drop the old volume

https://github.com/mdshack/shotshare?tab=readme-ov-file#run-in-https-mode

As noted, however, if you have the entire /app/storage directory mounted external to the docker image you don't have to change anything.


API Update verify() to return Result, and pass error message through to frontend on login failure

Requires https://github.com/silverstripe/silverstripe-mfa/pull/105

Replaced with #11 that does login & fixes tests.


fix err sio-set-wfp-connection-redirect-records.md

fix error sio-set-wfp-connection-redirect-records.md

@HeMinzhang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[python-package] mark EarlyStopException as part of public API

Doing some research for another contribution, I found that several large projects rely on importing lightgbm.callback.EarlyStopException, and using it to trigger early stopping in LightGBM.

autogluon: https://github.com/autogluon/autogluon/blob/f77a7b4ea2f6140685e73ef41f3b533cea272391/tabular/src/autogluon/tabular/models/lgb/callbacks.py#L8
FLAML: https://github.com/microsoft/FLAML/blob/4886cb56891af6ccf3e6d694bd97f571623fa6f8/flaml/automl/model.py#L1430

This PR proposes formally marking that class (and by extension, that mechanism of triggering early stopping) as a part of the public API, to prevent it from being removed or altered in a non-backward-compatible way in the future.

Thanks @jmoralez !
If you haven't seen it, take a look at those FLAML + autogluon links (and the wandb one in #6096). It was pretty interesting for me to see how other popular projects are using the callback system here to provide supported LightGBM integrations.


[TASK] ARMA agnosticism

Issue Description
Even though the DispatchManager can handle arbitrary ARMAs, there's still issues with the templating system detecting whether to include macro parameters (Year, Cluster, ClusterTime) in the outer-inner files.
This should be enhanceable by interrogating the ARMA files ahead of time to determine what their structure is. For now, it is required to have at least a one-year interpolated ARMA.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

This is directly related to #18, and may even be a duplicate technically.


Deprecate client from Dataset, Workflow, and DatasetInspector

Partially addresses #1249
This PR is intended to improve user experience by removing the need for users to specify a client object when one is already defined in the global python context.
TODO:

[x] Remove client usage from examples and benchmarks

@bschifferer @rnyak - It would be good to get your thoughts (since you are both developers and "power users").
After this change, the user will still be responsible for deploying a dask cluster if/when they want to perform distributed (multi-GPU) ETL.  However, the user will no longer be responsible for specifying client= to any NVTabular API (i.e. Workflow or Dataset). By default, NVTabular will find/use the dask client defined in the global python context. To disable this "automatic-client-detection" behavior, the user can call nvt.utils.set_dask_client(None).
cc @benfred and @albert17 as well :)

I think it will be easier for the user. Does it still work, when the dask_cluster is on another node?
Example:

we have one node, which runs the jupyter server
we have 1-n nodes, which runs the dask-workers

Is NVTabular able to auto-connect in this setup?

Is NVTabular able to auto-connect in this setup?

This PR does not change anything about what kinds of clusters NVT can connect to, or how those cluster should be deployed. If the user wants a multi-node dask cluster with a scheduler on a different node than the jupyter server, they still need to do this with a Dask-based api, and the user will still need to generate a client object on the jupyter server (to connect to the cluster).  The only difference is that the user will no longer need to specify the client when they define a Workflow or Dataset object.

rerun tests

CI failure is in test_export_run_ensemble_triton (added in #1292).  This seems unrelated to the current PR (probably?). cc @jperez999 (in case you have thoughts)

@benfred @karlhigley @jperez999 - Just a note:  No need to get this in for the nearest/current 22.01 release. However, we probably want to get it in soon after that to make sure there is time to find and fix/simplify old code with explicit client passing.


ollama segfaults on coodbooga & nexusraven

running coodboga & nexusraven segfaults and makeing the host unresponsiv.
they load w/o pbls and crash "on the first token".
(zephyr works good)
I tried that with stock ollama 0.1.7, (linux install), docker & selfcompiled (516).

checked the sha256: ok
running them with llama-bench (self compiled), all models pass.

host:
ubu: 22.04
4 x 3070 8GB
i5-7400
log:
Nov 01 13:15:02 utopia kernel: PREDICT[87637]: segfault at 90 ip 000055baddd22987 sp 00007f3d69ff56f0 error 4 in netdata[55baddb76000+474000]
Nov 01 13:15:02 utopia kernel: Code: 19 66 90 4c 89 f7 e8 b8 36 ea ff 48 83 7c 24 68 00 49 89 c4 0f 84 b9 00 00 00 49 8b 9c 24 a0 00 00 00 48 85 db 74 dc 48 8b 03 <8b> 80 90 00 00 00 a8 08 75 cf 48 8b 03 48 8b b8 98 00 00 00 e8 30
Nov 01 13:15:02 utopia kernel: traps: apport[94210] general protection fault ip:55ed725f58e0 sp:7ffe9cf1c7d0 error:0 in python3.10[55ed72523000+2b1000]
Nov 01 13:15:02 utopia kernel: Process 94210(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia systemd[1]: netdata.service: Main process exited, code=killed, status=11/SEGV
Nov 01 13:15:02 utopia dbus-daemon[781]: double free or corruption (!prev)
Nov 01 13:15:02 utopia kernel: x2gocleansessio[971]: segfault at 10 ip 0000563c3b0e2c8c sp 00007ffd36f14ec0 error 4 in perl[563c3b017000+1a0000]
Nov 01 13:15:02 utopia kernel: Code: 78 60 48 8b 70 48 44 8d 6f 01 44 89 68 60 41 83 fd 01 0f 8f 3e 04 00 00 48 8b 56 08 49 63 c5 48 8b 04 c2 48 89 85 20 01 00 00 <48> 8b 40 10 48 89 45 10 84 c9 74 71 4c 8b 00 48 8b 85 b8 00 00 00
Nov 01 13:15:02 utopia systemd[1]: x2goserver.service: Main process exited, code=dumped, status=11/SEGV
Nov 01 13:15:02 utopia systemd[1]: x2goserver.service: Failed with result 'core-dump'.
Nov 01 13:15:02 utopia systemd[1]: x2goserver.service: Consumed 2min 56.062s CPU time.
Nov 01 13:15:02 utopia kernel: apport[94212]: segfault at 158 ip 0000558fdfd3af94 sp 00007ffeadcaf248 error 4 in python3.10[558fdfc6e000+2b1000]
Nov 01 13:15:02 utopia kernel: Code: 89 e7 48 89 2c 24 e8 8b bd fe ff 48 8b 1c 24 e9 37 fe ff ff 48 01 f6 e9 5b f7 ff ff e9 a1 ec f3 ff 0f 1f 44 00 00 f3 0f 1e fa <48> 8b 87 58 01 00 00 48 85 c0 74 5f 48 8b 50 10 48 85 d2 7e 47 41
Nov 01 13:15:02 utopia kernel: Process 94212(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia kernel: apport[94211]: segfault at 0 ip<PHONE_NUMBER>000000 sp 00007ffdf6625168 error 14 in python3.10[558edd361000+6d000]
Nov 01 13:15:02 utopia kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Nov 01 13:15:02 utopia kernel: Process 94211(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia kernel: systemd[1]: segfault at 0 ip 00007ff94d1b0b5e sp 00007ffdbd7d6b68 error 4 in libc.so.6[7ff94d040000+195000]
Nov 01 13:15:02 utopia kernel: Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 89 f8 31 d2 c5 c1 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 <c5> fe 6f 0f c5 f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9
Nov 01 13:15:02 utopia kernel: gdbus[1975]: segfault at 4 ip 00007f0a8837b127 sp 00007f0a86ad0bc0 error 4 in libglib-2.0.so.0.7200.4[7f0a88323000+8f000]
Nov 01 13:15:02 utopia kernel: Code: 48 0f 42 f0 48 8b 05 80 3e 0c 00 31 d2 4c 8b 57 08 48 f7 f6 ba 04 00 00 00 48 89 d1 48 39 d0 48 0f 43 c8 48 8b 05 a1 3e 0c 00 <42> 8b 04 80 89 ca 85 c0 75 5f 49 39 d2 73 72 48 8b 05 1b 2e 0c 00
Nov 01 13:15:02 utopia kernel: unattended-upgr[889]: segfault at 18 ip 00007fe821e6010a sp 00007ffc229dfc80 error 4 in libglib-2.0.so.0.7200.4[7fe821e08000+8f000]
Nov 01 13:15:02 utopia kernel: Code: c5 48 8d 34 9b 49 89 db 4d 89 c1 49 c1 e5 04 48 c1 e6 04 4c 01 ef 49 c1 e3 04 48 39 c6 48 0f 42 f0 48 8b 05 80 3e 0c 00 31 d2 <4c> 8b 57 08 48 f7 f6 ba 04 00 00 00 48 89 d1 48 39 d0 48 0f 43 c8
Nov 01 13:15:02 utopia rtkit-daemon[1140]: Exiting cleanly.
Nov 01 13:15:02 utopia rtkit-daemon[1140]: Demoting known real-time threads.
Nov 01 13:15:02 utopia rtkit-daemon[1140]: Demoted 0 threads.
Nov 01 13:15:02 utopia rtkit-daemon[1140]: Exiting watchdog thread.
Nov 01 13:15:02 utopia rtkit-daemon[1140]: Exiting canary thread.
Nov 01 13:15:02 utopia avahi-daemon[778]: Disconnected from D-Bus, exiting.
Nov 01 13:15:02 utopia avahi-daemon[778]: Got SIGTERM, quitting.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface docker0.IPv4 with address <IP_ADDRESS>.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface zt4mrrjgxa.IPv6 with address fe80::6c84:49ff:fe9f:6f.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface zt4mrrjgxa.IPv4 with address <IP_ADDRESS>.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface br0.IPv6 with address 2003:a:271a:300:804d:2fff:fe3d:c3b1.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface br0.IPv4 with address <IP_ADDRESS>.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1.
Nov 01 13:15:02 utopia avahi-daemon[778]: Leaving mDNS multicast group on interface lo.IPv4 with address <IP_ADDRESS>.
Nov 01 13:15:02 utopia ModemManager[835]: <warn>  could not acquire the 'org.freedesktop.ModemManager1' service name
Nov 01 13:15:02 utopia ModemManager[835]: <info>  ModemManager is shut down
Nov 01 13:15:02 utopia avahi-daemon[778]: avahi-daemon 0.8 exiting.
Nov 01 13:15:02 utopia tracker-miner-fs-3[1381]: OK
Nov 01 13:15:02 utopia tracker-miner-fs-3[1390]: OK
Nov 01 13:15:02 utopia gvfs-mtp-volume-monitor[1630]: **
Nov 01 13:15:02 utopia gvfs-mtp-volume-monitor[1630]: GLib-GObject:ERROR:../../../gobject/gtype.c:2189:type_class_init_Wm: assertion failed: (node->is_classed && node->data && node->data->class.class_size && !node->data->class.class && g_atomic_int_get (&node->data->class.init_state) == UNINITIALIZED)
Nov 01 13:15:02 utopia gvfs-mtp-volume-monitor[1630]: Bail out! GLib-GObject:ERROR:../../../gobject/gtype.c:2189:type_class_init_Wm: assertion failed: (node->is_classed && node->data && node->data->class.class_size && !node->data->class.class && g_atomic_int_get (&node->data->class.init_state) == UNINITIALIZED)
Nov 01 13:15:02 utopia kernel: apport[94218]: segfault at 10 ip 0000561e3ecf2cf3 sp 00007ffe27ddc450 error 4 in python3.10[561e3ebf6000+2b1000]
Nov 01 13:15:02 utopia kernel: Code: 75 5b 48 89 fa 8b 7f 60 48 8b 4a 20 8b 41 28 01 ff 78 4a 48 83 ec 38 48 8b 71 78 4c 8b 15 85 bc 1e 00 c7 44 24 08 ff ff ff ff <48> 8b 4e 10 4c 8d 46 20 48 89 e6 4c 89 14 24 66 49 0f 6e c0 89 44
Nov 01 13:15:02 utopia kernel: Process 94218(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia kernel: apport[94216]: segfault at 30 ip 000055f1eccd8864 sp 00007ffd7a91f610 error 4 in python3.10[55f1ecc1a000+2b1000]
Nov 01 13:15:02 utopia kernel: Code: 00 41 89 94 24 b8 00 00 00 74 08 85 d2 0f 8e 27 03 00 00 48 83 c4 08 5b 5d 41 5c 41 5d c3 0f 1f 84 00 00 00 00 00 48 8b 57 08 <ff> 52 30 48 8b 75 18 48 83 eb 01 0f 83 9b fe ff ff e9 af fe ff ff
Nov 01 13:15:02 utopia kernel: Process 94216(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia systemd[1]: Caught <SEGV>, dumped core as pid 94213.
Nov 01 13:15:02 utopia systemd[1]: Freezing execution.
Nov 01 13:15:02 utopia kernel: Process 94215(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia systemd[912]: gvfs-mtp-volume-monitor.service: Main process exited, code=killed, status=6/ABRT
Nov 01 13:15:02 utopia systemd[912]: gvfs-mtp-volume-monitor.service: Failed with result 'signal'.
Nov 01 13:15:02 utopia kernel: Process 94220(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia kernel: Process 94221(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia systemd[910]: tracker-miner-fs-3.service: Main process exited, code=killed, status=11/SEGV
Nov 01 13:15:02 utopia systemd[910]: tracker-miner-fs-3.service: Failed with result 'signal'.
Nov 01 13:15:02 utopia systemd[910]: gvfs-mtp-volume-monitor.service: Main process exited, code=killed, status=11/SEGV
Nov 01 13:15:02 utopia systemd[910]: gvfs-mtp-volume-monitor.service: Failed with result 'signal'.
Nov 01 13:15:02 utopia kernel: Process 94237(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:02 utopia systemd[910]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 1.
Nov 01 13:15:02 utopia systemd[910]: Stopped Tracker file system data miner.
Nov 01 13:15:02 utopia systemd[910]: Starting Tracker file system data miner...
Nov 01 13:15:02 utopia tracker-miner-f[94248]: Corrupt database: sqlite integrity check returned '*** in database main ***
                                               Page 190: btreeInitPage() returns error code 11'
Nov 01 13:15:02 utopia tracker-miner-f[94248]: Could not create store/endpoint: Corrupt db file
Nov 01 13:15:02 utopia systemd[910]: tracker-miner-fs-3.service: Main process exited, code=exited, status=1/FAILURE
Nov 01 13:15:02 utopia systemd[910]: tracker-miner-fs-3.service: Failed with result 'exit-code'.
Nov 01 13:15:02 utopia systemd[910]: Failed to start Tracker file system data miner.
Nov 01 13:15:02 utopia systemd[910]: realloc(): invalid pointer
Nov 01 13:15:02 utopia kernel: Process 94253(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:02 utopia kernel: Aborting core
Nov 01 13:15:03 utopia systemd[920]: pam_unix(systemd-user:session): session closed for user pinokio
Nov 01 13:15:04 utopia kernel: Process 94267(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:04 utopia kernel: Aborting core
Nov 01 13:15:04 utopia kernel: Process 94296(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:04 utopia kernel: Aborting core
Nov 01 13:15:06 utopia kernel: Process 94336(apport) has RLIMIT_CORE set to 1
Nov 01 13:15:06 utopia kernel: Aborting core
Nov 01 13:15:07 utopia kernel: show_signal: 16 callbacks suppressed
Nov 01 13:15:07 utopia kernel: traps: python3[94361] general protection fault ip:53c600 sp:7ffc9b7591e0 error:0 in python3.11[41f000+233000]
Nov 01 13:15:10 utopia kernel: traps: python[94412] general protection fault ip:53529d sp:7ffea2782780 error:0 in python3.11[41f000+233000]

there seems to be a little progress.
just tested it with nexusraven on  0.1.10 (docker) and it does not crash the machine any longer.
but it's still producing garbage output, like in 961
ollama run nexusraven
>>> why is the sky black?
ROUP###########################################################^C

@mchiang0610 @jmorganca any news on that?
ollama is still completly unusabe on multi-GPU for me.

@chymian would you be able to retest with the latest (0.1.20) ollama? There's been significant improvements to model running including for multi-GPU.
$ ollama run nexusraven
why is the sky black?

I'm not sure if this question makes any sense at all, but it made me think: "Why is the sky black?"
The reason for this question is because the sun has set and it is dark outside. This means that the light from the sun has disappeared and there are no stars in the sky to illuminate it. The only thing left in the sky is a very dark blackness, which makes it look like nighttime.
But the real reason why the sky looks black at night is because of the scattering effect of the atmosphere. When light from the sun passes through the air, it is scattered by the tiny particles that make up the air (such as water vapor and dust). This scattering causes the light to be broken up into different colors, which can then be seen in the sky at night. The blue and green lights are scattered more than the red and violet lights, so this is why we see a lot of blue and green in the night sky.
The reason why the sky looks black at night is because it is dark outside, but it is also because the light from the sun has been broken up by the atmosphere into different colors, which can be seen in the sky.

nexusraven is best suited for function calling. Here's an example using the example from their huggingface repo:
$ cat <<EOF >Modelfile
FROM nexusraven
PARAMETER temperature 0.001
TEMPLATE """{{ .System }}

User Query: {{ .Prompt }}<human_end>
"""
SYSTEM """Function:
def get_weather_data(coordinates):
    '''
    Fetches weather data from the Open-Meteo API for the given latitude and longitude.

    Args:
    coordinates (tuple): The latitude of the location.

    Returns:
    float: The current temperature in the coordinates you've asked for
    '''

Function:
def get_coordinates_from_city(city_name):
    '''
    Fetches the latitude and longitude of a given city name using the Maps.co Geocoding API.

    Args:
    city_name (str): The name of the city.

    Returns:
    tuple: The latitude and longitude of the city.
    '''"""
EOF
$ ollama create weatherman
$ ollama run weatherman "What's the weather like in Seattle right now?"

Call: get_weather_data(coordinates=get_coordinates_from_city(city_name='Seattle'))
Thought: The function call `get_weather_data(coordinates=get_coordinates_from_city(city_name='Seattle'))` answers the question "What's the weather like in Seattle right now?" because it performs the following steps:

1. It calls the `get_coordinates_from_city` function with the argument `'Seattle'` to get the latitude and longitude of the city.
2. It then calls the `get_weather_data` function with the coordinates as an argument to get the current weather data for that location.
3. The `get_weather_data` function uses the Open-Meteo API to fetch the weather data for the given coordinates, and returns it in a JSON format.
4. The returned JSON data contains the current temperature, humidity, wind speed, etc. for the specified location.

Therefore, by calling `get_weather_data` with the coordinates of Seattle as an argument, we can get the current weather data for that city.

This output is very close to the example output from huggingface

@mxyng , I had some time to do a resetup of my GPU-RIG to give ollama  2 x 3070 (8G).
it loads the half of the  LLM's layer to the first GPU, rest to CPU.
it does not crash but is extremly slow.
trying to unload more layers with num_gpu -paramter (which in every other LLM-SW stands for amout of GPUS, not layers)
ollama (docker) crashes, when filled up the VRAM of the 1. GPU.
haven't found any parameters for loading a model to a distinct, or a group of distinct GPUs.
so, no its not working, even so the error changed.

@chymian it sounds like the original issue of crashing has been resolved on newer versions.  If I understand correctly, you're now facing challenges with multiple GPUs and how memory is loaded across them.  Can you upgrade to the latest version and share your server log, along with nvidia-smi output showing the skew so we can try to get a better understanding on what's going on?  Setting OLLAMA_DEBUG=1 for the server may be helpful to get more verbose logging.

Our approach to multi-GPU will change once PR #3418 merges, so I would recommend trying it out once that's available in a release.

Now that 0.1.33 is shipped with concurrency support, I'm going to close this one out.  If you're still having problems with the new scheduler logic in the latest release, please share an updated server log and I'll re-open.


Not on ansible galaxy

Hi There,
I see that you have a meta file for ansible galaxy but I don't seem to be able to find this package on there.
Is this intended?

It is in Galaxy https://galaxy.ansible.com/list#/roles/912


Feature/classification strategy

Coverage decreased (-1.1%) to 97.792% when pulling e272316d2ba1686acf374883e55904def7c4c053 on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.

Coverage decreased (-1.1%) to 97.792% when pulling e272316d2ba1686acf374883e55904def7c4c053 on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.

Coverage decreased (-1.1%) to 97.792% when pulling a9b84a73c51922302dc20ade26cbb95ec244a90a on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.

Coverage decreased (-0.2%) to 98.738% when pulling 9e19cc936bd7348a88deb06dd1932b6d5c0f449c on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.

Coverage decreased (-0.2%) to 98.738% when pulling 81261c6c174e94c28a9b767a7e73da4f05178ae2 on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.

Coverage decreased (-0.2%) to 98.738% when pulling 6d848885a86e332196d0178c80f0b9f24fdb747f on feature/classification-strategy into 13e7ae850048b6dbcfb260b9755bf1b0b91ab3b9 on master.


Logging - make sure each entry has a timestamp

this is the case

Dec  9 06:30:05 devsrv2 fworch-ui[1079]: Audit - AuthenticateUser (Login.razor in line 146): user admin successfully authenticated

@abarz722 could you check and find an example for a log entry without timestamp?


Let argpartition use the kth argument properly

Fixes #3287
Fixes #6812
argpartition now uses an indirect-sort version of the partition kernel

Does this implementation work with arrays whose ndim > 1?

Does this implementation work with arrays whose ndim > 1?

No, indeed, the returned indices need to be normalized w.r.t their axis and reshaped

Thanks for applying the edit! Would you also add a variation of the test below so that the code path you've added is covered by CI?
https://github.com/cupy/cupy/blob/704f87e927998f31534ab76b5d831f967114a84c/tests/cupy_tests/sorting_tests/test_sort.py#L641

/test mini

The errors on the CI are related to NCCL, not to the changes of this PR

Sorry for being less responsible. I'll get back next monday as I have days off this week.

No worries! Please have a nice holiday time!

Looks good to me. I'll mark this PR accepted then kick CI after accept_error removed https://github.com/cupy/cupy/pull/6921#discussion_r950990444

Also I checked test_argpartition_multi_dim_kernel to go through the path introduced here.

/test mini

/test mini

Would you merge this too, @kmaehashi?

Thanks, @andfoy!


Creation-service-list

The ALA microservice acts as a proxy between the MWDeviceInventory and the external tool APT (in which the acceptance logic is implemented).
The individual service /v1/provide-acceptance-data-of-link-endpoint was added. This provides the relevant data for MW-Acceptance to the tool APT.
Seven client services, which retrieve the relevant acceptance data from the MWDeviceInventory, were added.

Hi Katharina,
I corrected the uuids again. I assigned a unique uuid to each client service, even if these sometimes refer to the same service of the MWDI, just with different query parameters. For example:

          - operation-name: /node={mount-name}/yang-ext:mount/core-model-1-4:control-construct?fields=logical-termination-point(uuid;name;layer-protocol(local-id;layer-protocol-name))
            uuid: alap-1-0-0-op-c-is-mwdi-1-0-0-000

      - operation-name: /node={mount-name}/yang-ext:mount/core-model-1-4:control-construct?fields=top-level-equipment
        uuid: alap-1-0-0-op-c-is-mwdi-1-0-0-004

I hope this is correct.


Add ideas from LBNL. Bin.

Hi, @carlosmalt,
It looks like my committed files have some format issues, but I don't know where it is.
I had tried twice.
Could you help to have a quick look?
I used the latest template file now.
https://raw.githubusercontent.com/ucsc-ospo/ucsc-ospo.github.io/main/content/project/osre22/ucsc/polyphorm/index.md
Thanks.
Bin

Thanks @BinDong314 -- See my change requests. Then it will build and I can merge.

Here is a patch.

Thanks @carlosmalt.
It looks like all checks have passed now.