EditText setError draw icon only once.

EditText setError works for some sec , right after it loose focus it only draw circle but not the icon.

What is the icon? I assume that it is the icon, but with tint, so it looks like a circle.

Clearing tint on EditText was causing an NPE. I just pushed an update. To clear tint just set tint to null.

It was just the usual error icon. Let me check the update.

Ok now its kinda embarrassing , how can I get the latest update of this library in my project using gradle  ?
Followed from your sample project I tried -
dependencies {
compile 'com.github.ZieIony.RandomData:person:4b76016d78'
}
but it dose not seems to work.
is there any way I can use the  latest update without downloading it as a zip file ?

RandomData is just a library used for generating random data for samples. You don't need it to use Carbon.
To use it you have to add JitPack as a source of Maven dependencies.
allprojects {
    repositories {
        maven { url 'https://jitpack.io' }
    }
}

Thanks but I was asking how to get the latest Carbon which you update very often,
Right now I am using
compile 'tk.zielony:carbon:0.14.0'
Its not the latest one right ? it was updated in Feb 10.
Now to get the latest update I am downloading carbon as a zip file. So I was looking for a way to get it with gradle.
I was just testing RandomData to see if it works,

Oh. Yes, all the things I'm updating every day are available only as a source code. You have to clone the repo, build the aar and include it in your project as a library module. I know that it's not very convenient, but in that way you can get each fix as soon as possible.
A while ago it was possible to use JitPack to get an aar from sources automatically. Pretty much like RandomData you mentioned. I believe it doesn't work now, because JitPack doesn't provide ConstraintLayout library (which is needed to compile Carbon).
The recent bugfixes don't seem to be critical and I'm in the middle of updating other things. That's why I don't want to release to Maven.

Ok , thanks, You can delete this comments about library adding since its not directly connected with the issue here.


Update README

Update README

Pull Request Test Coverage Report for Build 120

36 of 40 (90.0%) changed or added relevant lines in 6 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.1%) to 32.93%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/service/SofaBootReadinessCheckEndpoint.java
0
1
0.0%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/service/SofaBootReadinessCheckMvcEndpoint.java
28
31
90.32%

Files with Coverage Reduction
New Missed Lines
%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/startup/HealthCheckTrigger.java
1
91.67%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/service/SofaBootReadinessCheckEndpoint.java
2
82.76%

Totals

Change from base Build 118:
-0.1%

Covered Lines:
599

Relevant Lines:
1819

💛  - Coveralls


Update URLs in CrossCompilingHowTo

Summary
Updates the Linaro and QT URLs found in CrossCompileHowto.md to be the same URLs as listed before, just with their new locations, as the old ones were outdated 404s. These are the same exact downloads as before.
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[X] Docs
[ ] Build-related changes
[ ] Other, please describe:

If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[X] No

If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's body (e.g. Fixes: #xxx[,#xxx], where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature
[ ] Related documents have been updated (docs/docs/en)
[ ] Related tests have been updated

PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD

[ ] Yes, CHANGELOG.md is also updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

Thanks for contribution


Navigation compose

Hi,
I'm using navigation-compose version 2.4.1 and 2.4.0-alpha07
I have error when navigating back (pop()) reached the init route
But in [komposable-architecture]/ todo-sample this version 2.4.0-alpha07 working fine and version 2.4.1 error as the same
What is that problem?
How can I fix it?
Thank you!

The problem in following todo-sample


1029 | Two City Scheduling | C++

Title - Two City Scheduling
What will change - Solution for the problem 1029 of LeetCode Two City Scheduling.
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Hi! Please assign this issue to me.


impl. credential revocation with StatusList2021

I was able to successfully test it locally, a few minor comments left:

We should use a proper version tag for the revocation service Docker image instead of "latest"
When calling the get status list credential endpoint with an unknown list id, an error 500 is returned - should be 404
We should double check which of the C-X issued credentials are revocable, I would argue that the BPN credential is not
What is the reason to update the lists only once a day and not immediately after a revocation?


Replacing ExampleScript with SimplePlaythrough

Implemented SimplePlaythrough MonoBehaviour, acting as a simple controller of a Playthrough class instance and featuring standalone functionality.
Users can opt to use the Standalone features, which hook into simple Player and Actor MonoBehaviours, which will be updated moving forward - or opt out and manually use the exposed public functions the SimplePlaythrough monobehaviour has.
With this change comes included two new scenes featuring identical functionality, acting as example of both Standalone and External implementations.

Hey Ben - I addressed the feedback of converting the SimplePlaythrough to a singleton. I do think there are some downsides to this approach that may be worth considering when looking at more complex systems like the plug and play:

