Not Supported: Multi Forest Deployments

I think "multi Forest Deployments" are also not supported or only with a forest trusts.?. I can use a separate ADFS-Service with every UPN Domain and so i can run multiple forests with a single AADConnect Instance  But can the PTA-Agent also authenticate users in another forest?  or are the authentication agents aware of the UPN they can authenticate ?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c535414b-05a2-d4b5-8f15-5c93274d25ef
Version Independent ID: 0bef709f-d10f-5fe6-68a8-f21d0204ecd5
Content: Azure AD Connect: Pass-through Authentication - Current limitations
Content Source: articles/active-directory/connect/active-directory-aadconnect-pass-through-authentication-current-limitations.md
Service: active-directory
GitHub Login: @billmath
Microsoft Alias: billmath

@FrankCarius Thanks for your feedback! We will investigate and update as appropriate.

@FrankCarius Yes, for Pass-through Authentication, Multi-forest environments are supported if there are forest trusts between your Active Directory forests and if name suffix routing is correctly configured.

Thanks for confirming my understanding. i'ld like to see taht information as part of the supported scenarios

Hi everyone,
Sorry but what type of trust do we need? One Way, 2 Way?
To me the document is not clear enough. And also for some of our customers.
Thank you!


php samples

Is your feature request related to a problem? Please describe.
php samples for distributed transaction.

Please assign this issue to me

php sample has moved to  https://github.com/CECTC/dbpack-samples/tree/main/php


support for code blocks

Hey, I have been waiting for such an extension for a long time... Thank you for doing this.
It seems that code blocks are not supported.  Any plans to ?

Glad you find the extension useful! I'm not planning on supporting code blocks, but likely would accept a PR to implement this.


Javascript logic error

Challenge http://freecodecamp.com/challenges/bonfire-return-largest-numbers-in-arrays has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
Here is the code:
function largestOfFour(arr) {
// You can do this!
var arraylength = arr.length;
//asdf
var finalArray = [];
var comparer = [];
var xterminate = 0;
while (xterminate !== arr.length){
if(arr[xterminate][1] < arr[xterminate][2]){
  comparer[1]=arr[xterminate][2];
}
else{
  comparer[1]=arr[xterminate][1];
}
    if(arr[xterminate][3] < arr[xterminate][4]){
  comparer[2]=arr[xterminate][4];
}
else{
  comparer[2]=arr[xterminate][3];
}
    if(comparer[1] < comparer[2]){
  finalArray[xterminate]=comparer[2];
}
else{
  finalArray[xterminate]=comparer[1];
}

xterminate++;
}
//asdf
arr = finalArray;
return arr;
}
largestOfFour([[4, 9, 1, 3], [13, 35, 18, 26], [32, 35, 97, 39], [1000000, 1001, 857, 1]]);
//The output on freecodecamp is [9,35,97,1000000]
//

Obviously I had a brainfart because everything usually starts with 0 not 1, including array indexes.


Dual Monitors on Mac Issue

Describe the bug: On macos, if you are running two monitors, your secondary monitor will go dark.
Screenshots or videos showing encountered issue:
Primary Monitor:

Secondary Monitor:

osu!lazer version: 12292020
Logs:

database.log
performance.log
network.log
runtime.log

I assume this is about exclusive fullscreen only, or borderless as well?
Does this work if you run the game with the --tk command line argument?

This is indeed only in borderless. How do you run the game from the command line?

This is not the case for me. Please include your system specs (graphics card, OS version, monitors).

System: Macbook Pro 13" late 2012
OS Version: 10.15.7
RAM: 8GB
GPU: Intel HD Graphics 4000
Primary Display (External monitor): Dell P2319H Resolution: 1920x1080
Secondary Display (Built-in screen): 13.3" Retina Display

Might be an issue with mission control.
Could you please confirm whether
System Preferences > Mission Control > Displays have separate Spaces

is checked?

Might be an issue with mission control.
Could you please confirm whether
System Preferences > Mission Control > Displays have separate Spaces

is checked?


e2e Tests fail

Hey @mjbvz it looks like e2e tests now fail since either the TypeScript update or VSCode update.
https://github.com/styled-components/typescript-styled-plugin/actions/runs/4601280928/jobs/8128959986#step:7:12
I reverted both TypeScript and typescript-template-language-service-decorator and it still fails, so it maybe an update in vscode itself.
I don't think this test suite has changed since you last wrote it
Do you know what this could be?
Example of a real request/response using current version
The below is adding background-color:  and hitting ctrl + enter with "typescript.tsserver.log": "verbose" enabled in the settings.
Info 362  [08:34:52.770] request:
    {
      "seq": 85,
      "type": "request",
      "command": "completionEntryDetails",
      "arguments": {
        "file": "/home/jase/workspace/vscode-styled-components/src/tests/suite/colorize-fixtures/attrs.js",
        "line": 5,
        "offset": 20,
        "entryNames": [
          "aliceblue"
        ]
      }
    }
Perf 363  [08:34:52.770] 85::completionEntryDetails: elapsed time (in milliseconds) 0.3259
Info 364  [08:34:52.771] response:
    {"seq":0,"type":"response","command":"completionEntryDetails","request_seq":85,"success":true,"body":[{"name":"aliceblue","kind":"const","kindModifiers":"color","displayParts":[],"documentation":[{"kind":"text","text":"#f0f8ff"}],"tags":[]}]}

We can see that its working fine, when ran for real.
However, looking at the e2e test, we see a different story.

There's been no changes made to these tests since its been forked, so I guess something upstream has caused these to stop working.

I'm looking into a bug and found that the e2e tests work for me, perhaps worth trying again now?

Yes I fixed it the other day so it’s fine now, this can be closed. Out of interest what big are you looking into?

@jasonwilliams this bug here: https://github.com/styled-components/vscode-styled-components/issues/440
I'll raise an issue here with a failing test case


Extract metadata from data uploads

Uploaded shapefiles (and other formats) may have embedded metadata that would be useful to expose in SeaSketch and could be reformatted to be incorporated in the markdown-based metadata doc. This should be extracted somehow as part of the upload processing pipeline.

It doesn't look like most uploads have xml metadata available so I'm going to close this. There is a start in packages/spatial-uploads-handler/src/metadata.py if we want to revisit this.


Model save destination refactor

Provide a single save destination for all models such that both the notebooks exploring their results and the ensemble usage can access them in order to remove clutter and memory usage

This issue extends to all meta-models created and additionally the pipelines, specifically to encompass the k-means clustering models.


Release workflow should work

This action failed:
https://github.com/magda-io/magda-auth-google/actions/runs/769671995

fixed on master: https://github.com/magda-io/magda-auth-google/runs/3621924217


Remove duplicated file

This file have another with the same name. The major issue is with case sensitive O.S. like macOS. When I forked this project I get this issue. Thanks.

Great, thank you!


Consider anylogger support?

First of all, thanks for noticing and mentioning ulog!  🤗
Now for this issue, I wonder if you noticed my other project, anylogger?
Would you consider helping to support it? I would love to have an anylogger-diary adapter 😃
EDIT: I already set one up: anylogger-diary. Would you like to help?

Firstly, no! Thank you for taking notice!
I guess I'll need to understand what anylogger is—perhaps you can help me understand this firstly.
But on the outset, sure! I'm sure we can work something out.

Thank you for that explanation @Download I mean that makes perfect sense. The rust world also has this concept, partly the motive behind some of the api design of this library.
However I don't think it's well suited to make anylogger a dependency of this library. But am more than happy to assist in anyway around the idea of anylogger-diary. So what we must do next, and why!

Got a new job and swamped with work, so basically didn;t do anything for over a month now. 🙄
You don't have to do anything of course :)
But if you feel like a challenge, you could have a quick look at anylogger-loglevel. It's an adapter for loglevel. I basically want to write a similar adapter for Diary. I will get to it one day but you could help make that happen sooner if you feel like it.


Update _row.scss

Removes !global to prevent display: table-cell; from being applied to all elements following a @include row(table); setting.

This, unfortunately, can't be removed as it's key to the core function. We know it's a bummer to have to reset this display after usage of table and are working to remove this nuisance in 2.0.


Added the OWASP encoding to prevent possible XSS attacks.

Added the OWASP encoding to prevent possible XSS attacks for the "security-mgt". Please review and merge.

Apply encoding for below also.
attribute encode
https://github.com/wso2/carbon-identity/pull/985/files#diff-8ece4d1dcc491095417a2aedee16f5f5R148
uri encode
https://github.com/wso2/carbon-identity/pull/985/files#diff-3223bc2a6e7febb1e90abfb989ab0355R44
https://github.com/wso2/carbon-identity/pull/985/files#diff-3223bc2a6e7febb1e90abfb989ab0355R49
https://github.com/wso2/carbon-identity/pull/985/files#diff-e180f2c71d74cda7ff46fcba08f2e54aR63
https://github.com/wso2/carbon-identity/pull/985/files#diff-e180f2c71d74cda7ff46fcba08f2e54aR69
https://github.com/wso2/carbon-identity/pull/985/files#diff-d063db1cd0b43de3fddc9be65014b216R67
https://github.com/wso2/carbon-identity/pull/985/files#diff-d063db1cd0b43de3fddc9be65014b216R75
https://github.com/wso2/carbon-identity/pull/985/files#diff-2ea8708e60a8956598b531c3ea97576eR38
https://github.com/wso2/carbon-identity/pull/985/files#diff-2ea8708e60a8956598b531c3ea97576eR44

Can merge


Add instructions for remote ray

Summary

Added instructions for fixing: PermissionError: [Errno 13] Permission denied: '/Users'
Relevant Issue(s)

https://github.com/PrefectHQ/prefect-ray/issues/26
Checklist

