Add the text "The time complexity of this " to the article

…t best case, average case or worst case. It's time complexity can be easily understood from the recurrence eqaution :T(n) = 2T(n/2) + n." to the article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@ayush163 thanx for the pr and congratulations on your first contribution to freecodecamp. we look forward to future contributions :balloon:


Version 2.0.2

Landed in https://github.com/metarhia/impress/commit/d3448cfa741623826ffd89d9062ae63f1a287fcb

Landed in https://github.com/metarhia/impress/commit/d3448cfa741623826ffd89d9062ae63f1a287fcb


LTR/RTL kernFeatureWriter

I'm not sure where to put this but I think it may be interesting for the current developments in #7 and #6 etc.
I extended the kernFeatureWriter of ufo2fdk/ufo3 branch for Jomhuria to support the creation of a fea-kerning file from ufo kerning.plist which works for LTR and RTL text.
Here: https://github.com/Tarobish/Jomhuria/blob/gh-pages/tools/getKernFeatureFromUFO.py
See this discussion unified-font-object/ufo-spec#16 where @behdad gave the hints how to approach this.
This is dependent on the ufo3k ufoLib.
If you're interested in this code we could look at how to integrate it. We should probably decide which is the best way to do RTL + LTR kerning from kerning.plist and subsequently discard some of the options from my code, to make it easier to use.

:+1:

Sorry for taking so long to get to this. From the linked discussion:

Here's the simplest heuristic that works:

Generate both an LTR kern lookup and an RTL one; including all kerning pairs in both.
Reference the RTL lookup from script systems that are RTL, and the LTR one for others.

That's the crudest heuristic, but it works. From there on, you can add more complexity to achieve smaller kern tables. [...] For example, a huge improvement:

Associate each glyph to a Unicode character,
Exclude from RTL kern table all glyphs associated with Unicode characters that have Bidi_Type=L,
Exclude from LTR kern table all glyphs associated with Unicode characters that have Bidi_Type=R or Bidi_Type=AL.

Is this still the suggested approach? I don't have any better ideas.

Is this still the suggested approach? I don't have any better ideas.

Yes, it is.


React-native 0.25 is available, could the code be updated to use this version

Hello,
how is the migration to newer released (like 0.25) planned?

Done.

I am using it and the warnings on react / react-native or gone for me.
as far as i can tell its working for me.
thx for the update.

I think this have been fixed in 2.0.0
Everthing works fine on 0.25.1 and 0.26.0.
So I`m closing this.


Venetian blind tilt - half open

Hello
thanks for the plug-in. I’ve been using rip-rts for a couple of years  but this would be much better for use in HomeKit.
I have my blinds working, however, Venetian blinds are tilt only and “open” when they are half way which I normally set using the MY command.
Is it possible to set Open as MY, otherwise the blinds are fully up for open and fully down for closed?
many thanks

Hi schweppy
Makes sense. It will need a minor code change but shouldn't be a problem to add this. I'll take a look at it for you tomorrow and let you know.

Hi Schweppy
I added a Beta version. Can you please test and see if it works for you. You'll need to add a new setting of openToMyPosition to your Config file. E.g.
        {             "accessory": "Somfy Blinds",             "name": "My Blind",             "id": 1234567,             "adminMode": false,             "openToMyPosition": true         }
Then if you goto the Homebridge plugins and select 'Install Previous Version', pick 'v0.4.0-beta.0' and restart. Hopefully this should then work.

Hi Schweppy
Can you try 0.4.0-beta.3. Also please add blindTimeToOpen to your config file specified in milliseconds. E.g.
{ "accessory": "Somfy Blinds", "name": "My Blind", "id": 1234567, "adminMode": false, "openToMyPosition": true, "blindTimeToOpen": 2000 }

Morning!
B3 installed. Opentomyposition shows in config UI where as blindtimetoopen does not? Is that how you wanted it to be?
More importantly, the tile in homekit now hangs on “opening” or “closing” forever until I force close the home app. Loading the home app again shows the blind in its correct state!?


Release 4.6.5

Summary of the changes / Why this improves CrateDB
:goat:
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please


Microsoft.Network/FirewallPolicies does not preserve tag key casing

Example:
az resource tag --tags TestCasing=Test2 --ids /subscriptions/<subscription>/resourceGroups/<resource-group>/providers/Microsoft.Network/firewallPolicies/<policy>
{
  [...]
  "tags": {
    "testCasing": "Test2"
  },
  "type": "Microsoft.Network/FirewallPolicies"
}

Expected behaviour is to return:
  "tags": {
    "TestCasing": "Test2"
  },

Any updates on this issue? It is impacting Terraform Azure Firewall Policies and force the tags to be lowercase. Most of the customers are using a combination of Upper and Lower. Creating some conflicts when Azure Policies enforce some tags with Upper and Lower case.

Just ran into this issue as well. Any updates?

We are still facing this issue in azurerm v2.98.0. Any update on that?

Any update on this?
Still exists in terraform provider 3.11.0 and az cli v2.38.0

@fengzhou-msft any chance this could be updated to reference the Firewall team, this isn't an ARM issue, but a Firewall RP issue?


prevent user with no permission from flag comment

Details

Fix: Prevent user with no permission from flagging comment
Fixed Issues

$ https://github.com/Expensify/App/issues/21719
PROPOSAL: https://github.com/Expensify/App/issues/21719#issuecomment-1610335825
Tests

Login with userA account
Go to the “New room” section
Enter room name and select userA workspace
Select visibility to “Public”
Click on “Create room”
Send some messages in room chat
Go to the room detail
Share code > Copy URL to clipboard
Go back and click on Settings > Who can post
Select Admin only
Open other browser and login with userB account
Join the room by pasting URL
Hover or right click on userB comment
Verify that there's no Flag as offensive option.

[x] Verify that no errors appear in the JS console

Offline tests
Same as Tests
QA Steps

Login with userA account
Go to the “New room” section
Enter room name and select userA workspace
Select visibility to “Public”
Click on “Create room”
Send some messages in room chat
Go to the room detail
Share code > Copy URL to clipboard
Go back and click on Settings > Who can post
Select Admin only
Open other browser and login with userB account
Join the room by pasting URL
Hover or right click on userB comment
Verify that there's no Flag as offensive option.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots

Web

https://github.com/Expensify/App/assets/16502320/c8aa4642-fce6-42ae-b20d-5bd4497bb00d
Mobile Web - Chrome

https://github.com/Expensify/App/assets/16502320/72647605-e913-451e-8770-1b17ea0a6171
Mobile Web - Safari

https://github.com/Expensify/App/assets/16502320/16c7fefe-dba7-497f-af13-5eb49d999da5
Desktop

https://github.com/Expensify/App/assets/16502320/58ee1e90-7583-442d-89dc-ccf6130d5bef
iOS

https://github.com/Expensify/App/assets/16502320/b38c50fd-fe09-4099-9353-43167deb3b6f
Android

https://github.com/Expensify/App/assets/16502320/aabc9c88-d77f-4d4a-8389-d968d0c14b85

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/danieldoglas in version: 1.3.37-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.37-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


[elasticsearch] Configure JVM options file

Describe the feature:
Realted to https://github.com/elastic/helm-charts/issues/1463, https://www.elastic.co/guide/en/elasticsearch/reference/current/advanced-configuration.html#set-jvm-heap-size
We must be able to configure options files under /usr/share/elasticsearch/config/jvm.options.d folder.
Describe a specific use case for the feature:

PR is on the way

fixed by #1496


Version 2.0.0

Accepting feedback on the release notes. Will publish first thing tomorrow.
/cc @MaxBittker @benvinegar

Based on our previous discussion, this seems right, but I think I'll leave to @MaxBittker to approve.

which points someone needs to be aware of for upgrading?
Mostly just the one point about shutdown conditions; added a bold callout.

Added the postgres autobreadcrumb removal to this.


ONG sending transaction has wrong metadata info

Summary of Bug

ONG send transaction is marked Claim Rewards transaction.
Expected Behaviour

Every send transaction by user should be mark as a Send transaction. Check info below.
Steps to Reproduce

More Info (for devs / optional)
Request details:
https://host/v1/ontology/AUyL4TZ1zFEcSKDJrjFnD7vsq5iFZMZqT7?token=ong

Response details:
{
  "total": 7,
  "docs": [
    {
      "id": "d3be042ae21a313bc70fbfea62d11fb32731126101859a66f523e081c3fd429c",
      "coin": 1024,
      "from": "AUyL4TZ1zFEcSKDJrjFnD7vsq5iFZMZqT7",
      "to": "Abm1FqnU4qur9bviXmrD5YnNixXGvMsi9R",
      "fee": "10000000",
      "date":<PHONE_NUMBER>,
      "block": 7836941,
      "status": "completed",
      "type": "any_action",
      "direction": "outgoing",
      "memo": "",
      "metadata": {
        "coin": 1024,
        "title": "Claim Rewards",
        "key": "stake_claim_rewards",
        "token_id": "ong",
        "name": "Ontology Gas",
        "symbol": "ONG",
        "decimals": 9,
        "value": "400000000"
      }
    }
  ],
  "status": true
}

where metadata.title is Claim Rewards but it should be Send according to the explorer data
Request details:
https://explorer.ont.io/address/AUyL4TZ1zFEcSKDJrjFnD7vsq5iFZMZqT7/ALL/20/1

Response details:

https://github.com/trustwallet/blockatlas/blob/7c842154b493f5af9029e55b1db3e9a2ff3e1948/platform/ontology/model.go#L128

@ArtemGoryunov can you remove sensitive information, please? like hosts

One way you can get claim reward transaction is to call rpc, instead of explorer.
http://dappnode2.ont.io:20334/api/v1/smartcode/event/txhash/63d39733db24d05a4072f8edf8afe9e5a42d62849324a8f1a8f87f49e1d285df
Smart contrat 36bb5c053b6b839c8f6b923fe852f91239b9fccc  is claim contract and<PHONE_NUMBER>000000000000000000000000000000   is  ong contract.

Closed by @Pantani #899


Pagination in Alamofire

I'm building a wrapper around my API where pagination happens on a request by just changing the page=<page_number> on the URL parameters. Ideally the wrapper should paginate somewhat like this
let sessionManager = SessionManager()
sessionManager.adapter = someAdapter

let searchRequest = sessionManager.request(SomeRouter.search(query))
searchRequest.responseCollection(){ // do something here }

// When the user wants the next page results he can just do
searchRequest = searchRequest.next()
searchRequest.responseCollection(){ // do something here }

I've tried subclassing DataRequest but the initialiser has internal enum references. Modification of the URLRequest object is also not possible as it is a get only property. This is what I could come up with (somewhat a hackish solution)
enum PaginationError: Error {
    case notSupported
}

internal extension URL {
    internal func paramValue(forParam param: String) -> String? {
        guard let urlComponents = URLComponents(url: self, resolvingAgainstBaseURL: false) else { return nil }

        return urlComponents.queryItems?.first(where: { $0.name == param })?.value
    }
}

public extension Alamofire.DataRequest {
    public func nextPage(sessionManager: SessionManager) throws -> Alamofire.DataRequest {
        guard let request = self.request,
            let url = request.url,
                let currentPageString = url.paramValue(forParam: "page"),
                    let currentPage = Int(currentPageString) else {
            throw PaginationError.notSupported
        }

        let nextPage = currentPage + 1
        let nextPageURL = URL(string: url.absoluteString.replacingOccurrences(of: "page=\(currentPage)", with: "page=\(nextPage)"))!

        var newRequest = request
        newRequest.url = nextPageURL

        return sessionManager.request(nextPageURL, method: HTTPMethod(rawValue: request.httpMethod!)!)

    }
}

And calling the next function requires the sessionManager to be passed in which looks a bit ugly.
Is there some other way which is more elegant? I would have been a piece of cake if the Request object had a reference to the URLRequestConvertible and someway to update the URLRequest object in Request.

Rather than doing this strictly at the Request (or subclasses level), I'd do it at the URLRequest level. That, combined with a router (perhaps a pagedResults route), should be able to give you the sequence of `URLRequests) needed to get all of the pages. Making them sequentially using the standard Alamofire APIs should be pretty straightforward after that.
We use our GitHub project for bug reports and feature requests. In the future, you should open questions like this on Stack Overflow and tag alamofire.
Cheers. 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