singleton can be requested inside of Playthrough entities, which means an object in service to the playthrough can start commanding it, which nullifies that hierarchy. (Players do have some ability to command the SimplePlaythrough ofc, but i dont think Actors should). Any exposed functionality for other systems would carry the risk of playthrough entitties calling them as well.
pinging for the singleton on Awake is alright, but I think users would want that specific control of Registering/Unregistering be it at edittime or runtime as pinging every x seconds is not ideal (note: Awake functions trigger in any order, so the playthrough can have its awake called after the _actor and _player, works better in unreal as I think the game mode script takes priority over any world entities).
i think message handling would be a bit awkward as well, registering to it directly means duplicating code in the simpleplaythrough, and exposing the playthrough event is out of the question imo (don't want users doing SimplePlaythrough.Playthrough.Disconnect() for example, without the Simple knowing)

Feedback from previous review should be addressed. I've also updated to accomodate for the latest SDK updates. Bumping this for review


Use of EXLA in Gradient Boosting guide

Hey, recently it was added to the Cross-validation with gradient boosting trees guide the use of EXLA as default backend. However, using EXLA with the XGBoost library seems to break when I run the first training cell. Using Nx.BinaryBackend works fine though.
** (FunctionClauseError) no function clause matching in Jason.Encoder.Nx.Tensor.encode/2

    The following arguments were given to Jason.Encoder.Nx.Tensor.encode/2:

        # 1
        #Nx.Tensor<
          f32
          EXLA.Backend<host:0, 0.2818844854.1719009302.198012>
          NaN
        >

        # 2
        {#Function<3.65781566/3 in Jason.Encode.escape_json>,
         #Function<1.65781566/3 in Jason.Encode.map_naive>}

    Attempted function clauses (showing 4 out of 4):

        def encode(%Nx.Tensor{data: %Nx.BinaryBackend{state: <<32704::integer-native-size(16)>>}}, _opts)
        def encode(%Nx.Tensor{data: %Nx.BinaryBackend{state: <<32256::integer-native-size(16)>>}}, _opts)
        def encode(%Nx.Tensor{data: %Nx.BinaryBackend{state: <<2_143_289_344::integer-native-size(32)>>}}, _opts)
        def encode(%Nx.Tensor{data: %Nx.BinaryBackend{state: <<9_221_120_237_041_090_560::integer-native-size(64)>>}}, _opts)

    (exgboost 0.4.0) lib/exgboost/internal.ex:114: Jason.Encoder.Nx.Tensor.encode/2
    (jason 1.4.1) lib/encode.ex:188: Jason.Encode.map_naive/3
    (jason 1.4.1) lib/encode.ex:37: Jason.Encode.encode/2
    (jason 1.4.1) lib/jason.ex:162: Jason.encode!/2
    (exgboost 0.4.0) lib/exgboost/dmatrix.ex:310: EXGBoost.DMatrix.from_tensor/2
    (exgboost 0.4.0) lib/exgboost.ex:215: EXGBoost.train/3
    #cell:gresv4jlhl6cp5ab:2: (file)

You can do Nx.backend_transfer or Nx.backend_copy accordingly. Can you please send a PR?
Maybe EXGBoost could raise a clearer message here too /cc @acalejos

Yes this is a known limitation of EXGBoost currently.
https://github.com/acalejos/exgboost/issues/41
Errors should be more verbose at least in the meantime until EXLA is better supported, but this overall is an issue with EXGBoost and not Scholar

In particular this is the cause of the issue
https://github.com/acalejos/exgboost/issues/22

@josevalim @santiago-imelio
I just pushed a patch to EXGBoost v0.5.1 that should fix this. I can make a PR here to update the notebook here


Fix typo

Removes extra semicolon in for loop example

You absolute madman.

Is there such a thing as a commit of the year award? Because I think I'd win it with this epic contribution.


Show avatar shape as square

Hello all,
I'd like to make the avatar image show as the original square image file rather than show a circle. Is there a flag or something I can change to do this?
Kind regards
Lee

Add a CSS Plugin with code along the lines of:
.portrait {
border-radius: initial !important;
}

For support, refer to the forums.


[bug]: Continuous Python errors after start.

Is there an existing issue for this problem?

[X] I have searched the existing issues

Operating system
Linux
GPU vendor
Nvidia (CUDA)
GPU model
3060
GPU VRAM
12gb
Version number
5.0.2
Browser
Brave (but doesn't matter for this bug)
Python dependencies
accelerate 0.30.1
compel 2.0.2
cuda 12.1
diffusers 0.27.2
numpy 1.26.4
opencv <IP_ADDRESS>
onnx 1.15.0
pillow 10.4.0
python 3.10.14
torch 2.2.2+cu121
torchvision 0.17.2
transformers 4.41.1
xformers 0.0.25.post1
What happened
I am not sure when this issue started, or even if it is an issue, but when I start invoke 5.0.2 it has a continuous stream of python errors. I am not sure when it started because I didn't notice it until yesterday after I had an unrelated system crash. I have the error log attached. Apologies for its size, I started the log, and then was pulled away to something else.
error.log
It does not appear to affect the ability for InvokeAI web interface to function, and I was able to generate several images even while this string of errors continue to occur. It may be related to a recent nVidia driver update, but this may have been happening ever since 5.0 released. I am sorry that I cannot nail it down further.
What you expected to happen
No errors on launch
How to reproduce the problem
For me, just starting invoke.sh  and choosing option 1 immediately causes the errors to start.
Additional context
I attempted to reinstall from the installer twice, the first time just running the installer, and the second time removing the .venv folder first. Neither helped.
Discord username
No response

The error relates to the python logging module. It looks like the app is attempting to output some log messages, but the destination for the logs is borked.
Did you maybe specify an alternate logging method in the invokeai.yaml file? If not, it's trying to log to the console/terminal, in which case the error sounds like something's gone sideways with your system...

Here is the contents of my invokeai.yaml

Internal metadata - do not edit:
schema_version: 4.0.2
Put user settings here - see https://invoke-ai.github.io/InvokeAI/features/CONFIGURATION/:
host: <IP_ADDRESS>
port: 42422
ram: 8.0
log_handlers:

console
file=/home/master/invokeai/invokeai.log
syslog=localhost

log_level: debug

I was logging, and the log file was 252mb in size. I deleted that file and restarted invokeai. I was still getting the same string of errors, and I stopped the process. A new invokeai.log file was created, which I've attached here.

[2024-10-06 11:00:39,476]::[InvokeAI]::INFO --> Patchmatch not loaded (nonfatal)
[2024-10-06 11:00:40,127]::[InvokeAI]::INFO --> Using torch device: NVIDIA GeForce RTX 3060
[2024-10-06 11:00:40,253]::[InvokeAI]::INFO --> cuDNN version: 8902
[2024-10-06 11:00:40,272]::[uvicorn.error]::INFO --> Started server process [1446991]
[2024-10-06 11:00:40,273]::[uvicorn.error]::INFO --> Waiting for application startup.
[2024-10-06 11:00:40,274]::[InvokeAI]::INFO --> InvokeAI version 5.0.2
[2024-10-06 11:00:40,277]::[InvokeAI]::INFO --> Root directory = /home/master/invokeai
[2024-10-06 11:00:40,277]::[InvokeAI]::INFO --> Initializing database at /home/master/invokeai/databases/invokeai.db
[2024-10-06 11:00:40,278]::[InvokeAI]::DEBUG --> Registered migration 0 -> 1
[2024-10-06 11:00:40,279]::[InvokeAI]::DEBUG --> Registered migration 1 -> 2
[2024-10-06 11:00:40,279]::[InvokeAI]::DEBUG --> Registered migration 2 -> 3
[2024-10-06 11:00:40,279]::[InvokeAI]::DEBUG --> Registered migration 3 -> 4
[2024-10-06 11:00:40,280]::[InvokeAI]::DEBUG --> Registered migration 4 -> 5
[2024-10-06 11:00:40,280]::[InvokeAI]::DEBUG --> Registered migration 5 -> 6
[2024-10-06 11:00:40,280]::[InvokeAI]::DEBUG --> Registered migration 6 -> 7
[2024-10-06 11:00:40,281]::[InvokeAI]::DEBUG --> Registered migration 7 -> 8
[2024-10-06 11:00:40,281]::[InvokeAI]::DEBUG --> Registered migration 8 -> 9
[2024-10-06 11:00:40,281]::[InvokeAI]::DEBUG --> Registered migration 9 -> 10
[2024-10-06 11:00:40,282]::[InvokeAI]::DEBUG --> Registered migration 10 -> 11
[2024-10-06 11:00:40,282]::[InvokeAI]::DEBUG --> Registered migration 11 -> 12
[2024-10-06 11:00:40,282]::[InvokeAI]::DEBUG --> Registered migration 12 -> 13
[2024-10-06 11:00:40,282]::[InvokeAI]::DEBUG --> Registered migration 13 -> 14
[2024-10-06 11:00:40,283]::[InvokeAI]::DEBUG --> Registered migration 14 -> 15
[2024-10-06 11:00:40,284]::[InvokeAI]::DEBUG --> Database is up to date, no migrations to run
[2024-10-06 11:00:40,287]::[ModelInstallService]::DEBUG --> Installer thread<PHONE_NUMBER>04448 starting
[2024-10-06 11:00:40,288]::[ModelInstallService]::DEBUG --> Installer thread<PHONE_NUMBER>04448 polling
[2024-10-06 11:00:40,313]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-2 (_download_next_item) starting.
[2024-10-06 11:00:40,314]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-3 (_download_next_item) starting.
[2024-10-06 11:00:40,314]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-4 (_download_next_item) starting.
[2024-10-06 11:00:40,315]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-5 (_download_next_item) starting.
[2024-10-06 11:00:40,315]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-6 (_download_next_item) starting.
[2024-10-06 11:00:40,363]::[InvokeAI]::INFO --> Pruned 174 finished queue items
[2024-10-06 11:00:40,365]::[InvokeAI]::DEBUG --> Waiting for next polling interval or event
[2024-10-06 11:00:40,539]::[InvokeAI]::INFO --> Cleaned database (freed 5.48MB)
[2024-10-06 11:00:40,540]::[uvicorn.error]::INFO --> Application startup complete.
[2024-10-06 11:00:40,540]::[uvicorn.error]::INFO --> Uvicorn running on http://<IP_ADDRESS>:42422 (Press CTRL+C to quit)
[2024-10-06 11:00:41,288]::[ModelInstallService]::DEBUG --> Installer thread<PHONE_NUMBER>04448 polling
[2024-10-06 11:00:41,367]::[InvokeAI]::DEBUG --> Waiting for next polling interval or event
[2024-10-06 11:00:42,289]::[ModelInstallService]::DEBUG --> Installer thread<PHONE_NUMBER>04448 polling
[2024-10-06 11:00:42,367]::[InvokeAI]::DEBUG --> Waiting for next polling interval or event
[2024-10-06 11:00:43,146]::[uvicorn.error]::INFO --> Shutting down
[2024-10-06 11:00:43,247]::[uvicorn.error]::INFO --> Waiting for application shutdown.
[2024-10-06 11:00:43,248]::[ModelInstallService]::DEBUG --> calling stop_event.set()
[2024-10-06 11:00:43,289]::[ModelInstallService]::INFO --> Installer thread<PHONE_NUMBER>04448 exiting
[2024-10-06 11:00:43,314]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-2 (_download_next_item) exiting.
[2024-10-06 11:00:43,315]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-3 (_download_next_item) exiting.
[2024-10-06 11:00:43,315]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-4 (_download_next_item) exiting.
[2024-10-06 11:00:43,315]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-5 (_download_next_item) exiting.
[2024-10-06 11:00:43,316]::[DownloadQueueService]::DEBUG --> Download queue worker thread Thread-6 (_download_next_item) exiting.
[2024-10-06 11:00:43,316]::[uvicorn.error]::INFO --> Application shutdown complete.
[2024-10-06 11:00:43,317]::[uvicorn.error]::INFO --> Finished server process [1446991]

The "going sideways with my system" is what I'm worried about. If that is the case, any clue where I should start looking?

My guess is a problem with the system API with which SysLogHandler interacts. Does commenting out the logging config fix it?
You could write a simple python script outside the Invoke venv with that same SysLogHandler (per python docs) to see if the issue occurs only in the context of Invoke or if it's truly a system issue. Not sure where to go from there, sorry!

OK, I commented out all the logging lines:
#log_handlers:
- console
- file=/home/master/invokeai/invokeai.log
- syslog=localhost
And was still getting all the errors.  Then I commented this last one:
#log_level: debug
And that seemed to solve it. Hopefully this isn't indicative of something borked in my system, though if it is it might be a good opportunity to switch my server backend to a different flavor of nix.

The messages you pasted in this comment are not errors. Those messages are expected when you set the log level to debug.
The attached log in the first post of this issue have actual errors. Sounds like you've got taht sorted now.
If you are seeing no errors/exceptions, I think everything is fine. Sorry for any misunderstanding.


Crash in ColorView - NULL pointer access

Hello
This is a great project, Thanks for sharing.
Also, the documentation and samples are amazing.
Today, I tried to build the library from source code (Windows 11, VS 2022)
When I run nappgui_src\build\Debug\bin\colorview.exe and click on any color
I get the message (NULL pointer access)
File: oscontrol.cpp
Line: 470
Greetings,
Mahmoud

Hi @MahmoudFayed!
The crash has been fixed in this commit: https://github.com/frang75/nappgui_src/commit/761ce9ab81a33f74f7591609f02508d5da2c1dc7
Thanks for report and welcome to NAppGUI.

Thank you very much


Explanation about to remove directory is not clear

This is a Bug Report
Problem:
The explanation about to remove created directory configure-pod-container is not much clear in Configure a Pod to Use a ConfigMap page
Proposed Solution:

If you created a directory configure-pod-container and no longer need it, you should remove that too, or move it into the trash can / deleted files location.

to be replaced as
If you created a directory configure-pod-container and no longer need it, you should remove that too, or move it into the trash.
Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#cleaning-up

/language en
/assign

Hello @tamilselvan1102 , the original content reads fine to me, even as a non-native English speaker. Please can you advise why the sentence is unclear?

@divya-mohan0209
The context is understandable that what mean to say but not much clear.
I am having following suggestions .

In this context already suggested  you should remove  or move it into the trash .
After that again repeating deleted files location

Remove can : If you created a directory configure-pod-container and no longer need it, you should remove that too, or move it into the trash / deleted files location.

@divya-mohan0209
looking for suggestion. I want to raise a PR after you point of view.

I am having one more thought about it.
There is a possibility to misunderstood about [/] in the context. weather [/] is representing the meaning of [OR] or root directory  because it explaining about directory

Closing the issue because not accepted.
Thank you

/close


Main panel of screen hidden by CSS

I've found that using this theme causes the main panel of any screen to be hidden, leaving only the side bars. I've narrowed it down to this line in app.css, which when commented out fixes the issue. My guess is the comma before .desktoproutes but I'm not completely sure what this line is meant to be doing!
Line 517 of Comfy-spicetify/app.css
.Root__main-view > div:first-of-type > div, .desktoproutes-homepage-takeover-ad-hptoComponent-parentContainer {
  display: none;
}

I'm using Spicetify 2.9.1 on Spotify for Windows <IP_ADDRESS>3.gc2965cdf.

Also /assets/_ad.scss

Cuz app.css is just the compiled version ;)

Same problem here, I guess we just have to wait for the dev to patch things up

Done

Fantastic! Thank you very much.


testFuture waiting for every

hi:
I'm reading the source code of  failsafe.
refactor from "net.jodah.failsafe.FailsafeFuture" to  "net.jodah.failsafe.future.FailsafeFuture"
then fixed the compile error for the package .
after compile passed ,  run the test case    AsyncFailsafeTest.testFuture  , but   it waitng forever !!!!
if i restore the  "net.jodah.failsafe.future.FailsafeFuture"  to  "net.jodah.failsafe.FailsafeFuture" it worked , why ???

is it a potential bug

i resolve it  ,  FailsafeFuture overload several "inject" method , when i moved it to other packages ,
AsyncFailsafe choose the visible inject method


flexalloc: Add opts struct to open call

We have two open calls in the api, one for a single device and one for single
device + a metadata device. This makes the code a bit ugly so this commit
introduces a parameter struct to the open call.
Signed-off-by: Adam Manzanares<EMAIL_ADDRESS>

@Joelgranados @jwdevantier can either of you update the python bindings. The C tests currently pass but there is segfault when hitting the python lib tests.


Build and Deployment pipeline - Limit workflow runs to the main repo so it will not try to run on a fork

The Build and Deploy Audit Image workflow is not limited to executing on a fork.  If it were to execute on another fork it would fail since the fork will not (and should never have) the secrets necessary for it to execute successfully.  Therefore the workflow should be limited to only run from the main repository where the necessary secrets are available.
Task:
Update the workflow with a conditional statement to ensure it will only run when executed from the main repository where the necessary secrets are defined.
Example:

https://github.com/hyperledger/aries-cloudagent-python/blob/421c4ed6a3f750c7f30af7b85d1481a762a5acc4/.github/workflows/nightly-tests.yml#L10

Acceptance Criteria:

The workflow will only execute on the main repository and it will not execute on any other fork.

@cvarjao, @rajpalc7, here is another enhancement or the workflow.

Ticket is completed now. Ready for demo today


Dllbuild

This adds a new kind of build, the dllbuild. This generates a DLL that can be injected into the original game and replace the implemented functions with our own.
It comes with several caveats that need to be documented before merging.

Overall looks very good to me :D


Added new amq version 1.5 and update application template version to 1.4.17

Signed-off-by: Howard Gao<EMAIL_ADDRESS>

@gaohoward, I'm not sure if we can merge/release these before sprint-25, as we're well past sprint-24, i.e. these may have to wait and be released with sprint-25.

@rcernich ok thanks.


Fix imports and add main function

@ocefpaf  -- once you merge this the commit will be added to your PR on the main repo. Feel free to just poach the changes instead of merging this if you want.

Thanks!


Runtime Stylx readme enhancements to clarify Runtime use

@mbranscomb recommended the following changes to the stylx readmes to clarify the runtime usage:

[x] Remove “ArcGIS Runtime 10.3+” from the readme.md (under requirements) – there is no 10.3 release of ArcGIS Runtime. The next release will be ‘Quartz’.
[x] Remove discussion of deploying the .dat files into the runtime symbols folder – we only support the symbol dictionaries which shipped with the product (CSM Note: pre-Quartz).

https://github.com/Esri/military-features-data/tree/master/data/mil2525c/stylxfiles
https://github.com/Esri/military-features-data/tree/master/data/mil2525c/dictionary

Fixed in https://github.com/Esri/military-features-data/pull/199


ClientUser.setAvatar() does not work on selfbots (needs email)

When attempting to use setAvatar on a selfbot/userbot, the response from the API is 400, with the specific message:
text: '{"email": ["This field is required."]}',
Since selfbots are in the proper oauth2 scope, the email is available through ClientUser.email. This could be used directly as needed in the setAvatar call to the API.

Fixed in https://github.com/hydrabolt/discord.js/commit/fbcea236c53ab19bb74928933d0d144141403312 install from indev to get fixes will be released with 9.2.1


Bluetooth: controller: Check for ticker operation failure

Add assert check to detect failure to enqueue ticker
operations. This will avoid HCI thread from stalling
forever on k_sem_take.
This assert will trigger on design fault, not defining
enough queued ticker operations count.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

This will fail during init, as ull_conn::ull_conn_reset() calls disable() and thus ticker_stop() on all possible conn handles. These calls all return with TICKER_STATUS_FAILURE and thus will trigger the assert.
I realized this just now as I did a test of this. Somehow another check is needed to handle this.

Morten and I have been discussing this. Out of which came a thought/suggestion.
Since we can get a FAILURE return code from ticker_start()/ticker_stop() through different paths, one of which does not lead to a call of ull_ticker_status_give(), and since we can not have unmatched take()/give() we thought of adding a flag to the return value (though *ret_cb) in ull_ticker_status_take() indicating wether a k_sem_take() was actually performed (ie ret != FAILURE). This will then allow ull_ticker_status_give() to check and clear this flag, and only perform k_sem_give() if needed.

Thinking and writing a bit more - simply checking the sem_count in give and only give if there is a need ;-)
Goes against all I believe, but there you are - only give when asked, I guess.

only give when asked

This does not work because in cases where semaphore is given in ISR, the semaphore in most cases is given first.
Giving more thought, ret and *ret_cb  can be used to detect ticker failure.
LL_ASSERT(ret == TICKER_STATUS_SUCCESS || *ret_cb != TICKER_STATUS_BUSY)
Will test later in the day.

Excellent, thanks - yeah I had realized when I woke up @ 4am thinking about this;-)
I will test this on target this morning