[ ] Summarized PR's changes in CHANGELOG.md

Tests fixed in https://github.com/PrefectHQ/prefect-ray/pull/48


Stopped to work in ver 1.25

Issue Type: Bug
Update VS Code version to 1.25. Try to run comand "Retrive Package". ERROR: command 'vsforce.retrieveCommand' not found
Extension version: 0.2.0
VS Code version: Code 1.25.0 (0f080e5267e829de46638128001aeb7ca2d6d50e, 2018-07-05T13:11:58.697Z)
OS version: Windows_NT x64 10.0.15063

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 3192)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: enabledvideo_encode: enabledvpx_decode: unavailable_softwarewebgl: enabledwebgl2: enabled

Memory (System)
15.88GB (11.13GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

I'm also getting not found errors when running any command with v 1.25 of VS Code and 0.2.13 for vsforce.
I'm on macOS 10.13.5

The same thing is happening with another extension: forcecode

This was suggested:
Re-downloaded v1.24 the project and all extensions loaded as normal.
https://code.visualstudio.com/updates/v1_24
Easy work-around until a fix is out.

I have just added the bug label.
I think this is related to a vscode breaking change in their core APIs that the extensions can use.
In the meantime if you need a local extension for salesforce development, Salesforce as a company has finally released one and it contains some of the features of this one (even if I preferred the way this one is built), this can be a workaround.
I do not have an estimate in when this could be fixed.


hard coded private static final String CALLBACK_PATH = "/Callback" in LocalServerReceiver.java

Currently CALLBACK_PATH is hardcoded to "/Callback" in LocalServerReceiver.
There should a way of overriding this

This issue may no longer be relevant due to its age. Feel free to re-open.


WIP: Check if project is missing from vendor during ensure

What does this do / why do we need it?
Currently it appears (see #883) that a project missing from the vendor directory isn't added during a dep ensure.
    If the vendor directory already exists, and the lock file hasn't
    changed, even though a project may be missing from the vendor
    directory, dep ensure would not add it.

    This change checks if we're not already writing the vendor directory
    whether any of the projects are missing from the vendor directory
    and if they are, ensures the writer writes out the vendor directory.

What should your reviewer look out for in this PR?
Everything, this is my first contribution, importantly, the original issue needs to be verified first. Then is this the best way and location to do this behaviour.
It's a WIP until the issue can be verified first.
Do you need help or clarification on anything?
The error handling from fs.IsNonEmptyDir, it's not clear how we should handle these errors (log the error and continue, or try and delete the directory?).
The verbose logging, I couldn't find nearby examples of best current practices, so I've just made it up. I think we should log this behaviour, but is this the correct logger, format, message and terminology (vendor path or vendor tree or something else)? Currently only one message will be written and then the loop is broken, so the message instead be %q (and potentially more) needs to be added to vendor path?
Commit message needs to be verified.
No tests are included, as this is pretty critical behaviour, I presume an integration test or similar would be in order?
Which issue(s) does this PR fix?
Fixes #883.

Note to self: try and remove the previous check if the vendor folder exists, no point checking parent and children, which just checking the children is probably enough. Also what's solution != nil in the previous if block?

Closing in favour of #889.


Enhancement: Export/back up instance

I might try to tackle some MarkUs issues that I can reproduce on an existing MarkUs instance; it would be helpful if I could back up the entire instance (using a MarkUs admin account) and restore on a different machine. Of course, some user account renaming (or built-in account with no external authentication) needs to be used so that authentication can take place on the new machine,

resolved by #5069

note that #5069 only archives/unarchives files on disk, you will also need to migrate the database manually to the new instance (if using postgres I would recommend the db_dump command)


ActiveJob and Que arguments compatibility issue

Since Que using HashWithIndifferentAccess as default json converter symbol hash keys and named arguments do not work with ActiveJob.
ActiveJob use transform_keys to deserialize symbol keys
# activejob/lib/active_job/arguments.rb

def transform_symbol_keys(hash, symbol_keys)
  hash.transform_keys do |key|
    if symbol_keys.include?(key)
      key.to_sym
    else
      key
    end
  end
end

BUT
{ "foo" => 1 }.with_indifferent_access.transform_keys(&:to_sym) # => {"foo"=>1}

So jobs like
class AwesomeJob < ActiveJob::Base
  def perform(params)
    # code using params[:foo]
  end
end

will fail with no obvious reason

Another reason to not use ActiveJob. There have been a few others, if you search the issues.
Does everything work as expected if you set Que.json_converter = Que::SYMBOLIZER instead? If so, I think the correct fix is probably to just document that, or to add it to the ActiveJob Que adapter.

@chanks Que.json_converter = nil works fine

Closing old issues. This should no longer be a problem, our ActiveJob integration is much better (and better-tested!) now.


Merge Foundations and Standards subprojects

This PR merges the Foundations and Standards projects into a single subproject. This was discussed with both Carol and Paul and both agreed to make this change.
CC @afshin

Calling a vote from the:

@jupyter/executive-council
@jupyter/software-steering-council

Quorum has been reached and the vote passed at unanimity (with one vote not cast).


[New] add "the number of vaccinated" to VaccineData as well as "the number of vaccinations"

Summary of this new feature
"people_vaccinated" (the number of vaccinated people) was added to the raw dataset in "Our World In Data".
https://github.com/owid/covid-19-data/tree/master/public/data/vaccinations
This is also informative data as well as the number of vaccinations (administored doses) and we can add this data to the cleaned dataset of VaccineData as Vaccinated records.

This is related to #573.

With vaccinations do we mean a single vaccine dose or a fully vaccinated individual (which is single or double-dose) depending on the type? Because if it is the first one then we have a problem in using these data. I think "our world in data" differentiates between these two with categories "Total number of people who have received at least one dose of the COVID-19 vaccine" and "Total number of people who have been fully vaccinated against COVID-19".

I think "Total number of people who have received at least one dose of the COVID-19 vaccine" could be used. By dividing "the number of vaccinations (doses)" with this new data, mean number of doses people received can be calculated. We should discuss the name of this new data (e.g. Vaccinated_once), but what is the problem when using this data?
The second one (fully vaccinated) can be also included in VaccineData, but definition of "fully" may be changed in the near future. We say "fully vaccinated" when received two doses currently. However, we may need to take doses more than twice to keep immunity for long time.

In exploratory analysis and visualization yes we can use either one.
But, in my understanding, in the modelling and the control factors there is no point in using half-vaccinated people. One vaccination should mean one full vaccination (one or two doses depending on the vaccine type). What might be needed in the future to keep the immunity or to extend it, is another issue I think.

No publications, but some studies are indicating that people who was (or might) infected asymptomatically show sufficient immune responses when half-vaccinated. https://www.bmj.com/content/372/bmj.n308
Because this does not show discrepancy with the role of vaccination and primary/secondary immunity, I'm looking at these studies with interest as a clinical research associate.
In data science, all of the three variables (the number of vaccinations, fully or partially vaccinated persons) can be used in parameter prediction of future phases. After adding them to the regression model for future engineering #611, we can select necessary features with Elastic Net model (which has been implemented).

Additionally, ISO3 codes will be added to the cleaned dataset of VaccineData.

With #630, added the following columns to the cleaned dataset of VaccineData.

ISO3 (pandas.Category): ISO3 codes
Vaccinated_once (int): cumulative number of people who received at least one vaccine dose
Vaccinated_full (int): cumulative number of people who received all doses prescrived by the protocol


fix(datahub-client): fix shadow jar build, correct spark-lineage url …

…parsing
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

LGTM!


1.3

Seaport version 1.3 addresses two limitations inherent to version 1.2:

On 1.2, token transfers could occur after restricted and contract order checks (validateOrder and ratifyOrder) under specific conditions (namely, when multiple orders are being fulfilled at once and conduits are utilized or there are unspent offer item amounts). 1.3 ensures that all token transfers across all fulfilled orders, even returning excess native tokens, occur before any restricted or contract order checks are performed. (Be sure not to transfer any tokens back to Seaport as part of zone or contract offerer logic as they will not be recoverable during the current fulfillment.) This change will make post-execution zone and contract offerers much easier to work with, as otherwise they would need to perform redundant checks and would require the fulfiller to specifically tailor their fulfillment methods to work around the transfer limitations — huge thanks to @androolloyd for raising this issue to the Seaport Working Group!
On 1.2, any fulfillments where the offerer and the recipient have the same address would be "filtered" from the executions array (as there is no reason an associated transfer needs to be performed). 1.3 allows for contract offerers to offer native tokens which are expected to be provided to Seaport as part of the call to generateOrder — in these cases, or as part of a match operation, those native tokens have already been supplied to Seaport by the time the execution is filtered, meaning the corresponding consideration item would not be accounted for and those native tokens would eventually be returned to the caller instead. (This means that offerers on 1.2 need to be very careful not to simultaneously offer native tokens and require native tokens as consideration items; this mainly affects contract offerers.) In 1.3, executions with native token item types are not filtered from the executions array.

There are also some additional optimizations:

The typehash directory has been replaced with a large conditional statement that selects an appropriate constant typehash value based on the height of the bulk order tree. This avoids needing to perform an extcodecopy (thereby touching another account and costing 2600+ gas) at the expense of additional runtime code on Seaport itself.
Some additional performance improvements have been made as a consequence of addressing the limitations above; for instance, fulfilling multiple orders where no restricted or contract orders are present is now less expensive, and implementing the _unmaskedAddressComparison check inline with the native token check as part of execution filtering led to the removal of a number of superfluous mask operations (it turns out that function was actually not unmasked as the address arguments were still being masked when entering the function).

Finally, the version has been bumped from 1.2 to 1.3. There are additional changes required to bring the reference contracts fully in-line with the optimized contracts, and more tests to be written to validate the new behavior and ensure that coverage gaps with implementing zones and contract offerers are fully addressed, but (barring any unforeseen issues) this PR contains the full set of changes between Seaport 1.2 and 1.3.

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

Coverage data is based on head (6e6d006) compared to base (e99e1e3).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #984   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           47        47
  Lines         2661      2671   +10
  Branches       393       394    +1
=========================================
+ Hits          2661      2671   +10

Flag
Coverage Δ

foundry
77.71% <81.25%> (-0.10%)
:arrow_down:

production
100.00% <100.00%> (ø)

reference
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

contracts/Seaport.sol
100.00% <ø> (ø)

contracts/lib/Consideration.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationDecoder.sol
100.00% <ø> (ø)

contracts/lib/LowLevelHelpers.sol
100.00% <ø> (ø)

reference/ReferenceConsideration.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationBase.sol
100.00% <100.00%> (ø)

contracts/lib/FulfillmentApplier.sol
100.00% <100.00%> (ø)

contracts/lib/OrderCombiner.sol
100.00% <100.00%> (ø)

contracts/lib/Verifiers.sol
100.00% <100.00%> (ø)

reference/lib/ReferenceConsiderationBase.sol
100.00% <100.00%> (ø)

... and 2 more

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

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


Has the  setTitleBarHint() been implemented ?

Hi, as the title says, has Has the  setTitleBarHint() been implemented ?
I am trying to show only maximize button in window/dialog, but for some reason, it is not working.
I have tried setting titlebar hints with
titleBar.setTitleBarHint(['max'])
But all three buttons still show.

That was indeed implemented but it would've not worked like that way because it only had the "print" function at that time, for testing.
I should've been explained that in commit message. Sorry for that
I've just changed up a bit to make setTitleBarHint work and it works like a charm (to me, at least).
Oh by the way happy new year.
If you have any questions feel free to ask 🙂

Thank you.
It works now.


[now-go] Improve test for custom build flags

This PR improve test for @now/go custom build configuration.

Codecov Report

Merging #2999 into canary will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           canary    #2999   +/-   ##
=======================================
  Coverage   13.37%   13.37%
=======================================
  Files         268      268
  Lines       10344    10344
  Branches     1218     1218
=======================================
  Hits         1384     1384
  Misses       8898     8898
  Partials       62       62

Continue to review full report at Codecov.

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


test-end-to-end-tests: TS5 fixes

Minor fixes to unblock TS5 adoption

/azp run Build - client packages


fix: wait for form submission before approve to confirm routing in multi-hop

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

Testing

Engineering

Operations

Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4927   👈

This comment was auto-generated by Graphite.


Using Koila with Big Sleep?

Hi, this project could be revolutionary, if only I knew how to use it :)
You surely heard of Big Sleep, right? Using CLIP and BIGGAN, from just a line of text it's capable of generating amazing visuals and unique works of art, which is why is getting more and more popular among an ever growing number of artists and curious people who have been deeply fascinated by the potential of these techniques...
However many of us have not been able to run these kind of projects on our machines because of low VRAM in consumer GPUs and crazy market prices and ended up stumbling almost immediately on the infamous CUDA Memory Error... (Yes, Google Colab is nice and all, but running this projects locally makes for a totally different kind of "technological chill" if you know what I mean :) )
So, I was thinking, would it be possible to apply Koila to Big Sleep, to fix those errors?
If so, that'd be a game changer! It would at the same time benefit a huge number of users, and translate into massive traction for Koila!
Looking at the README I thought the whole process would have been very simple so I tried looking at it myself... but in the end I had to give up because I've just approached this field and I still miss much of the necessary background to figure out these kind of details.
So yeah, would you consider providing a short example for this use case of Koila + Big Sleep, if feasible? In that case just a few lines of code could potentially mean the beginning of a little revolution :)

