[Firebase] Notification doesn't work when App is in foreground

Hey David,
I'm on Delphi 10.4.2:
with Kastri, everthing works fine on iOS, but on Android, I cannot get the Kastri demo app to receive the messages for push notifications, beep or sound alert a notification at the top when it receives a new notification unless I close it or put it in the background.  but I'm still not seeing the payload either way.
I read your article:
https://delphiworlds.com/2020/01/expanding-embarcaderos-fcm-implementation-revisited/#comment-10092
I also found
https://firebase.google.com/docs/cloud-messaging/android/client#manifest
In which they want
<service     android:name=".java.MyFirebaseMessagingService"     android:exported="false">     <intent-filter>         <action android:name="com.google.firebase.MESSAGING_EVENT" />     </intent-filter> </service>
added to the AndroidManifest.xml file.
That doesn't seem to work either.
Is there something wrong with the Kastri Messaging Demo Application or some settings I may have missed?
Thank you in advance.

There's an apparent problem with EMBT's implementation, as you've discovered. You might like to try with this demo instead.

In EMBT's implementation, if the app is in the foreground, it does not present a notification, however the payload is received. Is that what you mean, or are you not receiving the payload, either?

Thanks for the quick reponse.  I was using you "Firebase Cloud Messaging (FCM) Demo".  It will register the app and topics just fine for the notifcations when its in the background or off, but I don't seem to be getting the "FCMMessageReceivedHandler" to work correctly

Also what is your $(Firebase) setting in your envornment options?

Regarding Android: In the Kastri FCM implementation, you need to send a "data" type message, as per the instructions here.
Regarding iOS: If the demo uses $(Firebase) in the paths, then it will need to be set as a a User Override in the Environment Variables section of the IDE options. It should point to the root of Firebase iOS SDK 6.18. There is a "cut down" version of the SDK here.

Thank you for the response:
IOS: I cloned your FCMDemo.dproj file settings and I used the SDK you recommend.  After removing the CFBundleResourceSpecification from the .dproj file from this suggestion It will compile and run.  but now I get this error:
Debugger Exception Notification
Project AlertNotificationExample raised exception class EObjectiveC with message 'ObjectiveC class FIRMessaging could not be found'.
Break   Continue   Help

iOS: I've about got a new application working but i get "no valid ""aps-environment"" entitlement string found for application" from the FCMFailedToRegister for my app.  the demo app works find and is granted.
Any thoughts on where that setting is in Delphi (i've been looking for at least a hour)

If you have a "no valid ""aps-environment"" entitlement" error, you're likely using a provisioning profile that does not have an App ID with Push Notification entitlements. Please refer to the information here: https://github.com/DelphiWorlds/Kastri/tree/master/Demos/FirebaseCloudMessaging#apple-developer-portal-ios

I have two projects.  sharing the bundle identifer so I know it works on the apple side.  One I'm creating from scratch, the other  is the Kastri FCMDemo.dproj.   The FCMDemo.dproj with my own bundle identifier will work without generating the aps-environment error.  but My file new project generates that error.  I found the aps_development.cer file but I can't seem to figure out how to integrate it in Delphi. I just feel like theres a delployment option, a .pem .p12 .plist option strings.xml setting that I'm not seeing in the documentation you've provided.  Any other thoughts?

Android: I keep getting Granted: -1.  What a other tools do I have in the Kastri FCM Library to findout more about this kind of issue?

Can you clarify what you mean by "Granted: -1"?

Ok.  everything is working except the android foreground thing (my original issue).  I read through one of the links you sent me about sending "data" in the message to get the foreground app to receive the message, but what that documentation was missing was a code example of a JSON payload that should work.  I've tried guessing a couple of different ways with no success. It would help me if I could see a working json payload sample you know works (minus personal info of course).  Could you post one here update your docs and send me that link please?   Thank you in advance.

Can you let me know whether this is still an issue?

Closed due to no response


Resolve discontinuities when seeking into fragmented AC-4 audio

Related to google/ExoPlayer#11000
Proof of concept for resolving discontinuities in FMP4 AC-4 playback.
The underlying cause on our end appears to come from the fact that we can't anticipate sync frames when committing them to our sample queue. Once we reach the end of our first fragment, we begin committing samples to our sample queue, even if suitable sync frames are available in later fragments.
For this PR, we would have some sort of intermediate structure to retain samples before committing them, in the event that our format does not guarantee that every frame is a key frame. When we encounter a key frame, we empty the contents of this structure, as we can begin playback from that key frame instead. When we pass our start time, we commit any samples in the intermediate structure to our sample queue, allowing us to play from the nearest key frame.

Please can you sign the CLA, then we can take a look at this.


fix #3246

Coverage: 92.923% (+0.002%) from 92.921% when pulling 80a0326084ea07dc0cef761e96f14c27a96521ac on antgonza:fix-3246 into 6684ad0e2375e58450b05790d93456c0ad3d78e6 on qiita-spots:dev.


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2974

Questions ?
Please refer to the Backport tool documentation


tests: latency_measure: disable pm for mec15xxevb_assy6853

Disable power management for board mec15xxevb_assy6853 for
latency_measure test. This prevents the SoC from sleeping
which may skew the results. Also this prevents stopping
mid-test due to SoC being in sleep state, and there are no
external interrupts to wake up the SoC.
Fixes #24136
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

we probably should disable power management for everyone, not only this board.

we probably should disable power management for everyone, not only this board.

Updated to disable PM for all.


Add Blacklist for deprecations

If your project uses a deprecation heavily your whole output is full of it.
We should add a configuration to blacklist some deprecations.

It might also be useful to be able to exclude certain files or directories.

i agree on excluding certain files or directories, but i'm not sure about a deprecation blacklist.
I don't like the idea of extensive option usage like #17 provides as solution. maybe a blacklist by config file?
a config file would make it easy to exclude files and directories as well.

The implementation in #17 provides an option to implement a file/folder exclude as well. How you define the filter options can be decided for every filter separately. I think, the option to exclude certain calls is suited for being configured on the command line, but I am open for discussion on that matter.
The reason I think this is a good option is that the normal use case will probably be:

run the checker
see excessive use of one specific, deprecated method call
filter that call out on a consecutive run to get a better overview of the remaining problems

Adding such filter to a config file wouldn't be a convenient way to go, and moreover would probably encourage ignoring certain errors by default and forgetting about it.

after #17 we still need the implementation for other violations. May we should also add an output if a specific deprecation is filtered.

Adding active filters to the output is a good idea.

@bestform do you want to add the missing filters ?

@MarvinKlemp what do you mean exactly? The filters itself (if so: is there a list of missing filters?) or the information about active filters in the output?

if you want both :laughing:
But IMO we should wait until #45 is merged


Suppress iPad native keyboard

Is it possible to add functionality to suppress the native keyboard when viewing and HTML5 site that uses angular-virtual-keyboard for its text fields and areas?

It is not supported today by the directive. What you can do is the opposite solution, you could suppress the directive keyboard in the ipad, so the user will use only the native keyboard on the iPad. To do it use the showInMobile configuration (in readme: directive configurations). You will need to import the dependency angular-useragent-parser (in readme: dependencies)

Thanks @the-darc but the iPad's in question have scanners hooked up to them and those scanners act as keyboard input and hijack the iPad keyboard such that it doesn't show up on the first try.
That is why we wanted to use the virtual keyboard but we also want to make sure that once the virtual keyboard is in the picture, the native one doesn't shop up at all, at least not because the user went to the second or third input box or tried to edit their input multiple times within the same textarea by moving the cursor around via touch.
So we are actually searching for a shutout solution that stops whatever event would flow up from editable html components to the iPad.

Thank you for sharing. We are working on HTML5 cordova hybrid app.  We have integrated your directive(angular-virtual-keyboard) in our app. When bar code scanner connects to the iPhone or Android then phone native soft keyboard will disappear automatically which is good for us. But we want your keyboard should appear. For some reason, neither keyboard will show up. Can you please help regarding this.
Ex: 1)  If I browse your demo from my phone with bluetooth scanner connected.
Ex: 2) Angular-virtual-keyboard will not show up even bar code scanner is disconnected.


feat: miscellaneous results about finrank

From flt-regular.

I also fixed a couple of names.

bors r-


project creation problem

Hi,
Firstly, many thanks for releasing this project. It's impressive.
I try to configure the project using docker-compose on ubuntu.
I follow keycloak instructions. I got an error when I try to create a new project from the vindr frontend.
I think I miss something, like a keycloak permission configuration. (error logs attached)
Do you have any hints ? Thank you

Hi @guigautier, please send me your token and go to Clients/vinlab-backend, then go to tab Authorization, sub-tab Permissions and capture the UI for me.

This is the url that I try to reach : http://localhost:8080/dashboard/study-list/1b8fe726-a969-47da-8152-673c754902f1?tab=setting
In console I got this 2 forbidden request  :
http://localhost:8080/api/stats/projects_by_role?_offset=0&_limit=25&role=PROJECT_OWNER
http://localhost:8080/api/projects/1b8fe726-a969-47da-8152-673c754902f1
This is my Permissions UI  :

Thanks

Sorry for the delay, please send me the token you are using.

I've updated the installation docs, please follow this! Thanks!

I read the reply from Gitter channel, no more comments. I will close this!


gRPC Python Library incompatibility with future.ProcessPoolExecutor

What version of gRPC and what language are you using?
grpc 1.9.1 , python 3.6.0
What operating system (Linux, Windows, …) and version?
under docker with phusion/baseimage , also tried on debian jessie and Kali Linux
What runtime / compiler are you using (e.g. python version or version of gcc)
python 3.6.0
What did you do?
The issue is really similar to : https://github.com/grpc/grpc/issues/13873 also maybe with https://github.com/grpc/grpc/issues/12455 . This as well: https://github.com/grpc/grpc/issues/13536
What did you expect to see?
normal server response
What did you see instead?
Got the error: E0215 12:45:01.090952877      35 tcp_server_posiix.cc:228]    Failed accept4: Invalid argument in the logs while the server hangs and is made unavailable for future requests.
How to reproduce
easiest way of reproducing, which might help the other 2 issues referenced above as well, is to change this line:
https://github.com/grpc/grpc/blob/master/examples/python/route_guide/route_guide_server.py#L115
to server = grpc.server(futures.ProcessPoolExecutor(max_workers=10))
In order to get the logs I am attached an interceptor using opencensus, like this :
from opencensus.trace.samplers import always_on
from opencensus.trace.ext.grpc import server_interceptor
from opencensus.trace.exporters import print_exporter
from opencensus.trace.exporters.transports import background_thread

        sampler = always_on.AlwaysOnSampler()
        exporter = print_exporter.PrintExporter(transport=background_thread.BackgroundThreadTransport)
        tracer_interceptor = server_interceptor.OpenCensusServerInterceptor(sampler, exporter)
        server = grpc.server(
            futures.ProcessPoolExecutor(max_workers=self.max_workers),
            interceptors=(tracer_interceptor,)
        )