Optimistic concurrency using native EfficientDynamoDb API

Hi, developers.
There is a question related to optimistic concurrency using EfficientDynamoDb API.
In the documentation I found DynamoDbVersion attribute support (which enables optimistic concurrency by default), but you do not recommend to use Compatibility APIs like SaveAsync and DeleteAsync.
We are using DeleteItem, PutItem and UpdateItem APIs and want to have concurrency check.
Please, advise if there is a way to have something like "DynamoDbVersion" behavior.
Perhaps, Conditional checks could facilitate the issue, but looks like it requires additional complexity in my logic.
Hope for your support,
Thanks.

Hi @OleksiiBalanenko.
Conditional checks are the way for implementing optimistic concurrency for DeleteItem, PutItem, and UpdateItem yourself. We decided not to add any simpler way to do it yet because generic optimistic concurrency doesn't align well with the flexibility of these operations via custom conditions. Nevertheless, we're open to discussing API proposals in this area so feel free to share if you have any.
If you don't care about having a full object to perform SaveAsync  and DeleteAsync, it's ok to use them. These methods are not recommended because for the majority of DDB operations you don't really need to change the full object. But you have to reload data from DB in case of concurrency error despite updating data that could have been updated concurrently without errors with more granular conditions.

Hi @firenero,
Thanks for your answer. It was helpful.


add --host command line argument

Fixes #19

Thanks @kanekv!
Can you document this in this section of the README, and add a line to the changelog as well?

@di done

@kanekv I'll do the version bump in a separate PR, please add the changelog entry under the "Unreleased" header.

@di looks better now?

Thanks!


Wyscout Event data V3: Add card event parsing

Wyscout deserializer V3 not support actually all events types. It would be nice to add support for card events and then continue with the others.

This was implemented in #198


[loc][query] Translation question.

Description

IMPORTANT: if the defect is reproduced only in a workflow from within the Visual Studio IDE then do not report the issue here - instead, please report it using Visual Studio's "Send Feedback" option that can be accessed from the Help menu OR using this link https://developercommunity.visualstudio.com.

Question about the resource "NotRunTestIndicator" in the file vstest.console\Resources\xlf\Resources.xlf: need more information about the string "Not Run".
Does this mean "One test not run" or "Some/many tests not run"?

For a defect reproducable from the vstest command line, describe the issue you've observed.

Steps to reproduce

What steps can reproduce the defect?
Please share the setup, commandline for vstest.console, sample project, target
framework etc.

Expected behavior

Share the expected output

Actual behavior

What is the behavior observed?

Diagnostic logs

Please share test platform diagnostics logs. Instructions to collect logs are here.
The logs may contain test assembly paths, kindly review and mask those before sharing.

Environment

Please share additional details about the test environment.
Operating system, Build version of vstest.console

It means a single test.


Add support for GrabResult chunk data v2

See #19. This continues from there.
(@hirschenberger thanks for the ping, indeed I had missed your PR.)
I had to tweak your example to run on one my cameras as apparently "Framenumber" isn't supported on it. Are these changes OK?
Otherwise, this looks good in my opinion.

Yes thanks looks fine. Can you maybe also release a new version to crates.io. I'd need that feature for my Pylon lib, where I implement initial Sequencer support.

published in 0.4.3. Thanks again!


Add Missing and Adjust Renamed Product (Power Bi & Windows Autopatch)

Add: Microsoft 365 E3 Extra Features, Microsoft_365_E3_Extra_Features = "Windows Autopatch" right?
Rename: Power BI (free) to Fabric (Preview), POWER_BI_STANDARD

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

ID: 7c245452-161d-89a1-c026-99a0721cf071
Version Independent ID: 16dec59a-eb83-1837-4efd-4645e7aeaed2
Content: Product names and service plan identifiers for licensing - Microsoft Entra
Content Source: articles/active-directory/enterprise-users/licensing-service-plan-reference.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @Nicholak-MS
Microsoft Alias: nicholak

@weyCC81
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@Nicholak-MS
Can you please check and add your comments on this doc update request as applicable.

Hi @weyCC81 I have added the missing SKU's to the online document and the downloadable CSV. The changes will publish later today. Thank you for bringing this to our attention.
Thanks,
Nick
#please-close


docs: update installation documentation

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


Binding right shift to L_Command only works for certain shortcuts

Using 10.6 on OSX 10.10
When enabling this bind, all rshift + letter shortcuts work as expected (cmd + letter).
However rshift+lshift commands do not work for the following letters:
q w e r t y u i o
All other rshift+lshift + letter shortcuts work as expected (cmd + lshift + letter).

I cannot reproduce this issue.
Please show the result of EventViewer when you press rshift+lshift+e.
https://pqrs.org/osx/karabiner/document.html.en#eventviewer
And show me your enabled settings. (Preferences with "show enabled only" checkbox.)

Here is rshift +lshift + e
eventType:keyMod          code:0x37       name:Command_L       flags:Cmd                                misc:KeyCode::COMMAND_L	characters:
eventType:keyMod          code:0x38       name:Shift_L         flags:Shift Cmd                          misc:KeyCode::SHIFT_L	characters:
eventType:keyMod          code:0x38       name:Shift_L         flags:Cmd                                misc:KeyCode::SHIFT_L	characters:
eventType:keyMod          code:0x37       name:Command_L       flags:                                   misc:KeyCode::COMMAND_L	characters:
and here is a picture of my enabled settings

Thank you for information.
I guess that it is a 2-key rollover problem. (hardware limitation)
https://pqrs.org/osx/karabiner/faq.html.en#rollover
Please confirm whether shift+e event is fired by rshift+lshift+e without Karabiner setting.
If there is no output when you pressed e key with rshift+lshift, it's a 2-key rollover problem.
You should use another key combination.

Ah, the 2-key rollover! What an unexpected limitation! That must be it, as I am using a wireless apple keyboard currently.
Thanks for the help. Closing issue.


Graph Expansion

Add possibility to expand entire group node
Check possibility to expand all nodes in graph (maybe limit availability of feature based on size of graph)

added ability to scatter group node via outside event. CI/CD pipeline currently running


Install via Brew failed

Hi, I had an issue when installing via brew. I have attached the issue below.

Hello and thank you for reporting :D
Seems as the version was missing from the formula. I have updated the versions in the formula, can you try again?