Hi, thanks for the write up!
As a poor student, I feel you, the constant struggle to reduce memories so that our machines can handle it :(
As it stands, I could not make it work on Google Colab, which uses python3.7 (#7) and the library does not support a wide range of layers yet. In theory it could, but I haven't found the time to really implement all those interfaces. See #18 for the current status. Right now, it is more of a proof-of-concept rather than a productive ready library.
With that said, regarding your problem, since koila works as an automatic gradient accumulator (that slices up batches, calculates available memory, and the accumulates the gradients for you), have you tried using gradient accumulation to reduce memory usage yet? If not, it's a great way to lower memory foot print (on GPUs) for deep learning algorithms.

@rentruewang thanks for your reply! Now I understand things a little better.
I believe that Big Sleep is already using gradient accumulation.
In facts it provides a "--gradient_accumulate_every=" option right in the command line interface, which defaults to 4.
I tried increasing that number to much higher values, but it didn't help, and I always received "RuntimeError: CUDA out of memory".
So that probably means Koila won't help anyway in this situation, correct?
If so, well thanks anyway for your help... at least I learnt more about how Koila works and gradient accumulation, and probably I might be able to apply these concepts to other projects until Koila reaches a more mature state.

@illtellyoulater Actually, I think the gradient accumulation are used very differently, so using koila in big sleep may not help. Let me explain.
Disclaimer: This analysis is my explanation after a quick read over big sleep's source code.
Big sleep works by passing in a list of text samples, using gradient descent to find the best images that minimize the 'distance' that CLIP finds, and performs gradient descent on that image to make that image closer to a target image that minimizes the CLIP distance.
Here's how gradient_accumulate_every is used in the repo:
https://github.com/lucidrains/big-sleep/blob/49b20f9c8169667395b68d1bbe169d28137fea8e/big_sleep/big_sleep.py#L449-L453
It is used to increase the norm of the gradients, to make the optimizer step bigger. I'm curious as to why he is using gradient accumulation here; I may be wrong, but since the inputs are the same, it's effectively scaling the gradients by an integer factor (there's not a need for gradient accumulation here).
Compare to that, koila works by splitting up a batch by

Finds the batch size that fits into memory.
Splits a batch if the batch size is larger than that threshold.
Passes the splits through the model.
Accumulates the gradients.

So you see, it works by reducing batch sizes in forward passes, but uses gradient accumulation to maintain the same effective batch size. That means it has the following deficiencies:

When the batch size is already 1, then there's nothing to gain by using koila.
If the author doesn't use batches, then koila doesn't work at all.

Hope this explanation makes sense!

Great info, thanks! Probably it could be useful to add this to the repository README!

Good idea. Thanks!


⚠ Bofrost.de has degraded performance

In c70f6b1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1746 ms

Resolved: Bofrost.de performance has improved in 2226a56.


Cleanup code

I found multiple instances of unused code. I believe unused code should be removed/commented out for better code readability.
Screenshots
Location : src/components/Menu.jsx

Location : src\utils\canvas.js

Location : src\components\Footer.jsx

Kindly assign the issue to me🙏

I also want to add titles to the menu buttons which don't have it already(draw shape, fill shape, thickness, download)
I will also fix titles like IncreaseHeight, DecreaseHeight which are method names rather than descriptions.

@RushilJalal Under which program you want to contribute SSOC or GSSOC?

@RushilJalal Under which program you want to contribute SSOC or GSSOC?

SSOC

@RushilJalal Assigned you the issue, Best of Luck :)


The webservice url is no longer working

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 27b56c32-971a-739d-40b6-5e2a2fb82c65
Version Independent ID: 219c2bb0-0b17-1af4-7b87-1ea3e9c3f228
Content: Virtual table walkthrough using the OData Data Provider in Microsoft Dataverse - Power Apps
Content Source: powerapps-docs/maker/data-platform/virtual-entity-walkthrough-using-odata-provider.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

@akill25445 - As per the article just following the example web service URL.
Important
The web service url used for this walkthrough isn't a functioning web service.
Closing issue


Alexa/SmartHome: Wrong response for Alexa.PercentageController

Home Assistant release with the issue:
0.82.1
Last working Home Assistant release (if known):
n/a
Operating environment (Hass.io/Docker/Windows/etc.):
Debian Linux / Python Virtual Env (x86)
Component/platform:

https://www.home-assistant.io/components/alexa/#smart-home
Description of problem:
I have added a cover via the smart_home Alexa component and created a Skill with haaska. Sending commands from Alexa to HomeAssistant works (the cover is set to the requested position). However, Alexa always answers with "I'm not quite sure what went wrong".
When looking at the logs, it seems that the HA Alexa component returns a wrong response: The properties of the response contain the values for namespace Alexa.PowerController instead the properties for the namespace Alexa.PercentageController:
2018-11-25 18:53:21 DEBUG (MainThread) [homeassistant.components.alexa.smart_home] Received Alexa Smart Home request: {'directive': {'header': {'payloadVersion': '3', 'correlationToken': 'xxx', 'name': 'AdjustPercentage', 'namespace': 'Alexa.PercentageController', 'messageId': 'xxx'}, 'endpoint': {'scope': {'token': 'xxx', 'type': 'BearerToken'}, 'cookie': {}, 'endpointId': 'cover#oeq0983864'}, 'payload': {'percentageDelta': -25}}}
2018-11-25 18:53:21 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=cover, service=set_cover_position, service_call_id=98120b4af3c143bc825a840fedebf784, service_data=entity_id=cover.oeq0983864, position=0>
2018-11-25 18:53:21 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event alexa_smart_home[L]: response=name=Response, namespace=Alexa, request=entity_id=cover.oeq0983864, name=AdjustPercentage, namespace=Alexa.PercentageController>
2018-11-25 18:53:21 DEBUG (MainThread) [homeassistant.components.alexa.smart_home] Sending Alexa Smart Home response: {'event': {'header': {'payloadVersion': '3', 'correlationToken': 'xxx', 'name': 'Response', 'namespace': 'Alexa', 'messageId': 'xxx'}, 'endpoint': {'scope': {'token': 'xxx', 'type': 'BearerToken'}, 'cookie': {}, 'endpointId': 'cover#oeq0983864'}, 'payload': {}}, 'context': {'properties': [{'value': 'OFF', 'name': 'powerState', 'namespace': 'Alexa.PowerController'}]}}

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
alexa:
  smart_home:
    filter:
      include_entities:
        - cover.OEQ0983864

Traceback (if applicable):

Additional information:
Related documentation:
https://developer.amazon.com/de/docs/device-apis/alexa-percentagecontroller.html

Yes, issue still exists in HomeAssistant v0.87.1

Same issue with alexa cloud. v0.88.0

Same Problem for me

Problem still exists on 0.90.2

Problem is resolved for a few weeks already. This ticket should be closed


Aiida 1.0 compat

For the record, here is my AiiDA-1.0/python-3 compatibility branch

@yakutovicha my PR is a bit more invasive. One of the differences is that I adapted the tests to be run properly with pyunit. And that everything is Python-3.6+ only due to the timeframe (Python-2 supports ends this year), mostly due to the f-strings (could be changed back again, though).

Hi @dev-zero. I according to our internal discussions, aiida will keep supporting python2 at least till the end of this year. So the goal we set up for ourselves is make as much plugins as possible python2/3 compatible as well.
There are certain things that wouldn't work in your current version of the plugin. For example the following way of specifying inputs is not supported anymore:
"structure": {
'valid_types': StructureData,
'additional_parameter': None,
 'linkname': 'structure',
  'docstring': "Choose the input structure to use",
  },

Here you can find the draft of the migration guide.
A suggestion from my side would be: I merge my PR (which is already working) and then we discuss your design decisions during the plugin migration week and implement them upon agreement. Currently I am on vacations, so won't be much available this week.

Hi @dev-zero. I according to our internal discussions, aiida will keep supporting python2 at least till the end of this year. So the goal we set up for ourselves is make as much plugins as possible python2/3 compatible as well.

@yakutovicha well, those are the guidelines for AiiDA, and I see why you want to follow them in the plugins as well and eventually I would have brought back Python 2 support, but I wanted to start from something more clean and then introduce back-compatibility.

There are certain things that wouldn't work in your current version of the plugin. For example the following way of specifying inputs is not supported anymore:
"structure": {
'valid_types': StructureData,
'additional_parameter': None,
 'linkname': 'structure',
  'docstring': "Choose the input structure to use",
  },

Here you can find the draft of the migration guide.

Thanks, that guide didn't exist when I started :( or it didn't show up in Google searches.

A suggestion from my side would be: I merge my PR (which is already working) and then we discuss your design decisions during the plugin migration week and implement them upon agreement. Currently I am on vacations, so won't be much available this week.

Well, I can do another PR based on your code with the pylint-compatible tests plus some of the other changes/bugfixes I have.

@dev-zero yeah, that is unfortunate that we started to work on the plugin migration separately. Working together would require much less time.
Also, just to make you aware: I will most probably squash my commits into a single one, it order to make the history less polluted. And then will merge it into master.

@yakutovicha https://github.com/aiidateam/aiida-cp2k/network is otherwise a good way to check for (public) activity and is what I used to determine whether someone was already working on it


drivers: sensor: Fix pipeline issues

Pull in upstream changes to fix errors encountered in the pipeline

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

edtt
https://github.com/zephyrproject-rtos/edtt/commit/000fb87261beaf33f80a8868e73857bd62edc668
https://github.com/zephyrproject-rtos/edtt/commit/8ef968c1471769af61ba3e5befb6b119b22a7afe
<EMAIL_ADDRESS>

hal_nxp
https://github.com/zephyrproject-rtos/hal_nxp/commit/3ee6020efc1f8323d0fdc85615d3477161f0aa1f
https://github.com/zephyrproject-rtos/hal_nxp/commit/d957472002a3758154f402e982d95ce90cf58e12
<EMAIL_ADDRESS>

hal_stm32
https://github.com/zephyrproject-rtos/hal_stm32/commit/83cf59e4309e5f1758a76c0513c437e0fbcee40b
https://github.com/zephyrproject-rtos/hal_stm32/commit/c36136b253a46ed8dd63525eeee659393047ce83 (main)
<EMAIL_ADDRESS>

mbedtls
https://github.com/zephyrproject-rtos/mbedtls/commit/7fed49c9b9f983ad6416986661ef637459723bcb
https://github.com/zephyrproject-rtos/mbedtls/commit/6e166050075688fd3cf3d0cb3fc34a1c52df2496 (zephyr)
<EMAIL_ADDRESS>

nrf_hw_models
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/85ecf8e3bda805fa1405db5048d77e2980c976f0
https://github.com/zephyrproject-rtos/nrf_hw_models/commit/d8f125e1988221ebfea5944fc3118f1780787ccc
<EMAIL_ADDRESS>

openthread
https://github.com/zephyrproject-rtos/openthread/commit/a1979fdd8ed756468719cc4921b04a57efcf9f15
https://github.com/zephyrproject-rtos/openthread/commit/242c7cc7c3a80c985476689b64cdb6d8fbcf5b6d (main)
<EMAIL_ADDRESS>

picolibc
https://github.com/zephyrproject-rtos/picolibc/commit/04ada5951cbaf8e7b17f8226ce31cb6837c28ba7
https://github.com/zephyrproject-rtos/picolibc/commit/98e59b70d6ef8eb18f7dccc3d39cecaa0658fa4f
<EMAIL_ADDRESS>

psa-arch-tests
https://github.com/zephyrproject-rtos/psa-arch-tests/commit/f4fc2442b8e29e2a03d9899e46e5a3ea3df8c2c9
https://github.com/zephyrproject-rtos/psa-arch-tests/commit/24ed42e34e03ebbc945a7204819c1471cce2bda8 (master)
<EMAIL_ADDRESS>

tf-m-tests
https://github.com/zephyrproject-rtos/tf-m-tests/commit/bcb53bccccdc05c713aade707e7a8ddad35c210f
https://github.com/zephyrproject-rtos/tf-m-tests/commit/0f80a65193ddbbe3f0ac38b33b07b26138c11fa7 (master)
<EMAIL_ADDRESS>

thrift
N/A
https://github.com/zephyrproject-rtos/thrift/commit/10023645a0e6cb7ce23fcd7fd3dbac9f18df6234 (zephyr)
N/A

trusted-firmware-m
https://github.com/zephyrproject-rtos/trusted-firmware-m/commit/13abde213930ffdf600cf8f01113da8a5fdd9d9c
https://github.com/zephyrproject-rtos/trusted-firmware-m/commit/f2a639c8d1842acb2964a27461f5c9cfdfaa4d16 (master)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.


Magellan should notify traffic control when it successfully starts to use a claim

This may be only possible for frameworks that send rich data back to magellan, since we need to definitively know that the test has started running in selenium (session id acquisition may be a good way to signal this).
This would allow claims of VMs to more tightly track remote actual usage.

This is implemented.


fullWidth not working on

The component <Select /> does not support the property fullwidth from Material UI.

This is happening because fullWidth property belongs to <FormControl /> component. See the line.
I think we can add a new property to the component like formControlProps. In this case, the <Select /> component is more customizable.
I will make a Pull Request with this improvement.

I'm sorry, but this is out of my league. My intention was to use in a way like here. Anyway, I managed to make it work through classes, this way, so this was just a heads-up.
But I did find that the <Select /> component does not work when I try to send data from an api. I'm doing it through the useEffect and useRef methods, however while <TextField /> works fine, <Select /> does not, and, again, this is way out of my league.

@zys Can you provide examples to reproduce you issue with send data from an API?

Sure, here goes:
import React, { useRef, useEffect } from 'react';
import { makeStyles } from '@material-ui/core/styles';
import Grid from '@material-ui/core/Grid';
import { TextField, Select } from 'unform-material-ui';
import MenuItem from '@material-ui/core/MenuItem';
import { Form } from '@unform/web';
import { Scope } from '@unform/core';

import api from '../../services/api';

const styles = {
  gridRow: {
    margin: 0,
  },
  fullWidth: {
    width: '100%',
  },
};

const useStyles = makeStyles(styles);

export default function Example(props) {
  const classes = useStyles();
  const formRef = useRef(null);

  useEffect(() => {
    async function fetchData() {
      const dat = (await api.get(`someRoute/${props.match.params.id}`)).data;
      formRef.current.setData(dat);
    }

    fetchData();
  });

  return (
    <Form ref={formRef}>
      <Grid container item spacing={3} xs={12} className={classes.gridRow}>
        <Grid item xs={12} md={6}>
          <TextField name="name" label="Name" fullWidth />;
        </Grid>
        <Scope path="endereco">
          <Grid item xs={12} md={6}>
            <Select
              className={classes.fullWidth}
              name="country"
              label="Country"
            >
              <MenuItem value="br">Brazil</MenuItem>
              <MenuItem value="us">United State</MenuItem>
            </Select>
          </Grid>
        </Scope>
      </Grid>
    </Form>
  );
}

Console outputs this error:
SelectInput.js:301 Material-UI: you have provided an out-of-range value undefined for the select (name="country") component.
Consider providing a value that matches one of the available options or ''.
The available values are Brazil, United States.
This happens even with the correct value being sent, regardless of "Brazil" or "United States".
Since we are at this, the label of the <TextField /> stays overlapping the value that comes from the api.

@zys I made fast tests to reproduce your error with setData programmatically. it seems to be a real bug. But in this issue, we have two different issues. Can you open a new issue reporting this the new error?

I'll open two new ones, because neither has relation with the title of this issue. Ok?

@zys No, just one. This Issue already reports one of which you have cited. The issue with fullWidth property.

Olá bom dia,
Eu resolvi usando style={{ width: '100%' }}


Improve README.md

Language is awful.

Also add information about the little image size

Also add information about inspired by @anthonyzou's version.


chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-cos to v6.2.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-cos
module
minor
v6.0.0 -> v6.2.0

Release Notes

terraform-ibm-modules/terraform-ibm-cos
v6.2.0
Compare Source
Features

add support for one-rate plan (#337) (6c995dd)

v6.1.0
Compare Source
Features

Introduce management_endpoint_type_for_bucket input parameter allowing to specify what endpoint type (private, public, direct) the provider uses to interact with the COS management API. The parameter was previous named bucket_endpoint in version 5.X.X of this module.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

:tada: This PR is included in version 7.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update PeerSet metrics after every change

Motivation
We want accurate peer set metrics while we're analysing peer set behaviour.

Hey @oxarbitrage do you want to review this one?


BERTE-561 try skipping the merge through the queue when not needed

This pull request primarily focuses on improving the queuing system in the bert_e project. The main changes include modifying the pull request handling logic to check if queuing is necessary.

Hello tcarmet,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

one peer

LGTM but my knowledge in this area is limited

My knowledge as well 😅 , what I would ask is, if you can think of a high level scenario that I haven't covered, would be happy to write it up. (doesn't have to be now, can be later on as we work with the release of the feature).


Description fields associated with Derived Properties & Constraints

The Rosetta syntax which supports the ISDA CDM provides the ability to associate description fields to Conditions, with those being mapped as Constraints in Legend.
Those description fields are useful to state the rationale for a Condition/Constraint.  As an example, the cashflowAmount has an associated condition/constraint of being positive.   In Rosetta, the associated description states that "The cashflow amount should be a positive number, as the cashflow direction is indeed implied by the payer/receiver attribute."  It would be useful if Legend would provide the ability to specify this rationale alongside the constraint.
The same should probably apply to Derived Properties.

Thanks @pierrelamy! Adding @ffionwiggins to this thread as well. Would be great if we can add a bit more details to this feature request to properly evaluate feasibility. Is this something you could look into?

Technical-wise, we have a messageFunction for each constraint. This message would be output if the constraint is violated. However, I think what @pierrelamy means here is more like the description of the constraint. That, we don't have
As for description of derived property, it is the same as to how we provide description for normal properties. You can add a taggedValue to the property to do so.

This issue is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

This issue was closed because it has been inactive for 35 days. Please re-open if this issue is still relevant.


Ignore further unimportant pydocstyle error codes

I suggest always ignoring these two flake8 errors:

D202: No blank lines allowed after function docstring : does not affect HTML docs.
D405: Section name should be properly capitalized : docs will render fine either way.

Nb. These errors are not actually enabled at the moment in the CI suite; however, including the codes in the "ignore" list will ensure these checks aren't included when flake8 is run on the command line with flake8 --select=D path/to/file.py
See #290

Codecov Report

Merging #301 (2d15444) into integration (9bbc469) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           integration     #301   +/-   ##
============================================
  Coverage        62.28%   62.28%
============================================
  Files              108      108
  Lines            26780    26780
============================================
  Hits             16679    16679
  Misses           10101    10101

Impacted Files
Coverage Δ

resqpy/model.py
68.79% <0.00%> (ø)

Continue to review full report at Codecov.

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


About jdbc river

Hi Team
This is a question not a issue.
I have used old version elasticsearch-jdbc as a river.
Example:
curl -XPUT 'localhost:9200/_river/my_jdbc_river/_meta' -d '{
"type" : "jdbc",
"jdbc" : {
"driver" : "com.mysql.jdbc.Driver",
"url" : "jdbc:mysql://localhost:3306/test",
"user" : "",
"password" : "",
"sql" : "select * from orders"
"index" : "jdbc_index",
"type" : "jdbc_type",
"bulk_size" : 1000,
"max_bulk_requests" : 50,
"bulk_flush_interval" : "10s"
}
}'
Now，elasicsearch-jdbc is not a plugin,I read https://github.com/jprante/elasticsearch-jdbc/wiki/JDBC-plugin-feeder-mode-as-an-alternative-to-the-deprecated-Elasticsearch-River-API 。
Is't mean that i can only use shell to synchronous mysql data。
When i need to synchronous multiple mysql ，I need create multiple shell ？ Thank

Thanks for your request.
You have to run multiple JDBC importer on shell.
In a future version, I will find a better solution.

Thanks for your replay


docker-compose file for Mac

Summary
Fix #365
Details and comments
A new docker-compose-dev-arm64.yml file is added for Apply silicon system.

It can be great!
Also we can consider to provide an script to run (docker-compose pull and up) and detect it in automatic way in the script, pass to an argument (ARCH) and do it in transparent way.

I can not find a way to have only one docker-compose file so I'll create a small script file.


constants

I'm not a fan of having to declare a const, load it, then use it.
Better:
constants have a different index specifier: '%'
Still have to declare constants, but now you don't have to manually load it. Simply access it with it's index, prepended with a '%'.
Example:
const -32.5
const 12.2
mult $0 %0 %1
print $0

Decided not necessary for the IL


Docker Ports

Hello @raviwrk-official
Please configure Docker to use the below ports:

5005 for the uWSGI (not exposed)
85 for the Nginx (exposed)

As for all other AppSeed kits, once the user type docker-compose up --build the app should be LIVE at:
http://localhost:85
P.S. Usually ports 5000, and 80 are taken by other services.
ty!

Closing


gb test fails if the folder has name ending on '_test' e.g.: 'some_name_test'

gb test fails if the folder has name ending with '_test' e.g.: 'some_name_test'
I had directory named 'spec_test' with some integration tests inside and db test returned me that error:
# spec_test/testmain _testmain.go:12: can't find import: "spec_test"

Thanks for your report. Does this pass with the go tool ? Can you please
post the source of spec_test and testmain so I can create a test case.
Thanks
On Thu, Mar 24, 2016 at 1:20 AM, Viacheslav<EMAIL_ADDRESS>wrote:

gb test fails if the folder has name ending on '_test' e.g.:
'some_name_test'
I had directory named 'spec_test' with some integration tests inside and db
test returned me that error:
spec_test/testmain
_testmain.go:12: can't find import: "spec_test"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/583

@vgotsuliak I've not been able to reproduce this error. Can you please post some sample code that shows this issue. Thanks.


Including scripts selectively

The README generated by this project suggests that you can only include some scripts from a package with the following external-scripts.json:
{
  "hubot-fun": [
    "crazy",
    "thanks"
  ],
  "hubot-auto-deploy": "*"
}

However, trying this with the script package I just generated from this project, I am finding that I have to include the file extensions to get it to work:
{
  "hubot-fun": [
    "crazy.coffee",
    "thanks.coffee"
  ],
  "hubot-auto-deploy": "*"
}

Seems like there are three possibilities:

Something is screwy with my install, and for other people it works without the extensions
We've stopped adding .coffee extensions to our script files and I missed that memo
This is generating wrong documentation or wrong index.coffee, and these two should be reconciled

@probot-stale[bot] awww, that would be a shame! This is a real issue, after all.

Well, that's too bad. I wish someone would take a look at this issue besides you, stalebot.

@stale hi!

Have you tried recently? So much time has passed.


Allow to manipulate with multiple lines

[ ] Consider #105

This would be very useful.

+1!

+1. Is there any current support or workaround multiline items in an outline?

@sbc unfortunately, there is no workaround

Would be very cool, not many core things Roam have over Obsidian + Outliner combo.


question about modulated attention

when you visualize Figure7. Positional attention maps with different temperatures, why don't your figure have period ?
Since sinusoidal embedding has sin/cos func, does should it have some repeated shapes?

Fig. 7 presents the similarities between two positional embeddings. Each item is periodic, but the similarities are not.


chore(Dockerfile): update to base:0.3.0 image to get a slimmer image

[Current coverage][cc-pull] is 85.88%

Merging [#780][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master       #780   diff @@
==========================================
  Files            30         30
  Lines          2677       2677
  Methods           0          0
  Messages          0          0
  Branches        433        433
==========================================
+ Hits           2297       2299     +2
+ Misses          258        257     -1
+ Partials        122        121     -1

Powered by Codecov. Last updated by [a43f135...42b4809][cc-compare]
[cc-base-branch]: https://codecov.io/gh/deis/controller/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/deis/controller/compare/a43f1355f6365eedcf7a616c2fe3f53469c5aecc...42b4809de1015a5eec0b286e824ac5d47053842f
[cc-pull]: https://codecov.io/gh/deis/controller/pull/780?src=pr


[Bug] Handling the dynamic executor allocation.

for dynamic executor allocation, taking the max executors parameter and requesting the required executors.

LGTM


Feat:Add animation when liked button is clicked in the current playing song section

Describe the feature
The like button when clicked doesnt show any animation or anything which doesnt throw any indication whether the song is liked or not this can be improved by giving it some animation.Kindly assign me this under GSSOC'24.
Add ScreenShots
https://github.com/user-attachments/assets/055ae752-3f28-41a5-b340-b1c28326f296
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Riddhi162 go ahead


Make it possible to pickle accelerated model with AMP

Currently, when using accelerate with AMP, the resulting module is being modified so that it can no longer be pickled. The reason is that the forward method of the module is replaced by a decorated function:
https://github.com/huggingface/accelerate/blob/6ffab178accebda485295bddf8eb6bf436ff698f/src/accelerate/accelerator.py#L363
The decorated function, since it uses a closure, cannot be pickled. This is unfortunate because normally, PyTorch modules can be pickled and pickling is useful/necessary in certain circumstances.
A possible solution would be to wrap the function with a class instead of a closure:
import pickle
from accelerate.utils import convert_to_fp32, convert_outputs_to_fp32
from transformers import AutoModelForSequenceClassification

# PROBLEM
bert = AutoModelForSequenceClassification.from_pretrained('bert-base-uncased')
bert.forward = convert_outputs_to_fp32(bert.forward)
_ = pickle.dumps(bert)  # fails

# SOLUTION
from functools import update_wrapper

class ConvertOutputsToFp32:
    def __init__(self, model_forward):
        self.model_forward = model_forward
        update_wrapper(self, model_forward)  # optional
    def __call__(self, *args, **kwargs):
        return convert_to_fp32(self.model_forward(*args, **kwargs))

bert = AutoModelForSequenceClassification.from_pretrained('bert-base-uncased')
bert.forward = ConvertOutputsToFp32(bert.forward)
_ = pickle.dumps(bert)  # works

It's not beautiful but it would solve the issue. Alternatively, there might be a way to achieve the same thing using forward hooks but I'm not sure.
Info: accelerate.__version__ tested was 0.5.1.
NB: When using decorators, it is recommended to use functools.wraps. This way, help(bert.forward) shows the correct help. This is why I use update_wrapper in the proposed code, it does the same thing.

Thanks for flagging this and suggesting a solution. While using a class is not my first choice, it does work to solve the problem, so we should use this. Would you mind opening a PR with code since you proposed it?

I think you can test whether the model pickles or not as you did on any device. It's when trying to run training that we would need a GPU (and not even, basic operations can run on CPU with float16). I'm pretty sure the model in testing-utils/training can be used for instance in FP16 on CPU.


4.x: archetype - module-info opt-in

Description
fix #7735
By default, the module-info.java is not generated.
Documentation
no impact

This is done by #7775


db2 on zOS Support

Hello, just wondering - is there any plans to support db2 on zOS as well? Seems many of the SYS type tables are different from the Linux version of db2 used in the Debezium connection classes which determine tables with CCD enabled, etc.
Thanks in advance!

Unfortunately we don't have an access to zOS so it is quite difficult to provide the support :-(. For further questions or discussion please use our chat or mailing list. Thanks a lot!


mkDocs -> bash docstrings to mdbook

For the target use cases of makes (in large orgas / monorepos) it would be extremely useful to provide a doc generator function that generates mdbook docs from code comments.
Maybe some of the existing tooling such as https://github.com/nix-community/nixdoc/pull/25 can be hijacked.
To achieve the necessary standardization and reap it's benefits, I guess, it makes sense to think this through right from the start...

A natural extension of this Idew would be a mkRundeck funcrion that is like a manual & serialized version of a pipleline intertwimed in a markdown document with apropriate emergency response instructions.
See also: https://www.rundeck.com/

After my first half-way-through job implementation, I'm thinking that probably the best way to document a job is by just adding a README.md next to main.nix.

It will be nicely displayed in github
We could detect that and append it as a docs-md string to the scripts
We could then collect those outputs and build a mdbook out of it.
This approach can still be combined with parsing nix code comments in any main.nix, for things like function argument documentation.

I think I'll be working on this one next, since I want to set that standard & benchmark for our repo's evolution right from the start for myself & others.

This is going to be an absolute killer feature! :smile:

The readme to the side of main.nix sounds good, however readme's are free-form which means people can write in any order and not adhere to some standards
if we want to have some order (a schema), we can use YAML.

https://gitlab.com/fluidattacks/product/-/blob/master/makes/foss/modules/makes/criteria/src/vulnerabilities/data.yaml

and a schema for validating it with tools as https://ajv.js.org/ (we currently have it builtin into the framework):

https://gitlab.com/fluidattacks/product/-/blob/master/makes/foss/modules/makes/criteria/src/vulnerabilities/schema.json

Nix can process the YAML and render markdowns that then are feed into a markdown-to-html framework like https://docusaurus.io/ which make things look pretty nice:

https://docs.fluidattacks.com/criteria/vulnerabilities/

and since everything has a schema one can do further programmatic processing to generate inverse indexes, etc:

https://docs.fluidattacks.com/criteria/compliance/012

this is the source code of the generator, it uses a lot makeTemplate:

https://gitlab.com/fluidattacks/product/-/tree/master/makes/foss/units/docs/generate/criteria

@kamadorueda You make me have an idea!
Freeform, I guess is actually an advantage. Especially for things like runbooks, etc., which require some extensive context and explanation.
However, we can bake a structured short-help into the front matter! 🚀
Best of both worlds!

Re: frontmatter
Related #554

It would be nice to add two jobs (linux/macos) for /tests/scriptWithHelp into .github/workflows/dev.yml so we don't break it accidentally in the future


Choose a good name for this library

Context
In addition to what is discussed in this issue, there are also some discussions in Reddit:
https://www.reddit.com/r/rust/comments/q0wrhr/comment/hfbnom7/?utm_source=share&utm_medium=web2x&context=3
Names for other code generators
Let's look at how others name it.
python

pyo3 4.7k
rust-cpython 1.5k
milksnake 0.7k (inactive)

c/c++

cxx 3.2k
cbindgen 1.2k
autocxx 1.2k
cc-rs 0.8k
rust-cpp 0.5k
flapigen-rs 0.5k (multi language)

java

flapigen-rs 0.5k (multi language)
jni-rs 0.5k
java-rust-example 0.3k
j4rs 0.2k
robusta 0.1k
rjni 0.06k

javascript/js/node

neon 5.8k
napi-rs 1.1k
node-bindgen 0.2k

go/golang

rust-plus-golang 0.3k
rure-go 0.2k

Official doc
https://rust-lang.github.io/api-guidelines/naming.html

Crate names should not use -rs or -rust as a suffix or prefix. Every crate is Rust! It serves no purpose to remind users of this constantly.

https://github.com/rust-lang/api-guidelines/discussions/29
Most downloaded crates
https://crates.io/crates?sort=recent-downloads

cfg-if
range_core
rand
syn
proc-macro2
libc
unicode-xid
quote
getrandom
rand_chacha
autocfg
serde
bitflags
memchr
base64
lazy_static

Before you publish the packages to crates.io and pub.dev, do you have any plans to rename the project like suggested by some people on Reddit? To me flutter_rust_bridge, seems something very Flutter-related at first glance, which in fact is not true since the package is 100% compatible with pure Dart as well.

@shreyashsaitwal Ah good question! Indeed people in Reddit also suggests:

If you plan on releasing it on both, I'd give it the same name so people don't get confused.

So maybe I should use the same name to publish package for both flutter/dart and rust.

To me flutter_rust_bridge, seems something very Flutter-related at first glance, which in fact is not true since the package is 100% compatible with pure Dart as well.

Yes I totally agree. I originally thought it should be named dart_rust_bridge. But people in Reddit seems to be interested in how it can ease the programming Flutter+Rust. In addition, most people who uses Dart are using Flutter. Dart seems not to be widely used and the main usage is for Flutter.

README edited: https://github.com/fzyzcjy/flutter_rust_bridge/commit/efc14e58ecd7872b2486e3a076bc8d61208c93ea

So maybe I should use the same name to publish package for both flutter/dart and rust.

Yes, I think it makes more sense to publish it under the same name. Do you have any nominees for the new name?

@shreyashsaitwal Good question. People also suggest flechette and flap.
IMHO, if someone wants a ffi generator between Flutter/Dart and Rust, he may Google: flutter rust or things like that. The package name makes it possible to be found. On the contrary, if it has a fancy name, people may not be able to find it unless this package is really famous. Just my two cents.

It doesn't really matter to me what type of name you opt-in for -- fancy or descriptive. It's just that the current name seems too long to me. IMO, lib/package names shouldn't really exceed more than two words.

Good question. What do you think if I create a new Reddit post (or just add a comment in the current post?) asking for people to suggest and vote names?

What do you think if I create a new Reddit post (or just add a comment in the current post?) asking for people to suggest and vote names?

Nice idea, go ahead. 👍🏻

I am worried: I have already create one post yesterday about this lib. If I create one today, will people dislike this?

Given how great this project is, I don't think anyone would dislike it. But because the current post has already got some good engagement, editing it (or adding a comment in it) would be a good idea.

Thanks. Let me edit it.

Did you receive any kinds of notifications?

Nope, I didn't (and I've no idea if other people who commented would receive it. I don't use Reddit much). But after I refreshed the page I saw the edit.

I think any name is fine that is short. something like flut-rs or anything like that. people won't get reddit notifications when you edit post :) If you want to ask the community, ask in rust and rust-community discords, where people can reply immediately.

anyone who searches for a "flutter rust" is going to find it anyway because of the description or ReadMe. name doesn't really need to be too descriptive.

Okay, this just struck my mind rn. What if we called it ferb? Yes, it's inspired from Flutter Rust Bridge (frb).

@shreyashsaitwal That sounds like an animation https://en.wikipedia.org/wiki/Ferb_Fletcher

That sounds like an animation https://en.wikipedia.org/wiki/Ferb_Fletcher

Oh, that might cause copyright overhead maybe. Thanks for pointing out.

@shreyashsaitwal You are welcome!

Sorry, I should probably have created a new issue.

No problem.

Yeah. That was what I said long ago in this thread. But this thread literally is about naming, so I recommended short names, and it's easier to remember one word than 2.


Deployment failed at preflight stage

Today when I tried to deploy liberty-on-aro offer with an existing ARO cluster, it failed at the preflight stage with the following error message:
{
  "code": "DeploymentScriptError",
  "message": "The provided script failed with the following error:\r\nThe object Id of the service principal you just created is not successfully retrieved, please retry another deployment using its client id .. Please refer to https://aka.ms/DeploymentScriptsTroubleshoot for more deployment script information."
}

Additional issue found during the verification, when testing a deployment with an existing ARO cluster in the different resource group:
{
      "code": "DeploymentScriptError",
      "message": "ForbiddenError: The client 'b9b7b987-7498-4422-941c-166ab577750b' with object id 'b9b7b987-7498-4422-941c-166ab577750b' does not have authorization to perform action 'Microsoft.RedHatOpenShift/openShiftClusters/listCredentials/action' over scope '/subscriptions/1970354a-e600-4847-8848-89ea15c7a8c3/resourceGroups/jiangmaarorg/providers/Microsoft.RedHatOpenShift/openShiftClusters/clusteradae02' or the scope is invalid. If access was recently granted, please refresh your credentials."
}


WakaTime integration with Git Bash

Is it possible (or could it be added to the list) to integrate WakaTime with Git Bash? While I don't miss my Mac it was nice having WakaTime integrated with its terminal!
While I'd definitely prefer Git Bash if Powershell would cover a broader audience I'd use that as well.

Here's a command line git integration: https://github.com/rposborne/gitwakatime
Is that similar or were you thinking of something different?

I was actually hoping for the matching functionality to what is in the current Terminal integration, but for Git Bash.

Oh, I don't think the Git client supports extensions but maybe with a bash alias to wrap git?


Checking if update to mc version is possible

Check if and how many of mods can be update to a newer version of minecraft

Done in a3460581ab9a1496959e7279ba11b7d4068c7603


Tutorial crashes during final segment

Occasionally accompanied by minor graphical issues (score and accuracy disappearing or corrupting)
Running iPhone SE on latest iOS (12.2)

Just crashed again when returning to song select from the results screen after playing 6 maps or so. When I say "crash", I mean that the app freezes up entirely for 1-2 minutes while music continues to play, then eventually hard crashes back to home screen.

Fixed a while back :).


Use safe Snakeyaml yaml constructor

use safe constructor
Yaml yaml = new Yaml(new SafeConstructor());

@sbcd90

@sbcd90  Can we close this in favor of https://github.com/opensearch-project/security-analytics/pull/198


Small fix: Control reaches end of non-void function

Made/Proposed changes:

Made searchUsersWithPhoneNumbers: in QMUsersService.m line 554 to return desired BFTask

How should this be manually tested?
No need to test
Does the documentation need an update?
No
Reason:
QMServices/QMUsersService/QMUsersService/QMUsersService.m:556:1:
Control reaches end of non-void function
“searchUsersWithPhoneNumbers” has to return BFTask

Hi @joihelgi
Thank you for sending us your pull request. We can accept it, but can you please re-create it for our development branch?

No problem, it's done :)


[v1.19] Add v1.19.15

rancher/rancher#34632
rancher/rancher#34631

Note: Build failing cuz 1.19.15 isn't released yet, do not merge.


[in-review] Code Optimization for the Elixir SDK

I've added 2 most important packages i.e. credo and dialyxir - which pointed out many of the issues in the code. I've fixed most of them but few are still remaining, which can either be done by me or maybe other developers working on it. Alongwith that I've also added the module, function docs to Utils module.
Note: This is an open-source contribution

LGTM

Once the changes have been made @imahmedismail Could you resolve the conflicts, I merged other PR

All changes are as per description given in explanation of PR.


Updated: postman-canary 7.24.0-canary04

${}

34f03304-f40b-477d-93cb-5b0fcd2430a5

Newer version of postman-canary (7.25.0-canary05) is now available in master. 3a1435859c89405a04382b115df3872a402ae06b


add xsdb container

I tested it locally and works great

Jsut wondering why you closed this PR?

i closed the wrong one. sorry.


cgal: 5.1.1 -> 5.2

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107754 run on x86_64-linux 1

11 packages failed to build:

appcsxcad
libsForQt5.qcsxcad (libsForQt515.qcsxcad)
libsForQt512.qcsxcad
libsForQt514.qcsxcad
openems
python37Packages.python-csxcad
python37Packages.python-openems
python38Packages.python-csxcad
python38Packages.python-openems
python39Packages.python-csxcad
python39Packages.python-openems

4 packages built:

cgal_5
csxcad
prusa-slicer
super-slicer

builder for '/nix/store/v4dnvpcj4rhp6jdjbs3bc4jgdk9s4y9z-vtk-qvtk-8.2.0.drv' failed with exit code 2; last 10 log lines:
/build/VTK-8.2.0/Rendering/Qt/vtkQtLabelRenderStrategy.cxx:331:16: error: aggregate 'QPainterPath path' has incomplete type and cannot be defined
331 |   QPainterPath path;
|                ^~~~
/build/VTK-8.2.0/Rendering/Qt/vtkQtLabelRenderStrategy.cxx: In member function 'virtual void vtkQtLabelRenderStrategy::RenderLabel(int*, vtkTextProperty*, vtkUnicodeString)
':              /build/VTK-8.2.0/Rendering/Qt/vtkQtLabelRenderStrategy.cxx:442:18: error: aggregate 'QPainterPath path' has incomplete type and cannot be defined
442 |     QPainterPath path;
|                  ^~~~
make[2]: *** [Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/build.make:108: Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/vtkQtLabelRenderStrategy.cxx.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:7603: Rendering/Qt/CMakeFiles/vtkRenderingQt.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
cannot build derivation '/nix/store/m1h5cc42a4vl7xj4j3g3xz69q77wz5hl-qcsxcad-unstable-2020-01-04.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/mm3gavw3xascmnyg9372372sznnsh4vy-qcsxcad-unstable-2020-01-04.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/zzkz0wx2wm7a5azp6g5v29j6c1zk70b6-qcsxcad-unstable-2020-01-04.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/k9xpn8diqzvp0p04m1aqjw9g4xn4pgj9-appcsxcad-unstable-2020-01-04.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/k8bisv1jir5k6sllw5r20snnby2rclnv-openems-unstable-2020-02-15.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/8bh7mp47hacm3xqhlrb5wval50ka535r-python3.7-python-csxcad-unstable-2020-02-18.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/nv5i6d39jjlyrmr3knfmv402vllj4nqf-python3.8-python-csxcad-unstable-2020-02-18.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/pjwfp4l8jsi5xljmwvs1mn9pz2nn7vn1-python3.9-python-csxcad-unstable-2020-02-18.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/hbva1p4nv9lqplz5xk5j71j8awsi07vz-python3.7-python-openems-unstable-2020-02-15.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/raxvy0ym5fprn3kqvdzcldlw6xgmb4y2-python3.8-python-openems-unstable-2020-02-15.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/nlkvc5fvy8jp9kph205v8dnl2cn1gm61-python3.9-python-openems-unstable-2020-02-15.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/jgjb8pzk7dg1ij7ggbirmc7k6spc4b0d-env.drv': 11 dependencies couldn't be built

looks like an incompatibility with Qt5.15


Are Madmax plots working on Hpool?

I see reports of madmax plots not working in Hpool such as this..
https://twitter.com/sourabhs701/status/1403210660448641026?s=20
Does anyone here have success in making these madmax plots work in Hpool?

work

maybe he set the wrong keys, he should double check if the plots are accepted by official client

Thanks.. ticket closed.


repo: fix typo in "Sections" tutorial

Found it while looking into the tutorials 😄

Thanks for spotting this, merged :)


SASS-1658 - Navigation for income section

Description

Navigation for income section

https://jira.tools.tax.service.gov.uk/browse/SASS-1658
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ]  Have you checked to ensure its been rebased against the current version of main?