Anything else we should know about your project / environment?
At the moment I am considering dabeaz/curio or an asyncio alternative as temporary alternatives.
Also read the answers here https://stackoverflow.com/questions/38387443/how-to-implement-a-async-grpc-python-server , which unfortunately do not help a lot in moving the server from being thread based to a process based execution.
The need of using processes instead of threads in my architecture comes from looking to put better practices at work as well as I was looking that this piece of work can replace Gearman for me which was running in different processes. I agree there are alternative solutions, but solving this would be so much cleaner.

ProcessPoolExecutor uses fork() under the hood, which isn't generally supported.  We would like to support this case, so I'll leave this open as a feature request.

since I filled this issue I have come to believe that http://grpclib.readthedocs.io/en/latest/ might be a solution for me as it achieves the same purpose but through another mechanism, the asyncio library.

Do you know when you planning to add support for futures.ProcessPoolExecutor for gRPC python server?
The python limitation related to GIL (global interpreter lock) is always the issue. Before I started use gRPC server I have good experience with gunicorn where it was possible to start the server with multiprocessing workers https://gunicorn.org/

@rafalkasa, there is no immediate plan to support fork on the server side. This is low priority for us. The first step here would be to support pre-forking (possibly revive https://github.com/grpc/grpc/issues/13536).

Could someone explain the motivation for wanting to support ProcessPoolExecutor? Would that allow a grpc server to support more cpu heavy tasks since each request would get its own Python process? What's wrong with ThreadPoolExecutor?

@mattdornfeld, what you said is right. Concurrency with threads is limited by GIL in a given python process. For CPU intensive tasks, this won't scale with number of cores. Hence ProcessPoolExecutor is needed.

In the past, I worked on the project where the tasks run on threads limited by GIL making the whole process working slower and slower based on the number of threads that we start. The solution was resolved when we switch from ThreadPoolExecutor to ProcessPoolExecutor. As I remember it was better to not use threads and have one process instead of using python Threads. You can read more about GIL here https://www.dabeaz.com/python/UnderstandingGIL.pdf
So maybe this is not your the most important topic, but please to understand that this change will have a significant impact on services run with workers build based gRPC in Python.
We will resolve the multiprocessing run multiple instances of gRPC servers on Docker containers, but I would like to have the possibility to use in the future ProcessPoolExecutor. Thank you for your answers.

https://github.com/grpc/grpc/issues/16001 has a couple of suggestions to work around this limitation. It is not an ideal solution as it doesn't scale dynamically (you need to pre-allocate set number of processes) but something to consider if thread pool is not working for you.

Could someone explain the motivation for wanting to support ProcessPoolExecutor? Would that allow a grpc server to support more cpu heavy tasks since each request would get its own Python process? What's wrong with ThreadPoolExecutor?

simple most common problem that I have, you can't start a ProcessPool inside a ThreadPool (ProcessPoolExecutor throws an exception). While you can always do it the other way around.
@rafalkasa has given quite a good explanation for why you would want it as well.
Latest versions of python are walking away from threads or that is my impression due to numerous Syncronizations and tweaks Threads would entice, while processes due to the fact of not having a shared state are simpler to manage.


SyntaxError on valid Javascript: SyntaxError: Unexpected token ',' or missing ) after for-loop control

What is your Test Scenario?

HTML file that includes the following script:
new Promise(() => {
  var s = [1];
  for (var i of (console.log(s), s)) {
  }
  for (var a of s) {
    var d = 'hello';
    this[d];
  }
});

What is the Current behavior?

TestCafe fails with JS errors:

Browser: Firefox 78.0 / Linux 0.0:
JavaScript error details:
missing ) after for-loop control

Browser: Chrome 83.0.4103.116 / Linux 0.0
JavaScript error details:
SyntaxError: Unexpected token ','

What is the Expected behavior?

Valid JS should not fail TestCafe
What is your web application and your TestCafe test code?

      Repeat test actions in the browser and check the console for errors.
      If you see this error, it means that the tested website caused it. You can fix it or disable
      tracking JavaScript errors in TestCafe. To do the latter, enable the "--skip-js-errors" option.
      If this error does not occur, please write a new issue at:
      "https://github.com/DevExpress/testcafe/issues/new?template=bug-report.md".

      JavaScript error details:
      SyntaxError: Unexpected token ','

      Browser: Chrome 83.0.4103.116 / Linux 0.0

   2) A JavaScript error occurred on "http://localhost:7777/index-with-poison.html".
      Repeat test actions in the browser and check the console for errors.
      If you see this error, it means that the tested website caused it. You can fix it or disable
      tracking JavaScript errors in TestCafe. To do the latter, enable the "--skip-js-errors" option.
      If this error does not occur, please write a new issue at:
      "https://github.com/DevExpress/testcafe/issues/new?template=bug-report.md".

      JavaScript error details:
      missing ) after for-loop control
          No stack trace available

      Browser: Firefox 78.0 / Linux 0.0

 1/2 failed (1s)

Steps to Reproduce:

Clone https://github.com/AndersCan/testcafe-bug
npm i
npm run start
npm run test
See the error

Your Environment details:

testcafe version: 1.9.1
node.js version: v12.16.1
command-line arguments: npx testcafe all test.js
browser name and version: Firefox 78.0, Chrome 83.0.4103.116
platform and version: Linux Pop!_OS 20.04 LTS (basically Ubuntu 20.04)

@AndersCan, Thank you for your report. I've reproduced this issue using the repository you shared. We'll need time to investigate this issue. In the meantime, you can run TestCafe with --skip-js-errors to disable these errors.

The problem isn't reproducible with the latest TestCafe release (v1.14.2 for now), so I am closing the issue. Fixed in https://github.com/DevExpress/testcafe-hammerhead/pull/2575.


Fix .cshml compilation issue with VB project

I tried few days back to create an ASP.NET Core app using VB.NET, everything (models, controller .. etc) is working fine except the compilation and rendering the views, while vbhtml is not support yet, is there  a workaround to make the cshtml compiling without an issues
I don't wanna use another view engine - which will work fine - because I really like Razor
/cc @NTaylorMullen

is working fine except the compilation and rendering the views

What happens when you attempt to render a cshtml view?

FYI I tried to set the PreserveCompilationContext to true with no luck 😞

@ajaybhargavb can you take a look at this and see what's going on?

@hishamco, could you share a sample repro project?

Any updates on this?

I'd also love to see Razor come to ASPNET Core with VB.NET even if it it is the cshtml syntax!


[Major] onChange and onBlur undefined error parameter in Textarea

Closes #887

The easiest way is to do it like the example _"Handling errors"_ from the Radio Group. It would be like this (Pattern example):

What do you think of this way? I think it is easier:

The easiest way is to do it like the example _"Handling errors"_ from the Radio Group. It would be like this (Pattern example):

What do you think of this way? I think it is easier:

It was done like that to show the user how to manage the undefined/null value in only one place. Imagine if the use case is to treat pattern error at the onChange and the length error at the onBlur. If we do it like you've done the undefined/null value should be managed in each method, while with the other approach, it's only a few more characters when you pass the prop!
For further knowledge, I didn't use the nullish coalescing operator (??) since our code example environment doesn't support the latest version of javascript.


[REQUEST]: Composition of Utility Types

You guys have added a ton of useful utilty types and I look forward to many more!  They really do make the experience stronger.  I have been able to accomplish some awesome things with them and they really make the entire program semantic and easy to read.
That being said, I now find myself composing types from other types quite a bit.  In that sense I also find that it gets a bit ugly:
type StrictMessage = $ReadOnly<$Exact<$NonMaybeType<$Rest<IPC$Message, {| f: string |}>>>;

Obviously I could clean it up a bit with:
type WithoutFrom = $Rest<IPC$Message, {| f: string |}>;
type StrictMessage = $ReadOnly<$Exact<$NonMaybeType<WithoutFrom>>>;

However it would be nice to be able to compose them to make this easier to deal with.  I would imagine it would only really work with single element polymorphic types:
type WithoutFrom = $Rest<IPC$Message, {| f: string |}>;
type StrictMessage = $TypeAs<ReadOnly, Exact, NonMaybeType, WithoutFrom>

Just an idea to clear out the clutter of < | > that are starting to show.

So I just started some utility functions that are declared in a libdef.  This does make it a bit cleaner at least but a $TypeAs would still be cool to have if it's not difficult to implement!
type AsNonMaybeObject = <O>(O) => $ObjMap<O, <T>(T) => $NonMaybeType<T>>;
type AsStrictObject = <O>(O) => $ReadOnly<$Exact<$NonMaybeObject<O>>>;

declare type $NonMaybeObject<O> = $Call<AsNonMaybeObject, O>;
declare type $StrictObject<O> = $Call<AsStrictObject, O>;


[TASK] Performance and scalability report for Longhorn

What's the task? Please describe.
Need to update the performance and scalability report.
Describe the items of the task (DoD, definition of done) you'd like.

[ ] Performance of raw block device
[ ] Performance of fs on top of raw block devices (ext4 and xfs)
[ ] Performance of encrypted volume (might depends on the fs)
[ ] Performance of RWX
[ ] Scalability report.

Additional context

For performance, we can use https://github.com/yasker/kbench
For OS, let's stick with RKE2 + openSUSE.

A bonus might be to benchmark with and without the revision counter enabled as well.
https://longhorn.io/docs/1.2.0/advanced-resources/deploy/revision_counter/

Update (in-progress)
Native
1. Raw block device
=====================
FIO Benchmark Summary
For: /root/fio-results/native/raw-block-v2
SIZE: 50g
QUICK MODE: DISABLED
=====================
IOPS (Read/Write)
        Random:          80,060 / 37,036
    Sequential:          80,063 / 37,065
  CPU Idleness:                      87%

Bandwidth in KiB/sec (Read/Write)
        Random:        362,551 / 167,116
    Sequential:        362,548 / 167,084
  CPU Idleness:                      96%

