⚠ SolarOscp has degraded performance

In c9bfaf5, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 149 ms

Resolved: SolarOscp performance has improved in 617a223 after 10 minutes.


Setting command in C++/winrt programmatically?

If not using xaml designer, how can one set the command programmatically in C++/winrt? I have a large project that began before the xaml designer was available in C++/winrt, so I'm committed to code-behind UI. The paragraphs above seem to suggest that there is no way to set the command outside xaml designer.

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

ID: 1fc3748e-24db-fbb2-6020-747e142a5fd6
Version Independent ID: d837d584-8006-8545-c8ce-9d0abd0a45f1
Content: MenuFlyoutItem.Command Property (Windows.UI.Xaml.Controls) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.xaml.controls.menuflyoutitem.yml&version=GBlive&_a=contents
Product: uwp
Git Login: jwmsft
Microsoft Alias: jimwalk

p.s. for general info, I guess the solution is to just handle the Click event on the menuflyoutitem and implement the command directly that way, using the KeyboardAcceleratorTextOverride to show the key equivalent.

Hi, @jevansAN. Let's say I have a Windows Runtime type like this in my IDL.
...
runtimeclass BookSku : Windows.UI.Xaml.Input.ICommand
{
    BookSku();
}
...

And markup like this.
...
<MenuFlyoutItem x:Name="myMenuFlyoutItem" Text="Perform work" />
...

If I want to set an instance of BookSku to serve as the command object for that MenuFlyoutItem, then I can do something like this:
        MYNAMESPACE::BookSku m_bookSku{ nullptr };
...
        m_bookSku = winrt::make<MYNAMESPACE::implementation::BookSku>();
        myMenuFlyoutItem().Command(m_bookSku);

It's not unusual for topics in this area to show properties being set in markup. But you can still set such properties imperatively, too.
~Steve

This one's resolved, so I'll go ahead and close it. Thanks! ~Steve


The issue happens when going through the walk-through and getting to the step to delete the way-point, I think the screenshot below describes it well:

A workaround is to remove the curtain svg from the DOM.
The issue also happens with a new browser profile (without the plugins), screenshot:

However, at least with the same new profile, the issue does not appear in http://preview.ideditor.com/master/

Great thanks!  If it's fixed in http://preview.ideditor.com/master/ we can close it.. 👍


Not Disposable?

Why there is no Dispose defined in the library? you have it for texttospeech library which looks similar.

Doesn't need to be


Integrate versioning into AR touch method

Related to Issue 1061

Something to consider with this PR is the following lines:
https://github.com/westonganger/paper_trail/blob/master/lib/paper_trail/model_config.rb#L209-L208
Currently it will attach to the touch event always. Maybe this should be added as one of the available :on events and it included by default or must be specified?

Currently it will attach to the touch event always. Maybe this should be added as one of the available :on events and it included by default or must be specified?

Good thinking. I think the callback should be installed by default, but configurable via the :on option.

This will need a changelog entry and probably some significant changes to documentation in comments and in the readme.

I guess touch_with_version could be deprecated. Should that be a part of a separate PR? or would you want to do this yourself?

Okay the following items have been added to this PR:

Add touch to list of :on events (by default it is included)
Deprecate touch_with_version
Updated changelog
Updated readme documentation to use touch instead of touch_with_version

Thanks, Weston.