Whilst Reviewing

[ ]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current main that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of main?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[ ]  Have you checked the PR Builder passes?

To note this needs merging with journey tests and performance tests changing. If reviewing only APPROVE the changes until they are ready.

Can you please update the following:
uk.gov.hmrc:play-frontend-hmrc from 1.26.0-play-28 to 1.27.0-play-28


[Component Proposal] ChoroplethMapCard

Description
Both the EDS and Carbon data viz have a stance on the design of a Choropleth map. This issue is in place to track the decisions and actions taken to align these two approaches
EDS image:

EDS: https://ibm.invisionapp.com/share/U2NYW8D7DFV#/screens/319100265
Carbon: https://www.carbondesignsystem.com/data-visualization/advanced-charts#choropleth-map
Name of Pattern or Asset
Add the name and a link to the pattern you are referencing in IoT or Carbon
Choropleth map
Proposal
None at this time. There may be nothing to align, but as this is in the design only stage for Carbon data viz, we should ensure we involve them in any work on this chart in order to head off deviation before it happens.

closing. Implementation will come from Carbon charts. We can reopen if a team prioritizes this chart type.


[WIP] Update contributing

I think we should discuss the contributing.md so people will follow the correct process and so not to create a mess in the repo. Hello @Azzaare @arubhardwaj @Panquesito7. we should discuss this on discord lol.