Latency in ns (Read/Write)
        Random:         54,049 / 107,172
    Sequential:         93,820 / 107,398
  CPU Idleness:                      89%

1. ext4
1. xfs

Scalability tests (in-progress)

Scalability tests (in-progress)
Test evn:
* Kubernetes: RKE1 v1.18.20; 3 master nodes; 100 worker nodes
* Longhorn: v1.2.0

* OS: Ubuntu 18.04
* EC2 `m5.2xlarge` instance: 8 vCPUs 32 GB Memory

Longhorn installation time

Workloads with Longhorn volumes deploying time
pending

We will move this to the next patch 1.2.4 instead until figuring out the scaling test results.

This ticket is handled at https://github.com/longhorn/longhorn/issues/2598


question: is it possible to return array of nodes from render()

As title says. Is it possible to return array of nodes from render(). I'm building my own system of components, and my renderer can handle the case when several nodes are returned from render() method. So the question is, if skatejs would be fine with this behavior?

Yes, there is no restriction on what you can return, so long as your renderer can handle it.

thank you @treshugart


Bolster CI Actions

This change brings some extra functionality into the CI process. Using Github Actions, we should be able to

Run lint checks on change-sets
Audit dependencies
Runs the formatting tool

…on pull requests.
p.s: I've kept this away from pushes on the invariant that the development process here receives all contributions to the main branch through some pull request of some sort.
Fixes subconsciousnetwork/noosphere#94

@igbanam I'm not totally sure if this is the issue, but I think you need to set the working directory for some of these steps because our code in this project is one level deep in a rust sub-directory (example from our other workflow: https://github.com/subconsciousnetwork/noosphere/blob/f6956d5673659479b1ce630923f25e68c8d3d48d/.github/workflows/run_test_suite.yaml#L26).

@cdata I made the updates to the relevant checks. Checks are green now.

@igbanam I'm not seeing the check for the new workflow you added - I think it might have a typo in it somewhere (just referring to the message here: https://github.com/subconsciousnetwork/noosphere/actions/runs/3285863349). Are you seeing the workflow run for you?

I just realized it's failing early for me too.
Root Cause: The working-directory key only works for runs. actions-rs/cargo currently does not support changing working directory — but that issue is laden with forks with potential solutions. I'd have to go through these forks and select one which works for this use case. Worst case scenario, I'll add it myself.

Oh… we have lift-off :rocket:
The linters are catching errors now.
I'll fix the linter errors as part of this PR

I'm gonna pause here for your input, @cdata.
I trust the Rust tooling and all… but this is making more changes to your code than I am comfortable with. I'm checking that existing tests don't break per change; and we are green so far. But please have a look through and let me know if you're comfortable with my going on with this.
p.s: take a look at the current checker failures as well to know the nature of possible future changes.

Chose not to deny warnings because my rust-fu couldn't handle the refactor being asked.
╭─   ~/p/i/noosphere/rust on   chore/bolster-ci-actions ⇡2
╰─❯ cargo +stable clippy --all -- -D warnings                                                     ─╯
    Checking noosphere-cbor v0.1.0 (/Users/igbanam/projects/igbanam/noosphere/rust/noosphere-cbor)
    Checking noosphere-storage v0.1.0 (/Users/igbanam/projects/igbanam/noosphere/rust/noosphere-storage)
    Checking noosphere-collections v0.1.0 (/Users/igbanam/projects/igbanam/noosphere/rust/noosphere-collections)
error: module has the same name as its containing module
 --> noosphere-collections/src/hamt/mod.rs:7:1
  |
7 | mod hamt;
  | ^^^^^^^^^
  |
  = note: `-D clippy::module-inception` implied by `-D warnings`
  = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#module_inception

error: very complex type used. Consider factoring parts into `type` definitions
   --> noosphere-collections/src/hamt/hamt.rs:371:36
    |
371 |     pub fn stream<'a>(&'a self) -> Pin<Box<dyn Stream<Item = Result<(&'a K, &'a V)>> + 'a>> {
    |                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `-D clippy::type-complexity` implied by `-D warnings`
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity

error: very complex type used. Consider factoring parts into `type` definitions
   --> noosphere-collections/src/hamt/node.rs:156:10
    |
156 |     ) -> Pin<Box<dyn Stream<Item = Result<(&'a K, &'a V)>> + 'a>>
    |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity

error: could not compile `noosphere-collections` due to 3 previous errors

I tried refactoring the complext type with what I read up on the interwebs, but I got met with https://github.com/rust-lang/rust/issues/8995 which — after reading through — seems it's almost addressed, but not yet.

If we truly want to keep the high Rust bar, we can tune this up later.

@igbanam as part of #107 we ran cargo clippy --fix and cleared up all the warnings. I would recommend rebasing your change without the warning fixes, just the new workflow, and see how it goes!

Thanks for putting in the work on this change. Since it's getting stale, I'm going to close out the PR for now, but if you feel inspired to pick it up again we will re-open it right away.


Chrome Dev Tools -  First Exercise

Great! 👍  I love the HTML, i think the instructions could use some improvements in clarity.

👍  Can i merge?

Sure 👍


create root.crt and personal.crt, but chrome still ERR_CERT_COMMON_NAME_INVALID

I have  c# client lisetner to  Javascript via wss (site required client digital certificate + https).
I try create "<IP_ADDRESS>"  cert and use the for the client.
while check via browser to https://<IP_ADDRESS>:8181  on chrome consist they are not trusted.
boot on win7 + win10, both on Machine store and on CurrentUser store
#create the root
set OPENSSL_CONF=openssl2.cnf
openssl genrsa -out ca.key 2048
openssl req -new -x509 -sha256 -days 3000   -key ca.key -out ca.crt  -nodes -subj "/C=US/ST=Oregon/L=Portland/O=Company Name/OU=Org/CN=<IP_ADDRESS>ca"
#create the personal
openssl genrsa -out ia.key 2048
openssl  req -new     -sha256 -key ia.key -out ia.csr -subj "/C=US/ST=Oregon/L=Portland/O=Company Name/OU=Org/CN=<IP_ADDRESS>"
openssl  x509 -req -days 3000 -in ia.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out ia.crt  -extensions v3_req -extfile openssl2.cnf
#install them
openssl  pkcs12 -export -out ia.p12 -inkey ia.key -in ia.crt -chain -CAfile ca.crt
check the cert
1.docx
openssl x509 -in ia.crt -text -noout

This is almost definitely a chrome/trust-store issue and not an openssl issue.
What happens when you connect with openssl's s_client program?

try on goole.com worksf fine.
c:\Temp>openssl s_client -connect <IP_ADDRESS>:443
connect: Result too large
connect:errno=0

goole.com ?  Whatever.  If you say it works fine, then this is a Chrome issue, not an openssl issue.


[MICOM 1.0 API] Proposed new format for fluxes

This is a proposal for a new format for fluxes slated for MICOM 1.0. Feel free to comment :smile:
Checklist

[X] There are no similar issues or pull requests for this yet.
[X] The request is not specific for MICOM Qiime 2 plugin (q2-micom)

Current state
The current format for fluxes returned by MICOM is a table in wide format:
In [1]: from micom import Community

In [2]: from micom.data import test_taxonomy

In [3]: com = Community(test_taxonomy())
Building ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00

In [7]: sol = com.cooperative_tradeoff(fluxes=True)

In [8]: sol.fluxes
Out[8]:
reaction               ACALD    ACALDt      ACKr    ACONTa    ACONTb     ACt2r          ADK1  ...     SUCDi    SUCOAS      TALA          THD2      TKT1      TKT2       TPI
compartment                                                                                ...
       NaN       NaN       NaN           NaN       NaN       NaN       NaN

[5 rows x 115 columns]

This has resulted in some issues:

It is incompatible with cobra.Solution.fluxes which breaks a lot of the cobra functionality like for instance summary methods.
It can be pretty sparse for very divergent models (many NA entries)
It mixes medium and taxa fluxes
It does not specify if export fluxes denote import or export which is one of the most common help requests we receive
Basically all methods using flux results in MICOM will convert them to a long format

Proposed new API for fluxes
CommunitySolution.fluxes will retain the cobrapy format and will superseded by new accessors that all return fluxes in long format:
CommunitySolution.exchange_fluxes
Similar to the previous one but with the taxa annotated.
      reaction                     name               taxon          flux direction                       micom_id
0      EX_ac_m     ac_m medium exchange              medium  1.814984e-11    export                        EX_ac_m
1   EX_acald_m  acald_m medium exchange              medium  1.328645e-11    export                     EX_acald_m
2     EX_akg_m    akg_m medium exchange              medium  3.225128e-12    export                       EX_akg_m
3     EX_co2_m    co2_m medium exchange              medium  2.280983e+01    export                       EX_co2_m
4    EX_etoh_m   etoh_m medium exchange              medium  1.515389e-11    export                      EX_etoh_m
..         ...                      ...                 ...           ...       ...

CommunitySolution.internal_fluxes
    reaction                                               name               taxon          flux                    micom_id