Trying to install again, now I got different issue:

Got ya, I will check :) Do you have Cargo installed or pkgx?

I made some fixes, can you try again and open if you still get a issue?
I managed to install on my machine now


Update Event.php

Add weekends() method

It's unclear what weekends means. It will be a consistent point of confusion and not intuitive when reading the code. Does it just mean on Saturday, both Saturday and Sunday?


Remove dependency on github.com/packethost/pkg/log/logr

Description

The package github.com/packethost/pkg/log/logr is just a wrapper around https://github.com/go-logr/logr but makes updating dependencies difficult. This PR removes github.com/packethost/pkg/log/logr as a dependency.
Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

This is great! Thanks for doing this @jacobweinstock !

@jacobweinstock This looks good. Glad you bumped github.com/manifoldco/promptui to v0.9.0 since v0.8.0 of promptui was pulling in github.com/juju/ansiterm, an LGPL dependency.

@jacobweinstock This looks good. Glad you bumped github.com/manifoldco/promptui to v0.9.0 since v0.8.0 of promptui was pulling in github.com/juju/ansiterm, an LGPL dependency. Are there any breaking changes involved in this removal? I'm not familiar with the codebase, but as far as I reviewed, I observed that the packethost logr was being replaced with go-logr/logr and zerologr, and other methods fixed to use these new logging constructs.

Hey @abhay-krishna, from the protobuf API's perspective (here) there are no breaking changes. This change affects what the logs will look like. They'll be a little different than before.

@jacobweinstock That makes sense, thanks for clarifying. Any idea when this will be merged?

This change affects what the logs will look like. They'll be a little different than before.

Can you add some examples of before and after to the testing section?

Hey @nshalman, sorry your approval got dismissed when I rebased main. whenever you have a moment, please and thank you!

@jacobweinstock Thanks for merging this!! 🎉


Converter classes should be placed in 'Converters' namespace

All ValueConverter classes should be placed in Converters namespace to allow easy access in XAML without the need to reference a lot of namespaces.

Duplicate of #175


revealRange won't scroll horizontal with default reveal type.

https://code.visualstudio.com/docs/extensionAPI/vscode-api#TextEditor.revealRange
revealRange wouldn't scroll horizontally with default reveal type TextEditorRevealType.Default.
TextEditorRevealType.InCenterIfOutsideViewport and TextEditorRevealType.InCenter works fine btw.

:+1:

Thanks for reporting and sorry about it slipping through! :+1:


Using v0.7.0 doesn't include .tagged_with class method

I've just installed the latest version of the gem (0.7.0) but it doesn't pull in any changes after commit ba9b446f5819d8efef4d107ea0ce7a8272d78586

I have just forked this gem and increasing the Gem version, in my case I set it to 0.7.1, and it seems to fix the issue. I've added a pull request (#21), though I understand if the version number isn't right for you, or if there is more that needs to go into the next version.