@ReneganRonin it would be nice to not force push if possible ><

@ReneganRonin it would be nice to not force push if possible ><

Oh my bad. I just like it since i prefer my commit history is consistent with what i am doing. i will adjust and change my ways ><

@ReneganRonin it would be nice to not force push if possible ><

Oh my bad. I just like it since i prefer my commit history is consistent with what i am doing. i will adjust and change my ways ><

It is not problematic if it is on a branch that is not an active PR, but in that case you actually erased my work.
As I still had it locally it was okay, but force push should never occur (I still do it so it is a bit of do what I say not what I do ...) on a shared repo.
It is not too hard to git pull first to merge incoming changes. It is annoying to get the habits, but it helps a ton.

okay sorry. i wont do that again.

You erased my work again. Stop force push.
In case you want to work independently, please make a new branch.
I won't correct thing for tonight, I will take some time tomorrow.


reject stream frames that overflow the byte offset

i.e. a StreamFrame with a ByteOffset close to MaxByteCount.
A frame where frame.Offset + len(frame.Data) overflows MaxByteCount is currently accepted (and saved in the streamFrameSorter.

There's no error code that matches here. I'd suggest to use a QUIC_INVALID_STREAM_DATA.


Image Verbalization for Expansion

Hello, I'm a student reproducing the paper.
I have a question while reading the paper and looking at the code.
First of all, thank you for sharing the code.
Q1. In the paper 4.3 (IMAGE VERBALIZATION FOR EXPANSION), we need to obtain image verbalization results $V (I_j )$ to expend the raw captions passing through the text encoder.

$C^*_j = C_j ; [SEP]; V (I_j )$　　(8)

However, I could not find a part that generates a potentially matching caption or related queries that corresponds to the image verbalization result.
I would appreciate it if you could tell me which part of the code corresponds to Image Verbalization.
Once again, thank you for revealing the code and I look forward to your reply.

Hello, I found a breakthrough.
In folder data which I can download from Ali Drive,
There's all_img_query.json and all_img_exp.json.
I think all_img_query.json has generated related query and all_img_exp.json has generated potentially matching caption.

Sure, you are right. We train VinVL to generate related queries according to image captions and image features.


Classes not under 'entity'

The OMRSE OWL file contains OMRSE classes that are not under 'entity':
'ethnic identity role'
'gender identity role'
'Homo sapiens role'
'human patient role'
'identity datum'
'racial identity datum'
and their subclasses when they exist.
Is that intentional?

What version of Protege are you using? I can't duplicate this on my machine.

It seems that the problem is due to the fact that the URL for d-acts isn't resolving.

Fixed. D-acts no longer imported. Classes manually placed in hierarchy in OMRSE file.


Add Orlando, FL file

This PR adds the Orlando file to our directory.
@nobrzudDFS could I borrow your 👀 ?

File looks good

What kind of Mickey Mouse operation is this?


Cannot render on Linux because of "gtk theme"

Hello,
When trying to render on Ubuntu Linux 4.17.11-041711-generic I get the following error :
Theme parsing error: gtk.css:6777:29: Missing opening bracket in color definition

Here is a demo of the issue : https://asciinema.org/a/nrVz5y3NxIXMDL99Y7NrNh90q
I don't really understand how this error makes it impossible for the app to work as I run many other Electron apps on my desktop and have never had such a problem (where the app will simply die for no apparent reason)
The theme file isn't even mine, pretty sure it is a standard theme that came with Ubuntu.

There probably is a flag in electron somewhere that tells it to ignore GTK warnings or at least not die when it seems a GTK warning.

Maybe add some default valid fallback values packaged in the release as a "workaround".

Any updates on this? I see this when I execute terminalizer render recording.yml:
Error:
  Error:
(electron:16146): Gtk-WARNING **: 15:56:04.432: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(electron:16146): Gtk-WARNING **: 15:56:04.432: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

I don't know where those warnings come from, but they appear harmless - it took me a while to realize that apparently electron thinks they are deadly errors! Can't they be ignored somehow?
Running Ubuntu 18.04.

I was not able to ignore the error and ended up switching to a theme that the program did not complain about. I liked my theme before, but I also needed to run certain applications that would fail to load my GTK theme.
This is not a Terminalizer issue. Nor does it appear to be an Electron issue, but rather a GTK issue or how GTK is configured - based on seeing this warning pop up in non-Electron apps.
There is not a single fix to this problem after searching all of GitHub. See here. Or the Internet, for that matter.
If the theme is open source, you could file an issue like this person, but the theme still hasn't been updated. Or get lucky and only have 1 or 2 errors that need to be fixed in your gtk.css file like this person. Or be like me: have a thousand deprecation warnings and realize updating the theme to remove those warnings isn't a viable solution.

I'm debugging this and I found that Terminalizer escalates these warnings into errors - this will be easy to fix. Whether or not a specific GTK theme actually has issues that may cause trouble is a different question, but there's no reason for Terminalizer to die with errors as a result of warnings that Electron doesn't really care about (as you can easily see by running Electron by itself).
As part of my debugging work I have updated package versions and I'm still seeing some trouble I'm looking into. I'll submit a pull request when I find the solutions.

The underlying issue is described here
#102
And fixed on PR #97

Hello,
When trying to render on Ubuntu Linux 4.17.11-041711-generic I get the following error :
Theme parsing error: gtk.css:6777:29: Missing opening bracket in color definition

Here is a demo of the issue : https://asciinema.org/a/nrVz5y3NxIXMDL99Y7NrNh90q
I don't really understand how this error makes it impossible for the app to work as I run many other Electron apps on my desktop and have never had such a problem (where the app will simply die for no apparent reason)
The theme file isn't even mine, pretty sure it is a standard theme that came with Ubuntu.

This is closed but for anyone who comes across this, you are probably using a Mac theme of some sort. In my case it is MacBuntu-Sierra-light. The gtk-3.0/gtk.css of that theme has some errors in it:
6777:  text-shadow: 0 0 2px alpha #000, 0.3, 0 1px 2px alpha #000, 0.6;
6779:  -gtk-icon-shadow: 0 0 2px alpha #000, 0.3, 0 1px 2px alpha #000, 0.6;
6785:  box-shadow: 0 0 2px alpha #000, 0.3, 0 1px 2px alpha #000, 0.6;

these should read
6777:  text-shadow: 0 0 2px alpha(#000, 0.3), 0 1px 2px alpha(#000, 0.6);
6779:  -gtk-icon-shadow: 0 0 2px alpha(#000, 0.3), 0 1px 2px alpha(#000, 0.6);
6785:  box-shadow: 0 0 2px alpha(#000, 0.3), 0 1px 2px alpha(#000, 0.6);

Hope that helps


Request for HomeKit Integration of Away Mode

Is your feature request related to a problem? Please describe.
I want to achieve an automation where the heating/cooling system turns on away mode when everyone leaves the house and turns it off when someone arrives.
Describe the solution you'd like
I would like the away mode to be integrated into HomeKit. Specifically, I want to create an automation that turns the away mode on when everyone has left the house and turns it off when someone arrives. This would help optimize the system for better energy efficiency and reduce my electric bills.

I would like to do this - life is getting in the way of my hobby.
—
@.*** | +61 409 439 207

On 8 Jul 2024, at 20:24, Long Zhao @.***> wrote:
Is your feature request related to a problem? Please describe.
I want to achieve an automation where the heating/cooling system turns on away mode when everyone leaves the house and turns it off when someone arrives.
Describe the solution you'd like
I would like the away mode to be integrated into HomeKit. Specifically, I want to create an automation that turns the away mode on when everyone has left the house and turns it off when someone arrives. This would help optimize the system for better energy efficiency and reduce my electric bills.
—
Reply to this email directly, view it on GitHub https://github.com/jxg81/homebridge-actron-que/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALPRT7J6XGPMDGPPRI7HAVLZLJSG5AVCNFSM6AAAAABKQQ5TPGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TKMRUGY3TENI.
You are receiving this because you are subscribed to this thread.


build-std: Fix libraries paths following upstream

Fixes #8557

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Hmm, the failure doesn't occur on my local and fork action: https://github.com/JohnTitor/cargo/runs/921702330
It's spurious?

Hmm, the failure doesn't occur on my local and fork action: https://github.com/JohnTitor/cargo/runs/921702330
It's spurious?

Yea, that test was a little flaky.  I restarted CI, and posted a fix at #8559.

@bors: r+

:pushpin: Commit 7c77fedabb921e5d7530642cef458ef7d258d60b has been approved by alexcrichton

:hourglass: Testing commit 7c77fedabb921e5d7530642cef458ef7d258d60b with merge 6fb343394cb277727cd4a52793c34cbb0c0a520b...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing 6fb343394cb277727cd4a52793c34cbb0c0a520b to master...


Not hosted on rubygems?

gem 'ui_datepicker-rails3'
Doesn't work (since it's not hosted on rubygems?)
gem 'ui_datepicker-rails3', :git => 'git://github.com/kristianmandrup/ui_datepicker-rails3.git'
would be correct.

I just released 1.0.0. Thanks for notifying me ;)


fix(ionrangeslider): Bring in the shiny-preset ionrangslider rules to the precompiled CSS

Fixes #748
The prebuilt ionRangeSlider.css now includes the additional rules we added in the shiny preset in bslib. This ensures that the slider styles are consistent, even when the slider is used in a context where py-shiny's core bootstrap bundle isn't available (e.g. Quarto).
For a minimal diff and to match the current py-shiny dependencies, I used the following instead of installing each package from @main:
  pak::pkg_install(c(
    "rstudio/bslib@a076e72e78562d7f006889da4118cd781c66c84c",
    "rstudio/shiny@68546c319e465a9cb113ea4499912823e264e75f",
    "rstudio/htmltools@9338b7f3e2ed7b3fef8fd813904b9b05281344aa"
  ))

@gadenbuie , can you also make a PR for https://github.com/posit-dev/py-shinyswatch, please? Thank you!!

Thank you!

@schloerke shinyswatch doesn't need an update, the fix is only requires for themes that are using the shiny preset from bslib. If you'd like to use the ionrangeslider styles from bslib's shiny preset and mix them with the bootswatch styles, that's possible but would be a bit more work. Maybe you should open an issue for that?