0      ACALD           Acetaldehyde dehydrogenase (acetylating)  Escherichia_coli_1  1.312146e+00   ACALD__Escherichia_coli_1
1     ACALDt                  Acetaldehyde reversible transport  Escherichia_coli_1  3.236132e+00  ACALDt__Escherichia_coli_1
2       ACKr                                     Acetate kinase  Escherichia_coli_1 -1.304078e+00    ACKr__Escherichia_coli_1
3     ACONTa   Aconitase (half-reaction A, Citrate hydro-lyase)  Escherichia_coli_1  5.987675e+00  ACONTa__Escherichia_coli_1
4     ACONTb  Aconitase (half-reaction B, Isocitrate hydro-l...  Escherichia_coli_1  5.987675e+00  ACONTb__Escherichia_coli_1

This will consolidate GrowthResults and CommunitySolution and gives a more readable format. All those properties are generated on the fly when accessing the property.
Additionaly, we may also want to save the annotations in the solution but they may be large, so it might be better to have a property on the model class like Community.annotations.
Additional context
A similar format change is planned for Community.knockout_taxa. elasticities already uses a long format.

Sorry for perhaps the outdated question.
I am a graduate student working with MES scores from Marcelino et al., Nature Communications 2023
I am currently implementing MES framework for my metgenome data and confused about the res.exchanges['flux'] from the micom.workflow.grow function.
If I want to get the total production flux or consumption flux of a certain metabolite, should I weight each flux of each metabolite with relative abundance of each species? or are the flux of each metabolite already weighted by each species abudance?
I looked at CD_focus/MetModels_summarize_total_produc_consump.py and R_scripts_4_figs
/sulfur_stats_He2017.R and it seemed to me that it was the former case but I just wanted to be sure.

Yes, exactly it would be scaled by relative abundance, though you can also use the production_rates function that does that for you. Also note that MES scores are part of MICOM since version 0.35.0. See the MES function and new visualizations as well.


Add clarification to *LIST_IDS environment variables

Minor nit but hoping it saves someone else time down the road - the IDs need to be SteamID64 format which Valve documents here: https://developer.valvesoftware.com/wiki/SteamID
(Side note: today I learned there's a third SteamID format if steamid.io is correct. Thanks valve.)

So is it the SteamID64 hex format, e.g. 0x0110000100000000?

No, it's the 64-bit int.


Backtrace broken with latest RSpec

The backtrace is broken when using RSpec 3.3.1, possible older versions as well. The HTML for the links in the backtrace are escaped. See the discussion started here https://github.com/rspec/rspec-core/commit/74a286d1fe44fe6a3a6a248ee2e92718b7353e71#commitcomment-12159927.
Separate question. Based on myronmarston's last reply, perhaps the bundle should be moved to the TextMate namespace/project?
CC @myronmarston @JonRowe @infininight @sorbits

Fixed with https://github.com/rspec/rspec.tmbundle/commit/d3644929e12edd01d2410ed6aa209735b8227398


could not set breakpoint with vscode remote development

VSCode Version: 版本 1.34.0-insider (1.34.0-insider)
OS Version: macos
remote Os: linux

Steps to Reproduce:

open dir by ssh
set launch.json

      {
           "name": "Launch",
           "type": "go",
           "request": "launch",
           "mode": "auto",
           "program": "${workspaceFolder}",
           "buildFlags": " -gcflags 'all=-N -l' -i",
           "showLog": true,
           "trace": "log",
           "logOutput": "debuglineerr",
       }

F5, output:

InitializeEvent
SetBreakPointsRequest
All cleared
Creating on: XXX/main.go:39
Error on CreateBreakpoint: could not find Creating on: XXX/main.go:39
All set:[null]
SetBreakPointsResponse
ConfigurationDoneRequest
ContinueRequest
ContinueResponse

Please file this against the go extension https://github.com/Microsoft/vscode-go


Wine Theme Request

Wine
Wine support themes in the .msstyles and .theme file formats.

I will close this Issue for organizational purposes, as it is an old request without community proposals. 😅


Refresh and ID cookie values injected as headers on refresh requests

What
This PR is part of the wider new Auth work to replace Zebedee authentication with AWS Cognito via the dp-identity-api
Secure cookies that store ID and Refresh Tokens must be appended to the outbound requests leaving Florence on the path /tokens/self. These requests go to the dp-identity-api and once recieved will return a new session token (aka access token) once that session token has been provided this will replace the user's current session token and be used for all API requests.
How to review
Check tests pass.
If you want to test the functionality completely then there are a few steps to jump through, but I would probably say this isn't needed for the PR.
In Florence run make node-modules and then proceed to start Florence server-side with the feature flag ENABLE_NEW_SIGN_IN=true
Then create a new account with a REST client (e.g. ARC or POSTMAN)
Endpoint: http://localhost:25600/v1/users
Method: POST
Body: {
  "forename": "something",
  "lastname": "somethingElse",
  "email"<EMAIL_ADDRESS>}

Note please replace forename lastname and email values in the body with whatever you choose but the email must end with @ons.gov.uk
Run the following command in terminal (note require aws CLI installed): 'aws cognito-idp admin-set-user-password --user-pool-id [pool-ID] --username [user-id]  --password [desired-new-password] --permanent'
Where [pool-id] matches the user pool of the dp-identity-api (on startup this is outputted, or look at the code configs for this value)
[user-id] is the user id outputted from the HTTP request we sent in the previous step
[desired-new-password] is a new password you want. It must be more than 14 characters, have at least 1 upper case, 1 lowercase and 1 number. Or the request will be rejected (can read the output it will tell you something is wrong).
Once complete you can load up Florence login screen locally e.g. http://localhost:8081/florence/login and open the network tab in the dev tools.
Proceed to enter the email and password that you have set in the above steps. You will notice an error pop up at the bottom of the screen when you click Sign in.
When the button is pressed two requests are made, a post sign-in request and a
get permissions request. The latter one should be the one that fails, you can identify this in the network tab. So long as the first one was a success you will be given three tokens ID, Refresh and Session  these are stored in your cookies, but can't be accessed via JS as they are secure httpOnly cookies. As such only Server-Side applications can access them, which is where this PR comes in.
Finally, in the dev tools, you can open a console and enter the following code which will make a request to refresh the current user's session token by providing the current ID and Refresh Tokens
const fetchConfig = {
    method: "PUT",
    body: JSON.stringify({})
  };
fetch("/tokens/self", fetchConfig)
  .then(response => {
  	console.log('Well got a response')
	  if (!response.ok) {
    	throw response;
  	}
  	console.log('response was ok')
  	return response.json();
})

If you tab over to the window you are running the dp-identity-api you should notice it returning a status 201
Who can review
Anyone except me

Looks good, but the audit check is failing due to the copy-webpack-plugin - may be worth bumping the version and see if that resolves


Implement FromBytes and AsBytes for raw pointers

Previously, we omitted these impls out of a fear of creating a footgun in which it would be too easy to mistakenly transmute into a type with internal safety invariants. Recently, this omission meant that I was unable to get rid of a number of lines of unsafe code in a codebase that used raw pointers, and it made me realize that it is more important to enable this use case than to avoid a theoretical footgun.
Closes #170

Per tests, looks like tests/ui/transmute-illegal.stderr needs to be updated now that pointers may be transmuted.

Oh damn, that may actually be a clue to a soundness hole. For those following along, here's the error I get:
error[E0080]: evaluation of constant value failed
  --> tests/ui/transmute-illegal.rs:10:1
   |
10 | const POINTER_VALUE: usize = zerocopy::transmute!(&0usize as *const usize);
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^ unable to turn pointer into raw bytes
   |
   = help: this code performed an operation that depends on the underlying bytes representing a pointer
   = help: the absolute address of a pointer is not known at compile-time, so such operations are not supported

Are we guaranteed that rustc's const eval will catch every instance of turning a pointer into raw bytes? If so, this should be okay - it'll just result in a potentially confusing compile-time error for the user. If this is a best effort analysis, though, then introducing those trait impls may be unsound.

AFAIK the compiler will catch all cases where a pointer is transmuted to bytes at compile time. If you want to guarantee that we can't do that in const expressions, the macro could expand to a non const function that is immediately invoked. I don't think the guarantees around const UB are well defined.

Submitted https://github.com/rust-lang/unsafe-code-guidelines/issues/401 to get a clearer answer; if the answer is that it's guaranteed, I'll follow up with a change to the Rust reference to make it clear that it's guaranteed.
This also brings up another question, which is: None of our safety comments justifying FromBytes, AsBytes, and Unaligned impls mention the const context. If there are other operations which are sound in non-const code but unsound in const code, then those safety arguments may be incomplete. Do we need to come up with a general strategy for reasoning about const soundness?

I anticipate the answer will be that any time const soundness is more restrictive than runtime soundness, the compiler is guaranteed to emit a compile error. If that's not the case, then it's difficult to make a single coherent strategy

Closing for now; I'll reopen depending on the resolution of https://github.com/rust-lang/unsafe-code-guidelines/issues/401


Rust-core mock testing

Description
Mock Testing of the Glide-rs (Rust-core) system.
High-level diagram (see the third track):

This PR includes:

Rust core lib mock. It allows java wrapper to connect to this mock thru UDS instead of real Glide. Useful for testing unusual scenarios and for prividing code coverage.
Subsets of simple tests which use these mocks.
Couple of minor fixes in the client. Thanks to these tests for finding them.

To run tests use
./gradlew :client:test --tests ConnectionWithGlideMockTests
./gradlew :client:test

Out of date.  We can cherry-pick this feature in the future if we need it.


Add external memory integration and GL integration sample.

Will play with this in garbagefire when I have time. Looks awesome!


Updating action for use on GitHub Enterprise

Update Action for Use on GitHub Enterprise
Currently the action doesn't seem to be useable for Workflows running on GitHub Enterprise. This is because:

getVersion relies on Oktokit defaulting the baseUrl. In Enterprise, this baseUrl appears to be defaulted to the enterprise URL rather than public GitHub.
The GitHub token provided by a Workflow may not be able to authenticate with the GitHub API on https://api.github.com if it limited by scope - this is needed by getVersion()
The token needed by setUpTool() may therefore need to be different from the token used by getVersion().

Proposed changes:

Hardcode the GitHub API URL to get releases by tag so it doesn't default to the Enterprise URL
Add an additional Action input to set a different token used by the setUpTool function to set Allure job metadata. This is defaulted to ${{ github.token }} to avoid regressions.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


yarn start:macos / Xcode build error too

Environment
react-native -v = can't query by command , but in package.json its
    "react-native": "0.71", but in npm ls react-native the complete version is 0.71.19
npm ls react-native-macos =<EMAIL_ADDRESS>node -v: - v22.3.0
npm -v: - v10.8.1
yarn --version: - v1.22.22
xcodebuild -version: Xcode 15.2
Build version 15C500b

Steps to reproduce the bug

i just npx react-native-macos-init on my existing  react-native package
the command tells how to run it after init
"""
Run instructions for macOS:
• npx react-native run-macos

or -
• Open macos/cdms-app.xcworkspace in Xcode or run "xed -b macos"
• yarn start:macos
• Hit the Run button
"""

then i run npx react-native run-macos , it fails with the error bellow
"""
CompileC /Users/xxx/Library/Developer/Xcode/DerivedData/xxxxx-apslssjfyuyzkdffepeastytryrj/Build/Intermediates.noindex/Pods.build/Debug/Expo.build/Objects-normal/x86_64/EXAppDefinesLoader.o /Users/xxx/project/xxxxx/build/metro/node_modules/expo/ios/EXAppDefinesLoader.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'Expo' from project 'Pods')
(1 failure)
"""
then i tried to open the xcode project and hit run and the got the error below
/Users/xxx/project/xxxxxx/build/metro/node_modules/expo/ios/EXAppDefinesLoader.m:5:9 'ExpoModulesCore/ExpoModulesCore.h' file not found
then i tried the yarn start:macos as per the run instruction .  but yarn start:macos was not found
warning ../../../package.json: No license field
error Command "start:macos" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Expected Behavior
it will start the desktop app
Actual Behavior
error nothing happens
Reproducible Demo
No response
Additional context
No response

It looks like you're using Expo. Expo doesn't officially support React Native macOS out of the box, so there' likely additional work to get it running.


[Snyk] Security upgrade typeorm from 0.2.24 to 0.2.25

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

422/1000  Why? Confidentiality impact: High, Integrity impact: Low, Availability impact: High, Scope: Unchanged, Exploit Maturity: Functional, User Interaction (UI): None, Privileges Required (PR): Low, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.00301, Social Trends: No, Days since published: 1335, Reachable: No, Transitive dependency: No, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 9.08, Likelihood: 4.64, Score Version: V5
Prototype Pollution SNYK-JS-TYPEORM-590152
No
Mature

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution

test from Jira


Fix strconv

@eparis @wojtek-t
Fix problems the two of you found. Will push live shortly.

Live now.


Implement API update

Codecov Report
Base: 27.70% // Head: 28.00% // Increases project coverage by +0.29% :tada:

Coverage data is based on head (9c607bb) compared to base (cbc6e0d).
Patch coverage: 3.57% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #480      +/-   ##
==========================================
+ Coverage   27.70%   28.00%   +0.29%
==========================================
  Files         119      118       -1
  Lines       13396    13474      +78
  Branches     3103     3134      +31
==========================================
+ Hits         3711     3773      +62
- Misses       9491     9507      +16
  Partials      194      194

Impacted Files
Coverage Δ

...office-domain-service/ballerina/backoffice_dao.bal
0.00% <0.00%> (ø)

...ffice-domain-service/ballerina/backoffice_impl.bal
34.52% <0.00%> (-1.28%)
:arrow_down:

...omain-service/ballerina/backoffice-api_service.bal
21.83% <7.69%> (-2.49%)
:arrow_down:

...ter/internal/oasparser/envoyconf/routes_configs.go
58.66% <0.00%> (-0.08%)
:arrow_down:

adapter/internal/oasparser/model/http_route.go
0.00% <0.00%> (ø)

runtime/runtime-domain-service/ballerina/Error.bal

...ime/runtime-domain-service/ballerina/APIClient.bal
40.46% <0.00%> (+1.57%)
:arrow_up:

...2.apk.devportal.sdk/APIClientGenerationManager.bal
19.17% <0.00%> (+16.43%)
:arrow_up:

...tal/devportal-domain-service/ballerina/apiImpl.bal
82.35% <0.00%> (+58.82%)
:arrow_up:

... and 1 more

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.

Fix https://github.com/wso2/apk/issues/472


Card subtitle not aligning correctly

Using MDL version 1.3.0, on Chromium 55 (and Firefox 52) on Debian Linux (Stretch), the subtitle of cards (mdl-card__subtitle-text) does not align properly:

I found #1002 which is the exact same issue, but the workaround listed there does not work, the Title is still on the right. The jsfiddle linked there demonstrates the issue:

Does anyone have a workaround for this?
Thanks,
Thomas.

Duplicate of #1002.

Hi,
Yes, I have listed that issue in my issue, the problem is that the workaround there does not work. Is there a new workaround that works for 1.3?

Same as the one mentioned in the previous issue.

Oh, didn't see the .mdl-card__title-text. Thanks!
On Feb 8, 2017, 11:58 AM, at 11:58 AM, Jonathan Garbee<EMAIL_ADDRESS>wrote:

Same as the one
mentioned
in the previous issue.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/google/material-design-lite/issues/5031#issuecomment-278388986


Feature: Refine documentation and optimize the usage of configs

Description
Refine documentation and optimize the usage of configs.

Codecov Report
Patch and project coverage have no change.

Comparison is base (82a2112) 93.01% compared to head (bfa25b0) 93.01%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #165   +/-   ##
========================================
  Coverage    93.01%   93.01%
========================================
  Files          302      302
  Lines         4755     4755
  Branches       636      636
========================================
  Hits          4423     4423
  Misses         214      214
  Partials       118      118

Flag
Coverage Δ

build
94.64% <ø> (ø)

core
94.36% <ø> (ø)

extension-dbt
97.43% <ø> (ø)

extension-debug-tools
98.11% <ø> (ø)

extension-driver-bq
85.21% <ø> (ø)

extension-driver-duckdb
96.46% <ø> (ø)

extension-driver-pg
96.11% <ø> (ø)

extension-driver-snowflake
96.22% <ø> (ø)

integration-testing
90.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@fredalai

((Not sure will be in this PR to do it or not)) Update related catalog feature figures, and describe more detailed information. E.g., Adding descriptions for each API.

Will not be done in this PR.


Exact versions of all the packages

Hey Sachin, thanks a lot for sharing this code of ESPNet. You must be aware that how difficuilt it is to lay down the correct platform to make the code run. Giving the code the required environment is almost half the work done. Can you please share the exact versions of different packages used in this project. Thanks in advance.

These are the packages that are required for this codebase:
https://github.com/sacmehta/ESPNet#pre-requisite
The main dependency is the PyTorch. This code was written 3 years back, and back then PyTorch version is 0.3.0. You would have noticed it if you spent a minute reading the documentation, and actually interested in learning about the code. Anyways, with few modifications, you should be able to use it with the latest PyTorch version. Several people in the community have reproduced our results successfully (including TensorFlow), so I believe there is no issue with the documentation and code.
Please read more about using old versions here:
https://pytorch.org/get-started/previous-versions/


Hex logo

As part of creating a packages page for the NHSRcommunity website https://github.com/nhs-r-community/nhs-r-community/issues/219, I've designed a hex sticker for this package. Will do a PR shortly with the code and logo, but happy to take feedback and tweak the design as desired.

Looks great! Linking this comment to the PR but keeping it open to add this to the README and pkgdown.

@all-contributors please add @anyaferguson for design


Cannot deselect Signing Server on create vault

When choosing the Signing Server as a cosigner on the create vault it is not possible to deselct it.

Need to check if this issue is still happening


Performance degradation on Pytorch 1.10 / Torchvision 0.11.0

When I upgraded the Pytorch and Torchvision to 1.10.0 and 0.11.0 and then trained the pointpillars (https://github.com/traveller59/second.pytorch/blob/3aba19c9688274f75ebb5e576f65cfe54773c021/second/configs/pointpillars/car/xyres_16.config), the final evaluations of eval.kitti/official/Car/* were 3-5 point worse than before (Pytorch 1.9.1 and Torchvision 0.10.1).
AOS was broken in both cases but I think it is due to https://github.com/traveller59/second.pytorch/issues/238 . So it is not the main subject.
Did anyone reproduce this phenomenon?

Sorry it seems just my fault


Add support for downloading packages from private sources

This changeset provides support for downloading autobuild packages from restricted sources such as private repositories using GitHub release artifacts or GitLab generic packages.
The way this works is by the addition of an optional parameter: creds, which may be specified when adding or editing dependencies:
autobuild installables edit my-pkg creds=github url=...

This property is used to inform autobuild that it should set a HTTP authorization header specific to the provider (github, gitlab) when downloading the respective artifact. An environment variable containing credentials is expected to be set per-provider in order to keep authorization strategies separate:
AUTOBUILD_GITHUB_TOKEN - GitHub Personal Access Token
AUTOBUILD_GITLAB_TOKEN - GitLab Personal Access Token

For example, a GitHub actions runner could do the following:
export AUTOBUILD_GITHUB_TOKEN=$GITHUB_TOKEN
autobuild install

Future
This functionality could be enhanced to include more providers or authorization schemes. The autobuild install command could also be enhanced with equivalent kwargs --github-token and --gitlab-token.

I think my request is beyond the scope for this PR, but would it be a good idea to incorporate use of the python keyring module for handling these kind of credentials in the future?

Great idea. Yes, I think that should be looked into in the not-too-distant future.


DataFrame.unstack() issues DeprecationWarning with MultiIndex

>>> import warnings
>>> warnings.simplefilter('error')

>>> import pandas as pd
>>> pd.__version__
u'0.17.0rc1'

>>> df = pd.DataFrame({'A': list('aabb'), 'B': [0, 1, 0, 1], 'C': range(4)})
>>> gf = df.groupby(['A', 'B']).sum()
>>> gf
     C
A B
a 0  0
  1  1
b 0  2
  1  3

>>> gf.unstack()
Traceback (most recent call last):
..., line 4274, in _reference_duplicate_name
    return np.sum(name == np.asarray(self.names)) > 1
DeprecationWarning: elementwise == comparison failed; this will raise an error in the future.

what version numpy?
there are 'lots' of these. We do have to fix this at some point. But its not a big deal.

this is covered in #8537
pull-requests always welcome!

Yes, sorry, I just realized this seems to be due to this in the numpy 1.10.0b1 I am using here.
The line in the traceback seems to involve a comparison like: -1 == np.asarray(['A', 'B'])

We actually test with this: https://travis-ci.org/pydata/pandas/jobs/81396483
numpy master with DeprecationWarnings turned on. I try to get rid of them; I think I got most but their are some (also the 3.4 build has some as well).
so eventually have to fix!

Yup, I just hit this one today too when I did a fresh pull of the latest pandas and numpy.
Another repro case:
pd.DataFrame([[1, 2], [3, 4]], columns=['a', 'b']).groupby('a').b.value_counts().unstack()

yeh this is a numpy warning - never got around to tracking this one down
you are welcome to it!

Maybe this should be re-opened (does #8537 mention mixed-type comparisons?).
I hope, we already tracked it: Wouldn't it be enough to replace this
return np.sum(name == np.asarray(self.names)) > 1

with this?
return sum(name == n for n in self.names) > 1


Make Registry state strict

This should be a relatively simple PR.
Will benefit from #965.

bors r+


change the font

The font is unclear and its not based on the arabian alphabet. for a clearer version we need to change the fonts.

you can change the source and see if it works on the local host? if it does we can proceed easily.


receive: too large gRPC message

Messages sent to Thanos receiver fails when msg size is above 4MB due to gRPC maxRecvMsgSize = 4MB

Thanos, Prometheus and Golang version used:
Thanos: 0.15.0
Prometheus: 2.20.0
Golang: 1.15.4

Object Storage Provider:
AWS S3
What happened:
Messages sent to Thanos receiver fails when msg size is above 4MB due to gRPC maxRecvMsgSize = 4MB:
err="forwarding request to endpoint thanos-receiver-prometheus-0:10901: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4194776 vs. 4194304)"
What you expected to happen:
Metrics should be accepted, receiver default grpc maxRecvMsgSize should be increased or make configurable via additional flag,  code example with fix
Problem was fixed after increasing grpc MaxRecvMsgSize to 64MB in receiver (via additional custom flag).
How to reproduce it (as minimally and precisely as possible):
Start Thanos Receiver, send metrics in grpc messages with size >4MB
Example logs to relevant components:
Logs

level=error name=receiver ts=2020-11-12T06:48:36.068665815Z caller=handler.go:331 component=receive component=receive-handler err="forwarding request to endpoint thanos-receiver-prometheus-2:10901: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4850187 vs. 4194304)" msg="internal server error"
level=error name=receiver ts=2020-11-12T06:48:34.988160212Z caller=handler.go:331 component=receive component=receive-handler err="forwarding request to endpoint thanos-receiver-prometheus-0:10901: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4194776 vs. 4194304)" msg="internal server error"
level=error name=receiver ts=2020-11-12T06:48:34.224506555Z caller=handler.go:331 component=receive component=receive-handler err="forwarding request to endpoint thanos-receiver-prometheus-2:10901: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4850187 vs. 4194304)" msg="internal server error"

Messages sent to Thanos receiver fails when msg size is above 4MB due to gRPC maxRecvMsgSize = 4MB
Thanos, Prometheus and Golang version used:
Thanos: 0.15.0
Prometheus: 2.20.0
Golang: 1.15.4
Object Storage Provider:
AWS S3
What happened:
Messages sent to Thanos receiver fails when msg size is above 4MB due to gRPC maxRecvMsgSize = 4MB:
err="forwarding request to endpoint thanos-receiver-prometheus-0:10901: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4194776 vs. 4194304)"
What you expected to happen:
Metrics should be accepted, receiver default grpc maxRecvMsgSize should be increased or make configurable via additional flag, code example with fix
Problem was fixed after increasing grpc MaxRecvMsgSize to 64MB in receiver (via additional custom flag).
How to reproduce it (as minimally and precisely as possible):
Start Thanos Receiver, send metrics in grpc messages with size >4MB
Example logs to relevant components:
Logs

Hi! Hmmm... have you encountered this while using Thanos Receive "normally" or have you followed some steps to reproduce this?

This is happening for rather standard Prometheus instance (2M samples scraped per minute) connected via remote write API, remote_write configuration itself does not control precise size of individual request (only number of samples), the same time decreasing this value has negative impact on E2E performance. We observe such errors even when max_samples_per_send is in range a few thousands (2-10k), apparently depending on number of labels in individual batch.


Display some info like the title of a link

It would be nice to see the title of a link, would be very informative, and allow users to see what it is before clicking it

This was completed as of f152cfe38fe42d5ec213805b1ba57007463ed274

(and this is why we branch)

@julianpoy Naw naw naw naw, this is a super personal project, it aint even close to going anywhere yet

@torch2424 I was just teeezing

@julianpoy I know <3 ;)


No "chardet" module in dependencies

Missing chardet module in dependencies.

The chardet dependency is included in the requirements.txt
https://github.com/cubewise-code/rushti/blob/master/requirements.txt
Do you think we should list it in the readme.md as well?

Yes, thx

@cubewise-gng
Let's make chardet an optional dependency. If it isn't installed RushTI should skip the preprocessing of the file.
Is that OK?


[GLUTEN-3718][VL] Set connector file handle cache size to 20

20 is big enough for most case.
(Fixes: #3718)

disable file handle is better.


Styling for comments

Merging because it's small and I want to try out with the other PR. Happy to make further changes here.


X-Forwarded-For or X-Real-IP is not forwarding client ip to backend

After setting the mentioned header in the webserver 'nginx', the backend still receives DNS queries from nginx IP and not from the client IP.
Even in the logs, I only see the IP of the web server and not the client.
Is it bugged or I'm missing something here?
from nginx config:
...
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
...
proxy_pass       http://ungound-dns;
from DOH config:
...
log_guessed_client_ip = true

I haven't seen this problem before.
Would you please try to do a packet sniff between Nginx and doh-server using either Wireshark or tcpdump?

By the way, the IP guessing feature ignores any private IP in the proxy chain and detects only the first public IP in the proxy chain. This is designed for GeoDNS -- a private IP can not indicate any geographical information.

In the debug logs of nginx I can see that nginx has set the headers correctly.
and from the pcap file I can the headers are set with the client public IP.

Thank you for your info. I will try to diagnose this problem.

By the way, for each request there will be two lines of log:
<IP_ADDRESS> - - [29/Feb/2020:08:46:00 +0000] "example.com. IN A"
<IP_ADDRESS> - - [29/Feb/2020:08:46:00 +0000] "POST /dns-query HTTP/1.1" 200 121 "" "Go-http-client/1.1"

One of the 2 lines are generated by my code, which contains the guessed client IP.
The other line is generated by the Gorilla web toolkit. And I just currently have no idea how to change the IP address in this line.

I'm the log_guessed_client_ip patch author. I suggest set whatever environment/argument to remove the gorilla log and add dns-over-https's user-agent log

I'm having the same issue with Apache. I have verified that Apache is sending the X-Forwarded-* headers, but the doh-server is logging <IP_ADDRESS> for both log lines. I've put relevant config and log files in this gist.
https://gist.github.com/jordanbtucker/0988c34e54089ca11d850840986bf56e

Thank you for your information. I think I need to replace the code provided by Gorilla and rewrite it ourselves.

First off - I am not proficient in Go so I could be way off base.
Could the ProxyHeaders handler in the gorilla toolkit be used to generate the needed data? As far as I can tell the only handler from the gorilla handlers package in use is the CombinedLoggingHandler.  There are some notes in the documentation that using ProxyHeaders when the go http server is not behind a proxy creates a potential vulnerability.
Can the log_guessed_client_ip setting in doh_server.conf be used when set to true to (1) assume a proxy is used upstream and (2) add the ProxyHeader handler to the list of handlers that are used?

@buckaroogeek Looks like you are correct about the global IP issue. It checks for a global IP here, here, and here. Perhaps we could have an option to return any forwarded IP rather than just global ones?

I've had the same issue since version 2.0.1. Running 2.2.1 now. Nginx is setup to pass the IP address to DOH Server. However, the IP does not passed to the back to, in my case, Pihole-FTL. Until this thread, I thought this was just normal behavior. With Pihole there's value in seeing the IP to understand which devices are making the most blocked requests. Thanks.

Thank you for your report!
I am currently rewriting the part from Gorilla and soon I will be able to get this thing fixed.

Please check the latest version and see whether it fixes this problem.
Note that X-Forwarded-For or guessed client IP is not used in HTTP log due to security concerns.
But you should be able to pass X-Real-IP from the frontend nginx/Apache/Caddy to doh-server now.

Please check the latest version and see whether it fixes this problem.
Note that X-Forwarded-For or guessed client IP is not used in HTTP log due to security concerns.
But you should be able to pass X-Real-IP from the frontend nginx/Apache/Caddy to doh-server now.

Working for me now.

@m13253 Thanks for the fixes. The 2.2.2 update seems to have partially fixed the issue, at least for my configuration. doh-server is logging the right external IP (verbose = true and log_guessed_client_ip = true). However, the upstream provider to doh-server (in my case pihole-FTL) does not see the external IP. It still just sees <IP_ADDRESS>. Is that normal? If so, is there a way to config doh-server pass the IPs to the upstream provider? Thanks.

I am having the same issue as @aniqueta. This issue is not closed for me.

@m13253 Should we create a new issue for this, since this one is closed, or would it be possible to reopen this? Any additional info we can help with? Thank you!

Reopened the issue. But currently I don't have an idea of how to fix it. Maybe we can work out together.

I think the problem is that findClientIP is only returning IP addresses that pass jsondns.IsGlobalIP. I want to know which IP address on my local network made a query.
https://github.com/m13253/dns-over-https/blob/4f46b89febf08ad906be51765b1703cb61e2f90a/doh-server/server.go#L248-L280

After a second look, it appears my issue is different from @aniqueta's.
To answer @aniqueta's question, I do not think it is possible for DoH to forward the original IP address upstream (pihole in your case, BIND in mine). Since DNS servers receive requests over UDP and/or TCP, there is no way to include the original IP address in those packets, and as far as I know, the DNS protocol does not provide a way to include that information either.

as far as I know, the DNS protocol does not provide a way to include that information either.

Edns0-Client-Subnet protocol

I want to know which IP address on my local network made a query.

I guess according to the code at https://github.com/m13253/dns-over-https/blob/master/doh-server/ietf.go#L99-L106 , doh-server is already trying its best to log the client IP address.
I want doh-server to satisfy two requirements:

The IP address I want to forward to upstream using ECS must be global IP address, so the upstream DNS server can know which country the client is from and resolve to a fast edge server. Providing local IP address does not help with this.
Since a typical doh-server deployment usually includes multiple cache servers (both at HTTP side and DNS side), skipping local addresses are designed to skip these cache server's addresses.

I understand that you would like to know which host submitted the original DNS request, but I cannot figure out a good way to implement this and also fulfill the above two requirements.
Therefore I am not sure how to solve the problem right now. Let's discuss about it.

Edns0-Client-Subnet protocol

Oh, that's right. Sorry, it's been a while since I worked on this issue with my DNS server.

Another reason my original design is to skip all local addresses are because the Google DoH protocol (at that time the IETF thing did not exist) is human readable. Therefore, an Apache log is enough to log the client's address, doh-server's log is only used to debug ECS deployment.
But nowadays the IETF DoH uses a base64-encoded request, which makes the Apache log hard to decipher (still able, though). So that's how this issue comes into place.

That makes sense. In my use case, doh-server will never see an X-Forwarded-For or X-Real-IP with a global IP address because it only serves my local network. It's not public facing. So a configuration option to forward non-global IP address via ECS would be ideal for my use case. Then BIND could do all the logging.

Then BIND could do all the logging

Maybe you can try to log the client's IP at BIND side, because that can solve the problem and, you know, since that is a valid workaround, I am a little bit lazy about this.
Also, if anyone implements this function, feel free to send me a Pull Request.
At this time, I think we can temporarily stick to the UNIX Philosophy -- combine with a BIND or unbound or dnsmasq, since we will surely need a cache after all.

I would love for BIND to do all the logging, but BIND cannot get the original IP address from doh-server because it only includes global IP addresses in the ECS info. If there was an option for doh-server to include local IP addresses in the ECS info, then that would solve my problem.

If there was an option for doh-server to include local IP addresses in the ECS info

That would confuse the upstream resolver and probably give you a resolution results in a different country, or use the IP address of their best guess.

By the way, if you are satisfied with current solution (or workaround), please notify me so I can release version 2.2.3.
Otherwise, I will delay the release and see if we can come up with better solutions.

I do think what @m13253 is trying to achieve matches my use case and addresses my reason to reopen the ticket, although the above conversation is difficult to track, so I'd like to confirm.
My DOH setup takes in queries from the web, and so I do want the upstream provider to log the global IP address originating the DNS query. For security, there is a firewall and reverse proxy protecting DOH exposed to the web, and I do not care to log its IP. I think that's exactly the functionality @m13253 is trying to maintain, per this comment:

I want doh-server to satisfy two requirements:
1. The IP address I want to forward to upstream using ECS must be global IP address, so the upstream DNS server can know which country the client is from and resolve to a fast edge server. Providing local IP address does not help with this.

2. Since a typical doh-server deployment usually includes multiple cache servers (both at HTTP side and DNS side), skipping local addresses are designed to skip these cache server's addresses.

Will the proposed solution here work to log the global IP address on Pi-hole (a dnsmasq variant)? I'm not knowledgeable enough about ECS, and whether that will do the trick. Thank you!

Solved with #92

@m13253 Apologies for my very delayed reply on this. Just got around to testing this, and it solves my use case with pihole as well. Thanks and good to close this, I think.


menus black and not useable

If I right click or click on ana meue for e.g. file is is just black and not useable

Can you provide more info about your platform (Linux, version, etc). You can get this by Ctrl+Shift+P > About

I am using Pop!_OS 20.04 version. and visual studio code version1.48.0

@deepak1556 linux native menus


Do not force capitalise upload images etc

Upload images filenames can be entirely lower case.

Not fixed yet, this is a known issue in v2.0.0


OTG Test Update - P4RT 3.2 capture verification

Added pcap verification for the received packets on the ATE port.
Resolves #882

Pull Request Functional Test Report for #2089 / 9bec001da89378dd1d9d80db9493d6ba6a7b3c9b
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

P4RT-3.2: Google Discovery Protocol: PacketOut

Cisco 8000E

P4RT-3.2: Google Discovery Protocol: PacketOut

Cisco XRd

P4RT-3.2: Google Discovery Protocol: PacketOut

Juniper cPTX

P4RT-3.2: Google Discovery Protocol: PacketOut

Nokia SR Linux

P4RT-3.2: Google Discovery Protocol: PacketOut

Openconfig Lemming

P4RT-3.2: Google Discovery Protocol: PacketOut

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

P4RT-3.2: Google Discovery Protocol: PacketOut

Cisco 8808

P4RT-3.2: Google Discovery Protocol: PacketOut

Juniper PTX10008

P4RT-3.2: Google Discovery Protocol: PacketOut

Nokia 7250 IXR-10e

P4RT-3.2: Google Discovery Protocol: PacketOut

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1347

Relevant Lines:
2947

💛  - Coveralls


Basic setup

I've spent hours or setting up DBFlow, however I couldn't get it running. I've tried following combinations:
1- As described in Readme:
In root build.gradle:
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
    }
}
allProjects {
  repositories **{**
    // required to find the project's artifacts
    maven { url "https://jitpack.io" }
  }
}

In inner build.gradle:
  apply plugin: 'com.neenbedankt.android-apt'

  def dbflow_version = "3.0.0-beta6"

  dependencies {
    apt "com.github.Raizlabs.DBFlow:dbflow-processor:${dbflow_version}"
    compile "com.github.Raizlabs.DBFlow:dbflow-core:${dbflow_version}"
    compile "com.github.Raizlabs.DBFlow:dbflow:${dbflow_version}"
}

Problem: Doesn't import DBFlow
2- Using an older version
buildscript {
    repositories {
        mavenCentral()
        maven { url 'https://dl.bintray.com/raizlabs/Libraries' }
    }
    dependencies {
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
    }
}

apply plugin: 'com.neenbedankt.android-apt'

dependencies {
    apt 'com.raizlabs.android:DBFlow-Compiler:2.2.1'
    compile "com.raizlabs.android:DBFlow-Core:2.2.1"
    compile "com.raizlabs.android:DBFlow:2.2.1"
}

Problem:   Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.raizlabs.android.dbflow.config.GeneratedDatabaseHolder
Also, I've disabled instant run & have tried lot of permutations & combinations. Can someone help on this?

ensure incremental compilation is off, that there's no compile issues in your app.


MultiRabbit containerFactory SpEL Resolution Bug

In what version(s) of Spring AMQP are you seeing this issue?
3.1.6
Describe the bug
The resolveMultiRabbitAdminName method in MultiRabbitListenerAnnotationBeanPostProcessor does not properly resolve SpEL expressions for the containerFactory attribute of @RabbitListener annotations. According to the JavaDoc, the containerFactory attribute should support SpEL expressions, but the current implementation does not resolve these expressions, potentially leading to incorrect admin name resolution.
Additional context
JavaDoc for containerFactory() method in RabbitListener:
 * The bean name of the
 * {@link org.springframework.amqp.rabbit.listener.RabbitListenerContainerFactory} to
 * use to create the message listener container responsible to serve this endpoint.
 * <p>
 * If not specified, the default container factory is used, if any. If a SpEL
 * expression is provided ({@code #{...}}), the expression can either evaluate to a
 * container factory instance or a bean name.
 * @return the
 * {@link org.springframework.amqp.rabbit.listener.RabbitListenerContainerFactory}
 * bean name.
 */
String containerFactory() default "";

https://github.com/spring-projects/spring-amqp/blob/d7058bbac660741bbd84cd14904683fc65696015/spring-rabbit/src/main/java/org/springframework/amqp/rabbit/annotation/RabbitListener.java#L124
To Reproduce

Define a @RabbitListener annotation with a SpEL expression for the containerFactory attribute.
Observe that the resolveMultiRabbitAdminName method does not resolve the SpEL expression.

Expected behavior
The method should resolve SpEL expressions for both admin and containerFactory attributes. A proposed fix would be:
protected String resolveMultiRabbitAdminName(RabbitListener rabbitListener) {
    String admin = super.resolveExpressionAsString(rabbitListener.admin(), "admin");
    if (!StringUtils.hasText(admin) && StringUtils.hasText(rabbitListener.containerFactory())) {
        String containerFactory = super.resolveExpressionAsString(rabbitListener.containerFactory(), "containerFactory");
        admin = containerFactory + RabbitListenerConfigUtils.MULTI_RABBIT_ADMIN_SUFFIX;
    }
    if (!StringUtils.hasText(admin)) {
        admin = RabbitListenerConfigUtils.RABBIT_ADMIN_BEAN_NAME;
    }
    return admin;
}

Confirmed.
And I think the fix you propose is OK, but it would only work if those expressions are evaluated to bean names.
See resolveExpressionAsString() impl:
	protected String resolveExpressionAsString(String value, String attribute) {
		Object resolved = resolveExpression(value);
		if (resolved instanceof String str) {
			return str;
		}
		else {
			throw new IllegalStateException("The [" + attribute + "] must resolve to a String. "
					+ "Resolved to [" + resolved.getClass() + "] for [" + value + "]");
		}
	}

So, if that is resolved to the RabbitAdmin instead it would fail.
Same for containerFactory() attribute.
We probably can workaround for the RabbitAdmin because it goes with a BeanNameAware contract implementation.
But RabbitListenerContainerFactory does not have one.
However that must not be hard to do that as well, although this is going to be more involved fix.
But yeah, more robust.
There is a workaround for the problem. Use explicit admin attribute on the annotation.
Therefore I am not going to back-port the fix to the previous version.
Sounds like a plan?

Hi,
The issue not fully resolved, open PR:
https://github.com/spring-projects/spring-amqp/pull/2936


Updated Broken Links

updated the broken links referencing cookbook Readme, and corrected file location for README_TYPEDOC.md

Closing as changes have been addressed in #1261


Add explicit flush to clEnqueueMapBuffer test

We have concerns about this change given that the queue is in-order. Our understanding of the spec is that command B enqueued to an in-order queue should execute as if the previously enqueued command A had fully completed. In this context, interference between an EnqueueUmapMemObject command and subsequent EnqueueMapBuffer commands would point to an implementation issue.
Thanks,
Balaji Calidas


[BUG] pageInfo.title not working

Environment
Self-Hosted (Docker)
System
No response
Version
2.1.1
Describe the problem
In the website's  tag (and hence in the browser's window/tab title, etc), it always says "Dashy", regardless of the setting configured in pageInfo.title.
The page itself however shows the correct title in the header.
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

I'm also experiencing this issue running Dashy using Docker.

I'm also experiencing this issue. Looks like this was an issue in 2.0.4 (https://github.com/Lissy93/dashy/discussions/562) but it was fixed. Now it's back, at least for me on 2.1.1 running in docker (24.02).

can't change:
title-description

Some progress fixing that?

Anybody has a workaround for this?

Unfortunately no

This is a know issue, we are currently working on this, for a termporary fix, just manually trigger a rebuild

Hi
This problems seems to be related to dashy not automatically rebuilding on changes, see #1479 and https://github.com/Lissy93/dashy/issues/1290#issuecomment-1884249018
A new release has just been published, which should fix this issue, so please upgrade to the latest version.
If this is not the case just respond back to this ticket and I'll reopen this issue.
Thanks and have a nice day.


[NFC] Bwd multi-kernel spatial bnorm solver

Testing in process.

My bad, tidy fix didn't get pushed. I have ran my bench, it passed, started yours.

Your bench passed as well, but it has 0 cases with the affected solver.

@DrizztDoUrden what does NFC label mean? it was used for quite a few previous and similar PRs, but not this one :) Just out of curiosity.

Vasilii Filippov what does NFC label mean? it was used for quite a few previous and similar PRs, but not this one :) Just out of curiosity.

No Functional Changes

@DrizztDoUrden what does NFC label mean? it was used for quite a few previous and similar PRs, but not this one :) Just out of curiosity.