Ergh, about 14 months between releases. Sorry about that - just pushed 0.8.0 (took a little longer than I hoped, had to wrangle some things to ensure the test suite was happy with various Ruby and Rails versions.


Orthos Deepeye

Mob Id
12210 - Orthos Deepeye
Content Type
DeepDungeon
What threat level sould the mob have
Caution
What agro type does the mob have
Sight
Vulnerabilities for the enemy

[X] Stun
[X] Heavy
[X] Slow
[X] Sleep
[X] Bind
[ ] Undead

Additional mob text guide
Hypnotize | ? | 360 degree gaze AoE
Heirloom Scream | 55 | instant untelegraphed pointblank AoE; inflicts vulnerability up (5% per stack, 25s)

if this is from sept 7th and it still has not been added in.. im going to assume this is an abandoned project and will remove this plugin.. thanks


[WIP] Add first iteration json-stat SSB-pocos

Another topic for tomorrow: directory setup for more reusable classes (i.e. formats). We could perhaps create another root directory containing the json-stat and other base-classes that can be implemented in the models directory by other POCO's.
Ex:
BaseModels

JsonStat

JsonStatBase.cs

Models

MetAPI

all MetAPI-stuff (sidenote: does this conform to any widely used standard? We could perhaps abstract this one as well)

SSB

AgesInNorway.cs (which implements JsonStatBase.cs)

This way we don't need json-stat-files in all directories containing json-stat-like objects.


Working with CapacitorJs

Aries Askar now exclusively works with Nodejs and React Native. Is there a way to modify or integrate it to work with CapacitorJs (https://capacitorjs.com/)?

It's definitely possible to support other environments, but you'd need to implement the AriesAskar interface defined in the shared package.
We do that for Node.JS and React Native. I'm not familiar with capacitorJS so not sure what that would involve, but I suspect creating a wrapper around the c callable binary for ios/android (there's a repo that is working on kotlin and swift wrappers: https://github.com/hyperledger/aries-uniffi-wrappers)

@TimoGlastra I've implemented most of this with @bao-sotatek for Android. The problem we're facing now is some of the AriesAskar functions do not return promises.
For Capacitor, every native call must return a promise or you'll end up with a delayed response and undefined in JS. This seems unavoidable as Capacitor uses a WebView and the calls over this boundary are always async.
Would it be possible to convert all of these functions to async (+ in NodeJS/React Native wrappers), and add the necessary awaits in aries-askar-shared and the Askar module in AFJ? We intend to make this Askar Capacitor plugin fully open source once it's out of this "PoC stage".
If you are OK with this, I can fork the libraries to do this myself, and finish the development of the plugin (in case there are other issues) and then contribute it back. I think I'd need to stay on a fork for a while anyway since we are still using<EMAIL_ADDRESS>with<EMAIL_ADDRESS>but could merge in for 0.5.0.
Thanks!

@berendsliedrecht what do you think?
I quite liked the API being sync now, but I also want the interfaces to allow for other integrations besides the two we have now.
I think we should make the methods all return Promise | T, so that you can still return a non-promise. Benefit is that we don't have to add a promise wrapper around everything and the code will still run as sync in Node.JS / React Native.

Changing the API to make it Promise<T> | T will cause a major headache for both sides as you have to be aware of the environment you are running in and handle accordingly.
For a CapacitorJS wrapper, I would suggest a new repository that could reuse the binaries from this repository, but a fully separate wrapper.

@berendsliedrecht If I have a fully separate wrapper, then I need to re-write and maintain a new @aries-framework/askar right? (...or adapt it to accept either wrapper, but this still means adding async there)
I'm not sure I get the headache though - in aries-askar-shared, you just need to get Promise<T> | T down to T by awaiting, rather than checking environment.
The awkward TS part is that get methods can't be have the async keyword, but can be worked around with something like:
public get algorithm() {
  return Promise.resolve(ariesAskar.keyGetAlgorithm({ localKeyHandle: this.handle })).then(keyAlgFromString);
}

...or simply having async getAlgorithm()

if we resolve the Promise within aries-askar-shared we would have to make every function async, correct?
public get algorithm() {
  return Promise.resolve(ariesAskar.keyGetAlgorithm({ localKeyHandle: this.handle })).then(keyAlgFromString);
}

this call we would still have to await when called. We essentially chose to write all these modules in TurboModules in React Native so that we could have a mainly sync API, and to me this (not fully of course) gets rid of those benefits.

If I have a fully separate wrapper, then I need to re-write and maintain a new @aries-framework/askar right?

It would be Android + iOS plugin for CapacitorJS and a thin JS layer on top of that which can just be an async version of the functionality in aries-askar-shared.
IMO, all wrappers (node.js, js, python, etc.) should not live in this repository anyways and at some point will be moved out as well. So I am hesitant to add any wrapper for that matter.

I do think it would be good to allow for another platform to be supported in AFJ/Credo without having to recreate the Askar Shared interfaces, as well as the @credo-ts/askar package.
The whole reason to have the shared interface is that we didn't have to recreate indy-sdk-react-native poorly adapted based on indy-sdk api.
I think the get methods can be transformed to normal methods and optionally return a promise. I agree it's not optimal, but allowing a different environment to plug into the shared interfaces like that is good for adoption of Credo.
A good chunk of the calls are already async either way.

Changing the API to make it Promise | T will cause a major headache for both sides as you have to be aware of the environment you are running in and handle accordingly

That's not true, you just have to be aware of whether the method retirns a promise. If you want easy you always await, otherwise you check the return type.
All methods in Credo that call askar are already async, so we lose nothing by awaiting each call (you can await a non-promise and it won't add runtime overhead, only if you return Promise.resolve to make the return type async)

That's not true, you just have to be aware of whether the method retirns a promise. If you want easy you always await, otherwise you check the return type.

That's exactly my point. You can always await everything or check the value, or environment, whether it is a promise and await or not.

All methods in Credo that call askar are already async, so we lose nothing by awaiting each call (you can await a non-promise and it won't add runtime overhead, only if you return Promise.resolve to make the return type async)

I am also looking at this from other usages next to Credo.
If there really is good value for it and it will stay maintained by the contributors, I am okay with it. But since the main maintainers of the nodejs and react native wrappers are not experienced with capacitor, I will see issues come up with out-of-sync implementations. Not to mention if this work will also apply to anoncreds and Indy vdr.

We won't be using Indy VDR, and Anoncreds is not on our roadmap at present. So just Askar, but this important for us (Cardano Foundation) so we will maintain it.
If there's a concern with non-Credo usages - a possible middle ground might be a separate async shared library interface, but allow the Credo package to work with both async and sync implementations? (since Credo calls are async anyway)

@berendsliedrecht After a lot of consideration, our wallet has recently dropped support from DIDs to focus our efforts in the KERI ecosystem. So this issue can be closed, as we no longer rely on Credo-TS.
We still have interest in Askar (subset of it, at least, just the encryption at rest), so we may end up writing some custom wrappers. Right now, we don't need it since most of our data is held in a KERI cloud agent. Thanks.


Rotation: Do two rotation scans in the one datafile/detector arming

Two nexus files pointing to these
Changing x/y/z/chi in between

duplicate of #960


#1 Updating README to contain action support

Pull Request Test Coverage Report for Build 44

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

Totals

Change from base Build 42:
0.0%

Covered Lines:
948

Relevant Lines:
1185

💛  - Coveralls


bazel build error

Ubuntu16.04 Cuda8.0 cudnn4 gcc-5.4 g++5.4 tensorflow0.9.0,
i experienced the issue blow when using bazel build -c opt --config=cuda //tensorflow/tools/pip_package:build_pip_package  and there also is a warning.
what should i do to correct this? i am new to tensorflow .  Need Help
WARNING: /home/keithyin/workspace/tensorflow-0.9.0/util/python/BUILD:11:16: in includes attribute of cc_library rule //util/python:python_headers: 'python_include' resolves to 'util/python/python_include' not in 'third_party'. This will be an error in the future.
ERROR: /home/keithyin/workspace/tensorflow-0.9.0/tensorflow/stream_executor/BUILD:5:1: C++ compilation of rule '//tensorflow/stream_executor:stream_executor' failed: crosstool_wrapper_driver_is_not_gcc failed: error executing command third_party/gpus/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object ... (remaining 100 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
tensorflow/stream_executor/cuda/cuda_blas.cc: In member function 'virtual bool perftools::gputools::cuda::CUDABlas::DoBlasGemm(perftools::gputools::Stream_, perftools::gputools::blas::Transpose, perftools::gputools::blas::Transpose, tensorflow::uint64, tensorflow::uint64, tensorflow::uint64, float, const perftools::gputools::DeviceMemoryEigen::half&, int, const perftools::gputools::DeviceMemoryEigen::half&, int, float, perftools::gputools::DeviceMemoryEigen::half_, int)':
tensorflow/stream_executor/cuda/cuda_blas.cc:1683:22: error: 'CUBLAS_DATA_HALF' was not declared in this scope
CUDAMemory(a), CUBLAS_DATA_HALF, lda,
^
tensorflow/stream_executor/cuda/cuda_blas.cc: In function 'cublasOperation_t perftools::gputools::cuda::{anonymous}::CUDABlasTranspose(perftools::gputools::blas::Transpose)':
tensorflow/stream_executor/cuda/cuda_blas.cc:406:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
tensorflow/stream_executor/cuda/cuda_blas.cc: In function 'cublasFillMode_t perftools::gputools::cuda::{anonymous}::CUDABlasUpperLower(perftools::gputools::blas::UpperLower)':
tensorflow/stream_executor/cuda/cuda_blas.cc:417:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
tensorflow/stream_executor/cuda/cuda_blas.cc: In function 'cublasDiagType_t perftools::gputools::cuda::{anonymous}::CUDABlasDiagonal(perftools::gputools::blas::Diagonal)':
tensorflow/stream_executor/cuda/cuda_blas.cc:428:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
tensorflow/stream_executor/cuda/cuda_blas.cc: In function 'cublasSideMode_t perftools::gputools::cuda::{anonymous}::CUDABlasSide(perftools::gputools::blas::Side)':
tensorflow/stream_executor/cuda/cuda_blas.cc:439:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 5928.835s, Critical Path: 282.48s

this is my bazel version .  i dont know what is wrong with it
keithyin@keithyin-PC:~$ bazel version
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Jan 01 00:00:00 1970 (0)
Build timestamp: Thu Jan 01 00:00:00 1970 (0)
Build timestamp as int: 0

I am also having the same issue.

Is anyone working on this? Please help me to resolve this. @jart

Hi @asispatra. Out of curiosity, how did you build Bazel? I'm not seeing the version in the output above. Could you try installing 0.3.1?

CUDA 8.0 isn't officially supported yet. Please see #2559. We're working on it now.

Please have a look at this set of changes. https://github.com/tensorflow/tensorflow/pull/2556/files. This fixes the problem.


Export - .goto file metadata is not exported and lost

Describe the bug
When I export my profile hyperdrive, all files are saved on drive, even .goto files. However the .goto files are zero bytes and the metadata is lost.
To Reproduce
Steps to reproduce the behavior:

Export a hyperdrive to your file system
Open the folder where you exported the hyperdrive to and locate a .goto file
Notice how the .goto files are zero bytes and the metadata is lost

Expected behavior
As user would expect the metadata to be exported as well and not lost.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Beaker Version: 1.0.0-prerelease.1

Electron: 9.0.0-beta.22
Chromium: 83.0.4103.34
Node: 12.14.1
Hyperdrive: 10.10.3
API: 0
Daemon: 1.13.6
Client: 1.14.5
Schema: 1.9.1
Fuse Native:
Fuse:

Additional context
Add any other context about the problem here.

Thanks for reporting, I'll check into it

I just noticed this as well. I first noticed this when doing a drive fork/copy... no file metadata carries over. I figured file export/import would prob not support metadata since k/v data is not part of any file itself. But fork/copy I expected it to work since it can carry over the hypertrie (unless I misunderstand the underlying handling of file metadata).
The simplest way to see this is with .goto files.

I just noticed this as well. I first noticed this when doing a drive fork/copy... no file metadata carries over. I figured file export/import would prob not support metadata since k/v data is not part of any file itself. But fork/copy I expected it to work since it can carry over the hypertrie (unless I misunderstand the underlying handling of file metadata).
The simplest way to see this is with .goto files.


Update request: linuxKernel.kernels.linux_zen 6.6.10 → 6.7

Package name: linuxKernel.kernels.linux_zen
Latest released version: 6.7

Current version on the unstable channel: 6.6.10
Current version on the stable/release channel: 6.6.1

[x] Checked the nixpkgs pull requests

Notify maintainers
@thiagokokada @JerrySM64

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Merged as of #279946.

Merged as of #279946. I'm watching the zen-kernel repo so when there's a new update, I do it as fast as I can. 😄

oh i didn't see that when looking at the pull requests. sorry about that. thank you


Rename process-reports to update-expected

This is implemented as of https://github.com/ErichDonGubler/moz-webgpu-cts/pull/88.


upd/fix

PR

Types of changes

[x] New feature
[x] Bugfix

Description

Checklist

[x] added grid css
[x] added new dev/design icons
[x] fix anchors links

 Created from VS Code using CodeStream

test

done


Explain why avoiding shared storage accounts in production

In the Shared Storage Accounts section, it is not explained why this practice should be avoided in production.
It would help an explanation to understand the pros and cons.

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

ID: a4d93f2d-6c04-7fc6-3f86-5ea7f9cca5c4
Version Independent ID: 77469c95-fd85-0f8a-0a2d-f4d284657845
Content: Storage considerations for Azure Functions
Content Source: articles/azure-functions/storage-considerations.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hello @Marco-Santoni, Thank you for your feedback! We will review and update as appropriate.

Hello @Marco-Santoni, as the document suggests Function App relies on Azure Storage for managing triggers and logging function executions . For Consumption/Premium hosting plan the function code and binding configuration files are stored in the storage account . In production environment, as function apps scale,  and if there are multiple function apps linked to the same storage account it might create some issues at scale as the bindings and logging are user configurable.
Using a separate storage account for each function app  is also helpful in maximizing the performance of the  function app.

Hello @Marco-Santoni, just following up here to see if above response was helpful.

Hello @Marco-Santoni,
Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


Product, Dependencies:  add Semigroup instances for GHC 8.4 SMP compat

Fixes #276. Tested with GHC 8.4.

cc @sol

@deepfire thanks a lot for looking into this!  I agree with the analysis of @quasicomputational.  Would you be willing to adapt the code?

I'll try to, sure : -)

On master and amended with https://github.com/sol/hpack/commit/729423e7aff2fdd2e5b63e1808a29aa82393c6c7.

@deepfire thanks a lot for the contribution!

Sorry for not being active enough on this!


bug: beerus-rpc hurl example "Empty reply from server"

Bug Report
Beerus version:
Latest
Current behavior:
Some hurl example files in beerus/examples/beerus-rpc return errors.
Expected behavior:
In beerus/examples/beerus-rpc/ directory hurl files are there to provide examples of working requests to inform user of format and responses for reference. They are formed when adding that rpc method to beerus-rpc and should not break on code changes to the main branch of beerus.
Steps to reproduce:
Requires hurl installation
Wait for beerus-rpc server to be ready.
Run hurl starknet_l1_to_l2_message_nonce.hurl or hurl starknet_l1_to_l2_message_cancellations.hurl
Response Empty reply from server and beerus crash
EDIT: Moving the below to its own issue, this is unrelated to Empty reply from server
Other information:

Need to run all hurl example files and see if they are returning errors.

Some examples of other rpc examples not working:
Request:
hurl ethereum_call.hurl
Response:
{"jsonrpc":"2.0","error":{"code":-32602,"message":"No more params"},"id":1}%
Request:
hurl ethereum_coinbase.hurl
Response:
{"jsonrpc":"2.0","error":{"code":-32601,"message":"Method not found"},"id":1}%

I've been looking into implementing the starknet_getStorageAt method, but I'm getting a Response Empty error from the server and Beerus crashes. It's the same error detailed in the comment above. It seems like all methods that start with starknet_ and use some Helios method are experiencing this issue. Telegram user ncitron mentioned that Helios has an error, which may or may not be related.
Either way, we should handle this error in our error handling code so that Beerus doesn't crash.
These methods include:

starknet_call_contract
starknet_get_nonce
starknet_l1_to_l2_message_cancellations
starknet_l2_to_l1_messages
starknet_l1_to_l2_messages
starknet_l1_to_l2_message_nonce
starknet_get_transaction_receipt

You can find all of these methods in this file beerus.rs
What do you guys think @phklive @drspacemn ?

Great research guys, indeed we shouldn't let beerus crash but this is problematic, considering we are relying on Helios for those methods if the problem comes from their side. Hence we should research more to find out if the problem comes from beerus implementation or from Helios. If it comes from Helios I will get in contact with Helios community to sort out a solution and make those methods work.

Incrementing helios version fixes this issue, as soon as it is merged will close.


Fix $msCompile regex to match Microsoft C++ Compiler messages

VSCode Version: 1.2.1

The fix is rather trivial: in problemMatcher.ts replace msCompile regex
/^([^\s].*)\((\d+|\d+,\d+|\d+,\d+,\d+,\d+)\):\s+(error|warning|info)\s+(\w{1,2}\d+)\s*:\s*(.*)$/

with
/^([^\s].*)\((\d+|\d+,\d+|\d+,\d+,\d+,\d+)\)\s*:\s+(error|warning|info)\s+(\w{1,2}\d+)\s*:\s*(.*)$/

BTW, what predefined pattern is expected to be used with MSVC compiler? msComplie or cpp? If the latter, cpp regex should fixed instead.

Thanks. The msCompiler pattern is used for MS compilers including C/C++.


feat(devtools): add timeline (draft)

Clone of https://github.com/TanStack/query/pull/3841 at is was easier to start from scratch after the v4 merge (closing the other one as a result).
This is to add a timeline in the chrome devtools as discussed here: https://github.com/TanStack/query/discussions/3753
Screenshot below of the current state of work:

it displays query events (fetch, success etc) ;
the number of observers attached to this query (number on the query "box") ;
when no observers are attached ("query cached"), the box is a bit more transparent.

TODO

[x] Add a tick to displays time at pointer ;
[x] Use query cache on start recording to populate entries ;
[x] Improve horizontal zooming
[x] Add support for scrolling horizontally
[x] Better tooltips
[ ] Review style (zoom buttons & move timer to head)
[ ] Check for all non nominative cases (error, retries)
[ ] Add tooltips for events (fetch, success)
[ ] Check if we can display differently refetch from window refocus, interval refetch, retries

If someone has some feedback on how to add horizontal scrolling and zooming (I am not convinced with the current solution for zooming), it will be very appreciated :)

I don't feel very confident to merge this one in one piece given the scope of changes required:

I need to refactor components in multiple files to add support for panes (current architecture supports one pane) ;
there have been some changes and I don't want to do any regressions when adding this (all changes are not tested).

Going forward I think the best approach would be:

create a PR to refactor and add some tests on the devtools part (I can do this) ;
add a PR to add supports for panes.
add the timeline feature on top of these PRs.

1 and 2 could be done in one shot, but I don't want to put too much cognitive load on both myself and reviewers :-).
@TkDodo what do you think about this?

this sounds like a good idea. Maybe we should merge this one first though?

https://github.com/TanStack/query/pull/4352

this sounds like a good idea. Maybe we should merge this one first though?

feat(devtools): enable setting loading/error via devtools #4352

Yes indeed :). Would be best to avoid rework on related PRs.

I'll try to get that one over the finish line this week. Let's close this PR ?

Yes, I will create related PRs when #4352 is merged.

devtools have been re-written in solid and now work for all framework adapters.


Jexcel with database

it is possible to save the csv in JEXCEL to MYSQL database? Please reply...

Yes, it is possible. jExcel is a 100% frontend tool. You need a backend to support your database operations, you can choose PHP or NodeJS. And you can export the data from jExcel to your database through an ajax post request.
https://bossanova.uk/jexcel/examples/getting-data-from-table

Is there the possibility the data directly to the database via ajax, php?

Yes, this might help:
https://github.com/jexcel/jexcel-database-base


Update 404.txt

Translated to czech language

This is not the place to do that.
http://translate.3ds.guide


fix(rebuild): use sudo if rebuild with another user than root

In order to switch the NixOS configuration, we must have root access. If we are connecting to the target host with a non-root user, we use the "sudo" command.
We could instead use nixos-rebuild --use-remote-sudo --target-host but it would evaluate the nixos system again.

bors merge


Flip default for --incompatible_config_setting_private_default_visibility

Help to flip the default for https://github.com/bazelbuild/bazel/issues/12933 by explicitly setting --incompatible_config_setting_private_default_visibility=off in existing repos under Bazel CI, and land a PR in Bazel to change the default so that new Bazel users get the right value.

looks like this is happening upstream for 6.x https://github.com/bazelbuild/bazel/issues/12933


feat: add title to "ask for help" forum requests

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Having no default title for "Ask for Help" requests can and does lead to a lot of badly titled forum requests.
This PR intends to give a well-structured default title so helpers can find.
The title will be structured as:
<Superblock / Section> - <Current Challenge / Step> - \<Username\>

These titles get a bit long - do we have 'short names' for the project and step?

Not really, unfortunately. With the new step-based design, we could trim the "Learn X by building a" off the title but this won't work for the older style challenges.

Could you maybe change this at the same time?

@ieahleen Would you have a suggestion as to what we could change it?
Maybe:
Challenge: <block> - <challenge title> to resemble the title?

@alpox yes, that would be perfect!

@ieahleen Thank you for your input. I added the challenge block-title to the description.

Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝

I really do not like seeing the extra clutter (21 random characters) in the forum topics. We are always telling users to make sure their topic titles describe the issue they are having.  Now we just seeing the challenge title (or step)?  I am not seeing how this any better than what we had before especially adding the garbage characters at the end.  I understand the intent, but they solution is not great in my opinion.  Maybe this should just be used for the new curriculum instead of the legacy?  What is really needed is a way to force users to enter a question on topic creation.  Currently, there is nothing stopping a user from entering no new text from what gets copied over from the challenge/step.

What is really needed is a way to force users to enter a question on topic creation.

Should we open a new issue on this?

I like the less crappy titles - giving the users something to start with prevents the "Im stuck copypasteportionsoftheinstructions' sort of titles and really there aren't that many unique ways to concisely write 'CatApp Step 12 - wrong anchor text'. We simply get too many users with the exact same question.
I'm all for adding something else to force users to actually ' Describe your issue in detail here.'

I am fine opening an issue as I do not think there was ever an issue opened to discuss this other than the PR.  I am fine with the titles just not the extra random characters at the end.  This can be accomplished with the enabling the allow duplicate topic titles feature of Discourse.


Improve error "Failed to start cln plugin"

It doesn't provide a reason.
for me it was due to running two lightningd in parallel.
https://github.com/fedimint/fedimint/blob/46487a37b463a7f45f10ce7f6218583e8ef5d371/gateway/ln-gateway/src/bin/cln_extension.rs#L194-L196

I'd like to work on this issue

Go for it @isaack-njama

Hey @justinmoon  picking up on this too, is it okay ?

Go for it @masikotimo

(not going to assign this to anyone ... anyone can give it a shot)

I think https://github.com/fedimint/fedimint/pull/2181 basically closed this. cln_plugin::Builder::new() returns Option so there isn't anything more we can say. We aren't given an error message.


Not setting the rank when creating a new object

Is there any way to not set the rank when creating a new object? For example, if I have
class Car < ActiveRecord::Base
  ranks :rank
end

Can I save a new Car object and keep the rank field nil?

Hi @dlynam, I don't believe so. The point of the rank is that everything in the scope has a rank. You could try scoping in such a way that the non-ranked car is outside the scope, then it wouldn't receive a rank?

Closing due to inactivity.


JS error when importing scss

Description
I'm using the ES6 skeleton, importing scss files in js like this:
```import 'styles/main.scss';````
Expected behavior
No JS error is expected...
And I expect that the compiled app.js shouldn't include
require('styles/main.scss');
(which it does)
Actual behavior
The compiled scss ends up in public/app.css. (works as expected)
I'm getting an error
Uncaught Error: Cannot find module 'styles/main.scss' from 'initialize.js'
But only in the browser (chrome), not in brunch build process.
Environment

Brunch: 2.9.1
Node: v6.2.2
NPM: 3.8.6
Operating system:

package.json contents
  "devDependencies": {
    "auto-reload-brunch": "^2.0.0",
    "autoprefixer": "^6.5.3",
    "babel-brunch": "~6.0.0",
    "babel-preset-es2015": "~6.3.13",
    "brunch": "^2.4.0",
    "clean-css-brunch": "^2.0.0",
    "css-brunch": "^2.0.0",
    "javascript-brunch": "^2.0.0",
    "postcss-brunch": "^2.0.5",
    "sass-brunch": "^2.7.0",
    "uglify-js-brunch": "^2.0.0"
  }

brunch config contents
module.exports = {
  files: {
    javascripts: {
      joinTo: {
        'vendor.js': /^(?!app)/,
        'app.js': /^app/
      }
    },
    stylesheets: {joinTo: 'app.css'}
  },

  plugins: {
    sass: { mode: 'native' },
    babel: {presets: ['es2015']}
  }
};

Hello there, @subpublic and thanks for creating the issue.
I don't see cssModules enabled in your config and guessing you just want to link your component's stylus with its code like you would do in Webpack.
In Brunch, we don't think that using import in this way is cool: putting .js and .scss in the same dir with the same names seems enough for me. All stylesheets will be joined and copied to app.css, no imports are necessary.
Hope that helps.

Please reopen if you have issues with using css-modules + Brunch.


Commit shape #399 Learn more card with button

Issue fixed: shapes, Creator - Web design  #2735
Added .html
modules\shapes\shape_#399_LaythonChilders

Heartfelt Thanks for Your Contribution to Our Open Source Project!
Dear @LaythonChilders (None),
I trust this message finds you in good health and high spirits. I am reaching out with a heart full of gratitude for your recent contribution to our open source project. Your dedication has not only elevated the functionality of our project but has also exemplified the collaborative spirit that lies at the core of thriving open source communities.
A heartfelt congratulations are in order for your exceptional work! Your commitment and expertise have played a pivotal role in the success of our project, and we consider ourselves truly fortunate to count you among our community members.
I must extend my sincere apologies for the delay in responding to your pull request. Your patience and understanding during this time are immensely appreciated. As our project continues to grow, we acknowledge the imperative need to enhance the quality and response time for contributions. To address this, we've kickstarted a call for maintainers and reviewers who can help us uphold the high standards of our project and ensure swift responses to pull requests.
Your involvement and insights would be invaluable in this initiative. If you, or someone you know, is interested in taking on a more active role in the project, please don't hesitate to reach out. We firmly believe that with a robust team of maintainers and reviewers, we can elevate both the quality of the project and the speed of our responses.
On an exciting note, I am thrilled to share that we have activated the sponsorship button for our project. This development allows supporters like yourself to contribute to the sustainability and growth of the project. Your ongoing support, whether through code contributions or sponsorship, is genuinely appreciated.
Once again, congratulations on your outstanding contribution, and thank you for being an indispensable part of our open source community. We eagerly anticipate your continued collaboration and shared success.
Best regards,
Ntem Kenyor K.
Lead
Kwickerhub


Local dev with phony Slack client

I was thinking maybe the PhonyClient implements an event emitter or something under the hood. That way, it's super easy to test, and we can test commands through the client as well. Thoughts?

Yeah an EventEmitter makes a lot of sense!

Alright I have a basic thing working here but I'm curious whether to focus on the event handler portion or the slash commands. Would it be easiest to just focus on the app_mention event and parsing out the message that is received? Then we don't have to mess with the slack app configuration any time we want to add capabilities to the bot.
Thoughts?

Yep I think listening for mentions is the way to go here!

@KalebMills alright I think this is ready for review. I know it's a lot of change, sorry about that! Things are now set up so that "commands" are specifically things sent to the bot in app_mention events.

We also need to update the .env.default CONF_FILE to local so folx can spin it right up with the `PhonyClient1


Update to<EMAIL_ADDRESS>break the builder

Bumping @angular-devkit/build-angular from 0.1100.5 to 0.1100.6 break the CLI and log the following error when running nx run semver:version:
Unable to resolve @jscutlery/semver:version.
Cannot find module '/home/edouard/work/jscutlery/semver/packages/semver/src/builders/version/builder'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>
Does it is related to Nx, or the angular-devkit itself? While this being resolved I revert the update.

It seems to be a conflict with the package inception. When I re-run yarn add @jscutlery/semver -D -W it works, but the package @angular-devkit/build-angular get downgraded to 0.1100.5 in yarn.lock, at this point if I run yarn and try to version then it fails.

It seems to be a conflict with the package inception. When I re-run yarn add @jscutlery/semver -D -W it works, but the package @angular-devkit/build-angular get downgraded to 0.1100.5 in yarn.lock, at this point if I run yarn and try to version then it fails.

Close it since it's conflict with deep npm modules duplication, the solution is to rerun yarn add @jscutlery/semver -D -W without committing the package.json (even if it's not perfect).

Close it since it's conflict with deep npm modules duplication, the solution is to rerun yarn add @jscutlery/semver -D -W without committing the package.json (even if it's not perfect).


BUG: Fix bugs with corrmap computation

Pretty sure from going back to the original paper that our corrmap code has been EDIT: a little bit incorrect ever since it was added in 0.10 in #2104 (which took over #1985, which took over #1795 -- the bug is present in all). We used the mean of some weirdly transformed maps  instead of just the mean of rms-normalized maps like noted in the paper. Our code in main did something like a z-score but not quite, even when fixing the incorrect usage of std to mean.
Fortunately I don't think it makes a big difference -- at least in our tutorial and tests the newtarget in this PR and the newtarget on main have a correlation coefficient > 0.99. But it should be better to use the correct / reference implementation I think.
Looking at the paper, one difference still remains where we use the median correlation (across ICs) rather than using a mean with a Fisher z-transformation, but I think that part's okay to stay as is -- especially since some of our correlations can be near 1. which will be a problem when subjected to a Fisher Z transformation. So I think the existing use of median is a justified departure for us.
Closes #11858

@jona-sassenhagen any chance you have time (& inclination) to review this one?

Thanks @larsoner


s7: move patchPhase to postPatch, fix installCheck problem

Move the patchPhase of s7 to postPatch to allow custom patches applied by the users.
Fix the problem of installCheckPhase found by @jian-lin.

Limitations
During installCheckPhase, the program reported
ffitest 2038: load ~/cl/ffitest.scm not found

;append second argument, #f, is boolean but should be a string
;    (append "/home/" username "/cl/")
;    s7test.scm, line 20439, position: 850325
; (append "/home/" username "/cl/")
; ((test *cload-directory* (append "/home/"... ; old-dir: ""

to which the corresponding code snippet is
    {
      s7_pointer e, val;
      e = s7_inlet(sc, s7_nil(sc));
      gc_loc = s7_gc_protect(sc, e);
      val = s7_load_with_environment(sc, "~/ffitest.scm", e);
      if (val)
	fprintf(stderr, "%d: load ~/ffitest.scm found!?\n", __LINE__);
      val = s7_load_with_environment(sc, "~/cl/ffitest.scm", e);
      if (!val)
	fprintf(stderr, "%d: load ~/cl/ffitest.scm not found\n", __LINE__);
      else
	{
	  if (s7_symbol_local_value(sc, s7_make_symbol(sc, "loaded_var"), e) == s7_undefined(sc))
	    {fprintf(stderr, "%d: load ~/ffitest.scm unhappy? %s\n", __LINE__, s1 = TO_STR(e)); free(s1);}
	}
      val = s7_load(sc, "/home/bil/snd-motif/");
      if (val)
	fprintf(stderr, "s7_load(directory) did not fail?\n");
      s7_gc_unprotect_at(sc, gc_loc);
    }

in ffitest.c. I don't know whether this is about something or it is just a upstream mistake.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

A priori username could be taken from $USER which is not likely to be set within a build? Even if it is set, /home/ is not what this code expects. Does setting $HOME to something writeable change the situation?


Error: DEPTH_ZERO_SELF_SIGNED_CERT

for Local Azure Cosmos DB Emulator.
when run "node app.js" getting the following error message.
Completed with error {"code":"DEPTH_ZERO_SELF_SIGNED_CERT"}
Add the following to the beginning of app.js fixed the issue
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0" // Avoids DEPTH_ZERO_SELF_SIGNED_CERT error for self-signed certs
I have copied the fix from:
https://github.com/request/request/issues/418

I also run into this issue. but after i use process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0", i still get different error now:
401
{"code":"Unauthorized","message":"Required Header authorization is missing. Ensure a valid Authorization token is passed.\r\nActivityId: 6d587555-f707-4442-a9ca-3fccb4805594, Microsoft.Azure.Documents.Common/<IP_ADDRESS>"}


FABG-937 FileSystemWallet

Implement pluggable wallet stores and identity handlers
Implement filesystem wallet
Signed-off-by: andrew-coleman<EMAIL_ADDRESS>

/azp run

/azp run

I wanna know what is this module "gateway" used for.


Move timestamps to first columns in migrations

Move the timestamps to the first columns in migrations

Check with @brittballard, but I don't think we'd want to modify old migrations, just make this a habit for new tables in the future.

I would agree, it's probably best to just use this convention moving forward. Otherwise we run the risk that new people's schema.rb files differ from ours, which could get to be a pain.

Yeap, agree with both of the above.
That said, we have a mountain of migrations. We could delete them and add a migration with the current schema.rb contents. You could rearrange the existing schema to put the timestamps first then. Leave it for others to decide if this is a good idea.

ok, cool.  I'll close the ticket.


Should not use 'System' as the namespace to qualify your library

Readline should not use System namespace. This will make it not possible to use this library in any enterprise project that has any package reviewing process.
I suggest the root namespace be created called something e.g. Tonerdo or similar and a new release be created (version 3) with the new namespace.
Great library btw! nice :D

Do not use Tonerdo build or old release.
The 'System' namespace was refactored a long time ago.
Use my forked release found on my page.  It is the latest release since I do not have admin access to overwrite 'master'.

just checked it out! txs looks good 👍
link here in case anyone else reads this thread later :
https://github.com/Latency/ReadLine
cheers,
A


Some incomplete and general things

why router when you only have one route?
why you no typescript or no flow?
redux installed but not used, instead I see setState quite a lot
service is not common in react, but this looks like a valid use case for it

Thanks for taking the time Oliver.

there will be routes! 😊
no idea how to integrate TS or flow but seems legit
yeah need to migrate those to Redux. No biggy
I see Services!

Cool, I can help with either TypeScript or Flow. All you need to do is to decide which one you like better:
TL'DR: TypeScript has the better tooling and seems more mature, but Flow still lives in the Babel world and is easier to integrate into an existing project. It also has the more powerful type system.

Also you can generate propTypes from Flow types using a babel plugin.


AdminLTE 2.1.0

The progress in AdminLTE v2.1.0 has begun and I would appreciate your feedback along the way.
The first step was to create the sidebar mini which has been long awaited for.

Updates about the progress will be posted here until we are ready for alpha.
Here is test url https://almsaeedstudio.com/themes/AdminLTE-dev/index2.html <- this url will only work until alpha is ready.
Known issues with sidebar mini:
1- Can't be used with fixed layout. This is because SlimScroll requires overflow: hidden wrapper on the sidebar. (I am not sure if we can fix this since I tried several times but it didn't work but if you have a solution don't hesitate to let me know).
2- Labels don't appear correctly. (should be fixed soon).
3- An issue we can't fix but we should make the users aware of is that the logo must have two variants. A "logo-mini" and "logo-lg" for collapsed and non-collapsed respectively, producing:

  ALTE

  AdminLTE

Sidebar mini is an optional feature. It can be activated by adding the class .sidebar-mini to the body tag. We also created a separate .less file for it. This way the user gets to comment it out form the main LESS file when it is absolutely not needed.
Note: please use this post only for reporting bugs and suggestions for v2.1.0.

Great progress, congratulations @almasaeed2010.
With the introduction of v2.1, I suggest moving the search form the top menu. The current location in the sidebar does not make it handy for use. If you are a user who prefers the hidden/mini sidebar and you need to search for something, you need to expand the sidebar, enter something and search, then collapse the sidebar again. This is three steps instead of one. Imagine if you need to search a lot! Not streamlined from a usability point of view. Search boxes better be always visible and accessible.
Also keep in mind the mobile screen version, the search form could be stacked under the title and the menu or converted to an icon that expands to a full search input or popup dialog.

@almasaeed2010 simply great!
+1 "search form the top menu"
i was thinking: why not add a media gallery/file explorer (starting by attachments blocks in mailbox ".mailbox-attachments")? or integrating a good plugin http://www.responsivefilemanager.com/

@almasaeed2010 thanks for all the great work. However I would have suggested the side bar mini to be for a right side bar. In other word possibility to keep the formal side bar and have the right side bar minified. However since it is optional, glory be to God.
Now please I u can add a drop down search button somewhere at the top ..
To me the search field is one of the most important thing needed. In the previous version it was placed on the left side bar and the problem is that if someone visits the website with his mobile he may not know that there is a search field there. Therefore if we can hav a search field like facebook on mobile that will be great

@YasserHassan I noticed the issue and I thought about using a feature that AdminLTE already provides which is a search form in the navbar. However, that also has its limitations. In small devices, it is difficult to make space for all of that in the navbar. The best soution I could think of is this:

Now, that will work but the breadcrumbs have to go. I tried adding them in a new line but it just didn't look good. So, until now, keeping the search form in the sidebar is our best bet. Nonetheless, if I find a fix that I am capable of implementing, I will for sure give it a try.
@adaniello That's a nice plugin but we are using Bootstrap WYSIHTML5 and I am not sure if it's compatible with it. I will look into it and if it is possible I might add it in the todo list for a future release.
Currently, for 2.1.0, we want the sidebar mini, right sidebar, and light sidebar skin. We'll always add more plugins and features as we go on.
Thank you for the feedback. Please keep it up!

@kressly I understand your concern. However, think of it this way, if the user can't find the search form then he can't navigate the site to begin with. I mentioned a couple of things about that in my previous post. I will keep working on finding a solution. Thank you!

@kressly the mini sidebar makes more sense as it is now in the preview above. It's the intermediate state between the fully expanded and the hidden states that preserves the sidebar navigation functionality without occupying too much space especially in medium screen sizes. The right sidebar suggested earlier was for extra information that needs a relatively large space to display so replacing it with a mini sidebar would probably be good form a usability point of view unless you have another navigation or menu at the right.
@almasaeed2010 you do not need to move the search form to the breadcrumbs area. Besides my previous suggestions of stacking the search on mobile screens under the menu on a 3rd line or converting it to an icon that expands or launches a search popup dialog box, I am adding another suggestion, converting the menu search on mobile screens to a search icon in the top menu (beside the messages icon) that shows/hides the 3rd search line when clicked. We have like 3 alternatives for the search functionality that make it usable on all screen sizes.

I must have misunderstood you. I'll see what I can do about that soon. I'll report any progress back here.

@almasaeed2010 Super work ! thanks
When the sidebar is in mini, it could be very interesting to expand the multilevel menu on hover instead by click like now. On mobile of course, we keep the click to expand.
Thank you !
Kind

@almasaeed2010 thank you for your consideration. In addition to the above, many mobile apps like Facebook's and LinkedIn's handle the search functionality in a streamlined way that does not clutter the user interface while keeping the search accessible. They can be good starting points to brainstorm this area which in my opinion is a weakness point in this great design.

@laudeco that sounds good. I will try it as an experiment and see how it goes.
@YasserHassan these companies don't use responsive design. What'd I'd like to do is to have only one search form instead of implementing it twice (in sidebar and navbar for example). So, if I could modify the current design to be easily accessible from the sidebar, it would be ideal. The idea I have is to replace the form with a search icon in the mini sidebar. On hover, the form would appear and stay open until a click outside the form container occurs (along side with keyboard event listeners like enter or esc).

@almasaeed2010 I know that the examples I mentioned are not responsive designs, they are mobile apps after all. What I meant was to see how those apps make the search functionality accessible and streamlined from a user's point of view, then see how to make it happen in AdminLTE as from a layout perspective, the mobile apps is comparable to the small version of AdminLTE and their application of the search functionality is more intuitive.

@almasaeed2010 I most at time on Facebook with my mobile However I do not really use their left menu because most thing that i need are either on the top or displayed directly there. On mobile devices, the left menu is closed by default. So for a beginner (a new user) he may not know how to open that menu. In my case and i think also in the case of Facebook most important things are either on the top menu. Facebook also use to put the search on the menu (left) but lately they have moved it to an icon on the top just like the message box that we have on AdminLte only that when you click on the search icon the menu drops down with the search field.
@YasserHassan My problem is that most people make the left side bar menu as the main menu and most users are expecting a left side bar menu more than the right. Now when the side bar is reduced to icon like in the image above, the user must now guess the meaning of every icon and for a new user, he may be afraid of clicking. For example I personally do not even know the meaning of these icons

But If I were to have a link made of Icon with a text, it will be more easier for me to click. How much more for a new user who may be on an accounting website or a sensible website.

@kressly The mini sidebar is an convenient middle ground between a completely hidden and fully expanded sidebar. This mini state is user-optional and of course is not meant for new system users until they become familiar with the meaning of the icons which usually takes a very short time to grasp.
It's normal that you don't know the meaning of the icons above as this is a template and you don't use it regularly but if it is used for an application that you use on regular basis, you'll appreciate such unobtrusive mini sidebar.
Add to this that there are additional ways to add more clarification to the mini sidebar if required such as icon tooltips and fully expanding the sidebar on mouse hover.

Hi ! It would be cool if the new version could be more requireJS aware. Where we could put all your stuff in a vendors/module directory of a new app. create an AdminLTE-config.js and call an AdminLTE.js module. I use it with backbone.js View and need many work on each update and dispatch all your file inside my apps. But thanks it's a great theme anyway ;-)

@goof03 I am not very familiar with RequireJS and Backbone.js. So, I don't think v2.1 would provide such support. However, it is good that you have pointed this out. I will look into it more and perhaps implement a solution in future releases. Thank you for contributing!

Just to clarify you dont have to be familiar with Backbone.js if you make your theme require.js compliant it could be use simply in many other javascript framework like angular.js, backbone.js, etc…
And more, require.js could simplify your work with your plugins dependencies, minifying your code.
Another thing come into my mind is there a reason to not using CDN for jquery and boostrap ? because if you follow Google PageSpeed advice it better to load file from many cdn than the same domain for latency, caching and parralelism. A better explanation :
http://encosia.com/3-reasons-why-you-should-let-google-host-jquery-for-you/

@goof03 intersting! I want to keep the page load and dependencies to a minimum. Since, not everyone uses RequireJS or similar scripts, how do you suggest we provide support without having to actually use it in the template?
I understand how the use of CDN could be beneficial. However, many users complained about them since they require offline support. This template is being used in a few NodeJS apps that work offline (which I think is awesome, btw). For that reason, I am trying to lower the usage of CDNs when unnecessary. Wouldn't you agree?

I prefer the non CDN. My application could easily be put offline and on an internal limited network for security reasons.

I don't want to feed the troll i will continue to modify the theme with CDN ;-). It's two face of the same coin …
For require.js my advice is to read the documentation and make your own choice … But it's only 14.9k and it load js only when it's need. With r.js you can create just one js file minified with just one command line for exemple you can automate this optimisation when you push a production version of your project. It's more clearer when you aggregate many library and many javascripts files from the web. It avoid to have many  line in your index.html.
you create your dependencies tree and you forget it when you call a module and when you launch optimization of all your project.
But i'm not a require.js Ayatollah there is other library to do the same thing.
RequireJS is a way to have the code organized and it avoids to use libraries without previous dependency.

@almasaeed2010  @YasserHassan
Yes I think tooltip and especially fully expanding the bar on mouse over will be great. However none of these will work on mobile, therefore on mobile the user will have to take a leap of Faith and click... Hum... I am just concern about new users

I will, again, request an example of a  'data' page where a lot of information would be, like the Facebook about page.

:+1:  @kasperhartwich
I greatly would like to suggest that app.js and other javascript code in AdminLte to come, will be with a jquery noconflict mode in other word, instead of using $ as variable, it will be wonderful to directly user jQuery as variable.
example
instead of  $('#messages_content'). we can have  jQuery('#messages_content').
That way most people using other libraries like me will not face much difficulties and will not need to open app.js and apply some patch here and there.
@almasaeed2010  you are the best. Hope you know that :+1:

http://stackoverflow.com/questions/4811807/hidden-sidebar-that-shows-up-on-hover
would something like this compliment the sidebar small nav?

Light Sidebar Preview
Fully expanded

With sidebar mini

@almasaeed2010 looks good. It would look better if the bar's right vertical edge is not obscured by the 2nd-level menu in the area shown below so the menu looks sticking beside the bar instead of above it.

@YasserHassan thanks for pointing that out

@almasaeed2010 thank you for the quick response.

Right Sidebar
Currently only available in dark skin. The sidebar will be implemented with two show options, a slide over content options and stick option. The first will take the effect as seen below. The second will move the content to make space for the sidebar. This feature hasn't been implemented yet. We will provide it with the beta release.

The preview has been updated to reflect the new changes. Please be advised that only Dashboard 2.0 has right sidebar.

:+1:  Wonderful
But please let lower the well that enables to choose skins otherwise it makes it difficult to click on the right side bar.

And please let us have an option so that those who wants the left side bar to be completely displayed by default on large screen and only reduced when the user clicks it will still have that.
Personally I loved the white skin at the left that you show in the first image and if we can have a white skin for the right side bar, it will be good
Thanks

@almasaeed2010 looks very good. Here are some suggestions to think about:

An option to integrate the right sidebar in the main area like the left one instead of hovering. This can be particularly useful when used on big screens to display frequently updated information that the user likes to keep an eye on without obscuring the main content or prevent interaction with it.

The opposite for the left sidebar, an option to make it hover like the right one.

hey，how can i use Light Sidebar  in 2.0.*

I found out little error in avatar size when activated the mini sidebar.
I'm using the latest Firefox browser, in Chrome it's fine.

@yufieko I noticed this issue yesterday and am trying to figure out why is it happening. I will let you know once it is solved. Thanks for keeping me informed!

@pakey the light skins have not been implemented yet. It is a work in progress. And will be available only in v2.1.0 and above.

@almasaeed2010 okey,3q.I'm looking forward to the arrival of the 2.1.0 version, what can I do, to make 2.0.1 earlier put into production environment.

@almasaeed2010 @yufieko At a glance, it looks like you can fix the mini-sidebar avatar issue in Firefox by adding a 100% width to the collapsed sidebar user panel image.  I haven't tested it in IE/Chrome, but one of the following should do the trick in FF.  Cheers.
/* set 'width: 100%' on the collapsed sidebar user panel image */
.sidebar-mini.sidebar-collapse .main-sidebar .user-panel img {
    /*max-width: 100%;  >>> might be able to get away without this assignment  */
    height: auto;
    width: 100%;  /*added*/
}

Or here...
.user-panel > .image > img {
    width: 100%;  /*changed from 45px*/
    height: 100%;  /*changed from 45px*/
    max-height: 45px;  /*added*/
}

Or via less...
 //Sidebar user panel
.user-panel {
  padding: 10px;
  .clearfix();
  > .image > img {
    width: 100%;
    height: 100%;
    max-height: 45px;
  }

Static Right Sidebar
Added the ability to disable slide over content.

Fixed bugs:

Sidebar mini user image out of bounds as mentioned by @yufieko
Nested box widgets collapse and open issue #321
Added new skins and control sidebar options to demo menu

You can now review changes in Master branch and preview the demo here

Wow :+1: Impatienly waiting for the download link. This is awesome. Can we add something like friedns online (like facebook's own ) on the right side bar  ?

@almasaeed2010 the option to embed the right sidebar is very good. I would be better if the sidebars change is unified, either both dark or both light. It would be good too to add right sidebar to the skins thumbnails in the options settings form.

There's an issue in the left sidebar expansion behavior. I does not exactly reverse the collapsing steps so at a certain point during expansion, content that's supposed to appear only after expansion is complete is shown during the transition leading to an undesired effect as shown below.

@kressly thanks :+1: You can download and test the master repo since I updated it. Just keep in mind that it isn't ready for production yet.
@YasserHassan the right sidebar will have two different skins with the release of beta. However, it won't be affected by skin classes. It will have its own color scheme class. This is so the user can have each sidebar a color if they want. I actually like having the control sidebar dark with light skin. It all comes back to preferences and I'd like to keep the options open. Since the skins don't affect the right sidebar colors, I will add an option to the demo menu to toggle between light and dark colors instead of showing that in the skins section. I will also update the demo menu to look more appealing and position it at the bottom of the page instead of top right.
I know the effect might be a bit annoying but that's the result of having transitions added to the sidebar.  The js solution will add unnecessary overhead on the browser and animation is not supported on all browsers. I will try to find a CSS based solution, which would be ideal. Thanks for reporting this.

Issue: right sidebar doesn't work with boxed layout.

@almasaeed2010

Having the option for color each sidebar separately is even better.
If the only solution for the the expanding sidebar issue above is JavaScript with some overhead, I vote for it. I don't think overhead would even be a problem with today's computers.
I suggest that you add a 3rd tab to the right side menu. I know developers can add them easily but it'd be better to make sure it's done by you to make sure there are not unexpected issues, then reduce by the developer to 2 or 1 tab if required.

FYI: The expanding left sidebar issue currently is a blocker for even demo'ing it to customers.
A solution would be nice.

@ChristianWeyer I agree it's an important issue.
@almasaeed2010 there are a couple of templates out there similar to AdminLTE in the mini sidebar regard and they work smoothly. I don't think AdminLTE will have a problem if adopted their development approach to the mini sidebar.

AdminLTE 2.1.0 Alpha has been released

Fixed sidebar mini overflow issue.
Fixed right sidebar + boxed layout issue
Added demo menu to right sidebar by creating a third tab (one of @YasserHassan's suggestions and to provide responsive support as @kressly suggested)

Release notes can be found in the [releases section] (https://github.com/almasaeed2010/AdminLTE/releases/tag/v2.1.0-alpha-1)

Wow. Just saw this. @almasaeed2010 you are the best ! :+1:  :+1:

How i can deactivate the sidebar transition?

@goof03  i've just read your comments and thought you may be able to help me. I'm new at front end developing, and I've chosen to use Admin LTE since it's a really nice template, but using Backbone.js and RequireJS. I've encountered myself with several issues since I don't completely undertand how to adapt this html template to those librarys. For example UI stopped working after I implemented require, I think it's related to a problem with the javascript, do you have any idea why this could be happening? thx!

add AdminLTE to rails app with gem 'rails-assets-adminlte', (then download 2.3.5 from source), i have this trouble...

premium theme logsout when opening in mobile and clicking on any link why kindly tell me...

Hello sir, i am currently using your template(version 2.3.3) for my admin console. I am running it on apache PHP 7. However, i noticed that when try to view it on the browsers for mobile devices and tablets, it looses the styles. The page appears as though there are no style sheets applied to the them. I am wondering why this happens and would like to get help. I tried to allow javascript on the privacy settings for the browsers of the mobile devices but that didn't solve the problem. will waiting to hear from you.


DatePicker field option optional, allow to provide date formate for InputField in DatePicker.

Hi
Recenrtly i have upgraded the flutter version to v1.17 and observed the changes in DatePicker. I have also tried switchable field option which is really great. but it seems that the field option only accepts the date formate (mm/DD/yyyy). I didn't find any option to change the dateformate of that InputField.
Also i did not find an option to disable the switch option and make the toggle button hidden.

Hi @mangoliprasanna,
There's a similar open issue, 55535. Please follow-up there for updates.
I am closing this one as duplicate. If you disagree please write in the comments and I will reopen it.