@erbr-ot @mtpr-ot  I keep this PR DNM until I get a message from you that your issues have found a root cause. Lets give this PR 5 days.


duplicate symbol '_GetDirectoryOfType'

Steps to Reproduce

add  dependencies
dependencies:
path_provider: ^1.4.0
flutter_sound: ^1.5.1
console
flutter run   on  ios  simulator IPhone 8 Plus
error

duplicate symbol '_GetDirectoryOfType' in:
        /Users/FlutterWorkspace/flutterdemo/build/ios/Debug-iphonesimulator/flutter_sound/libflutter_sound.a(FlutterSoundPlugin.o)
        /Users/FlutterWorkspace/flutterdemo/build/ios/Debug-iphonesimulator/path_provider/libpath_provider.a(PathProviderPlugin.o)
    ld: 1 duplicate symbol for architecture x86_64

Logs
 1 warning generated.
    === BUILD TARGET Runner OF PROJECT Runner WITH CONFIGURATION Debug ===
    duplicate symbol '_GetDirectoryOfType' in:
        /Users/FlutterWorkspace/flutterdemo/build/ios/Debug-iphonesimulator/flutter_sound/libflutter_sound.a(FlutterSoundPlugin.o)
        /Users/FlutterWorkspace/flutterdemo/build/ios/Debug-iphonesimulator/path_provider/libpath_provider.a(PathProviderPlugin.o)
    ld: 1 duplicate symbol for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)

Could not build the application for the simulator.
Error launching application on iPhone 8 Plus.