If someone has No F* Clue what NFC means, then that's my bad. I brought it here from llvm, https://llvm.org/docs/Lexicon.html, sorry.

@DrizztDoUrden Please do not delete branch until a ~ week passed since merging.


Docs for persistent compilation cache are superseded

Description
I followed the docs here: https://jax.readthedocs.io/en/latest/persistent_compilation_cache.html, but I still do not get cache hits.
Is there something I am missing?
import os
import jax

cache_dir = "/tmp/jax_cache/"
os.makedirs(cache_dir, exist_ok=True)
jax.config.update("jax_compilation_cache_dir", cache_dir)

def f(x, y):
    return jax.numpy.matmul(x, y)

x = jax.numpy.ones((2, 2))
jax.jit(f)(x, x.T)

!ls -a /tmp/jax_cache/

System info (python version, jaxlib version, accelerator, etc.)
jax:    0.4.26
jaxlib: 0.4.26
numpy:  1.25.2
python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
jax.devices (1 total, 1 local): [CpuDevice(id=0)]
process_count: 1
platform: uname_result(system='Linux', node='1210851b0b9c', release='6.1.85+', version='#1 SMP PREEMPT_DYNAMIC Sun Apr 28 14:29:16 UTC 2024', machine='x86_64')

The flags are confusing. You need to do:
jax.config.update('jax_compilation_cache_dir', '/tmp/jax_cache')
jax.config.update('jax_persistent_cache_min_entry_size_bytes', 1)
jax.config.update('jax_persistent_cache_min_compile_time_secs', 0.0000000000001)