Is there a way to globally disable the tracking of the touch event?  Or more generically, set the default /create/update/destroy/touch global 'on:' defaults ?
As implemented, it breaks when using the delay_touching gem (specific case is when a delayed touch is for a record that was marked for destruction, the attempt to create the version  association in record_update() in record_trail.rb throws an exception because the @record no longer is persisted (as it was deleted before the touch events are fired - touch having been delayed as the function of the delay_touching gem).
Given this was not the default behavior before and the alternative is updating potentially hundreds of models (we have a pretty large app) to disable on: :touch, I'd much rather have a PaperTrail.config.xxxx setting once.
We upgraded from 7.x to 10.x and had this break (it worked before, likely because it was before touch versioning was done)

@gduprey 	https://github.com/paper-trail-gem/paper_trail/pull/1166 adds this

.... of course it does, you wrote it.


Upgrade player to videojs v5.0.0

This upgrades the videojs player to v5.0.0. The caveat is that it does not yet use ES2015 recommendations of videojs v5.
Fixed #74

This pull request seems to work well for me. Could someone merge this soon ? @carpasse ?

@kahwee Thanks a lot for this PR @wmcmurray added a new PR that contain your changes among others. We are going to try to merge that one, still we are very grateful for your PR and very sorry we were not able to take a look at it sooner. We've had a very tough time this last 3 months.


Baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions

Follow https://github.com/opensearch-project/.github/issues/125 to baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions.
Close this issue when:

[x] 1. MAINTAINERS.md has the correct list of project maintainers.
[x] 2. CODEOWNERS exists and has the correct list of aliases.
[x] 3. Repo permissions only contain individual aliases as collaborators with maintain rights, admin, and triage teams.
[x] 4. All other teams are removed from repo permissions.

If this repo's permissions was already baselined, please confirm the above when closing this issue.

We still need to correct the permissions. I'll work this item.

This is now complete.

Verified permissions, thanks.


Enhance UI/UX of Navbar and Revamp Login/Signup Pages with Google Authentication

🖥 Frontend Issue
Description
The current UI/UX of the navbar lacks aesthetic appeal and usability, negatively impacting user navigation. Additionally, the login and signup pages are not properly connected, creating confusion for users attempting to transition between them.
Furthermore, the eye button for toggling password visibility is missing in the password section, which affects the functionality and user experience of the login interface.
To address these issues, I propose to:

Redesign the Navbar: Improve the overall layout and visual appeal to ensure intuitive navigation.
Connect Login and Signup Pages: Establish clear links between the two pages to facilitate a seamless user experience.
Integrate Google Authentication: Add a login/signup option with Google, providing users with faster and more secure access to their accounts.
Implement the Eye Button: Ensure the eye button is properly placed within the password field to enhance usability.

These updates will significantly improve the user interface and experience, making the platform more user-friendly and accessible.
Kindly assign this issue to me under the GSSoC'24-Extd program.
Thank you for your consideration.

Go ahead @ritiksingh-01

Hi, @dhairyagothi
I apologize for the delay in resolving the issue. I'm actively working on it and doing my best to deliver a quality output, as this is my first open-source project. I appreciate your patience, and I will provide the update as soon as possible.
In the meantime, I kindly request that you don’t assign this issue to anyone else or merge any related pull requests.
Thank you for your understanding!

Hi, @dhairyagothi
I apologize for the delay in resolving the issue. I'm actively working on it and doing my best to deliver a quality output, as this is my first open-source project. I appreciate your patience, and I will provide the update as soon as possible.
In the meantime, I kindly request that you don’t assign this issue to anyone else or merge any related pull requests.
Thank you for your understanding!

take your time


ERROR in The Angular Compiler requires TypeScript >=3.4.0 and <3.6.0 but 3.7.2 was found instead.

🐞 Bug report
Command (mark with an x)

[ ] new
[ x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....

Hi Typescript 3.7 is not supported in version 8.
Please use TypeScript 3.4.X or 3.5.x


Genomic Info: 1064 non unique library ids in genomic info

v0.50 ... File attached
select count(*)
from (select library_id, count(*)
	  from genomic_info
	  group by library_id
	  having count(*) > 1)as_

This is because some file-sample combinations have multiple sequencing experiments. we handled this last before by having sequencing experiment as part of the ID here.
I'm working on adding sequencing experiment id back in to the library ID


Maximum number of records that can be ingested this way?

I see there's a mention of For example, the command can retrieve 1000 CSV-formatted blobs from Azure Blob Storage.  Is 1000 the max number of records that a statement can contain?  It would be good to note that on the page explicitly if that's the case, or whatever the actual limit is along with any recommendations on best practices on how many files to include.

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

ID: 8367589f-76cb-1a24-37d0-e4355594fb18
Version Independent ID: 3455ea4f-4ce4-ee0d-007c-d4ca3b7ec89e
Content: Kusto .ingest into command (pull data from storage) - Azure Data Explorer
Content Source: data-explorer/kusto/management/data-ingestion/ingest-from-storage.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@dwhathaway  Thanks for the question! We are investigating and will update you shortly.

@dwhathaway thanks for the feedback. The text you quoted is just an example and not a limit.
We created a WI to clarify this statement in the doc.
I will now close this issue. If you need more information on product limitations, feel free to
create a thread on the forums - Microsoft Q&A or stackoverflow.
I am now closing this issue.


BUG: Wither Rose bees do not produce Strange Honey

[I am using Forge with version 1.18.2]
Hi there! To be very concise, as far as I can tell, while bees can sometimes pollinate wither roses (assuming you keep them alive, of course), the product you get is ordinary default honey.
I tested by encasing a number of spawned bees in a glass dome with a bee box that was blocked off from all other sides. I am not 100% certain of my testing methods (I noticed a single glass pane that already-pollinated baby bees could have hypothetically squeezed through to get in, so it's possible the test was contaminated), and I may attempt to test it again tomorrow just to be sure. That being said, I wanted to bring it to your attention.
As a sidenote, it's extremely challenging to test this without knowing commands to give the bees invulnerability, especially since beekeeping is a slow job regardless. I wound up using a dispenser with a clock to launch lingering Regen potions in every five seconds, which feels a lot less "small beekeeping-y" than the mod seemed to intend and seems like it could be exorbitantly expensive in Vanilla, so I can't tell if I'm doing something wrong.

Thanks for the report! I admit, I haven't specifically tested wither roses in-game for all the reasons you described, but I did add it while knowing it would be extremely difficult to actually obtain. Which makes it all the more important it actually works! I'll see if I can replicate the issue (although it'll have to be late next week) and keep this issue updated.

@KoboldCatgirl Oh, and just to check off all my boxes:

Which beehive variety were you using?
How many bees were in it?
Are you running any other mods that might affect bees or flowers? (Texture packs don't count, don't worry about any of those)

Hi there! I figured out how to do invulnerable bees and ran the test again today. Barring some weird "bees that take damage count as having pollinated default flowers" glitch, I believe I can safely call this a false alarm, and apologize for any confusion or wasted time this may have caused!
There are some other bee- and flower-related mods installed, but since the test was a success, I'm not too fussed digging them out unless it'd be of use to you!
In case you're curious:

Three wither rose enclosures and a control group orchid enclosure, with 6-7 invulnerable bees and all other access points fastidiously blocked off. Birch boxes.

Three wither roses and seven very determined bees. (Three are inside already.)

A very brave survivor of the previous Wither Rose Trials. I gave her a nice new bee box and some tulips.

Wither rose enclosures, with Strange Honey!

And the control group, of course.

No worries, I'm just glad to hear it's working! And thank you for the pictures :D


has_xpath? ignores visible

The following
node = ::Capybara.string(html)
node.has_xpath?('/html/head/title', :visible => true)

returns true, when it should be false, i.e the title is not visible.
The issues/techniques for testing visible elements in Capybara need to be brought into the readme.
This comment indicates some unnecessary blow back is developing[0]
[0] http://testobsessed.com/blog/2011/03/01/checking-invisible-elements/comment-page-1/#comment-10666

Sorry to be dense, but I don't yet see the difference.  What does only_visible mean that is different from visible?
Specifically, if you say the behavior is correct, but the documentation is ambiguous then in my example, I would still get true when I still expect to have false returned - correct?
There are several blog posts/gists out there trying to get this behavior, I've seen at least four.  Could it be that the behavior people are implementing themselves is not in Capybara?

:visible => false finds all elements, regardless if they are visible or not. You will have to do what you are trying to do manually, since Capybara does not have an API for that built in.

Isn't that a bug then?

Closing this as a duplicate of issue #544

No, it's an intentional feature. This behaviour is way more useful than checking for only invisible elements. Why would you ever care if an element is invisible in an acceptance test? But sometimes elements are invisible for some obscure reason and still need to be checked (though even that should be avoided imo).
Just realized, I misread the question above though, so apologies, my answer didn't really make sense.
The reason that :visible => true doesn't work in this case is because RackTest doesn't parse CSS and doesn't have any default browser stylesheets. Element#visible? in RackTest and Capybara.string only checks inline styles, and not styles applied through external stylesheets or browser default styles. Which, btw, is the reason that Capybara.ignore_hidden_elements is still set to false by default.
Does this mean we should add a CSS parser to Capybara, add default stylesheets and make sure this method works in 100% of cases?
No.
Why? One – it misses the point of Capybara, you shouldn't care about these kinds of details when you write an acceptance test. Two – it would have atrocious performance. Three – It likely still wouldn't work in absolutely all cases.
So for most intents and purposes you can simply consider that RackTest and Capybara.string don't really support :visible => whatever and just deal with that.
That blog post is pretty bad, imo. The suggested solution is even more deficient than Capybara's current behaviour.

To make sure that it is invisible and not leaking into the users experience.
For cases such as Capybara.string (simple node) shouldn't an exception be raised when unsupported behavior is invoked - or at least a stderr report that all is not well?


Plan PalaestrAI integration

PalaestrAI will not be directly integrated. Instead, the SAC RL algorithm will be used with a wrapper class. The same goes for the power grid environment.


Decide on git content

Are we teaching git basics?
If so, are we asking class to do homework before class?
At a minimum, may want to teach how to fork repo and pull over any updates.

Yes
Yes, will need to have students install git. Need to provide instructions for both Windows and Mac.
Will start out by teaching how to fork the repo and open up project

Include some basics in reproducible research lesson


Content: update docs headless home and playwright / puppeteer basics

Affected Components

[x ] Content & Marketing
[ ] Pricing
[ ] Test
[ x] Docs
[ ] Learn
[ ] Other

Overall minor content updates and updating of messaging.

@stefanjudis can I get your input as well here?

@modern-sapien could you give this another go? the Headless Guides are not supposed to mention Checkly at all - they are entirely Playwright focused. Let's keep them this way as part of this rewrite.

@modern-sapien actually, could you remove the Checkly mention from the Puppeteer page as well?

updated @ragog


What is MemcachedBackend config Look like?

Hi! I'd like to ask the problem about using memcached as backend . I install memcached by using its office document, but i can't find the files named 'server_list_cfg' or 'client_cfg'. What tool memcached client you used? Could you give me an example about "server_list_cfg","client_cfg" and "sys_path"in your spare time?Thanks a lot!!!!!!!!!!!!!!!!!!!!!!!!!!!

This problem is related to MMCV. Please open another issue in MMCV.


Update index.d.ts

Missing parameter declaration.

Thanks! @dreamsavior Could you please publish another release with this PR?

Done, updated the NPM package.


Benchmark - launch in VR

Hello. Although launching into VR works nicely, it isn't working for benchmarks. I've even set the +VR flag in Steam myself, but it still starts in pancake mode if I hit the Start Benchmark Queue button.
Thanks for updating your invaluable widget for the new release and for doing it so quickly. Your efforts are much appreciated.

Hi, thanks for the report. I'd have to implement a UI element letting you choose VR/pancake for the benchmark but I'm afraid I won't find the time within the next 2 weeks.

THis has been adressed:
github.com/tappi287/rf2_video_settings/releases/latest


Remove obsolete argument in throttleHelper

Remove obsolete argument in throttleHelper as per issue #807

Are tests passing?

@Andarist  Yes, all 139 passed.

Thanks for the PR!


Error on build npm package for react redux

i'm creating an HOC to connect container and representational component.
I'm using webpack for build both on development test and production.
The package exports a function that return the react-redux connect component
On develempent everything works as expected. When i build the package and link to test in production build i got

Could not find "store" in the context of "Connect(NameComponentPres)". Either wrap the root component in a <Provider>, or pass a custom React context provider to <Provider> and the corresponding React context consumer to Connect(NameComponentPres) in connect options.

i don't think that is a problem with react because it works on development, but i had already create a stackoverflow question and post it on reactflux without success
this is my configuration
webpack.config.js
const path = require("path");

const outputPath = process.env.BUILD
   ? path.resolve("./build")
   : path.resolve("./test");

const testConfig = {
   mode: "development",
   entry: "./demo/index.js",
   devtool: "inline-source-map",
   externals: "./build/redux-simple-container.js",
   output: {
       path: outputPath,
       filename: "index.js"
  },
  module: {
    rules: [
        {
            loader: "babel-loader",
            include: [path.resolve("./demo")]
        }
    ]
  }
};

const buildConfig = {
  entry: "./src/ReduxSimpleContainer.js",
  mode: "production",
  output: {
      path: outputPath,
      filename: "redux-simple-container.js",
      libraryTarget: "commonjs2"
  },
  externals: ["react", "react-dom"],
  module: {
      rules: [
        {
            test: /\.js?$/,
            use: "babel-loader",
            exclude: /(node_modules)/
        }
    ]
  }
};

module.exports = process.env.BUILD ? buildConfig : testConfig;

.babelrc
{
  "presets": [["airbnb", { "modules": false }]],
  "plugins": ["transform-object-assign"]
}

./src/ReduxSimpleContainer.js
import { connect } from "react-redux";
const ReduxSimpleContainer = (actions, stateRequested, Component) => {
  ....
  ....
  return connect(
    mapStateToProps,
    mapDispatchToProps
  )(Component);
};

export default ReduxSimpleContainer;

Please provide a project that reproduces the issue.

i have tried it in two different projects.
this is the shell of both projects.
import React from 'react';
import { hydrate } from 'react-dom';
import Loadable from 'react-loadable';
import BrowserRouter from 'react-router-dom/BrowserRouter';
import { renderRoutes } from 'react-router-config';
import { applyMiddleware, createStore, compose } from 'redux';
import { Provider } from 'react-redux';
import logger from 'redux-logger';
import ReduxThunk from 'redux-thunk';
import Parse from 'parse';
import routes from './routes';
import maydayReducers from './reducers';

/* eslint-disable no-unused-vars */
import robots from './robots.txt';
/* eslint-enable */

const preloadedState = window.PRELOADEDSTATE;

delete window.PRELOADEDSTATE;
/* eslint-disable no-underscore-dangle */

let middleware = [ReduxThunk];
let enhancer = applyMiddleware(...middleware);
if (process.env.NODE_ENV !== 'production') {
  middleware = [...middleware, logger];
  const composeEnhancers = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || compose;
  enhancer = composeEnhancers(applyMiddleware(...middleware));
}
const store = createStore(maydayReducers, preloadedState, enhancer);
/* eslint-enable */

const AppRouter = () => <BrowserRouter>{renderRoutes(routes)}</BrowserRouter>;

Loadable.preloadReady().then(() => {
  hydrate(
    <Provider store={store}>
      <AppRouter />
    </Provider>,
    document.querySelector('#app'),
  );
 });

for example i export the component like this
export default
  ReduxSimpleContainer(
    [{ type: INVESTOR.SAVE_EMAIL, params: ['contactId'] }],
    ['investor'],
    FormContact,
  );

i have used it in 3/4 projects with copy and paste and now i want to use it via npm

I can't do much to diagnose this without an actual separate project repo I can clone.

@markerikson can i add you to the repo?

If it's public, just give me a link.  If it's private, yeah, add me.

It looks like the repo you've got is just for an NPM package.
It would help if you can put together an entire repo that completely demonstrates the problem, just by cloning it, installing, and running some kind of a "start" command.
Also, does this problem happen if you copy and paste that HOC file into an application, without trying to build it separately?

i'm creating the repo.
I agree with you that isn't a issue with react-redux and i'm sorry for having opened that issue but I'm trying everything to understand what is wrong with the build.

Well, I've cloned both repos, and I've tried building and starting the second one, but I'm not seeing the error you described.  I do see that the second repo has a copy of that HOC file and appears to be using it directly.
I'm sorry, but this is too far off-track for me at this point.
I'd suggest looking at something like https://www.npmjs.com/package/create-react-library as a starting point for creating a reusable library.

I solved the problem. i have change webpack with babel to build the package. it seems that the problem was from where the package requires the react-redux npm package. if my package require it from his node modules it throws the error otherwise it works. I hope that it can be useful for someone.


0-point puzzles shouldn't affect the leaderboard ranking

Okay, this is a bit of a selfish request, but a request to ignore 0-point puzzles in the following manner:

Solving such a puzzle shouldn't update the "last solve" counter
The leaderboard probably shouldn't be first tiebroken by # of solves (if this is desired by a hunt, make these puzzles worth epsilon>0 points)
# of solves can still be reflected on the leaderboard though. This allows for easter eggs to be found

This (0-point puzzles shouldn't affect the leaderboard ranking) was always intended. for Magic Hunt. So 26793bc has been pushed to fix speedrun mode's default ordering, leaderboard should look normal now.
For the rest of points, I will properly think on them before changing - All changes are retroactively global on Myus

Thanks for implementing point 2!
Point 3 is the current behavior, so nothing would need to be changed there.
I think point 1 makes sense - solving an easter egg shouldn't be detrimental to placement as either (and indeed is strongly disincentivizing my team to try submitting ideas for that puzzle :p ). I don't know if there are other hunts on myus that have optional 0-point puzzles that could substantially change the rankings (at least I don't believe myus hunt has a solvable credits page)

Oh it's not about whether it's a good idea, but whether the implementation is worth the overhead.
I want to avoid jank logic in implementation, otherwise it will be something to fix in future hunts.


IUS-COMMUNITY-EUA file is missing on CentOS 7

It looks like the IUS RPM package for CentOS 7 may have changed upstream, now no longer including /usr/share/doc/ius-release-1.0/IUS-COMMUNITY-EUA, which causes this role to fail.
To check this, download https://centos7.iuscommunity.org/ius-release.rpm and do rpm -qlp ius-release.rpm

I'd also recommend switching the release RPM URL as well.  IUS no longer builds separate packages for RHEL and CentOS, so the following URL can be used for both.
https://repo.ius.io/ius-release-el{{ ansible_distribution_major_version }}.rpm


move EnvoyProxy API to gateway.envoyproxy.io

this keeps all CRDs/APIs under the gateway.envoyproxy.io group

this is a breaking change, that needs to be highlighted in the release notes. Undesirable but acceptable since these APIs are experimental (alpha) and are not yet stable

Fixes: https://github.com/envoyproxy/gateway/issues/809

will this be a break change for existing end users? especially upgrade?

will this be a break change for existing end users? especially upgrade?

yeah this will be a breaking change, we had discussed this in the community meeting and looks like we reached some consensus on this


Capturing errors, e.g. forbidden transitions

When using this library, I have found that there is no ability to capture certain errors.
There is an on_failure callback but this callback only knows the event and the state. It does not know the actual error.
For example, when a particular transition is not allowed, we get a warning-level log message:
                Logger.warning("[⚐ ↹] transition failed " <> inspect(err))

But that err is then lost. In fact, this err does not seem to be accessible in any way!
I think this is of critical importance if this library is to be truly useful. FSM-logic errors need to be capturable.

Hi @peaceful-james, sorry for the not instant response,
There is an optional callback in the module that calls use Finitomata, on_failure/3, allowing to handle everything.

Hi @peaceful-james,
two kinds of issues might happen with an FSM implementation: the developer’s failure and the violation of the business logic. The latter is perfectly accessible from on_failure/3 via state.last_error (set in the line 1011.)
The former, though, has nothing to do with the FSM itself and should be simply fixed in the code. Hence there is no trace of it in the state, only in logs. That’s basically why we have different else clauses to catch.


Add auto expansion of * to all columns on ctrl space

Hello,
I would really like to see the following:
Write "select * from mytable"
Place cursor after "" - hit ctrl + space
DBeaver replaces "" with column names, ie "Select myCol1, myCol2, myCol3 from myTable"
It would save a lot of typing!
Many thanks

Agreed, I like this


tests require linter to pass in order to run

Simple check so that tests are not run if linter fails.

verified in https://github.com/redpanda-data/helm-charts/pull/475


Source code for v0.9.9 not available on GitHub

Hi,
it seems like the source code of version https://crates.io/crates/uncased/0.9.9 and the respective commit c44154668584669e77f568752a902bfa8ae4ed7b (https://docs.rs/crate/uncased/0.9.9/source/.cargo_vcs_info.json) is not available here in the GitHub repository. Would it be possible to push the code and create a tag?
Kind regards
Moritz

Whoops! Thanks for letting me know.


windows support?

Unfortunately many of our production environments are Windows. Has anyone had success installing/running airflow in Windows 7/Server 2008 and up?

I'm not sure if the libs we use do support Windows, but if they do it seems like it may not be too hard to support windows. Well I mean for Airflow to be retrofitted to work on windows. It's probably mostly a matter of making sure all file references use os.path.join instead of  FOLDER + "/foo".
Though there may be more to it, I haven't touched a Windows server since NT4. I tried to SSH in one for Tableau one time and was told that you couldn't do that.
Airbnb won't be driving Windows support but if someone from the community wants to send PRs in that direction we'll be happy to review / merge them.


ci: build example_bass on linux and mac

This is still WIP.

Ugh, OK. So this (obviously) need BASS installed into all of these, which can be a pain...
I wonder if it's better to do this as part of #93 instead...

Nah, turns out it was simple to do that manually...


[G2M] Updates/notion

Changes:

add md-to-notion converter
upload updates to Notion Digests db
notify updates summary in slack
upgrade notion client version

also carrying here the suggestion to leverage markdown fields to leverage the space a bit more horizontally too


Replace nullOk by maybeOf

New flutter master has remove the nullOk in this commit and it's causing error
No named parameter with the name 'nullOk'

According this feature, it needs to change to maybeOf
 _invertColors = MediaQuery.maybeOf(context)?.invertColors ??
        SemanticsBinding.instance.accessibilityFeatures.invertColors;

we are working on stable branch. master is always changing.

Well, I need to work on master or dev because I use flutter for desktop & web.
I temporary use my fixed branch like below at the moment
dependency_overrides:
  extended_image:
    git:
      url: https://github.com/ductranit/extended_image

but it'd be good if you can create an alpha build on master channel, that's will help someone

thanks, code is change in dev, 1.3.1-dev is ready on pub.dev


Set github workflow permissions to be minimally scoped

I'm from Google working with the OpenSSF to improve supply-chain security in many open source projects.
I would like to suggest to volatile project to set minimal scoped permissions to its github workflows (in this case the build.yml file). This means setting the permissions as read only on the top level and any write permission be given at the run level.
This is necessary due to a behavior of github workflow to grant to GITHUB_TOKEN write permissions to all types of permissions, regardless of they being used or not. In case of the workflow getting compromised, an attacker can exploit this permissions.
This can be seen in the Action run step "Set up job" such as https://github.com/rust-osdev/volatile/actions/runs/3974296184.

Considering the changes are quite simple, I'll also suggest the PR together with this issue.
Thanks!

That is a weird default indeed.
Can we modify the default permissions for the whole rust-osdev organization instead? https://docs.github.com/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization seems to suggest that it's possible.

Yes it is possible to change it to default indeed, and this is good because any new workflow added in the future, that does not declare its dependency due to human error, will only be granted read-all permissions.
Besides that, it is a good practice to also declare the permissions on the yml file to be minimally scoped too, because this will ensure this workflow won't depend on any configuration to be secure besides bringing transparency to the users that the workflows are running with the principle of least privileges.

Thanks a lot! I just merged your PR.
I agree that changing the default at the organization level is a good idea too. However, we would probably need to update some of our repos for that. So we should look through all of our build jobs before to avoid breaking something.


DRILL-7654: Add support for JDK 14

DRILL-7654: Add support for JDK 14
Description
Allowed building Drill with JDK 14, updated ASM and javassist to the latest versions, updated GitHub Actions script to build and run tests for Java 14 instead of 13.
Documentation
NA
Testing
Checked that Drill is starting without errors or new warnings on Linux and Windows, made sanity checks to ensure that functionality is preserved.

+1


Compare page styling

[ ] Allow for filter dropdown specificity - both custom for a realization and universal options


sowm: Border

Patch adding border as requested in #72
https://github.com/dylanaraps/sowm/pull/74.patch

Works perfectly, managed to also make it use different colours for some specific programs using XGetClassHint and checking res_class, is it a good solution or is there a better way to check what program the window belongs to?

That’s a legit way, you can update border-color via XConfiureWindow()

Maybe you need to clean the patch? When I apply the patch, it asks me to apply 2bwm patch blah blah, which is quite annoying.

Attached for your convience is the transcript of printf "pwd $(pwd)\n"; yes | patch -p1 < 74.patch, where 74.patch was downloaded from the website at approx.<PHONE_NUMBER> (unix timestamp), the sowm repositiory was the latest there was (at the time of writing), and running on a fully patched and updated Arch Linux.
pwd /home/usr/sowm
patching file Makefile
patching file README.md
patching file config.def.h
Reversed (or previously applied) patch detected!  Assume -R? [n] y
patching file sowm.c
Hunk #1 FAILED at 8.
Hunk #2 FAILED at 68.
Hunk #3 FAILED at 101.
Hunk #4 FAILED at 108.
Hunk #5 FAILED at 129.
Hunk #6 FAILED at 170.
Hunk #7 FAILED at 210.
Hunk #8 FAILED at 252.
Hunk #9 FAILED at 264.
Hunk #10 FAILED at 284.
Hunk #11 FAILED at 312.
11 out of 11 hunks FAILED -- saving rejects to file sowm.c.rej
The next patch would create the file sowm.h,
which already exists!  Assume -R? [n] y
patching file sowm.h
Hunk #1 FAILED at 1.
Not deleting file sowm.h as content differs from patch
1 out of 1 hunk FAILED -- saving rejects to file sowm.h.rej
The next patch would delete the file patches/.sowm-wheelresize.patch.swp,
which does not exist!  Assume -R? [n] y
File patches/.sowm-wheelresize.patch.swp: git binary diffs are not supported.
patching file patches/sowm-2bswm-style.patch
patching file patches/sowm-almost-tags-0.3.diff
patching file patches/sowm-almost-tags-1.0.diff
patching file patches/sowm-handlebar.patch
patching file patches/sowm-init.patch
patching file patches/sowm-normal-kill.patch
patching file patches/sowm-primitive-multimonitor.patch
patching file patches/sowm-rect-to-move.patch
patching file patches/sowm-rounded-corners.patch
patching file patches/sowm-wheelresize.patch

@EnricoMonese, would you mind sharing your implimentation of what you described? Or is it in a repo somewhere? If so, please point it to me.

@Unixsys basically at line 28 here the color of the border gets set. This patch has a fixed color, instead of using that directly I first check the class/name of the current window being configured by reading cl.res_class or cl.res_name. And based on what program it is I choose a desired color.

@EnricoMonese do you bychance have any idea on how to impliment window border color changes if a window is selected? I tried modifying win_focus with code to set the border a different color (like the code in map_request), and quickly realized the functions used in map_request (XSetWindowBorder & XConfigureWindow) required the window object be passed to it somehow. The win_focus function gets passed a client object, but sadly not the window object. Thus my implimentation failed. :(

I'll close this PR, use the updated one(PR #82 ) instead.


correct readme scripts for preprocessing

Updates for README.md to correct path for data download/preprocessing.

thank you @thomasarmstrong98 for catching the error!

all good, thanks for releasing the code @tung-nd !


Add happy path_v2 variant for the native token

This just tests the erc20 representation flow with the native token specifically to see if any errors are triggered.

@jkilpatr I amended your commit in order to de-duplicate some code.


Decrypt a word crypted in 3.1 don't work

I crypted a word in 3.1 and I update to 4.0 to test and I can't decrypt it and when I crypt a word in 4.0 I can't decrypt it in 3.1. I made something wrong probably but I just followed the instructions. But it dosn't work.
Is there maybe a configuration to use with secret_iv cipher_algorithm to have it work with the old version ?
Thanks

Make sure that you keep the same bundle configuration between the two versions and it should work.

it was the case I just changed in config.yml :
nzo_url_encryptor:
secret_key: *************
i didn't use secret_iv and cipher_algorithm but not the same result.

If you change the secret_key value the "decryption" and the "encryption" result will change accordingly!
So make sure you have the same secret_key value, otherwise you to rollback by using the base value.

it was the same value but the crypt result isn't the same.

I'm talking about all the configuration, not only the secret_key

Just to know is it the variable secret_key in 4.0 the same to secret in 3.1 ? becuse if it was the case I didn't change it I just changed the name in config.yml.

I don't know what do you mean by secret as the bundle doesn't contain this variable anyware in the configuration.


News styling

This PR:

Styles the news list for desktop and mobile.
Styles news forms for desktop and mobile.
Styles news detail view for desktop and mobile.
Styles confirmation for deletion of news
Styles editing news

Additional styling for Library version alerts and avatar corner rounding.

@nessita just to let you know, in this PR I commented out a few assertions in the view tests that were testing values of context that was either removed completely or changed outside of the views.


Non-ASCII character '\xc2' in node.py

I receive this error when using miosqp with Python 2.7:
SyntaxError: Non-ASCII character '\xc2' in file miosqp/node.py on line 17, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

https://github.com/oxfordcontrol/miosqp/blob/e15c5aa5be2674fea5c850d1bf969769ae310dbc/miosqp/node.py#L16

That was a typo. Fixed in this commit ba02ad6e7c6d2bf0282f1abfe8c7671446beb86b. Thanks for spotting it.


Forcings Evaluation Viz Notebook

Overview
Review visualization notebook in its entirety.

Issues,

Closes https://github.com/hytest-org/hytest/issues/518
Closes https://github.com/hytest-org/hytest/issues/443

Peer Reviewer Expectations

[x] General review of both code and text
[x] Suggest any additional text or code that a user may find helpful

Next steps

[ ] Address merge conflicts with main

After author has addressed next steps peer reviewer must approve request and then branch can be merge.

I have reviewer changes to this in PR https://github.com/hytest-org/hytest/pull/561.


Align OutOfBandManager.receive_invitation with other connection managers

Refactoring step before proposing changes in mediation connection
setup.

Align OutOfBandManager.receive_invitation signature with the
ConnectionManager.receive_invitation and
DIDXManager.receive_invitation

rename first parameter to invitation
change return type to ConnRecord and leave serialization work
for users of the manager

Serialize the received ConnRecord in
protocols.out_of_band.v1_0.routes

Adapt related tests. assert ConnRecord.deserialize(conn_rec) is dubious as a test assertion but boiled down to assert conn_rec is not None.

Use this refactoring to reduce branching in mediator connection
handling in conductor.py.

Signed-off-by: Clément Humbert<EMAIL_ADDRESS>

Codecov Report

Merging #1382 (ee301d7) into main (53878e7) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1382      +/-   ##
==========================================
- Coverage   95.28%   95.27%   -0.01%
==========================================
  Files         476      476
  Lines       29034    29025       -9
==========================================
- Hits        27664    27655       -9
  Misses       1370     1370


Improve handling of hyphenated words

We want to be a bit more intelligent when we see a trailing hyphen, maybe?
/**
 * really long line containing multi-part-word | just before threshold
 */

Right now we break before the m in multi-part-word, but maybe we want to break before the w in word?

So there is a problem that kind of blocks this, which is that the split function uses different parsing logic than the merge function so there is room for divergence. Technically I should wait to do this until that logic is unified.
However, for now, I think I want to mess around with tokenize.

https://www.compart.com/en/unicode/category/Pd

U002D -
U2010 ‐
U2011 ‑  (this is "non-breaking" so intentionally omitted)
U2013 –
UFE63 ﹣
UFF0D －

probably want to treat -- specially as its own token and not a joiner of words?

hyphenated merging is partly supported, but hyphenated split is not yet supported.

to support hyphenated splitting i first have to merge the block-overflow and line-overflow logic, then i have to unify the tokenize logic with findContentBreak. i think it is best to create separate issues for these. this issue is just about hyphen support in merge and it mostly works apart from the leaving extra whitespace in the next line, but that bug was already present and is yet another issue.


Dropbox user limit reached

When I tried to log on with dropbox, it said that the app user limit has been reached, and that the app developer needs to increase the user limit from the app console.  Hopefully this is as simple to fix as the notice makes it sound.

I see. The Dropbox account was in development phase. I have applied for production in Dropbox console and lets see what happens :)

I have changed from Dropbox to nw.js. You can download win-32 version of the game in the release section.


Need to write unit tests for ipaNumbersToUnicodeText, unicodeTextToIPANumbers

Need to test these two functions using unit tests.

Unit tests have been written for the character conversion functions as of commit: 7fef9baa14b892ab96f44dde7e2dc85026b057c5


Lint rule to indicate missing return staement when testing inside promise then or catch block.

Do you want to request a feature or report a bug?
Feature
What is the current behavior?
It is mentioned in the jest docs to return a promise when you want to test inside its then or catch block. In case, if a developer misses to add a return statement, then that expectation will not get executed and may result in test which is false positive.
What is the expected behavior?
A lint rule
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
jest: 21.2.1
node: 8.0.0
npm: 5.5.1
OS: Sierra (10.12.6)

@SimenB Given that https://github.com/facebook/jest/pull/4844#issuecomment-343069667 was closed, I guess we should close this issue also and then reopen it in https://github.com/jest-community/eslint-plugin-jest?


Laboratory work #1, Galkin Nikita - 19FPL2

Hello!
I'm sorry for missed deadline. I had some troubles with my local repository and because of this I recreated my fork and create new pull request.

Open another PR for the second lab


refactor-WIP add DropTableTaskPool for DROP_TABLE task

Proposed changes
Issue Number:
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[x] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


ats-metadata/A.17.IR22.IR23.ds.temporal

The TG Req 23 is not checked by the test because it requires that at least one date is given. Whereas the test is valid even if no date is given and only a timePeriod is given.
In the test method, change the statement “The test will fail if and only if all of the above checks evaluate to false” with “The test will fail if and only if at least one check among date of publication, date of last revision or date of creation doesn’t evaluate to true”.

Resolved by commit 01a52ee6fb99162e451e2e314a133f3248aac481


undeterministic behavior of capi

from ninja test, occasionally (1 time out of 10?), I can observe
[ RUN      ] nntrainer_capi_nnmodel.train_01_p
../test/tizen_capi/unittest_tizen_capi.cpp:306: Failure
      Expected: status
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/tizen_capi/unittest_tizen_capi.cpp:309: Failure
      Expected: status
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/tizen_capi/unittest_tizen_capi.cpp:312: Failure
      Expected: status
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/tizen_capi/unittest_tizen_capi.cpp:41: Failure
      Expected: status
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
-------

Sometimes, I get
[ RUN      ] nntrainer_ccapi.train_with_config_01_p
../test/ccapi/unittest_ccapi.cpp:166: Failure
      Expected: model->loadFromConfig(config_file)
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/ccapi/unittest_ccapi.cpp:167: Failure
      Expected: model->compile()
      Which is: -22
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/ccapi/unittest_ccapi.cpp:168: Failure
      Expected: model->initialize()
      Which is: -1073741822
To be equal to: ML_ERROR_NONE
      Which is: 0
../test/ccapi/unittest_ccapi.cpp:171: Failure
      Expected: model->getTrainingLoss()
      Which is: 0
To be equal to: 4.434051
../test/ccapi/unittest_ccapi.cpp:172: Failure
      Expected: model->getValidationLoss()
      Which is: 0
To be equal to: 2.9646113
../test/ccapi/unittest_ccapi.cpp:173: Failure
      Expected: model->getLoss()
      Which is: 0
To be equal to: 2.8036859
[  FAILED  ] nntrainer_ccapi.train_with_config_01_p (14 ms)
[ RUN      ] nntrainer_ccapi.train_dataset_with_file_01_p
#1/2 [ =                    ] 0% ( Training Loss: 2.38573 )
#1/2 [ =======              ] 31% ( Training Loss: 2.37778 )
#1/2 [ =============        ] 63% ( Training Loss: 2.29484 )
#1/2 - Training Loss: 2.35278 >> [ Accuracy: 6.25% - Validation Loss : 2.3133 ]
#2/2 [ =                    ] 0% ( Training Loss: 2.09096 )
#2/2 [ =======              ] 31% ( Training Loss: 2.23402 )
#2/2 [ =============        ] 63% ( Training Loss: 2.21693 )
#2/2 - Training Loss: 2.18064 >> [ Accuracy: 16.6667% - Validation Loss : 2.25438 ]
../test/ccapi/unittest_ccapi.cpp:221: Failure
      Expected: model->getTrainingLoss()
      Which is: 2.1806376
To be equal to: 2.1934659
../test/ccapi/unittest_ccapi.cpp:222: Failure
      Expected: model->getValidationLoss()
      Which is: 2.2543814
To be equal to: 2.2051108
../test/ccapi/unittest_ccapi.cpp:223: Failure
      Expected: model->getLoss()
      Which is: 2.2429025
To be equal to: 2.1751201
[  FAILED  ] nntrainer_ccapi.train_dataset_with_file_01_p (1283 ms)
[ RUN      ] nntrainer_ccapi.train_dataset_with_generator_01_p
#1/2 [          0           ]  ( Training Loss: 2.30068 )
#1/2 [          16          ]  ( Training Loss: 2.40239 )
#1/2 [          32          ]  ( Training Loss: 2.46805 )
#1/2 - Training Loss: 2.39037 >> [ Accuracy: 39.5833% - Validation Loss : 2.16501 ]
#2/2 [          0           ]  ( Training Loss: 2.11128 )
#2/2 [          16          ]  ( Training Loss: 2.2695 )
#2/2 [          32          ]  ( Training Loss: 2.18525 )
#2/2 - Training Loss: 2.18867 >> [ Accuracy: 60.4167% - Validation Loss : 1.96841 ]
../test/ccapi/unittest_ccapi.cpp:270: Failure
      Expected: model->getTrainingLoss()
      Which is: 2.1886747
To be equal to: 2.2109976
../test/ccapi/unittest_ccapi.cpp:271: Failure
      Expected: model->getValidationLoss()
      Which is: 1.9684099
To be equal to: 1.995334
../test/ccapi/unittest_ccapi.cpp:272: Failure
      Expected: model->getLoss()
      Which is: 1.9472635
To be equal to: 1.9843285
[  FAILED  ] nntrainer_ccapi.train_dataset_with_generator_01_p (1063 ms)

:octocat: cibot: Thank you for posting issue #868. The person in charge will reply soon.

:octocat: cibot: Thank you for posting issue #868. The person in charge will reply soon.

Is this with tizen or ubuntu, or does this happen with both?

Is this with tizen or ubuntu, or does this happen with both?

tested only on ubuntu with meson build && ninja test
only tizen api fails occasionally
will do the loop and report back

tested only on ubuntu with meson build && ninja test
only tizen api fails occasionally
will do the loop and report back

Could you try this? You are expected to observe it fails 100% after the first iteration,
build/test/tizen_capi/unittest_tizen_capi --gtest_repeat=5

[  FAILED  ] 3 tests, listed below:
[  FAILED  ] nntrainer_capi_nnmodel.train_01_p
[  FAILED  ] nntrainer_capi_nnmodel.train_with_file_01_p
[  FAILED  ] nntrainer_capi_nnmodel.train_with_generator_01_p

Could you try this? You are expected to observe it fails 100% after the first iteration,
build/test/tizen_capi/unittest_tizen_capi --gtest_repeat=5

[  FAILED  ] 3 tests, listed below:
[  FAILED  ] nntrainer_capi_nnmodel.train_01_p
[  FAILED  ] nntrainer_capi_nnmodel.train_with_file_01_p
[  FAILED  ] nntrainer_capi_nnmodel.train_with_generator_01_p

It shoud fail.
The unittests in tizen capi start with a random data based on a fixed seed always which makes NNTrainer deterministic in all its run. The function getSeed() function in util_func.cpp provides the same seed when called 5 times from two different processes.
However, with test/tizen_capi/unittest_tizen_capi --gtest_repeat=5, its 1 process running the unittest 5 times, and so when a uni test runs the 2nd time, the getSeed() can produce the same seed (which is intended behavior).
There are two workarounds -

We fix the init values and load it from file. But this will have to all the unittests where the outputs must be matched and this list will keep increasing.
Run the unittests in different processes by invoking test/tizen_capi/unittest_tizen_capi one by one.

Same argument applies for ccapi.

It shoud fail.
The unittests in tizen capi start with a random data based on a fixed seed always which makes NNTrainer deterministic in all its run. The function getSeed() function in util_func.cpp provides the same seed when called 5 times from two different processes.
However, with test/tizen_capi/unittest_tizen_capi --gtest_repeat=5, its 1 process running the unittest 5 times, and so when a uni test runs the 2nd time, the getSeed() can produce the same seed (which is intended behavior).
There are two workarounds -

We fix the init values and load it from file. But this will have to all the unittests where the outputs must be matched and this list will keep increasing.
Run the unittests in different processes by invoking test/tizen_capi/unittest_tizen_capi one by one.

Same argument applies for ccapi.

Acked, let's convert this to an issue then a bug

Acked, let's convert this to an issue then a bug

Actually, let's close this for now and if we have time deal with this. I think it's hard to say it's a bug or sth.

Actually, let's close this for now and if we have time deal with this. I think it's hard to say it's a bug or sth.

Actually, let's close this for now and if we have time deal with this. I think it's hard to say it's a bug or sth.

This is not a bug for the framework. Just a limitation of the way the unittest has been designed.

Actually, let's close this for now and if we have time deal with this. I think it's hard to say it's a bug or sth.

This is not a bug for the framework. Just a limitation of the way the unittest has been designed.


ViewModels and ABP in demo

Lee, I was watching your videos on YT, very nice I gave you a TU.
Can you explain what happens with a view model and where does it belong, for e.g. do I put it in the DTO object?
thanks

Sorry @papyr I didn't see this until just now.  ViewModels's are typically associated with an MVVM design pattern.  That pattern is generally more applicable to UI's with live 2-way databinding like Xamarin or UWP.  The ABP architecture generally just has models and DTO's.  Anything you might use a ViewModel for with ABP'd you'd use a DTO.  Does that help?


fix(client): SASS - show error messages instead of timeout

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.

Closes #39432

I don't know if this totally closes #39432. I was just fixing the issue the last comment in the issue had pointed out which was
that it wasn't displaying a better error message than the timeout default error in the console.
I also found out that the main cause for the timeout is happening in execute-challenge-saga.js inside of the previewChallengeSage function. I noticed that getting rid of the delay did help significantly but then was updating the console consistently and from my understanding is not the desired effect.
I just wanted to point out that's where the timeout is originating from and not sure if the this issue was being held open because of the error message needed to be handled better or if there still needs to be a fix for this.

@ojeytonwilliams
I have gone ahead and assigned this to you to help resolve the merge conflict in this PR due to recent Lerna changes and also give this a review while you are at it.
Thanks.

I am auditing PRs in limbo. @ojeytonwilliams mind taking a look?

I was going to clean this up, but I realised that the error message would have to be "Something went wrong, here's a hack to fix it...". That didn't feel great.  So, I went down the rabbit hole and fixed the bug.
@jacob-oreilly made a nice improvement, giving us a better error than 'timeout', so I'd be happy to accept that change.
Since this is a bit stale :cold_sweat: I'll sort that out myself.

Yep, it's there as a fallback in case something weird happens.


Adding a 2 step OTP verification for the signin/login form for user authentication

Adding a 2 step OTP verification for the signin/login form for user authentication

not needed at all , thanks


How to change the naming scheme of Files Tree?

Category
A feature request.
GitBook Editor

What is the current behavior?
If the article name is same although in different part, the article file is same!
For example:
1 GitHub @ github.md
1.1 record @ record.md
2 GitBook @ gitbook.md
2.1 record @ record.md

What is the desired behavior?
I hope GitBook Editor can rename article file automatically, just like this:
1 GitHub @ 1 github.md
1.1 record @ 1.1 record.md
2 GitBook @ 2 gitbook.md
2.1 record @ 2.1 record.md
2.1.1 this @ 2.1.1 this.md
And if I change the article name, the file name (include section number)  can be changed  automatically

Additional information

same

You can change it for an existing entry using: Left-Click then "Edit Pointer".
We'll try to improve the filename generation.

@SamyPesse I know this but it is boring to do in such way. Look forward to your improvement about this. Thank you.

@SamyPesse Hi! Is there any progress?


[Network] az network firewall create: Add validation for duplicate firewall name

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

Network

We should not change the default behavior. Recommend using the --on-exist argument with following options:

overwrite (default)
skip
error


Add CHANGELOG.md

Is your feature request related to a problem? Please describe.
Missing CHANGELOG.md
Describe the solution you'd like
Add CHANGELOG.md

Pull Requests:

https://github.com/Senzing/docker-hello-world/pull/11
https://github.com/Senzing/docker-hello-world/pull/13


Renders the texture based on the space component's size and render component's repeat

This allows the RenderComponent's Repeat to work properly. It's based on the size of the SpaceComponent relative to the size of the RenderComponent's Drawable * Scale. This closes #237
It adds a new TextureRepeat as the default, NoRepeat. If this is selected (or none are), it will draw the texture as if the View() were 0,0,1,1; just like it did before.
However, if another one is chosen it will now look at the SpaceComponent's size to get how big it should draw the the screen, as well as the results for the View. If the SpaceComponent is smaller, it'll only draw a portion of the texture; if it's larger it'll repeat the texture based on the selected Repeat.

Fixed ^_^ Thanks


Error HTTP/418: Operation aborted.

Describe the problem
Error HTTP/418: Operation aborted.
Bravo version
0.9.3 (0.9.8139.22766)
Tabular model
Power BI Desktop, import mode
Power BI
ower BI Desktop version
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots
No response
Anything else ?
No response

Hi @marahwa7d, I can't reproduce in my environment.
Could you please provide more details or steps to reproduce the issue? Thanks

Closing the issue for lack of response.


Need to install  npm everytime new project is created & run for the first time (per project)

Versions
[    ]  Visual Studio version  : Visual Studio 2017  Community/Enterprise 2017
[    ]  SPFx Generator version latest version
Expected or Desired Behavior
SPFx Visual Studio Project should launch Workbench without the need to install npm everytime new project is created & when we try to run the project for the first time.
Observed Behavior
Hi Vesa,
We have installed latest SPFx Visual Studio Template for visual studio 2017 (as described above 1.4.0 latest)
but when we run the project to launch the workbench..
We need to install gulp everytime the new project is created.. like npm install gulp
after it is done we need to fix
Error: Cannot find module '@ microsoft/sp-build-web'
after this is fixed we get the error
Error: listen EADDRINUSE
so after all command prompt instances are closed above error goes away..
How to avoid these errors
Error Log as follow
C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5>gulp package-solution
[10:11:40] Local gulp not found in ~\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5
[10:11:40] Try running: npm install gulp
C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5>install gulp
'install' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5>npm install gulp
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm notice created a lockfile as package-lock.json. You should commit this file.
<EMAIL_ADDRESS>added 270 packages in 35.049s
C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5>gulp package-solution
module.js:549
throw err;
^
Error: Cannot find module '@ microsoft/sp-build-web'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5\gulpfile.js:4:15)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5>npm install --save-dev

Most likely, you already have Node tools for Visual Studio installed and it's trying to use the wrong version. The SPFx Yeoman generator requires a more recent version than the one installed by default in VS. We have documented the workaround for this here:
https://github.com/SharePoint/sp-dev-fx-vs-extension/wiki/Node-tools-in-Visual-Studio-2017

**still getting this error
https://imagebin.ca/v/3vAV14pVta1i
Error: Cannot find module '@ microsoft/sp-build-web'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (C:\Users\jaiswati\Documents\Visual Studio 2017\Projects\MyWebPart5\MyWebPart5\gulpfile.js:4:15)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)


chore: Remove redundant internal properties from metadata and schema (DEV-3929)

DEV-3929

Only one question, why in this repo and not in dsp-meta? As far as I understand it, this repo will never be published again.

Only one question, why in this repo and not in dsp-meta? As far as I understand it, this repo will never be published again.

We're keeping this the source of truth until the new version is on prod. Moving these changes over to the new repo literally only takes a couple of seconds.

issue: When removing the ids we cannot reference the data anymore.
I would like to keep the __id for most of out data so these can be referenced in future. Also some Data is already reference within the data model, e.g. Person, Dataset ....

I only removed IDs for project, where they are not referenced anywhere

I only removed IDs for project, where they are not referenced anywhere

Yet... And maybe never will?
question Are there planned updated to the json data?
The problem with integrating your PR first is that we then cannot simply copy over the data but will have to change code in the new service, are you planning on backporting it to the dsp-meta?
I am ok with your changes but it potentially leads to a bit of a confusion. All depends on when we do the GoLive.

I only removed IDs for project, where they are not referenced anywhere

Yet... And maybe never will? Unless we decide to add linked data support again.

If you look at the project IDs, they were only dependent on the shortcode which we still have (except for the rome project, where I'm not sure why the ID was changed, but it should not have happened), so in the future we can still add those IDs if we want, or generate them on the fly as needed.

question Are there planned updated to the json data?

Sorry, I'm not sure I understand the question.

The problem with integrating your PR first is that we then cannot simply copy over the data but will have to change code in the new service, are you planning on backporting it to the dsp-meta?

Yes, I will of course adapt the BE to backport this (if it gets merged)

I am ok with your changes but it potentially leads to a bit of a confusion. All depends on when we do the GoLive.

I will wait with this until the GoLive is through, so we can be sure to avoid confusion.

If you look at the project IDs, they were only dependent on the shortcode which we still have (except for the rome project, where I'm not sure why the ID was changed, but it should not have happened), so in the future we can still add those IDs if we want, or generate them on the fly as needed.

AFAIU we will need the projects IDs for the "RDF and FAIR data assessment" project eventually.  These ids should stay the same as they currently are I would suppose. I feel like we need a stronger reason to remove them than just "because". Am I missing something?


Makefile build-web update

Make target 'build-web' is not needed for 'all',
the web part gets pull in through  use crate::APP;
trunk build does a cargo build, no need to do it twice.

For making merge possible (previously would the commit conflict with
another change in the Makefile)


Add "Copy URL" button as well as just "view"

I use separate browsers for general browsing and for work-related stuff. (It helps with managing logins and other extension config things).
When I do a git blame, the extension only gives me the option to "view" which opens a new (default) browser window.
It would be better if there was a button to "Copy URL" (or an option in the config to change "View" to this). Currently I have to "view", copy the URL from the address bar, open a new tab in the other browser, paste the URL, then close the default browser window. It's pretty cumbersome.
There are a number of cases where it's preferable to just copy the URL to clipboard rather than open a browser tab.
If I get chance to, I'll implement this myself. But, as it stands, I don't really know anything about VSCode's extension API.

Hey Tom!
Thank you for the feature request. It sounds like a great idea!
If you want to look into doing a pull request know that dealing with the clipboard is not supported by the VSCode API and we will need to use something like node-copy-paste (and its types).

Cool, I'll bear this in mind. I don't know when I'll have the chance to take a look, bit I'll try to get round to it soon.

Did some digging in the VSCode API and it looks like there is a Clipboard object that was added in a recent version.

I have started working on this and it will be in the next version. No planned date for release yet.

I implemented it a bit different than suggested:
I have added two new commands that can be bound to keyboard shortcuts or executed from the command panel. One will copy the tool URL to the clipboard and the other will copy the git commit hash to the clipboard.
I hope to release it tomorrow (2019-03-17).

This was released today in version 2.7.0.


Add Engine for Gpt4all

This will not work until my patch to the gpt4all gem is taken - https://github.com/jaigouk/gpt4all/pull/3
@jaigouk let me know if you have any question.

oh. i will check


Autocompletion outside of a project produces stack trace

See original issue on GitLab
In GitLab by [Gitlab user @jennis] on Mar 13, 2019, 16:29
Summary
I tried to autocomplete (I'm using a bash shell) bst show  within a directory which was not a BuildStream project and received the following stack trace :
 $ bst show Traceback (most recent call last):
  File "/home/jennis/python-virtual-environments/bst/bin/bst", line 8, in <module>
    sys.exit(cli())
  File "/home/jennis/python-virtual-environments/bst/lib/python3.6/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/home/jennis/Software/buildstream/buildstream/_frontend/cli.py", line 176, in override_main
    if main_bashcomplete(self, prog_name, partial(override_completions, args)):
  File "/home/jennis/Software/buildstream/buildstream/_frontend/complete.py", line 335, in main_bashcomplete
    do_complete(cmd, prog_name, override)
  File "/home/jennis/Software/buildstream/buildstream/_frontend/complete.py", line 325, in do_complete
    for item in get_choices(cli, prog_name, args, incomplete, override):
  File "/home/jennis/Software/buildstream/buildstream/_frontend/complete.py", line 294, in get_choices
    choices.extend(get_user_autocompletions(all_args, incomplete, ctx.command, cmd_param, override))
  File "/home/jennis/Software/buildstream/buildstream/_frontend/complete.py", line 243, in get_user_autocompletions
    incomplete=incomplete)
  File "/home/jennis/Software/buildstream/buildstream/_frontend/cli.py", line 163, in override_completions
    return complete_target(args, incomplete)
  File "/home/jennis/Software/buildstream/buildstream/_frontend/cli.py", line 91, in complete_target
    project_file = os.path.join(base_directory, project_conf)
  File "/usr/lib/python3.6/posixpath.py", line 80, in join
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Expected behaviour
There should not be a stack trace

In GitLab by [Gitlab user @tpollard] on Mar 14, 2019, 05:12
mentioned in merge request !1228

In GitLab by [Gitlab user @marge-bot123] on Mar 14, 2019, 06:36
closed via merge request !1228

In GitLab by [Gitlab user @marge-bot123] on Mar 14, 2019, 06:36
mentioned in commit 3c0aab96219c0c669daa964bd93abc384f699049


Question, how do you call a function after a dispatch returns

My dispatch makes an async call to get account data dispatch(fetchAccountView(this.props.params.accountId));
I have another function that needs to use that data, how do I trigger the next function once the dispatch completes?
I don't think passing the next function as a parameter to the fetchAccountView() action is the correct way.

Seems like the return value of dispatch is the return value of the action creator (this doesn't seem to be emphasized enough in the docs), so if your action creator returns a promise, then you can just add .then() after the dispatch
It's in the Async Actions section of the docs although
store.dispatch(fetchPosts('reactjs')).then(() =>
  console.log(store.getState());
);

This is correct.

Also, a PR amending the docs to better emphasize this is welcome.

I tried that but I think it's because my setup is slightly different, when .then() gets run the response hasn't come back yet.
In the example below I'm using a mock json file because the API isn't set up yet.
export function fetchAccountView(accountId) {
  	return function next(dispatch) {
	  	dispatch(requestAccountView());

	    return fetch('http://localhost:9999/public/mock/account_' + accountId + '.json')
	        .then(response => response.json())
	        .then(json =>

	        setTimeout(() => {
	        	dispatch(receiveAccountView(json));
	        }, 1000)
	    );
	};
}

export function fetchAccountView(accountId) {
    return function next(dispatch) {
        dispatch(requestAccountView());

        return fetch('http://localhost:9999/public/mock/account_' + accountId + '.json')
            .then(response => response.json())
            .then(json =>

            return new Promise(resolve => {
                resolve(dispatch(receiveAccountView(json)));
            }, 1000)
        );
    };
}

Currently the only way I know how to do this is to pass the next function as a callback but I feel this is a little dirty. The original example closely follows the AsyncActions doc so I was hoping there was a better way.
export function fetchAccountView(accountId, callback) {
  	return function next(dispatch) {
	  	dispatch(requestAccountView());

	    return fetch('http://localhost:9999/public/mock/account_' + accountId + '.json')
	        .then(response => response.json())
	        .then(json =>

	         setTimeout(() => {
	        	dispatch(receiveAccountView(json));
	        	if(typeof callback === 'function'){
	        		callback();
	        	}
	        }, 1000)
	    );
	};
}

I think you should review promise chaining...

@tkiethanom I wrote the solution just above.

export function fetchAccountView(accountId) {
    return function next(dispatch) {
        dispatch(requestAccountView());

        return fetch('http://localhost:9999/public/mock/account_' + accountId + '.json')
            .then(response => response.json())
            .then(json => new Promise(resolve => {      // <---- use the Promise constructor!
             setTimeout(() => {
                dispatch(receiveAccountView(json));
                resolve();   // <------- it lets you specify when stuff is done
            }, 1000)
        )};
    };
}

// later
store.dispatch(fetchAccountView(accountId)).then(() => {
  console.log('Woot! It is done.');
});

Nice that worked! Yes, I think I'm beginning to understand how Promises work now.


feat: add new ios events

Description

Adds new focus and blur events to iOS docs

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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


hotFix: Fix calculateBackoff redaclarring fun

Issue : #16

Thanks for the fix. Please, modify the changelog file.

@koladev32 can you check again please .


Update messages.md

@peeyushchoudharymsft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


feat(vscode): implement VSCode extension for .ask syntax highlighting

Closes #318

@mhagmajer , please take a look and comment.
This directory should be a separate VSCode project, so that you can easily run the extension when developing it.
Therefore I would keep the readme file here and link to it from the main README.md.
Of course, I will edit the readme, it's just a dummy template now.


Picker is not getting closed after clicking outside If it used on modal

Picker is not getting closed after clicking outside If it used on modal

Use StackBlitz to build an app and show the issue you mention about
I would close this until it is confirmed as an issue


Custom validation plugin API

Firstly I would like to say that I love Lotus validations. I have actually almost entirely replaced my ActiveModel validations with it, and it has been a dream to work with.
Since I use Lotus separately from the rest of the Lotus framework, there is one feature I really would love to have: the ability to create custom validations. Looking in the source, there are a finite number of accepted validation types in the API, specifically:
      VALIDATIONS = [
        :presence,
        :acceptance,
        :format,
        :inclusion,
        :exclusion,
        :confirmation,
        :size,
        :type,
        :nested
      ].freeze

I would like to be able to create my own validations, and append to this list. For example, say I wanted to validate the authenticity of a token, it would nice to be able to create my own validator for this:
attribute :jwt_token, authenticity: true

This would allow me to create my own logic to verify the authenticity of a token, and have it validated by Lotus.
Currently, to achieve this, I can do some somewhat nasty monkey-patching by overriding #valid?
def valid?
  super()
  validate_jwt_token_authenticity
  errors.empty?
end

def validate_jwt_token_authenticity
  if external_jwt_validation
    errors.add :jwt_token, Lotus::Validations::Error.new(:jwt_token, :presence, true, false)
  end
end

Would you guys accept a PR which created a way in which users could add custom validations to the validation set? I would like to add this functionality if possible :smile:
Thoughts? Concerns? Would love to hear what you guys think about this!

Ian

@ianks Hello and thanks for sparking this discussion. This is something that we want to do for sure before 1.0.
We didn't found an elegant/convenient way to describe custom validations, but we look for new ideas. Would you love to contribute on the brainstorming? Eg. how do you imagine the API? Thanks! :+1:
/cc @lotus/core-team

FWIW here's how you can do it in dry-validation already and it doesn't require any special API:
schema = Dry::Validation.Schema do
  configure do
    def is_it_awesome?(value)
      value == 'awesome'
    end
  end

  key(:text).required(:str?, :is_it_awesome?)
end

Notice that you compose custom predicates with built-in ones, so you can leverage that easily w/o any special code.


As a site editor, I want to import project data from multiple files without overwriting hugo content, so that I can import or update multiple groups of data at the same time.

dev notes

[ ] handle multiple files; ensure numeric ids don't collide
[ ] include branch label in page metadata when importing


Use earbuds and hats as currency

It would be nice, if the bot could use earbuds and hats as currency, instead of boring old refined metal and keys.
They are supported by backpack.tf according to /IGetCurrencies/v1. Why does the bot not support it then ?
Not supporting these currencies is very unfair, and that is the reason, I think we need this feature.
I will give anyone who helps the community and implements these popular currencies into the bot 50 keys as a reward.

I may be interested in pursuing this for you. Where can I reach out to you to discuss this more?

I think this is unnecessary.
The currency in earbuds and hats was introduced because back in the day, you can only trade 8 to 8 items per trade.
Nowadays, you can trade a lot of items in one trade (within the inventory limit), thus making this feature pretty much uncommon.
Closing this. Thanks for the suggestion btw.


Update Args data types of tf.ones and tf.zeros

At present as per documentation of tf.zeros and tf.ones, both APIs have argument shape which accepts "A list of integers, a tuple of integers, or a 1-D Tensor of type int32 ".
But its find out that when Boolean data types True, False passed to the shape argument it also accepts it and convert them into 1, 0 respectively and outputs correct results. Hence i am proposing to add a note under the 'shape' argument description that it also accepts boolean data types.
Attaching the gist also for referring the results.
Also fixes #60457

No, not useful.  Python bools are just another type of integer, so end up being converted to int32 automatically.  There is no valid semantic meaning to tf.ones(True), and we do not accept boolean tensors in general:  tf.ones(tf.constant(True, dtype=tf.bool)) fails.


[5.2] Disable failing test PackageDescription5LoadingTests.testSerializedDi…

…agnostics

@swift-ci smoke test

@swift-ci smoke test linux

@swift-ci smoke test linux

Thanks for the fix.  Is the reason the underlying test is failing understood, and tracked by a bug report?

Ah, no. We are still investigating this. I meant to close this PR, as we decided that disabling the test is not the right thing to do here.


Office hour #1

We will have an office hour next week on Thursday at XXX time.
The idea is to offer a time and place for people who are using mybinder.org and all its related tools and who have questions about them to meet. There will be several members of the binder team there too. The main meeting point will be the gitter channel (https://gitter.im/jupyterhub/binder) and maybe also a video chat. If you have questions about your Binderhub deployment, want to get involved with the projects or chat about ways to use it come and stop by.
This is an experiment for us as well, so what exactly will happen is up in the air.

How about the above as a starting point to publicise the office hours?

Both you and @willingc will be away next Thursday, so we should pick a better time!

Changed date to 22nd Feb. Feel free to edit the top comment with ideas about a time slot.

Office hours held and we even had some people asking questions!

@betatim That's awesome!


eni: Fix Cilium overallocating network interfaces

This fixes a bug where Cilium wrongly overestimated the amount of available
ENI IP addresses. This bug was introduced when we removed the primary
ENI IP address from the IPAM pool, but forgot to adjust the number of
addresses used to compare with the AWS instance limits.
This led to the operator overestimating the number of available IP
addresses by one. This in turn could lead to the operator first failing
to allocate more IPs (because it exceeded the limit) and then
unnecessarily creating a new ENI to fulfill the allocation request.
Fixes: 7c1bb3592c46 ("aws/ec2: Exclude primary ENI IP from IPAM pool")
Fixes: #15877

test-me-please

test-me-please

retest-1.16-netnext

retest-gke

retest-1.16-netnext

test-1.19-5.4

test-1.16-netnext

Marking this ready to merge, the CI failure is in the datapath which is not affected by this very ENI-specific PR. Created an issue for it #15998


Add OnEach bloq

It's convenient to have, say, a Hadamard on log N qubits. This bloq should do that. Would be nice to replace ^ with $^{\otimes n}$

@tanujkhattar can this go in?


require() of ES modules is not supported - netlify-cli deploy

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/is-promise/index.js
require() of ES modules is not supported.
require() of C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/is-promise/index.js from C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/run-async/index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/is-promise/index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/is-promise/package.json.
at Object. (C:/Users/frozensoil/AppData/Roaming/npm/node_modules/netlify-cli/node_modules/run-async/index.js:3:17)
- If the current behavior is a bug, please provide the steps to reproduce.
netlify deploy
- What is the expected behavior?
deploy normally on netlify
- Local Environment Information

netlify-cli/2.41.0 win32-x64 node-v12.16.2

Could fix by removing all node_modules from %AppData% and reinstalling netlify-cli.


Link porting instructions

Module migration and forward porting a module is not the necessarily same. I guess semantics are a bit mixed up, but to have clarity one needs to start somewhere on some point.
I prefer the most precise wording available, that's why I chose "forward porting".
Module migration, in the context of the Contributing.rst and other contexts, clearly refers to writing migration scripts.

Thanks!
In the long run the wiki should be moved here.


Add files via upload

Added assignment-3 file containing required code
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Replaced assignment-3 file with a file containing required code.
What did you learn from the changes you have made?
More on stat concepts, how to plot, bootstrapping, clustering, elbow calculations
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I tried to stay closer to the material described during the lecture.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Answering last question and interpretation some of the non code related questions
How were these changes tested?
In VScode
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[YES ] I can confirm that my changes are working as intended

A3 complete


Update event handler usage link [skip ci]

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

thanks for the contribution @marcelocarmona! Can you please sign the CLA?


Can I return to the previous position when I close a panel and reopen it

Could you explain the question in a little more detail?

I second this.  When we close a panel, it might be temporary, when we want to re-show, it doesn't return to its position in the flow.  The user has to re-position it manually.
If the previous container and stack are still available, it would be good if on the show, that it could return its previous position so the user isn't inconvenienced


FairOrderedMemoryAwareThreadPoolExecutor has severe memory leak under heavy load

Netty version 3.10.4 Final
As per your own documentation the order of events on the pipeline is not guaranteed which is definitely the case under heavy load. Therefore when WRITTEN_AMOUNT event comes after CHANNEL_CLOSED event, executor re-registers already closed channel in it's internal map again thus producing a memory leak as these channels will not be ever removed from the map and therefore never garbage collected. Using weak keys in the map helps a bit, but not much as cleanup is deferred and may not happen before OOME occurs. Also if the load comes in bursts of high intensity with dead pauses in between, stale reference queue will not be cleaned until next access. By that time it may be already too late as next burst will hijack the CPU bandwidth required for clean up. Reliance on GC to initiate further clean up is a bad idea.
The issue is easily reproduced with apache bench with high concurrency level (e.g. -c 1000 or so).
Reimplementing the doExecute() method the following way
    @Override
    protected void
        doExecute(Runnable task)
    {
        if(task instanceof ChannelEventRunnable)
        {
            ChannelEventRunnable run = (ChannelEventRunnable)task;
            SffEventTask prev, next = new SffEventTask(run);
            Channel channel = run.getEvent().getChannel();
            if(channel.getCloseFuture().isDone())                                   // remove the entry when the channel closes.
                prev = map.remove(channel.getId());
            else
                prev = map.put(channel.getId(), next);
            if(prev != null
            && uNext.compareAndSet(prev, null, next))
                return;
            task = next;
        }
        doUnorderedExecute(task);
    }

solves the problem (and does not require weak keys in the map).
On an unrelated note:
Using private- and package- scoped variables in open source code is an insult to your fellow developers who use and extend your code.
Instead of simply sub-classing your class and overriding a single method, I had to re-implement the whole class with all it's internals because you use private and package access for no reason. I will also have to do it again if you do any changes and watch manually for any incompatibilities instead of delegating it to the compiler. Please don't use private/package access. Do use protected instead.
Thanks, Oleg

@novos40 maybe you want to submit a PR that we can review and just merge to fix it ?
About package private and private scoped things... This is mainly to limit the "public apis" as otherwise it may become very hard to do changes later on without break the API.

@normanmaurer
I'm not sure if PR will do you any good as my implementation is rather different from yours in almost every aspect (i.e. coding style, name conventions, variable names, etc.). It would not merge easily if at all.
On the other hand, the idea of the fix is very simple: instead of pipeline events (which are unreliable in terms of their order), look for closeFuture to be done (which can happen only once) and essentially switch back to unfair mode as after the closure nobody would care about fairness any more. The snippet I've posted does just that.
Netty is a wonderful, very well designed library, so please don't get me wrong about my rant before. However, with all due respect, you would probably never think of (and much less design it for) ways how it can be used and how I use it in my project. For example, there is no leakage whatsoever of any netty's artifacts (e.g. import packages, classes etc) into other components. It is completely componetized and sealed off from the rest of the system (OSGi helps a lot with that). I've also extended it's capabilities quite a bit to accommodate fully dynamic nature of the project. All of this was possible mainly due to ability to extend your code (which I'm very grateful for). There are just a very few very annoying places like this when it's really impossible to do something in a simple way. I, personally, never use private/package access in my code unless I have a specific reason to do so, which I always document in the code. It's always easier simply to seal something off and never think that somebody would use you code in some way other that you made it for. I do believe that using privates is a sure sign of a sloppy and thoughtless programming and I know that you guys are better than that.
As per the protection of public APIs then it's a wrong tool for the job. APIs must be published and documented, everything else is implementation details which are subject to change and it must be made clear, that's it. In my case I don't really care about your APIs at all as it's all encapsulated in my own abstractions. In fact I, don't even use the concept of API as a software integration tool to begin with. I do care, however, about extensibility of your code to suit my needs and requirements (which are not API based)
Thanks again for a very useful library!
--Oleg

@novos40
“Therefore when WRITTEN_AMOUNT event comes after CHANNEL_CLOSED event”
In the same tcp connection, event is serially sent or received, why WRITTEN_AMOUNT event could comes after CHANNEL_CLOSED event？

Only external events are sent serially. Events generated by the system itself (e.g. WRITTEN_AMOUNT) can be sent out of order. Besides this only happens under heavy load when, apparently, thread generating this event got preempted for a long enough time to be "late". I don't know if it was changed/fixed in netty 4 as, I think, there is a message queue and assigned [same] thread to process it, but it is an observable behavior in netty 3.

Netty 3.x is end of life. So let me close this


Feature Request: Add Support for forceAuthn Flag for SAML IdPs

Hi Guys,
we are currently using UAA with a SAML IdP. We were trying to pass the forceAuthn flag as part of the login request, but it looks like UAA currently doesn’t support this.
From what I’ve you are using the Spring Security SAML extension for SAML SSO. The extension itself supports passing this flag, but UAA doesn’t seem to expose any way to configure it.
Would you please consider adding support for this flag?
Cheeers

recommend that you provide a PR, you can add your feature into
https://github.com/cloudfoundry/uaa/blob/develop/uaa/src/main/webapp/WEB-INF/spring/saml-providers.xml#L36


Add disks page description, change deploy btn

Changes

change style of add btn
add a description to disks page

Related Issues

#530
#531

Checklist

[x] Tests included
[x] Build pass
[ ] Documentation
[x] Code format and docstrings
[x] Screenshots/Video attached (needed for UI changes)

There's no environment for full vms right?

There's no environment for full vms right?

yes micro vm only have it


Consider disallowing the use of literal string as callback in Lodash functions

Description
Lodash allows the use of string literals to specify properties in methods like _.map. Although convenient, this can result in less maintainable code. We propose disallowing this practice in favor of explicit callback functions.
Rationale

Static Analysis: Improves code analysis and error detection.
Type Safety: Callback functions allow for better type checking.

Example
// ❌ Incorrect
_.map(students, "age")

// ✅ Correct
_.map(students, student => student.age)

We may make use of this rule:
https://github.com/wix-incubator/eslint-plugin-lodash/blob/master/docs/rules/prop-shorthand.md#property-shorthand

For similar reason, the lodash/matches-shorthand rule may also be considered:
https://github.com/wix-incubator/eslint-plugin-lodash/blob/master/docs/rules/matches-shorthand.md

For similar reason, the lodash/matches-shorthand rule may also be considered<EMAIL_ADDRESS>
The matches shorthand is type-safe and can be analyzed statically, so, I don't think we need to consider this rule.


note somewhere that macos & linux cargo produce different .wasm output & hence different kinode processes

https://book.kinode.org/kit/build.html#--reproducible


Mandatory fields sign

Closes https://github.com/apinf/platform/issues/1171

@nnn Not bad!
But Sing up form doesn't have the star

@marla-singer bypass:
.at-pwd-form label:after {
  content: '*';
  font-size: 0.8em;
  color: @brand-danger;
}

@nnn Merge it


feat: redefine data source protos

close vegaprotocol/vega#5714
This PR redefines the proto types related to oracles following the logic presented in https://github.com/vegaprotocol/specs/pull/1161
changes introduced:

For all external data sources - we care about pubkeys and filters -> so we apply same properties for all (this follows the logic in https://github.com/vegaprotocol/specs/pull/1161)
=> Everywhere where we have oracle definitions we use the generic data source type instead of custom oracle type

There is an option where we can embed generic data type into the oracle type - if we really need specific properties for oracles. Same of course can be applied further for different groups of oracles (ETH, or not), bridges as a separate group of external sources, whatever we would need.

The idea behind the changes is:

use a way as straight forward as possible (doing the correct thing is not always the simplest change)
do not involve the design with any workaround -> if a workaround is needed - isolate it from the design, so when it needs to be removed - it will not harm the idea.
have generic types on early stage (like now) ad build up on them if you have to

Just the commands might need updating relative to these changes.

@jeremyletang , Addressed all of your comments and rebased with develop

Those changes looks good to me @AnExsomnis, let's move them over onto the vega repo on a new PR please. thanks.

closing as done in:

https://github.com/vegaprotocol/vega/pull/5980


Tutorial

Hello!
Thank you for the amazing tool you are sharing with the world for free, you are doing an amazing job!
The only problem is, there are no tutorials / guides at ALL on how to use the tool. If you do not have coding knowledge, it will be almost impossible to use. There is a short documentation on how to install it, but no documentation for example; TOR browser support, .onion sites support. How to configure it, how to build a new config, etc. Please take this in consideration, a lot of people cannot really use it because of leak of knowledge.
Thank you.

Thanks!
I will check with the documentation department to see if there is still anyone working there.
Feel free to contribute if you want.

I will be more then happy to contribute, write down tutorials, video tutorials, but I first need to personally know how to use it / create configs for any website, make it work under TOR .onion domains, etc.

Any update ?

It is opensource. Study code and find out - this is the main point of why we are here.

If anyone needs an infograph tutorial..
https://github.com/jeretc/evilginx2-infograph


How consumers works?

Kafka consumers are pull-based so  at first it seems to be a mismatch between this and the  event-based approach like the one that Node.js takes.
From Kafka documentation:

The Kafka consumer works by issuing "fetch" requests to the brokers leading the partitions it wants to consume.

You  have taken an event-based approach for this, like if messages were events.

By default, we will consume messages from the last committed offset of the current group
onMessage: Function, callback when new message comes

Example:
consumer.on('message', function (message) {
   console.log(message);
});

My question is how you been able to translate the kafka fetch style to the node event style. Something like an libuv event thread polling to kafka topics?

There's a setImmediate call made after the fetch that kicks off the next fetch.


Can I use o3d.t... methods?

It saids can't use o3d.t... methods.
Is this possible?

 See https://github.com/kewlbear/Open3D/blob/355bad8759649efd063be8221a4ec2d7c5bc0e2e/ios/config.sh#L11.