flutter doctor -v
[✓] Flutter (Channel dev, v1.10.14, on Mac OS X 10.15 19A602, locale zh-Hans)
    • Flutter version 1.10.14 at /Users/issmac/Library/Android/flutter
    • Framework revision 1946fc4da0 (3 weeks ago), 2019-10-07 15:23:31 -0700
    • Engine revision 1d62160fdb
    • Dart version 2.6.0 (build 2.6.0-dev.1.0 d6c6d12ebf)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/issmac/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.8.3

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.2.2
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] VS Code (version 1.39.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Redmi Note 4  • AQZ5JZ89IJ65OFOR                     • android-arm64 • Android 6.0 (API 23)
    • iPhone 8 Plus • 398E1090-0C64-4FF3-8546-D36D8D0B2D88 • ios           • com.apple.CoreSimulator.SimRuntime.iOS-13-1 (simulator)

! Doctor found issues in 1 category.

Anothor
I found the code ### GetDirectoryOfType but do not known how to solve it
in  flutter_sound/FlutterSoundPlugin.m
NSString* GetDirectoryOfType(NSSearchPathDirectory dir) {
  NSArray* paths = NSSearchPathForDirectoriesInDomains(dir, NSUserDomainMask, YES);
  return [paths.firstObject stringByAppendingString:@"/"];
}

in  path_provider/PathProviderPlugin.m
NSString* GetDirectoryOfType(NSSearchPathDirectory dir) {
  NSArray* paths = NSSearchPathForDirectoriesInDomains(dir, NSUserDomainMask, YES);
  return paths.firstObject;
}

Last
Hoping flutter more  and more  better !

@songshitong It seems not to be related to Flutter sdk, but to implementation of flutter_sound. The issue is open here https://github.com/dooboolab/flutter_sound/issues/146 and is related to https://github.com/dooboolab/flutter_sound/pull/141 commit in v1.5.0. Before that is fixed I think you can use lower version of flutter_sound. Closing the issue here.


scanner with upper bound

scanner with upper bound.
ref https://github.com/pingcap/tikv/issues/1467
@BusyJay @siddontang PTAL

LGTM

Any test to cover upper bound and no upper bound?

Tests in test_select.rs has covered scan with upper bound and without upper bound.

LGTM

CI failed @zhangjinpeng1987


decodeUri errors out on % trailing on the url

Put these urls into chrome:
Examples:
https://reacttraining.com/react-router/web/guides/quick-start?test=0%
https://twitter.com/mjackson?test=0%

This should be fixed in #445


Airflow tasks get queued and never executed on redis-py 3.0.0

redis-py has updated new version to 3.x.x. and my Airflow tasks get queued and never executed.
See https://github.com/andymccurdy/redis-py#upgrading-from-redis-py-2x-to-30
And from Airflow https://github.com/apache/incubator-airflow/blob/v1-10-stable/setup.py#L203 it wrote 'redis>=2.10.5'
I don't know why I fork your repo and cannot make a PR
I created a PR here https://github.com/prideloki/docker-airflow/pull/1

Now they have redis>=2.10.5,<3.0.0. Airflow returns such error: "Unrecoverable error: AttributeError("'float' object has no attribute 'items'",)"
You can add 'pip install redis==2.10.6' before celery[redis] installation - its temporary but quick solution.


Extremely slow when generic relationships

Hello
I have a view showing the result of a model having generic relationships.
This template produces a 544 sql  queries (surely I will fix this) but the toolbar says that it 'only'
took 400ms.
Nonetheless the time to load the page varies from 30sec to 1minute.
Disabling the SQL panel seems to fix the problem.
Django 1.11
Django-debug-toolbar 1.8 and 1.9.1 (tried both)

Closing in favor of #1402


(400): 'submitted-url' and 'media-key' can not be both empty

I have recently started getting this error when using the add_company_share method. I am passing 'submitted-url' and 'submitted-image-url' into the content section, as indicated by the documentation here: https://developer.linkedin.com/docs/company-pages#company_share
For the life of me I can't find media-key anywhere in the documentation. What am I missing here? Any help would be appreciated.
Actual post code:
result = client.add_company_share(published_post.channel_account.channel_id, { comment: scheduled_post.post_text, content: { 'submitted-image-url' => scheduled_post.post_image.url,  'submitted-url' => scheduled_post.link  } })

Hrm... weird I haven't heard of media-key either.
Have you tried setting media-key to blank?

I just set media-key to blank and the post went through. Odd. Closing this issue, thanks for the help.

I just want to add content by myself and share a image with it and there is no url of any content. So i dont want to send submitted-url. When i tried that, it does not get posted and give the above error :+1:
"'submitted-url' and 'media-key' can not be both empty". So i changed it to below but still the error is coming
{"visibility":{"code":"anyone"},"comment":"testing","content":{"media-key":"","submitted-image-url":"http://brsresults.files.wordpress.com/2015/06/dodge-durango-ron-burgundy-asleep-at-the-wheel.jpg"}}

I just started encountering this problem in my app. I've set 'media-key => ''in my options hash but I still get the error whenever I'm not submitting asubmitted-url, even if I just set 'submitted-url' => ''` in my hash. This is strange because LinkedIn doesn't require you to include a link when posting a share through their native UI.

As best I can tell, you must include Submitted URL, Image URL, and media key in order to post anything that is not just a plain text post.
Justin Bolles connectthink
O |<PHONE_NUMBER>
C |<PHONE_NUMBER>
www.connectthink.com
On Mon, Nov 2, 2015 at 12:33 PM, Daniel Bonnell<EMAIL_ADDRESS>wrote:

I just started encountering this problem in my app. I've set 'media-key => ''in my options hash but I still get the error whenever I'm not submitting asubmitted-url, even if I just set 'submitted-url' => ''` in my hash. This is strange because LinkedIn doesn't require you to include a link when posting a share through their native UI.
Reply to this email directly or view it on GitHub:
https://github.com/hexgnu/linkedin/issues/258#issuecomment-153094280

So do I need to be submitting shares without a media-url as a comment?

yes, that will work


feat: short exact sequence of free modules

We prove that if the left and right term in a short exact sequence of modules are free, then the middle term is free as well, and related results.

Thanks for the quick review! I've resolved all your comments and added the rank formula you asked for

Thanks!
bors merge


chore: remove old issue template

This PR removes the old and unused PR template.

What kind of change does this PR introduce?
chore

Did you add tests for your changes?
No

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Nothing

This is still in use: https://github.com/webpack/webpack/issues/new

Ok so we need these 4 in total?


how to change toast style ?

how to change border-radius ?

Right not its not possible

bgcolor可以不用string类型吗？能不能弄成接受Flutter里Colors这个类

@TopGuo Please check the latest version now you can use Colors Class from Flutter

Ok thank you.
this version 2.1.4 use Colors.


update dependencies adding django 4.1

Tested django-dynamodb-cache with Django 4.1.5 and Python 3.9

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

Coverage data is based on head (fe569e0) compared to base (722eec6).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   89.73%   89.73%
=======================================
  Files          11       11
  Lines         302      302
=======================================
  Hits          271      271
  Misses         31       31

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.


monthly retention time

hello,
I'm trying the add a kpi with on value per month.
This kpi is calculated on another system and cannot be computed using daily values ( nb of distinct user using the service: one customer can use the services 2 différents days and must be show as 1 customer ).
Is there a way to indicate carbon to keep one value per month ?
BR

Is there a way to indicate carbon to keep one value per month ?

Yes, you can configure the storage schema accordingly ...

Not exactly no. The size of a [whipser] datapoint must be a fixed multiple of a second (true months are not).
One point per day is a good way to capture this however; in combination with @piotr1212's suggestion to output it [daily]. (Which amounts to just over 4KB per year)
Be aware that in graphite 1 month == 30 days ; 1 year == 365 days (see graphite/render/attime.py)

Hi,
Thx for your answers.
I can'to do that because my "customer" want to have a montly vision.
He wants to know how much customer used the service in january for exemple.
I will propose to compute continuousely one sliding month but it won't
answer to his need.
BR.
2017-09-08 20:15 GMT+04:00 Piotr Popieluch<EMAIL_ADDRESS>
Is there a way to indicate carbon to keep one value per month ?
Yes, you can configure the storage schema accordingly, see:
storage-schemas.conf
https://graphite.readthedocs.io/en/latest/config-carbon.html#storage-schemas-conf
This kpi is calculated on another system and cannot be computed using
daily values ( nb of distinct user using the service: one customer can use
the services 2 différents days and must be show as 1 customer ).
Not sure if I understand this, why can't you compute that value more
often? eg (pseudo code), select distinct count(username) from logins
where login_date > day(-31) and schedule that every minute.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/issues/2031#issuecomment-328148098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AclTLc7ZgAcuYPNAdvwkH9Uu5r6F1zk0ks5sgWgfgaJpZM4PQ7XY
.


Update Source IP Tutorial: Replace Deprecated echoserver:1.4 with echoserver:1.10 for Compatibility

Description
This PR updates the Docker image used in the Source IP for Services tutorial to registry.k8s.io/echoserver:1.10, replacing the deprecated version 1.4. The existing image (echoserver:1.4) is no longer supported due to its use of Docker Image Format v1 and Docker Image manifest version 2, schema 1, which have been deprecated in Kubernetes.
By updating to echoserver:1.10, this PR resolves image pull errors.
Warning  Failed     5m19s (x4 over 6m59s)  kubelet            Failed to pull image "registry.k8s.io/echoserver:1.4": [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release.

Changes made
Updated the image in the deployment command from registry.k8s.io/echoserver:1.4 to registry.k8s.io/echoserver:1.10.
Impact

Resolves the ErrImagePull issue in the tutorial caused by the deprecation of the older image format.
Ensures compatibility with current Kubernetes releases.

Localization Note
The deprecated echoserver:1.4 image is also referenced in some localized documentation, such as the Russian, Japan and Korean versions. It is recommended that these versions be updated as well to echoserver:1.10 for consistency across all languages.
Issue
Closes: #

/approve


Add some examples

Can you please add some examples about how to use your script?
like :
./elasticsearch-stress-test.py es_address "<IP_ADDRESS>" indices 3 documents 10 clients 3 seconds 60

Hey @zhaohangbo!
Sorry for the delay, added some examples in the main README
Please let me know if you need anything else


How to achieve continuous RSSI read with FastBle?

I connected with a Ble peripheral and after connection establish i called BleManager.getInstance().readRssi(bd, rssiCallback); but its only called at once and break .
    scheduleTask4Rsii = Executors.newScheduledThreadPool(1);
    scheduleTask4Rsii.scheduleAtFixedRate(new Runnable() {
        public void run() {
            Log.i("Requesting Rssi: ",  "");
            BleManager.getInstance().readRssi(bd, rssiCallback);
        }
    }, 0, 1000, TimeUnit.MILLISECONDS);`

    final BleRssiCallback rssiCallback = new BleRssiCallback() {
    @Override
    public void onRssiFailure(BleException exception) {
        Log.i("Failed Reading Rssi: ", exception.getDescription());
    }

    @Override
    public void onRssiSuccess(int rssi) {
        Log.i("Device Rssi: ", rssi + "");
    }
};

Please reply soon. thanks

I meeting the same problem

compile 'com.clj.fastble:FastBleLib:2.2.4'


Bug: CSS injection through font-family in unicode command.

Issue Summary
A user is able to inject custom CSS even if commands like \style is disabled. The style gets rendered into the style attribute of the element containing the unicode character.
This occurs because the font-family is not correctly sanatized and only ' characters are escaped. Whatever is passed as the fontFamily gets shoved into the style attribute.
Steps to Reproduce

Go to any website that uses MathJax and allows the \unicode command.
Enter the following code into the parser \unicode[some-font; color:red; height: 100000px;]{x1234}.

Technical details

MathJax Version: 3.2.2 (latest commit: 8565f9da973238e4c9571a86a4bcb281b1d98d9b)
Client OS: Windows 10 Education 19045.3570
Browser: Chrome 119.0.6045.123

Thanks for your report, and minimal example.  I will make a PR to correct the issue.
If you are allowing user input to be displayed, it is probably best to use the safe extension to help reduce the problems that can be caused by a  malevolent user.  Unfortunately, it doesn't handle this particular issue, but you configure it to do so yourself using the following configuration:
MathJax = {
  loader: {load: ['ui/safe']},
  startup: {
    ready() {
      MathJax.startup.defaultReady();
      const safe = MathJax.startup.document.safe;
      safe.filterAttributes.set('fontfamily', 'filterFamily');
      safe.filterMethods.filterFamily = function (safe, family) {
        return family.split(/;/)[0];
      };
    }
  }
};

This will filter the fontfamily attribute (where the unicode extension puts the font) to remove the first ; and anything following that.  You could have it return null when there is a semicolon in the font name to have the safe extension remove the fontfamily attribute entirely.


Style: Improve readability, layout and contrast

Increases text contrast :eyes:
Some moar borders :moyai:
Fix overlapped / cut-off time values :clock3:

Have a look :point_down:

Except my two minor comments, it's a very nice addition, and I will happily merge this (and extra kudos for the second commit 💯  )

And this is live for everyone on kin.today ;) , sorry for the delay in getting this out.
You're also officially on the "contributor" plan now, thanks again for this PR ;)

@zowesiouff Thanks man, appreciate it.


Support lifetimes on traits

Is this feature (or lack thereof) the cause of this issue I'm having? I was going to create an issue, but saw that this issue already existed.


Non-exist docker image in rancher-images.txt file

Bug in v2.3.0-rc1
The rancher-images.txt file from the Github release page (https://github.com/rancher/rancher/releases/tag/v2.3.0-rc1) contains the image rancher/coredns-coredns:1.1.2 which does not exist.
>  docker pull rancher/coredns-coredns:1.1.2
Error response from daemon: manifest for rancher/coredns-coredns:1.1.2 not found: manifest unknown: manifest unknown

It breaks the bash scripts for loading and saving images.

@guangbochen @loganhz would you happen to know why is this not available? I see that this image is present in 2.3-dev branch for system-charts, and that's why it's getting added to rancher-images.txt
https://github.com/rancher/system-charts/blob/dev/charts/rancher-istio/0.0.1/values.yaml#L131
https://github.com/rancher/system-charts/blob/dev/charts/rancher-istio/0.0.2/values.yaml#L134

Seems the coredns:1.1.2 image was missing in the previous image mirror syncs.
Link to https://github.com/rancher/rancher/pull/22678, the rancher/coredns-coredns:1.1.2 will be pushed once this PR is merged.

Will wait for rc2 to validate this issue.

The bug fix is validated during install rc2.
the image rancher/coredns-coredns:1.1.2 is available now
>  docker images | grep coredns

rancher/coredns-coredns                     1.1.2                     8558f8c47fd7        16 months ago       46.4MB


update vendor

This is the pre-2.17 release go vendor update.
Noticeable change:
https://github.com/Azure/go-autorest/pull/508
but should not impact our users.
Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

:+1:

LGTM


Introduce malloc_trim on linux to fix dirty page leak

To begin please understand that mruby is not doing anything incorrectly. There is no issue with the way mruby allocates and releases memory and does not have a memory leak. This is a discussion on using the glibc malloc/realloc/free as default will not return dirty allocated pages back to the kernel managed heap automatically. This issue exists on any dynamic language using glib allocator.
Summary

The glib allocator doesn't return dirty pages back to the OS heap automatically until the program allocations meet rare conditions
Calling glib specific malloc_trim forces glib allocator to return dirty heap pages
I propose adding a call to malloc_trim on a major GC and as a final step in mrb_close
Asking for advice on the lowest impact way of adding this code

Research
Following up on @FooBarWidget absolutely wonderful research about the glibc allocator I wanted to test the same with mruby. The short summary from his research is by default glibc free does not automatically mark free pages as unused with madvise without hitting a frankly absurd page usage threshold.
This is not a new discovery. It is obscure though discussed elsewhere through the years, and on C Ruby

https://stackoverflow.com/a/47061458
https://stackoverflow.com/a/3860495
https://bugs.ruby-lang.org/issues/15667

We can force marking the free pages by calling the glib specific malloc_trim. The results I observed with mruby are the same as presented with C Ruby, which is not a surprise.
Here is what I used for a test program along with a Rake file for automation. First, I built libmruby.a from master using defaults, and then libmruby-gcpatched.a using this patch. It calls malloc_trim on a major GC cycle
diff --git a/src/gc.c b/src/gc.c
index fd4fb240..8d653dfb 100644
--- a/src/gc.c
+++ b/src/gc.c
@@ -19,6 +19,7 @@
 #include <mruby/gc.h>
 #include <mruby/error.h>
 #include <mruby/throw.h>
+#include <malloc.h>

 /*
   = Tri-color Incremental Garbage Collection
@@ -1314,7 +1315,7 @@ mrb_full_gc(mrb_state *mrb)
     gc->majorgc_old_threshold = gc->live_after_mark/100 * MAJOR_GC_INC_RATIO;
     gc->full = FALSE;
   }
-
+  malloc_trim(0);
   GC_TIME_STOP_AND_REPORT;
 }

I also used the excellent heap analyzer tool from @FooBarWidget, placing ptmallocdump.c and visualize_heap.rb along side.
// main.c
#include <stdlib.h>
#include <stdint.h>
#include <sys/types.h>
#include <unistd.h>
#include <mruby.h>
#include <mruby/compile.h>
#include <malloc.h>

#include "./ptmallocdump.c"

int main(int argc, char **argv) {
  uint64_t base_address = 0;
  uint64_t pid_offset = 0;
  uint64_t total = 0;
  char cmd[255];
  char buf[255];
  FILE *f;
  struct malloc_state* ptr = 0;
  uint64_t trim = 0;
  memset(cmd, 0, 255);
  memset(buf, 0, 255);
  if(argc > 1 && (strcmp(argv[1], "trim") == 0)) {
    trim = 1;
  }

  // debug libc in a different place depending on platform
  // debian buster kind of hides it in a non obvious location
  // /usr/lib/debug/.build-id/ef/dd27c16f5283e5c53dcbd1bbc3ef136e312d1b.debug
  // use objdump or gdb on libc.so to find the real location
  // these use 2.27 on ubuntu x64, 2.28 on ARM also works so far
  f = popen("objdump -t /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.27.so | grep ' main_arena' | awk '{ print $1 }'", "r");
  while(fgets(buf, sizeof(buf), f) != NULL) {
    base_address = strtoull(buf, 0, 16);
    break;
  }

  memset(buf, 0, 255);
  sprintf(cmd, "grep '/libc-2.27.so$' /proc/%i/maps | grep ' r-xp ' | cut -d- -f 1", getpid());;
  f = popen(cmd, "r");
  while(fgets(buf, sizeof(buf), f) != NULL) {
    pid_offset = strtoull(buf, 0, 16);
    break;
  }

  total = base_address + pid_offset;
  ptr = (struct malloc_state*) total;

  mrb_state *mrb = mrb_open();

  // create a lot of 'heavy' objects, then free half of them
  // we want contigious segments of memory demonstrating how the default glib
  // allocator does not mark empty pages back to the OS without triggering absurdly
  // high thresholds defaults or forcing the allocator using malloc_trim
  mrb_load_string(mrb, "$a = []; $b = []; $c = []; $d = []; 2_500.times { $a.push(Fiber.new {}) }; 2_500.times { $b.push(Fiber.new {})}; 2_500.times { $c.push(Fiber.new {})}; 2_500.times { $d.push(Fiber.new {})}; $b = nil; $d = nil; GC.start;");

  if(trim) {
    malloc_trim(0);
    remove("trimmed.dmp");
    dump_main_heap("trimmed.dmp", ptr);
  }
  else {
    remove("default.dmp");
    dump_main_heap("default.dmp", ptr);
  }

  mrb_close(mrb);
  // chance for viewing mem usage before exit
  getchar();
  printf("exit\n");
  return 0;
}

task :default do
  sh 'cc -I../mruby/include -lm -g -o unpatched main.c libmruby.a'
  sh 'cc -I../mruby/include -lm -g -o patched main.c libmruby-gcpatched.a'
  rm_rf 'trimmed'
  rm_rf 'default'
  rm_rf 'default-patched'
  mkdir 'trimmed'
  mkdir 'default'
  mkdir 'default-patched'
  sh './unpatched'
  sh './unpatched trim'
  sh 'ruby visualize_heap.rb trimmed.dmp trimmed/'
  sh 'ruby visualize_heap.rb default.dmp default/'
  sh './patched'
  sh 'ruby visualize_heap.rb default.dmp default-patched/'
end

It finds the base address of glibc and then finds the base address of the shared glibc within the current program and uses it as the base address of the memory heap. Then, after creating a new mrb_state, creates 10,000 empty Fiber objects within the VM, partitioned into four global arrays.  After, code takes two paths. One is entirely default behavior with no changes from mruby master and then dumps the heap layout. The second when passed a trim parameter. When passed trim it calls malloc_trim(0) before dumping the heap layout. This gives us an indication on how mruby behaves and whether calling malloc_trim helps here.
The visualization divides the OS heap pages used by the program. Red dots are usage within the heap page. Grey dots are usage within the heap page marked as 'free, dirty' and not yet reclaimed by the kernel. White is previously allocated dirty pages marked as unused to the kernel.
This is the result of default behavior on a standard Ubuntu 18.04 system

The result of calling malloc_trim before dumping the heap.

And finally, default behavior with the patch, which calls malloc_trim after every major GC cycle.

We can also observe this by looking at heap memory usage as reported by the kernel. We can see that the defaults consume 19MB of heap memory reported by the kernel, while calling malloc_trim consumes 10mb of memory reported.
Since all of the VM is encapsulated in mrb_state we can go further with our research than observing C Ruby's global VM state. Moving the call to mrb_close in the above program to right after the mrb_load_string call we see some major results, like this
mrb_load_string(mrb, "$a = []; $b = []; $c = []; $d = []; 2_500.times { $a.push(Fiber.new {}) }; 2_500.times { $b.push(Fiber.new {})}; 2_500.times { $c.push(Fiber.new {})}; 2_500.times { $d.push(Fiber.new {})}; $b = nil; $d = nil; GC.start;");
mrb_close(mrb);

Calling mrb_close on the default path

Calling it on the trimmed path

Heap difference reported by the kernel.

I also replicated all results on the standard Raspberry Pi raspbian distribution. The results are 100% identical, so they're not worth including. It does give more evidence that in Linux systems with more of a focus on low power do not change glib defaults.
For fun I repeated the same experiment except I created 500,000 Fiber objects, then freed all of them using mrb_close with and without trim. The results are similar. Even at program exit without calling malloc_trim the program consumes 900 mb of memory, whereas calling malloc_trim right after mrb_close memory usage drops back to 0.3 mb.

(The heap visualizer as it is right now does not function well with this amount of memory usage)
Even after allocating 933MB of memory and marking all of it free, as the mrb_close function correctly does, that still does not trigger glibc defaults on marking memory as unused to the kernel! This is a major problem!
And finally, changing the code for using 4 mrb_states and closing half of them. Given the previous knowledge it also provides a predictable pattern. Changing the test program a bit
mrb_state *states[] = { mrb_open(), mrb_open(), mrb_open(), mrb_open() };

for(uint32_t i = 0; i < 4; ++i) {
  mrb_load_string(states[i], "$a = []; $b = []; $c = []; $d = []; 2_500.times { $a.push(Fiber.new {}) }; 2_500.times { $b.push(Fiber.new {})}; 2_500.times { $c.push(Fiber.new {})}; 2_500.times { $d.push(Fiber.new {})}; $b = nil; $d = nil; GC.start;");
}

mrb_close(states[0]);
mrb_close(states[2]);

Full defaults

Using malloc_trim

Knowing this I tried mruby-thread. Because it reads the parent mrb_state from the parent thread, copies that state into a child thread, and then deletes the child thread on join, the kernel reclaims the memory on joining the child thread.
About the glib defaults. We can control them through documented parameters, either through env vars or glibc compile time defines. I followed the research done with C Ruby by setting M_ARENA_MAX=2 and running the default program. An interesting difference is I do not observe a change in behavior running with that env var set with the default program, the heap output is the same as the default unpatched program. I also don't think it's responsible to make the end user set some obscure system parameters anyway.
It's a common scenario using linux and default glib even for linux systems destined for lower power devices. The default glibc allocator behavior defaults are dramatically out of line for this situation. This situation is obscure enough that I strongly suspect other embedded linux systems do not change any defaults either.
Because of that I feel we should introduce malloc_trim into mruby. The conditions for usage are if the compilation target uses glibc and mrb_malloc uses the default glibc allocator. I observed that calling malloc_trim after a major GC produces the same results as calling it outside of the VM execution. C Ruby reports the same behavior. I think that calling malloc_trim after a full GC is the most appropriate place as I'm not sure what the performance implications are if we call on every mruby page free. Also, because a host program can open and close mrb_state at will we should also call malloc_trim after freeing all the memory used.
I think the detection should go into the Rake tasks and set a define for the compiler, say MRB_GLIB_MALLOC_TRIM, and then within the C code do #ifdef MRB_GLIB_MALLOC_TRIM on that. These are simple additions that I will make a PR for. I am providing extensive documentation as to why here. I am also asking if there are ideas for a different way of detecting the environment for glibc and calling from the code.

Thank you for the report.
I just wonder how much malloc_trim(0) affects performance.

That's a great question! My hypothesis is it's imperceptible. If the research on C Ruby is correct calling malloc_trim is actually faster.
I don't know of a large project with mruby so I used the mrbtest program. I patched mrb_full_gc and mrb_close to call malloc_trim just before returning. I used callgrind for dumping function call weight, and KCachegrind for investigating. With my first analysis I discovered nothing in the the mrbtest causes a full GC cycle! So all of the work is looking at mrbtest with MRB_GC_STRESS and GC_PROFILE set.

When looking at call weight, malloc_trim is about 0.6% of the total x64 CPU instruction count in the mrb_full_gc function. Within malloc_trim are a couple low level kernel calls, sbrk and madvise (which is what the allocator should be doing anyway).
If we use the GC report time with GC_PROFILE and MRB_GC_STRESS enabled with the mrbtest program, running 5 times sequentially the last entry reported with themalloc_trim patch is
gc_total_time:         4.27906966209411621094
gc_total_time:         4.29512357711791992188
gc_total_time:         4.27969479560852050781
gc_total_time:         4.30843663215637207031
gc_total_time:         4.30021381378173828125

And default master
gc_total_time:         4.04845476150512695312
gc_total_time:         4.03771066665649414062
gc_total_time:         4.04702949523925781250
gc_total_time:         4.08767271041870117188
gc_total_time:         4.05192518234252929688

Interestingly a ~2% increase of time in conditions where there is a full GC every object allocation, the worst condition.
This is all synthetic in a way. I don't know of any long lived programs for murby I can use. If you do know of something I want to analyze it. My current mruby project is only Windows currently. I'm making it work on linux due to these investigations making me curious, I could use that when I have it working.

Send us pull-request.

Yes, it is on my list! I became sidetracked getting my mruby project working on Linux first.
Do you agree that a compile time flag is a good solution?

I think so. We don't use autoconf so there's no way to detect malloc_trim automagically (no, if I write new Rakefile task, it's possible. But it doesn't work for cross-compiling anyway).

I like the simplicity of being away from tools like autoconf. I’ll look at this now.


ImportError: cannot import name 'MailBot'

I installed it through pip install mailbot.  And it installed succesfully and registers as a package: 'mailbot==0.3'
From Docs: https://mailbot.readthedocs.org/en/latest/
from mailbot import MailBot, register

from mycallbacks import MyCallback

mailbot = MailBot('imap.myserver.com', 'username', 'password')

# register your callback
register(MyCallback)

# check the unprocessed messages and trigger the callback
mailbot.process_messages()

However whenever the code above is run, output = "ImportError: cannot import name 'MailBot'"

Actually
>>> from mycallbacks import MyCallback
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named mycallbacks

fails for me


Update to typescript 3.2.2

Description

Updated typescript to the latest version (3.2.2).
Updated monaco-editor to the latest version (0.15.6) as well to support the updated version of typescript.

Motivation and Context
TypeScript has introduced some cool features since 2.6.2 that would be neat to play around with or use in ScriptLab. Also, the latest developmental version of Office.js requires at least TS 3.0.
How Has This Been Tested?

Local testing. Smoke testing with various snippets. Made sure existing code is not affected by any breaking changes (https://github.com/Microsoft/TypeScript/wiki/Breaking-Changes).
Screenshots (if appropriate):
Types of changes

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

Checklist:

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

Since we are now using the new Script Lab React codebase, closing this pull request as no-longer-needed.  The old Script Lab is now essentially in "escrow mode", we don't want to touch anything unless it's really broken (since it is now a backup option for folks using the new Script Lab, in case they need something that isn't working for them in the new one).
For the Monaco version bump, it might seems like an innocent change, but we actually found that there are very specific issue with Monaco across platforms for add-ins (namely, latest doesn't work with Mac add-ins!).  Which makes me all the more cautious about introducing new code to this repo.


Concurrent Column Access

Dear Jinzhu,
How can i do wallet/balance management on database with concurrent access, lets say to make: lastBalance = lastBalance - Nominal
able to perform in concurrent access (Optimistic Locking is what i look for)
Thank You,
Regards

like this? DB.Model(&product).UpdateColumn("quantity", gorm.Expr("quantity - ?", 1))


Fix GraphKernel

Closes #74

It needs support of positional encoding as edge feature to feed into the model. It may need some design from GeometricFlux.

Maybe fix GraphKernel first. I will fix the example later.


CanBeNonNullable false-negative

Expected Behavior
assignedExpression violates CanBeNonNullable.
private fun visitAssignment(assignedExpression: KtExpression?) {
    if (assignedExpression == null) return
    val name = if (assignedExpression is KtQualifiedExpression) {
        assignedExpression.selectorExpression
    } else {
        assignedExpression
    }?.text ?: return
    assignments.getOrPut(name) { mutableSetOf() }.add(assignedExpression)
}

Observed Behavior
detekt is fine with that code
Context
If a function returns Unit any null check to exit the function if the parameter is null should be consider as a parameter that could be non-null.
I saw this false-negative while working on this PR: #4491
Your Environment

Version of detekt used: main
Link to your project (if it's a public repository): detekt.

Isn't #4431 supposed to catch this actually?

Yes, but it is not.

Hi!
Can I work on this?

Please go ahead :)

Should !is in if / when statements also be reported?
e.g.
fun foo(a: Int?) {
    if (a !is Int) return
    println(a)
}


python3Packages.diff-cover: fix to use pyproject

Description of changes
Upstream has moved to pyproject.toml so this package doesn't build without this fix.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[X] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build python312.pkgs.diff-cover
@ofborg build python311.pkgs.diff-cover


NIFI-401

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@beugley Thanks for the PR! Going to start reviewing... Sorry this lingered a bit. I see there are a couple conflicting files but I'm going to see if I can rebase them locally. If I have any issues, I'll reach back out.


question on creating resources

Should the following request work?
$ curl -i -v -X PUT http://malmo.lizenn.net:8080/collections/user/Merle -H 'Content-Type: text/occi' -H 'Category: user; scheme="http://example.org/occi/test#"; class="kind";' -H 'X-OCCI-Attribute: blog.user.name="Merle"' -H 'X-OCCI-Attribute<EMAIL_ADDRESS>Currently HTTP/1.1 404 Not Found

I have the same problem here with latest version of Erocci, i can't create an infrastructure compute resource. Note : Erocci-dbus-java set the infrastructure 1.2 occi schema.
here's my curl query (generated with cloud designer) :
curl -s -v -i -X PUT http://localhost:8080/compute/ab30d56e-aad7-411d-b7a6-87f100d40dcf -H 'Content-Type: text/occi' -H 'Category: compute; scheme="http://schemas.ogf.org/occi/infrastructure#"; class="kind";' -H 'X-OCCI-Attribute: occi.core.id="ab30d56e-aad7-411d-b7a6-87f100d40dcf"' -H 'X-OCCI-Attribute: occi.core.title="resource1"' -H 'X-OCCI-Attribute: occi.core.summary=""' -H 'X-OCCI-Attribute: occi.compute.architecture="x86"' -H 'X-OCCI-Attribute: occi.compute.cores=2' -H 'X-OCCI-Attribute: occi.compute.hostname="testinfra1"' -H 'X-OCCI-Attribute: occi.compute.share=no' -H 'X-OCCI-Attribute: occi.compute.speed=2' -H 'X-OCCI-Attribute: occi.compute.memory=2' -H 'X-OCCI-Attribute: occi.compute.state="inactive"' -H 'X-OCCI-Attribute: occi.compute.state.message=""'

occi.compute.share is a number not a string, so put '0' instead of 'no' as value.

I have the same result with occi.compute.share=0, i've tried other queries and all failed, all these queries worked before.

Welcome:-( I suspect that a recent commit since our last OCCIware meeting at Nantes introduced a regression.

I confirm that this issue is resolved.


Add modified Attention for shunted transformer

Signed-off-by: Jael Gu<EMAIL_ADDRESS>

/lgtm
/approve


fix: Connection.resolveExternalWSUri should return ws or wss schema

Modifies the behavior Connection.resolveExternalWSUri  so that it returns as URI with a "ws" or "wss" scheme instead of a "http" or "https" scheme as it does currently.
This avoids the need for callers of this function to correct the scheme in the results.  Most importantly in the WebviewComm the scheme was always replaced with a "ws" scheme, resulting in errors like
Mixed Content: The page at 'https://example.com' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://example.com'. This request has been blocked; this endpoint must be available over WSS.

in secure contexts.
No other clients of the Connection class seem to rely on the behavior of returning an "http" or "https" schema.

@microsoft-github-policy-service agree [company="Udacity"]

Can you create an issue associated with this?

@andreamah , this addresses https://github.com/microsoft/vscode-livepreview/issues/645

This seems right, as it's making the behavior in
https://github.com/microsoft/vscode-livepreview/blob/8573123141b6d98208bcb43a8a060b630fbe4a4b/src/server/serverUtils/HTMLInjector.ts#L79-L80
more universal across the repo. Currently, once I manually navigate to the websocket URL (as discussed in the FAQ, it seems to update just fine for me.

In your case, do you do this and it still doesn't update properly?

Actually, this change does not fix https://github.com/microsoft/vscode-livepreview/issues/645, which is the problem addressed in the FAQ, as pointed out by @andreamah .
The only consequence that been able to observe while running the branch in codespaces is that a "Content-Security-Policy: Upgrading insecure request" warning disappears. The websocket where behavior is affected is not the one responsible for refresh but the one that handles the page history.
Nevertheless, I do think that this is an improvement to code.  It can be seen as an alternative fix for https://github.com/microsoft/vscode-livepreview/issues/175.


Upgrade NuGetRestoreV1 to NodeJS16

Task name: NuGetRestoreV1
Description: This PR upgrades NuGetRestoreV1 to NodeJS 16
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) N
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

@microsoft/azure-artifacts-packages, could you please take a look and approve the PR? I will appreciate it if you will check that everything work as expected on your side

@microsoft/azure-artifacts-packages, could you please take a look and approve the PR? I will appreciate it if you will check that everything work as expected on your side

You've checked the "Checked that applied changes work as expected" checkbox, can you please describe what testing you've done and what you expect from the Artifacts team here?

Hi @JohnSchmeichel. Thank you for response. Since Artifacts team is codeowner of this task I asked to review the PR and test the changes. From my side I ran some dummy pipeline with updated task and also ran tests locally.


Handle narrow viewports

On the minimum supported screen size we should be able to see the panels UI and the realm in the background

[ ] when user is visiting the website from mobile - make sure there are no regressions
[ ] make sure minimum viewport width is displaying the realm panels nicely if it is not then

[ ] move leaderboard panel to the other side, below the realm panel when viewport becomes too narrow

Resolved by #838


replace is-size- with tailwind equivalent

ref #9013

:wave:

@pbkompasz are you working on this?

@prachi00 Yes I am, but you can take #9191.


cleaned up vagrantfile

General cleanup of vagrantfile, like grouping provider configuration together and such, for readability.

fixed username variable for suse images (was 'use' instead of 'user')

the inner variable prefix 'config' was replaced with 'node' due to nesting of 'config'; some IDEs warn about using identical variables when nesting and it's cleaner this way

added .git and venv to the rsync exclude list, so that these don't get synced on boot, saving about 330MB of rsync bandwidth and time on each vagrant up/down cycle

Vagrantffile expects $inventory be an absolute path; this is now fixed by adding code that translates it to that. Users can supply a relative path (eg. inventory/mycluster) and Vagrantfile will make it absolute.

The kubespray docs refer to hosts.ini as the name of the custom inverntory file, but Vagrantfile looked at 'hosts' instead; this is fixed by making Vagrantfile als use 'hosts.ini'

removed $local_release definition from Vagrantfile because the default /roles/download/defaults/main.yml is /tmp/releases works fine. Besides that, re-depfining vars complicates the kubespray vagrant configuration because vars that are set here are put in the inventory file, which overrides every other source of vars. I ran in to this when doing multiple ansible runs and changing $local_release in all.yml, but it wasn't taking effect because it was set in the inventory file generated by Vagrant.

Bento centos 7 image is added to the list of supported images. Bento has built in virtualbox tools and the sourcecode for the image is freely available and regularly updated.

This is one of the PR's resulting from splitting up the following bigger PR: https://github.com/kubernetes-incubator/kubespray/pull/3691

/assign @ant31


"Name has already been taken" issue when updating certain dashboards.

Just on some dashboards I've been presented with the following error.
➜  authenticator git:(master) ✗ curl -H 'Content-Type: application/json' -X PUT -d @prometheus/authenticator.json http://promdash/authenticator.json
{"name":["has already been taken"]}%

@pellegrino Does this still happen? Can you provide steps to reproduce?

@grobie I cleared this up in person with @pellegrino back then. Closing.


Show "warning" text for swagpaths that the user doesn't have the prerequisites for

Suggest "To get the most out of this swagpath, consiter following ..., ... or ... first"

Ok implemented... Instructions for testing... First go to the swagmap, consider the chain:
"How are you?" --> first-test --> "What are you doing?" --> another-test
So, the "first-test" swag is a requirement for "What are you doing?". If you go to the "What are you doing?" swagpath, without first completing the "How are you?" swagpath:
http://learning.tunapanda.org/courses/testing/what-are-you-doing/
You should see the warning. If you complete the "How are you?" swagpath and go back to the "What are you doing?" the warning should disappear.

It works!


Remove redundant codes

remove some redundant codes.

 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.


Question: Anyone has access to WideVine CDM plugin for OSX that compatible for the latest release of Electron (v0.36.8)?

Electron version: v0.36.8
Operating system: OS X 10.11.2 (15C50)

Anyone has access to WideVine CDM plugin for OSX that compatible for the latest release of Electron (v0.36.8)? Since the latest Chrome is 48.x I have no access to Chrome 47's WideVine.
Thank you!

I suggest seeking help from the community:
https://github.com/atom/electron#community


fix(oay): pass litmus copymove test

This PR fix litmus copymove test copy_overwrite, move and move_coll. Refer to dav-server-rs::LocalFs::rename
-> running `copymove':
 0. init.................. pass
 1. begin................. pass
 2. copy_init............. pass
 3. copy_simple........... pass
 4. copy_overwrite........ pass
 5. copy_nodestcoll....... pass
 6. copy_cleanup.......... pass
 7. copy_coll............. pass
 8. copy_shallow.......... pass
 9. move.................. pass
10. move_coll............. pass
11. move_cleanup.......... pass
12. finish................ pass
<- summary for `copymove': of 13 tests run: 13 passed, 0 failed. 100.0%

https://github.com/apache/incubator-opendal/issues/2586

Maybe we can add litmus test in our CI for oay.

Maybe we can add litmus test in our CI for oay.

yeah I think so, will make it next


[Search] Standardizes input search components

Hey, I just made a Pull Request!
Refs: https://github.com/backstage/backstage/issues/8483
Standardizes the component used as a search box in the search modal and in the composable home page.
After these changes, all search boxes exported by the search plugin are based on the <SearchBarBase /> component, and this one is based on the <InputBase /> component from Material UI. This means that when you use SearchBarBase or one of its derived components (like SearchBar and HomePageSearchBar) you can pass all properties accepted by InputBase that have not been replaced by the props type of those components.
For example:
<SearchInputBase color="secondary" debouceTime={500} />

The color property is inherited from InputBaseProps type and debouceTime defined by SearchBarBaseProps.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

In agreement with @camilaibs I made the changes so that default debounce value is 200 now and with that we don't need to use the prop on SearchPage or SearchModal. Can you confirm if we need a changeset for create-app now? @freben

Yeah make just a small note there that the prop now is unnecessary for most use cases, and that it's safe to remove to benefit from tweaks to the standard in the future. Just a couple words is fine since it's not breaking or vital so to speak

In agreement with @camilaibs I made the changes so that default debounce value is 200 now and with that we don't need to use the prop on SearchPage or SearchModal. Can you confirm if we need a changeset for create-app now? @freben
Commit here 15986e0

Thank you @emmaindal and @freben I agree with you!


Contact Microsoft - API for Dynamics online provisioning

Need to reach out to MSFT to see if this is feasible.  And if so, what are the requirements.

Email sent to Craig Timm & Scott Anderson outlining current process & requesting input/answers to automate the process

Initial response from Craig Timm - https://powerapps.microsoft.com/en-us/blog/new-connectors-for-powerapps-and-flow-resources/

Craig is still doing some testing & expects to get back to me later this week or early next (Friday or Monday)


position awareness

Hi,
can a module somehow know it's position?  I would like to reverse the rendering order depending on the side, the module is displayed.

Try: this.data.position
Also checkout the full this.data object for other module info.

perfect, thanks.


The application was unable to start correctly

Hello,
I have the redistributables - Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030
When I run heimdall help I get the error: The application was unable to start correctly (0xc0000013). Click OK to close the application.
Kind regards,

What version of Windows are you running?
Also, you need the x86 redistributables, not x64, although I believe they're usually bundled together.

What version of Windows are you running?

Windows 7 x64

Also, you need the x86 redistributables, not x64, although I believe they're usually bundled together.

They aren't bundled together, the download link offers which ones you want. With x86 redistributables the issue is fixed, however I have a new issue now:
C:\Users\Blake\Desktop\Heimdall Suite>heimdall print-pit --no-reboot
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12

@blakehawkins You're right, the README definitely could be clearer. The redistributables won't be required for the next major release of Heimdall, so that should simplify the process. I'll also see what I can do about automatically installing the drivers.
The last tip I have for you would be to take a look at the "Performing a Custom Flash with Heimdall Frontend" section of the README. If you have firmware that is not a "Heimdall Firmware Package", then that's the procedure you'll need to follow.

Excellent, thanks a lot, and thanks for maintaining this great tool


Make TaskGroup::run signal safe

Fixes #7

Coverage increased (+0.02%) to 94.444% when pulling 05c00cb5c7e690581f705fcd433056b53b13e665 on jlfwong:jlfwong/signal-safety into 91130f619c1f9958f85c9a4429db1c3430d885fd on chadrem:master.

@jlfwong awesome find. Thanks for the pull request. I'm going to merge it and get a new version out with the fix.

@jlfwong v0.6.1 is released with a slight change to remove some code duplication.

@chadrem Thanks for the super fast response!


BUG: fix stats.rv_histogram for non-uniform bins

Currently, stats.rv_histogram produces incorrect results if the histogram bins have different widths. For example:
>>> from scipy import stats
>>> counts, bins = ([1, 1], [0, 1, 1001])
>>> dist = stats.rv_histogram((counts, bins))
>>> dist.pdf([0.5, 200])
array([0.000999, 0.000999])
>>> dist.median()
500.5

etc. This happens because the PDF and CDF calculations in rv_histogram's __init__ are incorrect, though they give the right results in the common case of equal bin widths. After this fix, we get the expected results:
>>> dist.pdf([0.5, 200])
array([0.5, 0.0005])
>>> dist.median()
1

I added this example as a new test case.

I didn't mean any change in the histogram distribution itself.
Only the argument how the histogram is defined.
current docstring:
we can create histogram distribution from numpy.histogram, i.e. from counts per bin
definition what I would have expected:
we can create histogram distribution from numpy.histogram using density=True, i.e. from pdf values which are constant within bins
(I meant pdf and not pmf in my previous comment)
pdf, bins = ([1, 1], [0, 1, 1001])
means both bins have pdf 1 * scaling  (scaling to integrate to 1)
or
pdf, bins = ([1/1001, 1/1001], [0, 1, 1001])

Ah OK, so you would have expected rv_histogram.__init__ to take (density_in_bin, bin_edges) rather than (counts_per_bin, bin_edges). Sure, that seems an entirely valid convention too; though as you say, not what rv_histogram currently promises it does. Maybe it's worth making an alternate constructor for this, e.g. rv_histogram.from_density?

In terms of backwards compatibility
If the current code works correctly for (density_in_bin, bin_edges), then we might have to change the docstring instead of code.
At least in the old times, the bug was in incorrect docs and not in code, if docs and code did not agree.

@rgommers needs api design and backwards compatibility decision

I'll attempt to summarize:
The docstring of stats.rv_histogram shows that it an stats.rv_histogram can be initialized with the output of np.histogram using (default) density=False.

The docstring states that the first element of the input tuple (the tuple produced by np.histogram) is the "content" contained within the bins. If "content" means count, this is consistent with default np.histogram (density=False), but the wording is ambiguous.

When the bins are constant-width, the code currently works whether np.histogram is used with density=True or the default density=False.

import numpy as np
import matplotlib.pyplot as plt
from scipy import stats

rng = np.random.default_rng(4398410)
rvs = rng.random(size=1000)

x = np.linspace(0, 1, 100)
rv1 = stats.rv_histogram(np.histogram(rvs))
rv2 = stats.rv_histogram(np.histogram(rvs, density=True))

plt.plot(x, rv1.pdf(x), '-', x, rv2.pdf(x), '--')
plt.xlabel('rv_histogram.pdf')
plt.legend(("Defined with `density=False`", 'Defined with `density=True`'))

When bins are not constant-width, the code works as expected only if np.histogram is used with density=True. In the plot below, I've used the same code as above except setting bins=[0, 0.25, 1]. We expect the PDF to be that of the uniform distribution.

@JelleAalbers interpreted the documentation of rv_continuous as I would have - that rv_continuous always expects to be initialized with the output of np.histogram with density=False. This PR would change the way rv_histogram works to make it consistent with this interpretation of the docstring: rv_histogram would behave as expected with non-uniform bins only if np.histogram is used with density=False.
@josef-pkt noted that the code works correctly as-is, assuming that np.histogram is used with density=True, so he is suggesting that perhaps only the docstring should be changed.
Besides the fact that changing the documentation is more backward-compatible, there are a few other reasons to change only the documentation:

The docstring needs work anyway.
Some would suggest that the standard way to represent a histogram with nonuniform bins is in terms of its frequency density, not its frequency.

E.g. from Wikipedia:

(Maybe this really means that np.histogram should by default report frequency density when bins are non-uniform, but that is out of scope.)
With that in mind, what do you think @JelleAalbers?

Thanks for the clear summary @mdhaber!
Yes, this PR would break the code of people feeding rv_histogram with density/bin histograms with variable-width bins. Though giving such input is against (a straightforward reading of) the current docs, I agree it's a reasonable thing to do -- it makes the current code work, and variable-width histograms with counts/bin are somewhat strange.
So I would be happy with blessing the current behaviour and updating the docstring, as @josef-pkt suggested. But I would suggest doing more than a docs change: if someone passes an unnormalized "density" and non-uniform bins, they are almost certainly passing counts/bin (np.histogram's default output / what the docs have suggested so far), and are about to get nonsense results. That seems worth a warning at least.
I could try an implement that here -- or feel free to close this PR instead.

Non-uniform-binned histograms with counts instead of densities are not unusual, and are necessary for preserving the full information about the histogram, e.g. for computing error bars. They do need to be transformed into density-histograms for certain operations, but that's an information-losing step; I can go from (counts, edges) to (densities, edges), but not vice versa.
Can we add a keyword argument to stats.rv_histogram() to tell it which one is being passed? Unfortunately, I suspect that the most natural default, if we were designing it from scratch, would be backwards-incompatible with the ways that people have successfully worked around the implemented behavior. Maybe we need 3 options:

density=True meaning to treat the input as a density,
density=False meaning to treat it as counts,
and the default density='legacy' meaning to work in the current behavior, whatever that means.

I suspect that any attempts to inspect the (x, edges) input to infer the intention (even just to issue a warning) will be brittle due to floating point arithmetic, and hard to document.

@JelleAalbers would you be willing to try implementing @rkern's suggestion? I think it's fair to give both options.

Sure! I just pushed an attempt to implement your suggestions. It adds a density argument to rv_histogram.__init__:

density = True assumes the input histogram is (proportional to) a density, i.e. how the current code behaves;
density = False assumes the input histogram is (proportional to) a counts/bin histogram, i.e. what np.histogram produces / what the current documentation implies;
density = None, the default, sets density=True for backwards compatibility. However, it also generates a warning if the histogram has non-uniform bins: "Specify density=True or False to disambiguate histograms with variable bin widths"

Note density=None does not check the contents for normalization; it only checks if the bin widths are constant or not. This is still a potentially brittle floating-point check, but because the warning is easily avoided (by setting density), I think flagging a  common mistake most of the time is worth a rare misfire. Happy to remove the warning if you disagree.
I updated the tests (to cover both density options) and documentation. Probably the new density argument should have a .. versionadded:: tag, but I'm not sure at which stage you would add this.

Robert,

I can go from (counts, edges) to (densities, edges), but not vice versa.

In which case do we loose information?
AFAICS, The only information we use is the total number of observations, and that is irrelevant to defining a distribution.
adding a keyword sounds good to me.
Aside, is it clear (in docs, to users) that a histogram distribution cannot have unbound support, i.e. no open intervals, inf binedges, at the ends.

AFAICS, The only information we loose is the total number of observations, and that is irrelevant to defining a distribution.

Yes, but that is not the only thing one does with a histogram. I was responding to the suggestion that it was somehow unnatural to create a count-based histogram with uneven bins. The absolute number of observations in each bin is important information if I'm fitting a distribution to the binned data or even just adding error bars to the plot. It is indeed unnecessary information for specifying rv_histogram(), but it will not be uncommon to run into cases where one has (counts, edges) with uneven bins.

@JelleAalbers would you be interested in finishing this up? There is a review waiting for you.

Thanks for stepping in @mdhaber; these changes look great!


Add labels along with add_marker_layer and write pin to port layer on None

This PR does three things:

Support additional label on add_marker_layer
Write label to port layer in add_pins_rectangle_inside when given layer_label=None

Use the feature in Strip to ridge taper for having CrossSection expanded pins on only final component.

TODO refactor to in-place version of decorator


Restored JDK 7 compatibility

Replaced missing library for testing on Travis-CI
The version of openjdk7 used in Travis-CI for testing compatibility with Oracle JDK 7 is missing a crypto library.
These changes aim to solve the problem by letting Travis-CI use the BouncyCastle library to build and run the project, as suggested in eddyson-de/tapestry-react#122. Until we cease support for JDK7, this will allow to run tests for the Chino.io Java SDK in Travis-CI for both Java 7 and 8.

Added to branch develop.


Added quantity change form to update qty from cart page #7178

Added form to change quantity in cart page and submit the same on
change of qty field using javascript.
This change allow user to update quantity of items that need extra
fields, like gift-card requires recipient name and email.

Coverage remained the same at 67.88% when pulling 2fbb5cf3165e4bf21387c190f67d1bbd70f68587 on rajatguptarg:feature/task-7178 into 78254124c89f3e24e2805dff402f3b2379a59b01 on openlabs:develop.

LGTM


Question: Dashboard name validation

We ran into a scenario where one of our users created a dashboard with a slash ('/') in the name, i.e. "Test/Dashboard". While dashboard creation was successful, he then was unable to configure any of the widgets. This is so because the configure action was unable to hit the '/dashboard/myowner/{dashboardtitle}' endpoint, since his request was '/dashboard/myowner/Test/Dashboard'. My question to the group is, would there be interest in adding a validation around the dashboard name to prevent slashes and or any special characters? If yes, I'll open a PR on this. Thanks.

@Mpluya Sure.. please do. Thanks for the help.

@satishc1 thank you.

@Mpluya Closed.


Select a block of code and edit in new tab

Hi,
Suggestion here: the ability to select a block of code, and have an option to edit it in a new tab.

This is a great tool to work on a specific portion of code without being drowned in the whole content. A bit like an isolation mode in Illustrator.
Then, when you save the tab, it closes and the block of code is replaced.
It's available on Atom and SublimeText, let's get VisualStudio Code have it too!
Thanks!

fyi @bpasero

I see no reason why this cannot be done as extension 👍

Yes, this is something an extension could implement. Please see our extension authoring docs for information about writing an extension
Closing as extension-candidate


chroot won't unmount

So I'm sort of new to the bug/issue reporting thing; apologies if I'm doing it wrong.
Background: I was curious, making gdb debug dumps and prodding them with a hex editor because why not? Attached it to a running flash plugin (THIS is why not) and chroot is now impressively locked up - not a black screen, it looks perfectly normal and the mouse cursor moves, but xfce window/desktop/panels won't respond. ChromeOS side is still functional.
The issue: Tried to unmount nicely and I was rebuffed. The readout looks like what others w/ unmount issues have gotten before but since the session went rogue beforehand, I'm not sure its the same issue (or that it's even an error - like, major hanging process in the chroot, of course it'd say it's in use?) I'll use unmount -f next but just in case the nice way is supposed to handle this type of situation, here's the output/crouton version info.
chronos@localhost / $ sudo unmount-chroot -p xfcechroot
19656 su -s /bin/sh -c export SHELL='/bin/bash';'exec' 'startxfce4'  - andrea
Not unmounting /mnt/stateful_partition/crouton/chroots/xfcechroot as another instance is using it.
chronos@localhost / $ sudo enter-chroot -n xfcechroot
Entering /mnt/stateful_partition/crouton/chroots/xfcechroot...
(xfcechroot)andrea@localhost:~$ croutonversion
crouton: version 1-20151104200003~master:2a1fc9da
release: trusty
architecture: amd64
xmethod: xiwi
targets: xfce,xiwi
host: version 7390.68.0 (Official Build) stable-channel gandof
kernel: Linux localhost 3.14.0 #1 SMP Thu Nov 5 13:06:47 PST 2015 x86_64 x86_64 x86_64   GNU/Linux
freon: yes
(xfcechroot)andrea@localhost:~$ exit
logout
Not unmounting /mnt/stateful_partition/crouton/chroots/xfcechroot as another instance is using it.

This is very annoying. Sometimes -f will work, but you still then have to select SIGKILL.

Yeah, since you still have a (frozen) xfce session running in the background, unmount-chroot won't let you try unmounting the chroot without specifying -f.
@brmbrmcar: if you specify -y as well, unmount-chroot will escalate through SIGTERM and SIGKILL for you.


Add CTV + CSFS as Alternative Requirement for Eltoo

On this page
https://github.com/stevenroose/covenants.info/blob/master/content/use-cases/eltoo.md
APO is mentioned as a prerequisite, but CTV+CSFS is not mentioned as an alternative prerequisite so the reader has incomplete information.

Details: https://rubin.io/blog/2021/07/02/covenants/

Additionally, according to the latest Bitcoin Optech, Eltoo is now known as LN-Symmetry
https://bitcoinops.org/en/newsletters/2024/01/10/
It might also be worth mentioning @reardencode's LNhance soft fork.


Xmr.to service in mymonero wallet is working or also died

In view of the fact that xmr.to closed its doors, the service in mymonero is not working? In any case, I recommend you take a look at the service of https://changenow.io/es I have used it and it is an excellent alternative, I think it can be implemented to the wallet

Hi Isus182
Thanks for suggesting them. We actually have added ChangeNow support in version 1.1.19.
There is one issue with the integration that we're busy working on, which is that at present, it requires a 0.003 BTC minimum amount to exchange. We're busy working on adding additional providers and exploring other ways in which we can reduce that minimum limit.

Greetings, I am aware of the minimum, but I would recommend the exchange option with LTC where the minimum 0.0628

Hi Isus182
Thanks for suggesting them. We actually have added ChangeNow support in version 1.1.19.
There is one issue with the integration that we're busy working on, which is that at present, it requires a 0.003 BTC minimum amount to exchange. We're busy working on adding additional providers and exploring other ways in which we can reduce that minimum limit.

Greetings, I am aware of the minimum, but I would recommend the exchange option with LTC where the minimum 0.0628

#368 covers the request for LTC exchange pair


added twitter link to project

Fixes Issue
Example: Closes #210
Changes proposed
Added twitter link with icon in the project and also changes the readme file
Screenshots

Note to reviewers

could you please remove package-lock.json?

Yeah sure

@rupali-codes can you check now

Hi, this looks perfect tho, but having an issue, if we'll merge this PR then it's gonna packgae-lock.json from the repo. So could you please close PR and create a new one with the just file you have updated.
You can add files one-by-one if they are multiple by using this command
git add <your_file_name>

I have removed the package-lock.json file, it should not be visible in my latest PR.