You may also be interested in https://github.com/google/jax/pull/21394

I think we should update the docs to explain all the relevant flags, now that we also have LRU eviction.

Great, thanks both for the heads-up, I'll rename the issue to doc updates.
I cannot update the label, unfortunately.

@epignatelli Do you want to send a PR to update the doc?

Hi @ayaka14732, I haven't worked on JAX and this would be my first issue in this repo but if it is something that I can solve, I would love to open the PR.

@Bhavay-2001 Thank you for the interest, but let's see if @epignatelli would like to open the PR first.

Alright @ayaka14732. Any other minor issue from which I can start working with jax. I will start to learn and implement it in the coming days and then proceed with more advanced issues. Thanks

@Bhavay-2001 Great question! You can open a discussion in https://github.com/google/jax/discussions and maybe other maintainers can give you suggestions

Seems that @keshavb96 is working on this. Let's fix this on their side.

@ayaka14732 since #21819 is merged, can we close this issue?

Forgot this! Thanks!


[Error] breakpoint(... down) wrong?

Given I have the following scss:
@include breakpoint(mobile) {
    color: #000;
}

@include breakpoint(mobile down) {
    color: #111;
}

The generated css looks like this:
@media screen and (min-width: 28.125em) {
    color: #000;
}

@media screen and (max-width: 39.9375em) {
    color: #111;
}

But in my understanding this is not "mobile down". Instead this is the next greater breakpoint down, so all "large" screens also already get this styles!?
I think booth media queries should have the same value of: 28.125em

Have you tried mobile only?

Nope, but the only keyword wouldn't be a fix for this.
 This is a holdover from Foundation 5's -down CSS classes, which meant the same thing.
I'd encourage you to write your media queries entirely mobile first if possible, which negates the need for only and down ranges for the most part.

We try to not use it where possible, but somtimes we have the usecase :)
But when we know that it means mobile AND down, which isn't that clear by the docu in my mind, I'm happy ;)

I agree. The documentation on what down means could actually be better. I just banged my head on why my custom breakpoint wasn't working.
I had ...
$breakpoints: (
  small: 0,
  medium: 640px,
  large: 1024px,
  xlarge: 1200px,
  xxlarge: 1440px,
  menu: 1000px,
);

I was trying #{breakpoint(menu down) and was super confused why it wasn't working.


Update significant figures on methods

Several methods currently are able to return repeating decimals or irrational numbers. We should either standardize the level of precision that our methods return or (better) add in an additional optional argument to specify the level of precision.
This would require updating several of the methods but seems necessary for users to have consistent results.

Is this something you could take on @FranceJ ? Or should it be broken out into several issues?


Killing and restarting instance

What will happen with existing sell orders when the instance is killed and restarted?

Ok, i got it by myself - nothing, just reporting about completion


Selecting mat-option which has no value set fires valueChange and selectionChange events twice.

Bug, feature request, or proposal: Bug
What is the expected behavior?
When a mat-option with no value set, the event valueChange and selectionChange events are fired once.
What is the current behavior?
Those two events are fired twice.
What are the steps to reproduce?
https://angular-e2cc3n.stackblitz.io
Select the first option, which has no value set, and look at the console log, you will see the two events are fired twice.
What is the use-case or motivation for changing an existing behavior?
In some use cases, some XHRs are triggered by responding to these events. When the event is fired twice, the XHRs is triggered twice, which may have unexpected effect.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Material 6.3.3
Is there anything else we should know?

Duplicate of https://github.com/angular/material2/issues/10675.

This is not exactly the same as #10675.
#10675 is about when the option is selected the second time, change event is fired, but shouldn't.
This bug is about when the option is selected the first time, change event is fired twice, but should be fired only once.

I think the fix should cover both cases, otherwise we can reopen this one.


eCash prefix & derivation path

:tada: This PR is included in version 1.0.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Changing session_id to cookies

Below is just a rough draft of what the changes could look like. Someone pls help to implement them.
The backend can set cookies in the frontend via Response from fastapi:
from fastapi.responses import Response

@app.post("/sessions",  status_code=200)
async def user_login(r: rm.UserLogin, response: Response):
    result = sf.user_login(r.username, r.password)
    response.set_cookie(key="session_id", value=result['session_id'])
    return result

The session_id for all the other APIs can then be obtained from the cookies via Cookie from fastapi:
from fastapi import Cookie

@app.delete("/questions/{question_id}", status_code=200)
async def delete_question(question_id: str, session_id: str | None = Cookie(None)):
    return qf.delete_question(question_id, session_id)

Then finally, the session_id key needs to be removed from the request models, else it'll cause an error when the payload doesn't contain session_id:
class DeleteUser(BaseModel):
    session_id: str  # to be removed

Maybe we should also set the cookie's expiration date too, in the case where the session id also expires after a set amount of time

Also, to change the get_session and user_logout API URLs to respond to cookie session_id instead of having the ID in the URL:
ie. will needa change these 2 functions:
@app.get("/sessions/{session_id}",  status_code=200)
async def get_session(session_id: str):
    return sf.get_session(session_id)

@app.delete("/sessions/{session_id}",  status_code=200)
async def user_logout(session_id: str):
    return sf.user_logout(session_id)


Improve leniency of --no-modules output

Instead of assuming names like URL and Request are defined, instead
check to see if they exist first and otherwise skip the checks that
reference them.

cc https://github.com/rustwasm/wasm-pack/issues/689, the original motivator


Transaction flow

Current state:
I've implemented a layer on top of the both mesh (persistent) and TX mempool (in-memory) that stores txs organized by account and nonce. This layer has the logic to project an account's nonce and balance based on internally stored txs. All necessary hooks have been put in place to update this layer, for both mesh and TX mempool.
The next major step is using this layer to decide which TXs enter the mempool, which are put into blocks and which are finally chosen to be applied to the global state.
Smaller TODOs:

[ ] Calc and use TX fee instead of amount
[ ] Handle rejected txs from contextually invalid blocks
[ ] Handle concurrency
[ ] optimization Avoid storing lists in LDB objects

✅Automation passed
The following code was commented out:
https://github.com/spacemeshos/go-spacemesh/blob/8ea590f1a80db030d42730e9c18865c3ad53277c/miner/block_builder.go#L255-L259

✅Automation passed

✅Automation passed

✅Automation passed (with the exception of sync, due to test resource structure mismatch)

✅Automation passed (with the exception of sync, due to test resource structure mismatch)


Add 125 SU "Boqn Penev" in Sofia, Bulgaria

Even though there is no info talking about the subjects in the school, there are some aditionnal courses on a two languages - JavaScript and C++.
Site - www.125su.com

@juk4iuugmov lib/domains/com/125su: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@juk4iuugmov Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

The school with the same name has a different official domain, thus we have to double check that this domain belongs to the same school.

@juk4iuugmov Thank you for the clarification. Pull request merged.


Replace "root" in default connection string for SQL databases

Currently the docs and space-cloud init default to using the root user in the MySQL connection string. It would be better to use a different name like "user" to guide users away from actually connecting with the root user. Something like this:
conn: "user:my-secret-pwd@/project"

We need to fix this in the template.go file in the config folder. Need to fix this in the docs as well.

As far as I can tell this has to be changed in the config/generate.go.

@ledex you are right. My bad!


implement sin function

It'd be nice to have a function that would calculate the sine of whatever is passed in. Can someone write this please?
def sin(x):
"""Returns the sine value of x
"""

Perhaps write some tests too?

I got this.

I was going to do this but looks like it has been done? I suspect this issue can be closed.

@AFewMistakesAgo This has been implemented. I will close the issue, thank you!


The full Unicode 14 support for Android 10 or lower

What do you think? I think palm up and down and Heart hands are not good...

also i noticed moustache too

I'n going to modify the smileys and the heart hues
also there's like a lot of errors in these emoji

I'n going to modify the smileys and the heart hues also there's like a lot of errors in these emoji

It was actually made in scratch.mit.edu


change paths from root directory to current in build

at the moment when the app is built all the paths are related to the root drive, bot in asset-manifest.json and in index.html (below a snippet):
{
  "files": {
    "main.css": "/static/css/main.b751d087.chunk.css",
    "main.js": "/static/js/main.92f89f21.chunk.js",
    "main.js.map": "/static/js/main.92f89f21.chunk.js.map",
    "runtime-main.js": "/static/js/runtime-main.930faef0.js",
    "runtime-main.js.map": "/static/js/runtime-main.930faef0.js.map",

this makes the app not working if you host it in a subfolder and not in a root domain (e.g. it works on app.rawgraphs.io but not on rawgraphs.io/app).
I don't know if it's a matter of conventions, but i would simply remove the / from paths

You can change the value for "homepage" in package.json to indicate the subfolder rawgraphs will be served from.
I did get a bit confused about it at first but it is in fact dead simple, just do this:
 {
   "name": "rawgraphs-frontend",
-  "homepage": "https://app.rawgraphs.io",
+  "homepage": "/app/",
   "version": "2.0.0-beta.9",
   "private": true,
   "dependencies": {

I think this should allow serving the app from the "app" subfolder from any domain.

Would it be better to have "/" as the value in the distributed code?
This would by default allow anyone setting rawgraphs up to serve it from any domain.