Allow use of custom HttpRequestExecutor in HttpClient

Hello, we are currently using the library to make run jobs in our production environment. We need to collect metrics around requests to the Databricks API and we use a custom class extending HttpRequestExecutor to accomplish this right now. We had to implement our own extension of the DatabricksRestClientImpl in order to pass in our custom HttpRequestExecutor to the HttpClientBuilder which led to a lot of duplicated code with the AbstractDatabricksRestClient#initClient method since the builder is not accessible before initialization. We would like a way to pass this executor to the builder are willing to contribute to the project to make it happen.
My first thought was to add this executor to the DatabricksServiceFactory.Builder class so that it could be set in the initClient method, but it does not seem to fit the pattern of all the values in the builder being primitives or strings. Right now I do not see a pattern for passing custom parameters to the HttpClientBuilder. Is there a preferred way to accomplish this that I could work on?
Here is a snippet of the workaround we have implemented:
    public CustomDatabricksRestClient(DatabricksServiceFactory.Builder builder, ...) {
        super(builder);
        initClientWithExecutor(builder, ...);
    }

    @Override
    protected void initClient(DatabricksServiceFactory.Builder builder) {
        // No-op init
    }

    private void initClientWithExecutor(DatabricksServiceFactory.Builder builder, ...) {
        CustomHttpRequestExecutor customHttpRequestExecutor = new CustomHttpRequestExecutor(...);

        HttpClientBuilder clientBuilder = HttpClients.custom().useSystemProperties()
                .setRetryHandler(retryHandler)
                .setServiceUnavailableRetryStrategy(retryStrategy)
                .setRequestExecutor(customHttpRequestExecutor)
                .setDefaultRequestConfig(createRequestConfig(builder));

        List<Header> headers = new ArrayList<>();
        if (StringUtils.isNotEmpty(builder.getToken())) {
            Header authHeader = new BasicHeader("Authorization", String.format("Bearer %s", builder.getToken()));
            headers.add(authHeader);
        }

        String userAgent = builder.getUserAgent();
        if (userAgent != null && userAgent.length() > 0) {
            Header userAgentHeader = new BasicHeader("User-Agent", userAgent);
            headers.add(userAgentHeader);
        }

        if (!headers.isEmpty()) {
            clientBuilder.setDefaultHeaders(headers);
        }

        try {
            SSLContext ctx = SSLContext.getDefault();
            // Allow TLSv1.2 protocol only
            SSLConnectionSocketFactory sslsf = new SSLConnectionSocketFactory(
                    ctx,
                    new String[]{"TLSv1.2"},
                    null,
                    SSLConnectionSocketFactory.getDefaultHostnameVerifier());
            clientBuilder = clientBuilder.setSSLSocketFactory(sslsf);
        } catch (Exception e) {
            _log.error("", e);
        }

        client = clientBuilder.build(); //CloseableHttpClient

        url = String.format("https://%s/api/%s", host, apiVersion);
        mapper = new ObjectMapper().setSerializationInclusion(JsonInclude.Include.NON_DEFAULT);
    }

hey @travisemichael, first apologies for the delay in getting back to you.
I think I understand the issue and why this would be useful functionality to have.
What do you think about having it so that an HttpClientBuilder can be passed in? The pros of this is that it would allow people to do a lot of other customization including modifying the HttpExecutor.

hey @travisemichael I took a stab at trying to handle your request above as well as allowing for more configuration if needed. Here is the PR: https://github.com/edmunds/databricks-rest-client/pull/80
Would this be too backwards incompatible for your needs?

That looks like it would work for our case. The expectation is that we would extend the HttpClientBuilderFactory and override createClientBuilder to chain our custom builder parameters after calling createDefaultClientBuilder if understand correctly.
The downsides you're talking about would be that the implementation could overwrite params such as the headers/creds etc. right? I don't see any way around that except parameterizing everything that someone would want to set on the HttpClientBuilder object but I haven't put that much thought into it.
For backwards compatibility, I'm not too concerned over bumping the version and making the necessary changes.

ok its merged in, tentatively closing this issue. Feel free to re-open if needed


[production] [bug] "Invalid Date" displayed for View-only Links

Steps

Go to a private project.
Create a view-only link.

Expected
View-only link creation date will be displayed.
Actual
"Invalid date" is displayed.

This happens for newly created projects with newly created view-only links, view-only links created long ago to projects created long ago, and on newly created view-only links to projects created long ago.

I am seeing this as well.
Perhaps @nanchen47 will see the cause while looking at a different view-only link issue.

The pr is already merged and deployed on production.


[ENH] Improve efficiency of Histogram Distribution

Describe the maintenance issue

The Histogram distribution implemented in #382, #335  takes 2 parameters bins and bin_mass which consists of ragged arrays in the 2D case. These ragged arrays are stored in a list as it is not possible to vectorize the ragged inputs easily. One way to vectorize them and make all of them the same shape is to pad them with 0s in case of bin_mass and pad bins with -np.inf and np.inf on the left and right side to make them equal in length.
But the problem with this approach of vectorizing is that it takes longer time than the current approach, as although the running times of the methods mean,var per se are improved by a factor of 5 but the time to pad the inputs in the above mentioned way itself is taking a lot of time which is giving worse efficiency results overall than the current approach.
Refer here to know more about the benchmarking of the Histogram Distribution.
The idea of taking the input from the user itself in this vectorized way with all the inputs padded with 0s and infs does not seem to be a very good idea as this would be very inconvenient for the user to pad them manually in cases where the lengths of the inputs vary by a big number and this would also not allow for tuple inputs in cases where the bins are of equal widths.
The Histogram Distribution inherits from the _BaseArrayDistribution which inherits the BaseDistribution with some overriding of private functions to accomodate the array distribuitons. Thoughts on ways of merging this with BaseDistribution without having to create a separate base class for arrays is also appreciated.

Indeed - there is also the open question how the parameters should be encoded, as an "inefficient" representation may mask any benfits from vectorization.
This is an open question, I would guess that pd.DataFrame with nested row index might be a way to go, since we can make use of groupby etc.
Less of a priority for now though, so parking thoughts in this issue.


the unlocked activation key returns "ERROR: Expired activation key"

I employ the unlocked activation key to install mujoco200 on my school's HPC(High Performance Computing). However, it returns "ERROR: Expired activation key". This problem is quite strange because I am sure the right activation key is used. The same problem for installing mjpro150. Could you please help me?

Are you using the activation file from https://roboti.us/license.html ?
Separately, do you have a specific reason for using these legacy versions of MuJoCo?

Are you using the activation file from https://roboti.us/license.html ?
Separately, do you have a specific reason for using these legacy versions of MuJoCo?

Thanks. Yes, of course. I downloaded the activation file from the url as you provide. This is quite a strange problem because this activation works on my own computer but not the HPC of school.
The reason for using the legacy version is that my previous experiments were run with the old version. I will test whether the new Mujoco work for me.

Are you able to double check if the clock on the cluster is set correctly?

@saran-t, Thanks Saran. I have tested the new version, and it works. For the system clock, I run command "date" and receive correct time. For the hardware clock, I have written to the cluster administrators to check.

Thanks for the info. We don't have visibility on how exactly the clock is being used in mj_activate as all license management code has been removed from the MuJoCo codebase by Roboti before it has been transferred to us. We will follow up with Roboti on this.

The summary of our discussion with Roboti is that MuJoCo prior to 2.1.0 had some logic to detect tampering with licenses. This included various check to detect the system clock being set to an old date, including detecting files with modification timestamps in the future.
This is no longer an issue with new versions of MuJoCo, of course.


Enhancement: extend command definition with option set

In many commands we have a set of options where we require users to specify value for one of them, eg. in aad app get, we require user to specify appId, objectId or name. In all such cases, we implement validation logic in commands that checks if one of the options has been specified. We also check if only one of these options has been specified and not multiple. We repeat the validation for such options set in all commands. Instead, we should extend the command definition to allow commands to specify option sets. We should then extend the central validation logic, where we check if all required options have been specified, with checking if one option for each option set contains a value and return a relevant error message if that's not the case.
class Command {
  public optionSets(): string[][] | undefined {
    return;
  }
}

class AadAppGetCommand extends Command {
  public optionSets(): string[][] | undefined {
    return [
      ['appId', 'objectId', 'name']
    ];
  }
}

In the central validation logic we enumerate option sets and check if for each set, one of the specified options has a value. If neither of the options in a set has a value, we return error like Specify either ${options.join(', ')}. If more than one options have a value, we return error like Specify either ${options.join(', ')} but not multiple.
Once we have this logic, we should identify and refactor all commands to define their option sets and remove the obsolete validation logic and tests.

That will be an excellent enhancement. Code will be super cleaner with introduction of this centralized validation 🔥

@waldekmastykarz happy to try and work on this, please assign it to me.

@vipulkelkar all yours 🚀

Hey @vipulkelkar, in #2996 @zhenyasav mentioned zod as a possible alternative to manual validation that we're doing now. I wonder if it could help us with validation option sets as well. Perhaps you could have a look at it?

@waldekmastykarz sure, i will take a look at it

@vipulkelkar, when you're looking at zod, you could take as an example the validation logic of aad app add, which has a nice combination or option sets, enums, dependent property and optional properties with specific format (JSON)

haven't been able to dig deeper into this, here is the initial high level analysis. I was looking at a way to implement oneOf/anyOf type validation and came across this thread which led to 'Yup'
The dependent property validation, enum etc are available in Yup, below is the sample code (partially implemented) for the aad app add command

let schema = yup.object().shape({
               manifest:yup.string()
               .when('appname',{
                            is:(appname:string) => appname == null,
                            then:yup.string().required()
               }),
               appname:yup.string()
                              .when('manifest',{
                                             is:(manifest:string) => manifest == null,
                                             then:yup.string().required()
                              }),
               redirecturis:yup.string(),
               platform:yup.mixed().oneOf(['spa', 'web', 'publicClient'])
                              .when('redirecturis',{
                                             is:(redirecturis:string) => redirecturis && redirecturis.length > 0,
                                             then:yup.string().required()
                              }),
               aadAppScopeConsentBy:yup.mixed().oneOf(['admins', 'adminsAndUsers']),
               scopeName:yup.string(),
               uri:yup.string()
                              .when('scopename',{
                                             is:(scopename:string) => scopename && scopename.length > 0,
                                             then:yup.string().required()
                              }),
               scopeAdminConsentDescription:yup.string()
                              .when('scopename',{
                                             is:(scopename:string) => scopename && scopename.length > 0,
                                             then:yup.string().required()
                              }),
               scopeAdminConsentDisplayName:yup.string()
                              .when('scopename',{
                                             is:(scopename:string) => scopename && scopename.length > 0,
                                             then:yup.string().required()
                              }),

},[['manifest','appname']])

To get some clarification, are we looking at defining the schemas like above on each command or we implement separate validations centrally for 'anyOf', 'oneOf', 'enums' , then pass the arrays for each kind like you have proposed and then validate if the 'keys' on the options object

Thanks for looking into it @vipulkelkar. When I heard of zod and based on the few examples I've seen, I had hoped it would let us simplify validation. Looking at the above sample, it doesn't really feel like a simplification. I wonder if there are other ways to handle it. If not, then we could drop the whole idea for now and implement option sets like we speced initially.

this seems like a situation where you're actually looking for a union of multiple kinds of shapes that can be passed into a function. One of the benefits of this approach is that you can obtain typescript types from your validation schemas that are not redundant with it (i.e. you make one expression, and you get both a validator and a type which are guaranteed to be aligned).
Expressing some of the shape's fields as not required depending on what keys are present the way it's done above doesn't make it easier to infer a type, I wonder how much it makes sense to try to re-express this as a union - that way you'll get all the benefits it seems.

Expressing some of the shape's fields as not required depending on what keys are present the way it's done above doesn't make it easier to infer a type, I wonder how much it makes sense to try to re-express this as a union - that way you'll get all the benefits it seems.

Do you have an example of how that would look like @zhenyasav?

Expressing some of the shape's fields as not required depending on what keys are present the way it's done above doesn't make it easier to infer a type, I wonder how much it makes sense to try to re-express this as a union - that way you'll get all the benefits it seems.

@zhenyasav  Pardon me but I don't follow, an example would help understand a little better. For both Zod and Yup, the checks for dependent fields/any one field being required don't seem to necessarily reduce the code. But I may be missing something.

@vipulkelkar for now, let's use our original idea as we outlined in the spec. We can revisit the schema-based validation in the future as it would be a larger refactoring.


bug(material/table): Row of sticky column is transparent on hover in custom dark theme

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
14.2.7
Description

https://stackblitz.com/edit/angular-nhbxgc?file=src/app/table-sticky-columns-example.html
Reproduction
Steps to reproduce:

Custom material dark theme is applied
In table that has a sticky column, try horizontal scrolling.
The hover row in the sticky column is transparent so other columns show beneath it.

Expected Behavior
I expect the hovered row of the sticky column to not be transparent in a custom dark theme.
Actual Behavior
The hovered row of the sticky column is transparent in a custom dark theme.
Environment

Angular: 15.2.1
CDK/Material: 15.2.1
Browser(s): Chrome, Firefox
Operating System (e.g. Windows, macOS, Ubuntu): Windows

note that there's another bug which appears in that GIF, where the hover styling for table rows isn't getting applied when using a custom material light theme. Related issue: https://github.com/angular/components/issues/26203

This is still an issue in v16.1.7 and can also effect sticky footer rows. It can also be reproduced on the material docs site (material.angular.io) by switching back and forth between Deep Purple & Amber and any other theme a couple times. This causes table row backgrounds to become slightly transparent on mouseover.


App crash

I have integrated the chuck library as indicated in the documentation however the app is crashing as soon it is fired up. The logs aren't much help either as they don't show an explicit crash.
The only way to stop the crash is to remove the compile 'com.readystatesoftware.chuck from build.gradle. Commenting the code to add an interceptor doesn't help either. Only removing the library from the compile options works to successfully run the app.
Any suggestions on what I should be a on a lookout for, maybe popular libraries?

Do you have more than one process in your app?

No. Just the one.

I have the same problem. But I try to use Chuck in the library , maybe that is a problem ?

I am using Chuck as a library only, added in my Android Studio project via gradle. Is there any other way to use it?


scan() doesn't handle tabs as whitespace in struct tag .... field

I formatted my options like below using tabs and it took a bit to figure out what I did wrong. The scan code only skips spaces for whitespace when parsing the struct tag. Support for tabs (or any whitespace?) in the struct tags would be nice. Let me know if you want a pull request or take the snippet below.
var opts struct {
	Verbose          bool   `short:"v"	long:"verbose" 															description:"Show verbose debug information"`
	Local            bool   `short:"l"	long:"local" 															description:"execute locally"`
	Port             int    `short:"p"	long:"port" 		default:"80"  										description:"port to listen for HTTP"`
}

func (x *multiTag) scan() (map[string][]string, error) {

...
		// Skip whitespace
		for i < len(v) && (v[i] == ' ' || v[i] == '\t') {
			i++
		}

go-flags follows the go tags spec which does not allow newlines or tabs in tags. I prefer for go-flags to be up to spec so it's easier to explain.

The spec seems to indicate that any string_lit is a valid struct tag. It compiles and doesn't generate any lint or vet warnings.  Is there somewhere else this is spec'd?
https://golang.org/ref/spec#Struct_types
StructType     = "struct" "{" { FieldDecl ";" } "}" .
FieldDecl      = (IdentifierList Type | AnonymousField) [ Tag ] .
AnonymousField = [ "*" ] TypeName .
Tag            = string_lit .

https://golang.org/ref/spec#string_lit
string_lit             = raw_string_lit | interpreted_string_lit .
raw_string_lit         = "`" { unicode_char | newline } "`" .
interpreted_string_lit = `"` { unicode_value | byte_value } `"` .

Sorry, I should have been more precise. I was talking about the key/value tag parsing done by the go stdlib: https://golang.org/pkg/reflect/#StructTag


Support AF_PACKET socket family if available

Add an example for packet socket too.
Signed-off-by: Kirill K. Smirnov<EMAIL_ADDRESS>

Thanks for working on this!


error  Generator.afterGenerate (node_modules/@nuxt/generator/dist/generator.js:168:43)

Version
v2.10.0
Reproduction link
https://nolinks
Steps to reproduce
https://bug.nuxtjs.org/
Have the same issue as well. Just install 2.10.0 and the problem started acting. Node v10.15.3, and all projects with different nuxt version will have this error message.
What is expected ?
no errors during compile
What is actually happening?
stop here

This bug report is available on Nuxt community (#c9863)

please also refer to report https://github.com/nuxt/nuxt.js/issues/6513

I encountered the same problem after updating nuxt to 2.10.0 on a project. Then afterGenerate / renderroute problem was triggered on each build in spa mode, and for ALL my local 's nuxtjs projects in spa mode...
I finally solved this by running a "npm clean cache --force" and npm install.
Looks like update to 2.10.0 did corrupt my npm cache.. Hope this helps

Try to delete lock file and node modules and reinstall. If the error still happens - please provide a reproduction repo with lock file where this error happens for you.

I already tried, but deleting lock file and node modules did not work for me, the solution was to use the "npm clean cache"

i suggest to use yarn, it has less of this kind of problems

i suggest to use yarn, it has less of this kind of problems

yes i confirm, i tried a fresh yarn install and added all my dependencies to test and everything was fine, that's how i found that my package and scripts was correct but, the npm cache was corrupted

I tried with yarn, same error!
ERROR   /dashboard

TypeError: Cannot read property 'renderRoute' of undefined
    at Generator.generateRoute (/frontend/node_modules/@nuxt/generator/dist/generator.js:222:42)
    at Promise.all.routes.splice.map (/frontend/node_modules/@nuxt/generator/dist/generator.js:120:24)

@vinayakkulkarni please provide a full reproduction with lock files

@aldarund : #6519

Yes same with yarn, removed * nodes-modules and package-lock.json, did a clean yarn install, and when running yarn run build, I get exactly the same error.

Instead 'npm run build' use 'npm run generate' - for me works fine

run generate works but we still need to resolve the build issue.

related #6519

Tested with both yarn and npm (deleted node_modules and lock file) build doesn't work

@carlosesquivel-katoo if your issue different from https://github.com/nuxt/nuxt.js/issues/6519 please provide a full reproduction

It's probably the same issue as #6519 @aldarund

#6514 can be closed after this fix is deployed: https://github.com/nuxt/nuxt.js/commit/136777de1d7924f052c803c6397530de80bdea50

It's probably the same issue as #6519 @aldarund

It's the same, just emphasizing that using yarn or npm was the same. I'll wait for the fix to be deployed.
Thanks!!!

Duplicate of https://github.com/nuxt/nuxt.js/issues/6519


Unicode issue

When using
await this.client.set('api:cities', '.', '{"Mingá": {"id": "18", "name": "Mingá"}}');

in Redis I got this
{"Ming\u00c3\u00a1":{"id":"18","name":"Ming\u00c3\u00a1"}}

When using the redis-cli --raw I can handle keys with unicode, so I wondering how to make the set function to insert 'Mingá' as a key and not "Ming\u00c3\u00a1"??

@hadnet Hi, Thanks for the issue. I will see if I can do something regarding the problem.

https://github.com/luin/ioredis/issues/1427

@hadnet Seems like this is not too possible to adjust, but you could decode the result for your usages.
Look at here for an example: https://github.com/luin/ioredis/issues/1427#issuecomment-912124347


Update 1.5 HAPI docs to handle cf hardcode changes

[#163744682]
Signed-off-by: Huan Wang<EMAIL_ADDRESS>

Thank you, @iplay88keys.
I made a tiny change to make the link closer match out linking style convention. See Formatting Cross-References in our docs wiki.
Also, I feel that the note would be better if the impact to the user was moved to the first sentence: "These endpoints only support deployment names beginning with cf." But I didn't make that change.

@mlimonczenko Thanks for doing that! If you believe it would be better to make that change, please do!


You don't seem to have a generator ... installed

Hiya! So you think it's broken or missing a feature eh?
Welllllll, it just might be.  Do me a favor and check the following.

[X] Issue does not already exist
Identify exactly what aspect your issue is about

[ ] ignite base application
[x] ignite the cli
[ ] ignite generated code

Also, for the quickest assistance please run ignite doctor and paste in
everything (including the lines with 3 backticks).
So, I can't start a new project. I have followed the instructions to install Ignite with npm install -g react-native-ignite. But when I run ignite new Secretary it tells med You don't seem to have a generator with the name react-native-ignite installed..
~/Development/ReactNative
▶ npm install react-native-ignite -g
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
/Users/nonameolsson/.nvm/versions/node/v6.6.0/bin/ignite -> /Users/nonameolsson/.nvm/versions/node/v6.6.0/lib/node_modules/react-native-ignite/index.js

><EMAIL_ADDRESS>postinstall /Users/nonameolsson/.nvm/versions/node/v6.6.0/lib/node_modules/react-native-ignite
> npm i -g generator-react-native-ignite

/Users/nonameolsson/.nvm/versions/node/v6.6.0/lib
└──<EMAIL_ADDRESS>
/Users/nonameolsson/.nvm/versions/node/v6.6.0/lib
└──<EMAIL_ADDRESS>

~/Development/ReactNative
▶ ignite new Secretary
🔥 Setting Secretary on FIRE! 🔥
Error react-native-ignite Secretary

You don't seem to have a generator with the name react-native-ignite installed.
You can see available generators with npm search yeoman-generator and then install them with npm install [name].
To see the 4 registered generators run yo with the `--help` option.

~/Development/ReactNative
▶ ignite doctor

Computer
  Platform: darwin

Ignite
  Version: 1.12.0
  Path: /Users/nonameolsson/.nvm/versions/node/v6.6.0/bin/ignite

Node
  Version: v6.6.0
  Path: /Users/nonameolsson/.nvm/versions/node/v6.6.0/bin/node

NPM
  Version: 4.0.5
  Path: /Users/nonameolsson/.nvm/versions/node/v6.6.0/bin/npm

Yeoman
  Version: 1.7.0

React Native CLI
  Version: 2.0.1

App
  React Native Version: ¯\_(ツ)_/¯

~/Development/ReactNative
▶

Any comments? I still have this issue, and can't manage to get started with ignite. I have also installed:
npm install -g generator-react-native-ignite.
What am I missing here? I really want to get started with Ignite :)

@nonameolsson Looks like this might be an issue with npm installs on your system. Take a look at https://github.com/yeoman/yo/issues/403 for actions you can take to fix the problem.

Thank you @derekgreenberg! That worked.


Update go libraries to OPEV-0014, OPEV-0015 and spec

This pull request updates the go libraries to implement the first revision to the OpenVEX spec:

Implements OPEV-0014: Expansion of the VEX Product Field
Implements OPEV-0015: Expansion of the Vulnerability Field
Minor revisions to the spec to meet final VEX-WG Minimum Requirements for VEX document (https://github.com/openvex/spec/pull/25)

@luhring thanks for the review. I've gone through the comments on the PR, I've also noticed that this PR was referencing v0.1.0 of the spec while the rest of the PRs are targeting v0.2.0. I've changed this one to refer to the new version of the spec as  v0.2.0 to match the rest of PRs implementing the spec changes. PTAL!

Thanks everybody!


[5.2] Backport of #2543 for Swift 5.2 branch

Per discussion: let’s make any further changes on master. Good to merge once tests pass.

@swift-ci test


chore(master): release 2.3.1

:robot: I have created a release beep boop
2.3.1 (2023-05-09)
Bug Fixes

player: Player.connected being False sometimes (#73) (a7a9b8d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ooliver1/mafic/releases/tag/v2.3.1 :sunflower:


Implement multitenancy for windows

This change allows containers from different vnets to reside in a VM that belongs to a completely different infra-vnet. The isolation is achieved using vlan.
Multitenancy and snatonhost can be enabled using flags in azure conflist file. When multitenancy is enabled, CNI depends on CNS to get the goal state for the network container which includes the allocated IP.

@ashvindeodhar Please run a regression test on a single-tenancy environment. Thanks!


[Feature Request] Escrow

Feature Request
Describe the Feature Request
Implement an escrow module to holds funds designated for a payee until they  withdraw them.
reference: https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/escrow/Escrow.sol

Describe Preferred Solution

Describe Alternatives

Related Code

Additional Context

If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)

work


DataSource Upsert/Delete Block

On the recent documentation, I see that you can delete and create documents using the API, however I'd like to see this in action with DataSources

Create & Delete DataSource Block

Just to be super clear. You'd like to have the ability to upsert / delete a document from a Dust app?

Yes.

Closing for now, as Data Source are really though of as "source of data" that should be managed outside of the execution loop of an app.


[FEATURE] Add close old issue bot

Description
"By incorporating a bot that automatically closes old and inactive issues, we can ensure better issue management and keep the project organized."
"The bot's ability to identify and close outdated issues will streamline the issue tracking process, allowing the project team to focus on active and relevant tasks."
"Implementing an automated closing bot will help maintain a clean and up-to-date issue tracker, improving overall project efficiency and ensuring that active issues receive proper attention."
Screenshots
No response
Additional information
No response

How are you planning to do this?

@KOMALDEWNANI there is bot i will just integrate that
and you can let me know how many days old issues it should close
usually it closes 30 days or more old issue
but it is customizable as per your need

Ok, start working on it. 30 days time is fair enough


Increase build number to trigger another build

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

energy_tot_full

@conda-forge-admin, please rerender


Shopping App Updates

Updating 7 files within the "Optional: Sample Project: The Shopping Application" project.

Pulling is unnecessary.


RelationalDB with Appfog KB Update

Removes references to beta

Christine, I was about to create a pull request with updates as well. One thing I noticed is that your image show a large plan which is not available in the CF marketplace today. Below is the link to what I have updated the KB with
https://github.com/amwatson1s/PublicKB/blob/master/AppFog/using-ctl-mysql-with-appfog-apps.md

This looks fine Andy.  There is, however, a large plan included in the marketplace.  I confirmed it's in the marketplace and you can see it in my screenshot below when I use the cf command to show plan details.
[cid:55376BB6-FF74-4795-9B1B-9DFFB5B4A125]
Christine Parr
Product Owner, Database Services
575 Maryville Centre Drive, Suite 400
St Louis, MO 63141  cell:<PHONE_NUMBER>
christine.parr<EMAIL_ADDRESS>[cid:E624B485-76C0-495C-BF92-D7A9D4EC846D]
From: amwatson1s <notifications<EMAIL_ADDRESS>Reply-To: CenturyLinkCloud/PublicKB <reply<EMAIL_ADDRESS>Date: Monday, February 8, 2016 at 5:31 PM
To: CenturyLinkCloud/PublicKB <PublicKB<EMAIL_ADDRESS>Cc: Christine Parr <christine.parr<EMAIL_ADDRESS>Subject: Re: [PublicKB] RelationalDB with Appfog KB Update (#813)
Christine, I was about to create a pull request with updates as well. One thing I noticed is that your image show a large plan which is not available in the CF marketplace today. Below is the link to what I have updated the KB with
https://github.com/amwatson1s/PublicKB/blob/master/AppFog/using-ctl-mysql-with-appfog-apps.md

Reply to this email directly or view it on GitHubhttps://github.com/CenturyLinkCloud/PublicKB/pull/813#issuecomment-181622159.
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.


ARROW-7395: Do not warn or wrror on logical "or" with constants

This fixes a warning with newer clang++'s that was breaking the C++
debug build.

Can we resolve this problem by updating bundled xxHash to v0.7.2?

Can we resolve this problem by updating bundled xxHash to v0.7.2?

Nope: https://github.com/Cyan4973/xxHash/blob/v0.7.2/xxhash.c#L801


Bugfix for local repo casing issue on Linux

For the FindNameHelper() the regex was:
test_local_mod.\d+.\d+.\d+(?:[a-zA-Z0-9-.]+|.\d)?.nupkg
The first '.' matches any character whereas our intention with the regex is to match the literal '.' so I added a backslash before the '.' to escape it. If the package being searched for is test_local_mod it was matching test_local_mod.1.0.0.nupkg and also test_local_mod_<IP_ADDRESS>.nupkg where the '_' character was getting matched by '.' in regex
and <IP_ADDRESS> was getting considered as the version.
The main issue Amber had found was that for FindVersionHelper() the path for the .nupkg was being constructed and we use lowercasing so on Linux that path will not be correct. Instead, once we find a matching package (by name and version) we should use the path given from the file system that has the correct casing.
PR Summary

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Documentation needed

[ ] Issue filed:

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

Other than the digit issue, everything else looks good.

Do we still need
Match match = matches[0]; on line 276
and
Capture group = groups[0]; on line 284?
Looks like both variables aren't being used anywhere


fix spacing and add a newline at EOF

Minor styling adjustments to extra.scss file for consistency:

Added a single space after a colon.
Removed unnecessary spaces, leaving just the newline.
Added a newline at EOF.

Thanks!


Delete service resource on a config test failure

Description
The exception triggered by the execute resource upon a configuration test failure would not always prevent the service from being restarted with a bad configuration allowing a service impact potential. Delete the service resource upon a test failure to ensure that the service action is never attempted.
Issues Resolved
n/a
Check List

[x] All tests pass. See TESTING.md for details.
[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable.

          1 Warning

:warning:
This Pull Request is probably missing tests.

  Generated by :no_entry_sign: Danger

Released as 7.2.0


Localization Right to left support

hi
Any one has idea how to have arabic support /right to left

ok got it, it is already handled.


Add max_charge parameter to set_operation_mode for ET class

This pull request is for fixing a bug when using set_operation_mode with operation_mode = 4 on an ET inverter.
On ET inverters there is an extra eco mode parameter for maximum charge. This parameter is sometimes set to 0, when using the current version of this lib, resulting in the inverter not charging.
To fix this issue I implemented EcoModeV2 which handles this max_charge parameter and added this to the ET implementation:
inverter.set_operation_mode(4, power, max_charge).
The default value of max_charge is set to 100 so that:
inverter.set_operation_mode(4, power)
works as expected.
The device info for the inverter I have tested the new code on is:
modbus_version = 1
rated_power = 10000
ac_output_type = 254
model_name = 'GW10K-ET'
dsp1_sw_version = 8
dsp2_sw_version = 8
dsp_svn_version = 159
arm_sw_version = 19
arm_svn_version = 207
software_version = '04029-08-S11'
arm_version = '02041-19-S00'

I added the _supports_eco_mode_v2 function to handle when to use the EcoModeV2 registers or not. Do you think:
if self.dsp1_sw_version < 8:
    return False
if self.dsp2_sw_version < 8:
    return False
if self.arm_sw_version < 19:
    return False
return True

is the correct check?
I only have one inverter to test on so I cannot say...


[Bug Report] autocomplete on input elements always gets set to 'off' instead of the actual value

Element UI version
2.4.1
OS/Browsers version
OS X / Chrome 67.0.3396.87
Vue version
2.5.17-beta.0
Reproduction Link
https://jsfiddle.net/bartvanremortele/wnbucrg8/
Steps to reproduce
Set password autocomplete to "new-password", inspect html to see that it's being set to "off"
What is Expected?
Expected is that autocomplete takes the value from the el-input element and applies it to the input element.
What is actually happening?
Value is always being set to "off"

For now you need to assign auto-complete on <el-input>: https://jsfiddle.net/wnbucrg8/3/ . We'll support the native autocomplete attribute in the next major version.

This issue persists as of v2.12.0


dbeaver/pro#3257 Syntax tree to model mapping refactoring

Now, we don't throw exceptions if something is not correctly parsed (see case from the issue).
If we haven't parsed some part of the query, we build an incomplete model (not sure how to test it)
If the table is not found, we don't highlight columns and don't show errors for them - only for the table.

verified


GPU Nvidia H100 PCIe Not Supported

I've deployed Kepler on a Kubernetes to monitor a cluster with a GPU node with a NIVIDIA H100 PCIe.
In the kepler logs from this node, I've this error. In parallel I'm monitoring this GPU with a dgcm-exporter instance and it can collect gpu energy consumption metrics correctly.
I0125 07:04:48.972351       1 power.go:86] Failed to collect GPU metrics, trying to initizalize again: failed to get processes' utilization on device {0x7f639b40bdf8}: Not Supported
I0125 07:04:48.972407       1 gpu_nvml.go:62] found 1 gpu devices
I0125 07:04:48.972416       1 gpu_nvml.go:73] GPU 0 NVIDIA H100 PCIe
Do you have an idea ?

Bad repository sorry. I move it to Kepler repository


Send email verification

Fixes #46
Adds admin.auth().sendEmailVerification(uid). Tested it locally and it works great.
This could be made much nicer if the /getOobConfirmationCode endpoint was changed to optionally accept a localId (uid) instead of an idToken. This is how the other endpoints work. This would make the process use one less REST call and not require the use of createCustomToken which isn't supported by all environments.
Let me know if this is going in the right direction and I'll clean it up a bit and add tests (or you can).

Thank you for your interest in this feature. We really appreciate your contribution. For new APIs, you need to file a new feature requests.
We have an extensive internal API review process. This has to go through that review first.
https://firebase.google.com/support/contact/bugs-features/
That said, the API proposed is inefficient and combines admin and client endpoints. You are making 3 round trips for this feature. This is exactly what developers are already doing to support this via Admin SDK.
Thanks again for your effort. We plan to support this API with a dedicated endpoint. It is on our roadmap.

Just to clarify, no admin SDK endpoint should rely on an ID token to make an authorized call. That belongs on the client SDK. For Admin SDK a service account credential is enough to send the authorized call to send an email verification (without the same client side limitations). Client side calls are subject to throttling and different checks than admin endpoints. That is why we can't rely on internal implementations in the admin SDK with such restrictions.

Thanks for the response,
I agree that the implementation is a bit messy but do you think this could be handy as an interim solution because:

#77 has been open for a long time
The suggested solution involves including the client-sdk (fairly large) and has a number of steps. This strays from the simplicity most firebase services offer.
When the endpoint is eventually implemented the transition will be seamless to the developer.

Perhaps you could mark the method as experimental?

So for example, a developer using this implementation to send multiple email verifications could end up getting rate limited as from the perspective of the Auth backend, this is coming from a client API.

Correct me if I'm wrong but this would only prevent you from sending a large number of verify emails to the same user. This is probably desired behaviour for most use cases.

You are free to use this solution on your own. In fact, right now, your options are limited and this is a good workaround.
However, we can't accept a hack in our official SDKs for various reasons.
As I explained earlier, we have a rigorous review process for new APIs. Even if I wanted to roll out a new API, I can't just simply do it.

I think Auth backend servers will see this as initializing many login sessions from the same IP/device, which is a problem. I kind of like the idea of having this as an interim solution though (clearly marked as experimental in the documentation). But I'll side with @bojeil-google and the auth team's decision on this since they understand the implications of this far better than I do.

I can use this as a way to push harder for this feature. I totally understand the importance of having an easy way to send verifications via the admin SDK. We have several features in the pipeline that developers have been asking for for some time. You will be seeing them soon. Once we can get those out of the door, we can focus on this feature.
Once again, I think you can use this solution though don't be surprised if you get throttled.


css: Use SCSS nesting in widgets.scss.

Testing Plan:
Simple changes, manually tested.

This is great, and much more readable, thanks @vrongmeal!


Following your rtp forwarder example, getting nil pointer derefrence

go version
go version go1.17 linux/amd64
webrtc/examples/rtp-forwarder
export GO111MODULE=on
build .
# token stuff in fiddle
echo "$TOKEN" |  ./rtp-forwarder
# take response and put it in fiddle
Connection State has changed connected
Ctrl+C the remote client to stop the demo
Peer Connection State has changed: connected
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x7ac8d0]

goroutine 68 [running]:
main.main.func3(0xc0001a3e60, 0x3)
	/home/ryan/Repos/active/rtc/rtp/webrtc/examples/rtp-forwarder/main.go:166 +0x370
created by github.com/pion/webrtc/v3.(*PeerConnection).onTrack
	/home/ryan/Repos/active/rtc/rtp/webrtc/peerconnection.go:459 +0x17d

Thanks for reporting! I think https://github.com/pion/webrtc/pull/2204 should fix this issue.


If user change email in profile, we need to send new verify mail

Need to check if new email is valid.
Any ideas?

Hey @Sogl, thank you for your suggestion.
I think Laravel implemented this functionality only on create also to prevent bot to create thousands of records in your database for nothing.
I don’t remember the last time a service ask me to verify my email address on an update, do you have an example? If the email is wrong you can still change it again if you’re log in, right?
Thank you

It can be a problem when you use users table as a mail list and other situations when you need a valid e-mail address.
Situation:

user typed a valid e-mail and registered it
he changed it to<EMAIL_ADDRESS>or made a mistake in e-mail change
after some time you send e-mail in subscribe list to wrong address
in typo: user can't log-in because password reset link sent to wrong address

In step two we can block user actions before email confirmation

This is interesting, probably including the email address as the part of the token, then decrypt while it's used?

Ok it seems cool, feel free to open a PR, I don't have the time to develop this feature :/
Thank you


Profiletweaks

A couple more tweaks to profile.css

footer margins now consistent across different HTML reps (e.g. rep of a tiddler, rep of a collection of tiddlers)
renders pre tag contents properly

if there is a pre I want it to preserve whitespace exactly, not introduce new whitespace

ditto

Personally I like it wrapping where necessary so that
a) it doesn't break out of the pre element
b) I don't have to scroll within a specific element on a page
If wrapping is not right then I could change the overflow property so that a user can scroll to see the rest of the content.
Either would be better than what currently happens

scrolling the pre div would be fine with me
the goal is to be able to copy the text and have it be a "correct" copy


Add binary sensor name in config and allow multiple HDO signals

With this PR binary_sensor has unique id and it allow to have multiple sensors in config. It also do not break backward compatibility because it use optional parameter.

Diky


Consistent crashing with Stalker Trilogy (OpenXray engine)

Software information

Stalker Call Of Pripyat, using OpenXray engine. Setup instructions

System information

GPU: MSI 3080 10gb
Driver: 531.68
DXVK version: 733ca18

Reproduction steps

Use minimum settings
Start a new game
use console command rs_vis_distance 1.5 to set render distance to max
Game should crash right away, or after moving the camera for a bit.

Log files

a few examples of d3d9.log after a crash:
xrEngine_d3d9_0.log
xrEngine_d3d9_1.log
xrEngine_d3d9_2.log
xrEngine_d3d9_3.log

Notes

Sometimes, similar crashes will happen at minimum render distance, but setting render distance higher seems to ensure crash will happen at some point.
Crashes usually end with one of these errors:

err:   DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err:   DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST
err:   DxvkDevice: waitForIdle: Operation failed

Tested using minimum texture settings

I don't seem to get these anymore, using this release: 7b3884a
I am now able to set rs_vis_distance to max and run around without crashes.


Do not add run spacing if there are no run metrics

After the initial run we always add run spacing.  Detect this by checking if there are run metrics, and avoid adding the spacing.

Fixes https://github.com/flutter/flutter/issues/16285

Nice catch!


[Feature Request] Support blur event as the trigger of the validation for el-cascader component

Existing Component
Yes
Component Name
el-cascader el-form-item
Description
Currently, the cascader only generates el.form.change event for validating, el.form.blur is not supported. However, this will cause problem if the value in the cascader is loaded asynchronously after component is created. This will cause the el.form.change event being triggered, and thus trigger the validation, and the green border will be shown (or even red border with error message if the loaded value is invalid).
There is a fiddle showing this behaviour: https://jsfiddle.net/sn1L5867/
After asynchronous job is done, the cascader has a green border, because the validation has already been triggered, but the input doesn't have the green border.
It would be great, if the el.form.blur event can be dispatched after the visible-change event, so that only if the user has closed the cascader menu, the validation event will be triggered.
I've locally prepared a change. If needed, I could create a PR.

@xiGUAwanOU pr welcome. 👍

Is this a bug？？？


Can`t open tables in diagrams

After installed the latest DBeaver 6.1.5, i can not open tables(on double-click) in ER Diagram.
In version 6.1.4, this worked fine.

Thank you for the bug report.
It is a side effect of other ticket fix. We will include fix of this problem in the gotfix version (will be released tomorrow)


CXF-9076: Exception message is not unmarshalled with JDK17+ (limit the fix to JDK standard library exceptions)

Exception message is not unmarshalled with JDK17+ (limit the fix to JDK standard library exceptions)

@huhmare the fix should address your concerns, thank you

Thank you.
The CXF tests are run with "--add-opens java.base/java.lang=ALL-UNNAMED" by default. The test ClientServerExceptionTest.exceptionCustomExceptionMessageIsPreserved fails without it. The test is bit misleading, as the CXF-9076 is about using jdk17+ without add-opens.
As I understand, using this PR with JDK17+ without add-opens:

java.lang.*Exceptions will have detailMessages, if it has a constructor(String, Throwable).
Any other (Sub)Exception will not have it, so that we can have member variables in subclasses.

Difference to before CXF-9076 is that we will have detailMessage in some java.lang.*Exceptions. The necessary constructor is found in 11 / 29 Exceptions (openJDK17+35). For example SecurityException has it, and IllegalAccessException does not.
There are 3 exceptions (ClassNotFoundException, EnumConstantNotPresentException, TypeNotPresentException) in java.lang that have their own member variables. Only TypeNotPresent will be affected by these CXF-9076 changes. Not a big problem.
All in all, this and the previous PR are small step to right direction, but are not a complete solution to the general problem.
In the code base I am working with, we still probably have to use either:

add-opens OR
rewrite the code to not rely on detailMessage OR
rewrite subExceptions to hide Throwable.detailMessage with a our own detailMessage and get/set methods in the subclass.

These PRs might help us in case we have a java.lang.*Exception thrown out of the SOAP-interface. But it will not cover for example java.sql.SQLException.
Unfortunately I do not have a suggestion for a correct way of doing this. Dynamic Proxy works only with interfaces(?), so a way to create instance with getMessage returning correct value would propably need bytecode manipulation stuff.

The CXF tests are run with "--add-opens java.base/java.lang=ALL-UNNAMED" by default. The test ClientServerExceptionTest.exceptionCustomExceptionMessageIsPreserved fails without it. The test is bit misleading, as the CXF-9076 is about using jdk17+ without add-opens.

That is right, although I've tested it manually, the tests have to be run without --add-opens, I will try to isolate those since it is not only related to this specific test case

As I understand, using this PR with JDK17+ without add-opens:

java.lang.*Exceptions will have detailMessages, if it has a constructor(String, Throwable).
Any other (Sub)Exception will not have it, so that we can have member variables in subclasses.

Right

All in all, this and the previous PR are small step to right direction, but are not a complete solution to the general problem.

Right, this is a best effort.

Unfortunately I do not have a suggestion for a correct way of doing this. Dynamic Proxy works only with interfaces(?), so a way to create instance with getMessage returning correct value would propably need bytecode manipulation stuff.

I think it all runs down to the edge cases (and how often they appear in the wild), if we cover 80%+ with this fix, it is already a win I believe. Thanks @huhmare


PointerPressedEvent and PointerReleasedEvent will not fire properly if you press multiple mouse buttons

If I press left button and hold it, then press right button then there is no PointerPressed event for the second button press.
If I then release left button (while still holding right button) there is no PointerReleased event.
Finally if I release the right button I do get an event, but nothing indicates the left button was released.
I would expect either that the event is fired on every event and that I can read current state from the mouse buttons or that the events fire only when the first button that was pressed is released. The current behavior seems wrong.
I use Avalonia 11.0.9 when I'm testing this

It's by design, see #2857

Yes, and you can handle PointerMoved update event checking UpdateKind parameter.


Emoji picker - Unable to navigate with arrow keys when there's text in search box

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to e.cash
Navigate to a conversation
Click on the emoji icon
Type something in the search box
Press down arrow key to navigate through the options

Expected Result:
User should be able to navigate the emoji list with arrow keys after pressing the down arrow
Actual Result:
Pressing the down arrow does not allow the user to navigate through the emoji list
Workaround:
User has to manually select the emoji with the mouse cursor
Platform:
Where is this issue occurring?
Web ✔
iOS
Android
Desktop App ✔
Mobile Web
Version Number: 1.0.74-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/44479856/124185045-b7f52280-daba-11eb-80f8-9826d6a80bc1.mp4
Expensify/Expensify Issue URL:
View all open jobs on Upwork

From @mallenexpensify https://expensify.slack.com/archives/C01GTK53T8Q/p1625155126323200?thread_ts=1625154887.322400&cid=C01GTK53T8Q

With cursor in compose box, click tab > enter
Start typing a search for an emoji.
Observe you can't click the down arrow to then navigate the emoji selector to choose which emoji you want.

Triggered auto assignment to @roryabraham (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Triggered auto assignment to @mitchexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Upwork job!

Proposal

Due to the recent Upgrade of RN-Web version, we faced one issue where keyboard events are not bubbling from the TextInput. @roryabraham  fixed one of the issues where keyboard shortcut was not opening the search when Focused on the composer.

A similar thing is happening here, we already have arrow navigation for the Emojipicker but events are not bubbling so to fix this we need to attach the event in the capture phase.
So we update this line https://github.com/Expensify/Expensify.cash/blob/824e85f8099cdf903e88107c0b33d47ed93882ff/src/pages/home/report/EmojiPickerMenu/index.js#L113.
as
   document.addEventListener('keydown', this.keyDownHandler, true);

which fixes the arrow navigation.
Suggestion

we block arrows while the search for emojis to enable the arrow navigation on the Emoji picker but that seems a bad UX. Instead, I propose that a Down Arrow key would enable the arrow navigation on the emoji list while the text box is focused or the cursor is visible on the Search box. Then, arrow navigation will run as normal as now. I found that Slack has the same behavior.

Proposal
When ArrowDown is pressed, unfocus the search.
In src/pages/home/report/EmojiPickerMenu/index.js
<TextInputFocusable
    ...
    onKeyPress={this.unfocusSearchOnArrowDown}
>
unfocusSearchOnArrowDown(key) {
    if (key.code === 'ArrowDown') {
        this.searchInput.blur();
    }
}

@parasharrajat's proposal is better as it fixes the bug.
while mine is a hack.

@parasharrajat Great proposal as always! I agree that it's better to allow arrow keys to move the cursor around in the text input, then activate emoji-selection only with the down arrow key. When in the top row of emoji, the up-arrow key should refocus the text input.

When in the top row of emoji, the up-arrow key should refocus the text input.

Sure, I will add that too. Point taken.

This isn't working on Desktop Version 1.0.76-2
https://user-images.githubusercontent.com/22508304/125660872-2389d39f-b567-4dbd-839a-ad1532a52b36.mp4

@mallenexpensify Have you used the down arrow key to activate the arrow navigation?

Yes, I was trying to click the down arrow and nothing happened. I swear it worked days ago....

Sure, Bear with me. As soon as this PR is deployed to Staging, you will get back arrow navigation.

Desktop just updated to Version 1.0.77-5 (1.0.77-5) and it's working there for now, so closing again.  Thanks @parasharrajat

Paid in Upwork


Broken AnnexB support for RegExp (Annex B.1.4)

See "Annex B.1.4".   Cases like /{/;, /}?/u;, /{*/u;,  among others doesn't parse.

Since parsing of regular expressions uses the host JS engine, you might get different results in different engines. All your examples parse for me in Node 6.12.0.

@adrianheine  I tried this with the Chrome browser. V8 have build in-support for this. Testing it through AST Explorer failed for me. I then tested the same with my own parser using Chrome too, and it parses. I haven't pushed online my RegExp parser, so native host JS engine.
Howver. For NodeJS 8.x and 9.x it throws an error for both /}?/u; and /{*/u; Invalid regular expression: /}?/: Lone quantifier brackets.
To make a finale validation. Also validted this against both Shift and Esprima with AST Explorer, and both parses this.  They are both using native solution.
I did not validate this further before I opened this issue ticket.

We appear to be mostly conforming to this with 0d20f67b. Things like /}?/u still don't parse, but they don't in SpiderMonkey or V8 either, so I'm fine with that.


Fix Kofe engine with latest MIEngine

The Kofe engine was still using the old constructor for MIEngine, which was
removed with commit f6bb8986a159d1ee2a24143904ab47591d8dcdac
(Implement IDebugEngine3.SetEngineGuid).
This puts it back.

@faxue-msft FYI
@gregg-miskelly LGTM

I guess it's not necessary to add the constructor wrapper back into DebugEngineHost.ref.cs since Kofe isn't rebuilding against the new binary anyway.
LGTM


Lightgbm memory explodes in start train

Hey,
Using lgb on a dataset size of 3G numpy array
X is int8
Y is float32
400 features 32 leafes
Using the lgb.dataset
When starting the train  memory starts to increase massively more than twice the input size.. Getting to 16G.
I understood that lgb should be memory efficient, why does it us so much memory. The input is 3G so it shouldn't use much more.

can you share more settings about your jobs? what task?(regression?), what is the bin number?

Regression l2 task using 50 bins. Running on Ubuntu with 32G.
Can you explain the ram usage pipeline

When creating dataset there is no ram increase.. Is this because the dataset uses reference to x and y?
When start training I understand that the dataset constructor starts to build the histograms and here I think the memory starts to build up massively inspire of the low max bin 50

How many maximum leaves/depth are you using? Too large increases memory requirement exponentially.

Max leaves 32 max depth 5
Doesn't seem like much
There are 12Gb that I can't understand how it uses so much

I think your matrix is 6GB in reality (when taken as float16), but doesn't explain why it jumps to 16GB.
@guolinke int8 matrix is supported in Python?

@Laurae2 @beutlgb  actually not, all the value will be transfer to int32_t. so the size should be 12Gb + structure & additional logic

If the x is int8 why would it be converted to int32... lgb should be memory efficient?

Ah yes it is float32. Therefore, 16GB usage is normal.

@beutlgb we don't implement the responding logic in the C side(yet). you can change it at [here].(https://github.com/Microsoft/LightGBM/blob/master/include/LightGBM/meta.h#L16)

If I only change this line to int8_t and build would it work? Won't there be overflows?

@beutlgb
lightgbm do use int8 inside for you data set. however, the temporary memory for construct dataset in python package is float32.
If you want the efficient on memory, please use the CLI  instead. we didn’t ensure the memory efficient on python/R package.

BTW,  another solution is saving your data to csv or lightsvm, then constructing dataset from file.

I don't understand, I thought the memory explodes when the dataset is constructed because the constructor uses int32 regardless what the input type is

You are converting data in Python, it's normal the memory explodes there.  You must use another format (ex: on disk as CSV/SVMLight) if you don't want such overhead.

My data is int8 so I don't understand why loading from a csv file in Python will be better memory wise

So if I load the data in Python from a csv file you think the memory won't explode? The constructor of the dataset won't convert it to float32

@beutlgb the memory overhead is caused before Dataset constructed.
When constructing Dataset in python package, it will convert the whole Dataset to float32 type first (on python side), then pass the converted float32 dataset to LightGBM api.
If you pass filename to LightGBM.Dataset directly, the file will be read by LightGBM api, without python. As a result, it will be memory efficient.

Ok great! I will try that and updat
Thanks for the quick and effective  help guys

Hello,
got the same problem. LightGBM 2.0.10 just explodes in memory when training from the Python api.
I know that there are no warranties outside the CLI, but I was using intensively the 2.0.4 version through Python without that problem.
Could maybe be a change in any default parameter? I read something about the histogram parameter, I changed it but still crashing.
Thank you for this awesome library, by the way.

@Guillermogsjc did you use categorical feature ? can you provide the example code ?

@guolinke yes of course did, got many values in each categorical column. In fact i am putting this in model params, in lgb.Dataset when generating the dmatrix, and after also in the lgb.train command.
I cant provide example code because it is over a private dataset, this problem does not appear in the version i am used to work (2.0.4). Tried to move ahead into several new versions along the time but the Python api worked irregular (not happening in 2.0.4). I am over linux (Ubuntu)..
Kind regards

@Guillermogsjc The new categorical feature support will cause the increase of memory usage. You can try to disable it and see what happen.

@guolinke ok, thank you very much, thank for your quick responses

@guolinke Do you know which commit/PR increases the memory usage of categoricals?

@Laurae2
the reason is the categorical feature may exceed 255, as a result, it needs to use uint16 or uint32 type to store the feature values.
However, I think @Guillermogsjc 's case is caused by python package.

@guolinke @laurae i preprocess the categorical features reducing them to 63 or 255 distinct values  by column, so the train is fed with categoricals as uint8

@Guillermogsjc okay, so the reason is not caused by categorical feature. can you provide a example code?

I have a similar problem of memory explosion when training starts, I tried dumping the datasets to CSVs to build the Datasets from files on disk, but this actually results in even higher memory usage.

@MasterScrat you can try the parameter "two_round=true"


bin/setup failed on fresh install

Describe the bug
bin/setup failed on a fresh repo install.
To Reproduce
Steps to reproduce the behavior:

Git clone git@github.com:joemasilotti/railsdevs.com.git.
Run brew bundle install --no-upgrade and wait for it to finish.
Run bin/setup
See error. Full Console output Gist here

Expected behavior
The installation script should automatically get the application setup.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
On MacOS Monterey MacBook Pro (13-inch, 2020) 12.3.1

What version of PostgreSQL are you using?
$ psql --version

I'm at psql (PostgreSQL) 14.3

@themudassarhassan, any ideas what could be going on here? The error is coming from the the search index on developers.
db/migrate/20220416144523_add_index_for_searchable_fields_in_developers.rb

@joemasilotti let me have a look.

Okay. So I was able to do a fresh setup and the database was created successfully and migrations ran successfully. I'm not sure what is the exact root cause of this issue. But @malachaifrazier can you try to create db with bin/rails db:create and then run migrations afterward to see if this helps.

Will do!
On Thu, May 19, 2022 at 10:58 AM Mudassar Hassan @.***>
wrote:

Okay. So I was able to do a fresh setup and the database was created
successfully and migrations ran successfully. I'm not sure what is the
exact root cause of this issue. But @malachaifrazier
https://github.com/malachaifrazier can you try to create db with bin/rails
db:create and then run migrations afterward to see if this helps.
—
Reply to this email directly, view it on GitHub
https://github.com/joemasilotti/railsdevs.com/issues/426#issuecomment-1131836363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFZ26WEJY4G5ZBK5BAL6GDVKZJHPANCNFSM5WJFACDQ
.

StandardError: An error has occurred, this and all later migrations canceled:

PG::DuplicateTable: ERROR:  relation "active_storage_blobs" already exists
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20211028230858_create_active_storage_tables.active_storage.rb:7:in `change'

Caused by:
ActiveRecord::StatementInvalid: PG::DuplicateTable: ERROR:  relation "active_storage_blobs" already exists
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20211028230858_create_active_storage_tables.active_storage.rb:7:in `change'

Caused by:
PG::DuplicateTable: ERROR:  relation "active_storage_blobs" already exists
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20211028230858_create_active_storage_tables.active_storage.rb:7:in `change'
Tasks: TOP => db:prepare
(See full trace by running task with --trace)

== Command ["bin/rails db:prepare"] failed ==

I ended up manually going through a bunch of the migration files and adding if_not_exists: true see in this gist of git diff.
I then ran bin/setup again and reached this error once more:
➜  railsdevs.com git:(main) ✗ bin/setup
== Installing dependencies ==
The Gemfile's dependencies are satisfied

== Install JavaScript dependencies ==
yarn install v1.22.17
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.17s.

== Preparing database ==
==<PHONE_NUMBER>4523 AddIndexForSearchableFieldsInDevelopers: migrating ==========
-- execute("      ALTER TABLE developers\n        ADD COLUMN textsearchable_index_col tsvector\n          GENERATED ALWAYS AS (to_tsvector('simple', coalesce(hero, '') || ' ' || coalesce(bio, ''))) STORED;\n")
rails aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::SyntaxError: ERROR:  syntax error at or near "("
LINE 3:           GENERATED ALWAYS AS (to_tsvector('simple', coalesc...
                                      ^
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20220416144523_add_index_for_searchable_fields_in_developers.rb:3:in `up'

Caused by:
ActiveRecord::StatementInvalid: PG::SyntaxError: ERROR:  syntax error at or near "("
LINE 3:           GENERATED ALWAYS AS (to_tsvector('simple', coalesc...
                                      ^
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20220416144523_add_index_for_searchable_fields_in_developers.rb:3:in `up'

Caused by:
PG::SyntaxError: ERROR:  syntax error at or near "("
LINE 3:           GENERATED ALWAYS AS (to_tsvector('simple', coalesc...
                                      ^
/Users/malachai/Desktop/Projects/railsdevs.com/db/migrate/20220416144523_add_index_for_searchable_fields_in_developers.rb:3:in `up'
Tasks: TOP => db:prepare
(See full trace by running task with --trace)

== Command ["bin/rails db:prepare"] failed ==

That looks like your version of Postgres doesn't support that syntax, but you're running a version higher than me. (I'm on 14.2.) So I'm really not sure what's going on here!
Maybe a red herring, but I just reran the migrations and the following diff was made to my schema. I wonder if this is related?
diff --git a/db/schema.rb b/db/schema.rb
index c42ca61..72ba1a0 100644
--- a/db/schema.rb
+++ b/db/schema.rb
@@ -12,6 +12,7 @@

 ActiveRecord::Schema[7.0].define(version: 2022_05_01_021745) do
   # These are extensions that must be enabled in order to support this database
+  enable_extension "pg_stat_statements"
   enable_extension "plpgsql"

   create_table "active_storage_attachments", force: :cascade do |t|
@@ -227,7 +228,7 @@ ActiveRecord::Schema[7.0].define(version: 2022_05_01_021745) do
     t.string "processor_id"
     t.boolean "default"
     t.jsonb "data"
-    t.datetime "deleted_at"
+    t.datetime "deleted_at", precision: nil
     t.datetime "created_at", null: false
     t.datetime "updated_at", null: false
     t.index ["owner_type", "owner_id", "deleted_at", "default"], name: "pay_customer_owner_index"
@@ -264,8 +265,8 @@ ActiveRecord::Schema[7.0].define(version: 2022_05_01_021745) do
     t.string "processor_plan", null: false
     t.integer "quantity", default: 1, null: false
     t.string "status", null: false
-    t.datetime "trial_ends_at"
-    t.datetime "ends_at"
+    t.datetime "trial_ends_at", precision: nil
+    t.datetime "ends_at", precision: nil
     t.decimal "application_fee_percent", precision: 8, scale: 2
     t.jsonb "metadata"
     t.jsonb "data"

Ha! Found it 😄
Found it!
The root cause was because that syntax isn't supported by my old PostgreSQL version (installed via Homebrew).
Upgrading like so fixed all the things:
Installed PostgreSQL via Homebrew?
Check your PostgreSQL version like so:
psql [username with correct permissions]

Then, check your version like so:
select version();

Your version should be at least 13.7. Here's mine:
 PostgreSQL 13.7 on x86_64-apple-darwin21.3.0, compiled by Apple clang version 13.1.6 (clang-13<IP_ADDRESS>), 64-bit

If your version is lower than 13.7, upgrade like so:
brew install postgresql@13

Ah, that's great to know! Thanks for digging in and following up.
Unfortunately we can't set a minimum version in the Brewfile, so Brewfile.lock.json:272 will have to do for now!

Sweet. Think it's worth specifying postgresql@13 in the README?

In case anyone is trying to bin/setup in Debian 11 and you have multiple versions (e.g. 9.6, 12.x, 14.2) of "postgresql" installed, make sure that the server of the right version (13+) is listening on port 5432.
One could check/modify that in the postgresql.conf file, e.g. in case of version 13:  /etc/postgresql/13/main/postgresql.conf.
In my case, I had "postgresql v.9.x" running on port 5432 hence the syntax errors were popping up when running migrations.

Thanks for this @axhgl! Would you mind adding a note to the README for future contributors?

You're welcome, @joemasilotti! Sure. I'll soon give it a try.


Current Behavior
ScrollBox throws upon destroy if background is not set and background should be optional
Steps to Reproduce
Call ScrollBox destroy().
Environment

version: 2.1.2
Browser & Version: Chrome 126.0.6478.62
OS & Version: Microsoft Windows 11
Running Example: N/A

The problem seems to be caused by ScrollBox being instantiated without options parameter:
e.g.
const sb = new ScrollBox();
sb.addChild(new Graphics());

Closing as it's not a bug.


Timeout - and the response it has been writing for the past minute or two disappeared.

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Linux
- Continue: v0.6.15

Description
Please disable the timeout while streaming a response. Disable timeouts all-together, really. Earlier today, I had the same issue with it timing out when I sent my entire repo in the context and it had to spend a while processing all the prompt tokens. I have big context models, they do eventually respond :)
Please make timeouts configurable.
To reproduce
No response
Log output
No response

Nevermind, I found it.
"models": [
    {
      "title": "CtxExt DeepSeek Instr Coder 256k",
      "provider": "openai-aiohttp",
      "model": "deepseek-33b-256ctx",
      "api_base": "http://******",
      "context_length": 256000,
      "server_url": "",
      "request_options": {
       ---> "timeout": 30000 <----
      }
    }
  ],

256k 👀
Glad you found it. Starting in pre-release versions timeouts will no longer happen


Apply Time Picker for refreshing the Charts

NOTE: # Time Picker syncing and better Filters
Sync the Charts to be refreshed based on NR1 time picker, Filterable Host/App/Tags instead of search queries.
NOTE: # Refresh charts based on Time picker selection, Ability to filter based on drop downs
Refresh the Optimisation charts based on NR1 time picker, Ability to filter based on drop downs instead of Queries that need to be validated.
NOTE: # Refresh the Optimisation charts based on NR1 time picker, Ability to filter based on drop downs instead of Queries that need to be validated.
TIP:  # ( Do NOT give us access or passwords to your New Relic account or API keys! )
Possible Solution
Additional context

Closing as #106 is a complete rewrite and the views are different now.


Feature request: scrolling to cursor without requesting focus

Is there an existing issue for this?

[X] I have searched the existing issues

Use case
Currently the editor doesn't scroll to the cursor/selection set in QuillController without requesting focus.
Proposal
It would be great to be able to scroll to the selection when the editor is open, so that the user starts from the same part of the document he has finished before.
Currently it's possible to achieve this by requesting focus. However, in many cases it's convenient to look at the document first, instead of editing it. Moreover, on mobile platforms keyboard appears when focus is on, reducing the editor height, which is also inconvenient when viewing documents.

I am currently working on issue 1907 which referenced your issue.
In the current release, you can scroll to the position in the document but there are some gotchas!
How are you trying to set the remembered position?
Are you using QuillController TextSelection or are you using ScrollController initialScrollOffset?
In QuillEditorConfigurations are you setting autoFocus = true?
If you set autoFocus, it will set the editor to show the current QuillController text selection which is probably at the start of the document - this action prevents ScrollController offset being used. Net effect, you might think that it is not working.
QuillController selection is the offset in characters, ScrollController offset is vertical pixels and not rows.
If you can tell me more about what, and how, you are trying to do it, I may be able to get it working as part of issue 1907.

Don't use scrolling which uses pixels.
Use TextSelection when you create the document (or use UpdateSelection).
There is also RawEditorState.bringIntoView (TextPos ) which might work for you.


adding function to insert new values to toml table

I implement inserting new values directly into the Value.
I wrote about it in an Issue here:
https://github.com/alexcrichton/toml-rs/issues/231
We can already quickly get values from Value with index access, but inserting the new Value is kind of clunky, so I added the helper function directly inside the Value.

@dtolnay
hey, thanks for the feedback! I understand your point of view, writing as_mut_table().unwrap().insert(...) is not that much longer and there is a way to insert a value already so it is not that necessary. Still, I miss inserting values with index just like in serde. I think it is common operation and it is worth to consider adding inserting directly in the Value.

Maybe I have not used the toml crate enough myself to have hit this use case -- could you point out an example of real code that would benefit from having Value::insert?

@dtolnay
I edited my post, please read it again!
I was using serde json before and was confused why cannot I directly inserting things into Value (in json you can insert to value with index) and was doing it like this:
let mut t: Value = toml::from_str("a=1").expect("failed to create Value");
t.as_mut_table().unwrap().insert("b".to_owned(), Toml::Integer(1));

and this was little long so I thought we could use inserting new Value directly in the Value.
But toml crate is little different, I didn't know you are supposed to do:
let mut t: Table = toml::from_str("a=1").expect("failed to create Table");

So I agree with you, we don't need adding insert method in the Value. But I would add inserting example to readme/docs, because it is quite common pattern and people who used serde json may find it little confusing.

Adding some examples to the documentation sounds great to me as well!

toml-rs has moved to https://github.com/toml-rs/toml_edit.  Feel free to rebase your PR against that repo and open a new issue there.


/public directory dirty after building locally

I have a lot of files in /public after building locally.
@birkskyum I am not super familiar yet with Astro, but can we use a dist directory for output instead?

This isn't generated files - it's a cache of thumbnails to avoid being rate limited by the github api


refactor(authentication-service): update urls and add scope for keycloak idp

update urls and add scope for keycloak idp
BREAKING CHANGE:
yes
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

@Tyagi-Sunny update the readme file saying that people using the older version can still use this by only updating the KEYCLOCK_HOST and appending '/auth/realms' to its existing value

@Tyagi-Sunny update the readme file saying that people using the older version can still use this by only updating the KEYCLOCK_HOST and appending '/auth/realms' to its existing value

added


[Feature] Enable DWD probe to delay scale up or scale down of probes dependent resources via configurable values.

Feature (What you would like to be added):
Enable DWD (Dependency Watchdog) probe to provide mechanism to configure per resource delay for scale up or scale down operations when the external probe fails to reach the api-server.
Motivation (Why is this needed?):
Currently DWD probe allows configuring multiple dependent resources to be scaled up or down based on availability of api-server external probe endpoint.
This functionality is sufficient when we have only one dependent components to scale. For e.g. in current deployment only KCM is managed by DWD.
However, we have seen in productive scenarios that just bringing down KCM is not sufficient as MCM (Machine Controller Manager) can still continue to work on the machines unchecked and can lead to undesired state of the system as described in MCM[#679)
As a solution to the observed issue multiple things needs to be done -

We shall enhance the probe config for DWD to also scale MCM along with KCM  -- (MCM #354
However just scaling MCM along with KCM is not enough as MCM needs to wait for KCM to update the Node Status before starting to reconcile the status of the machines.
Currently the KCM has configuration before it acts on it.
--node-monitor-grace-period duration     Default: 40s
Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status.
Similarly Kubelet has a configuration
--node-status-update-frequency duration     Default: 10s
Specifies how often kubelet posts node status to master.

These semantics makes it important to not just scale the resources but also induce a relevant delay to ensure that they can work on the correct state of the system.
Approach/Hint to the implement solution (optional):
Ensure the solution is generic and is not coupled to only the Motivation mentioned here.

Thanks @ashwani2k. A few remarks:

However just scaling MCM along with KCM is not enough as MCM needs to wait for KCM to update the Node Status before starting to reconcile the status of the machines.

Also KCM must wait, so that the Kubelets have enough time to update their status after the API server got responsive again. So, KCM scale-up is ideally delayed somewhat (to give the Kubelets time) and MCM's even a bit more (to give KCM time).

Amount of time which we allow running Node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status.

That line/consideration is more relevant for the initial time DWD waits to scale down KCM and MCM and less in the context of the scale-up later (in which context, point 2, it is mentioned), is it not? I.e. --node-monitor-grace-period duration influences the decision when we shut down KCM and MCM and it should be safely within that time window, so that we prevent KCM from running amok before it jumps the gun and deregister LB listener and endpoints (not a problem if the API server is down completely and it can't, but very important if only the LB or the ingress gateway has issues).


Adopt Secret to Amazon Bedrock

added Secret to __init__ AWS params
updated the tests
moved all the fixtures to a conftest.py
added an extra fixture to define env vars for testing
changed the pyproject.toml

to reflect test coverage over the code
added an ignore to allow for calling functions as params

nit: @shadeMe do you know about a more concise/clean way to define the AWS params on the __init__() with Secret?


[Request]: 8BitDo Ultimate Software

PackageIdentifier: 8bitdoultimatesoftware
PackageVersion: 1.00
PackageLocale: en-US
Publisher: 8bitdo
PackageName: 8bitdo
License: proprietary
ShortDescription: configuration app for 8bitdo controllers
Installers:
Architecture: x64
InstallerType: zip
InstallerUrl: https://download.8bitdo.com/Ultimate-Software/8BitDo-Ultimate-Software-for-Windows.zip
ManifestType: singleton
ManifestVersion: 1.0.0

Closing in favor of  #12566.


UI Control: Navigate to external URL

Description

Add support for msg.payload.url to trigger navigation to external resources
Add in-Editor documentation
Add online documentation
Adds E2E test for coverage of the url option

Related Issue(s)
Closes #987

Test problems may be linked to https://docs.cypress.io/guides/guides/web-security#Different-superdomain-per-test-requires-cyorigin-command (thanks for sharing @cstns)

There is a way to circumvent this, it's not the prettiest thing in the world but it works:
cy.click() // get's redirected

cy.origin('https://www.google.com', () => {
    cy.url().should('eq', 'https://www.google.com/search?q=rick+astley')
})

You have to pass the new domain to origin. In my case I knew I would be redirected to https://www.google.com/search?q=rick+astley so i just manually added the origin

@cstns this is good for review now

console logs left in by mistake @cstns - tried removing them via the web interface and it's bugged out, will remove locally when Ig et the chance, locked in something else atm


airflow on windows

When I execute airflow webserver in a windows shell, I obtain this error message:
Traceback (most recent call last):
  File "C:\Python27\Lib\runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "C:\Python27\Lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "C:\users\afarbos\desktop\airflow\env\scripts\gunicorn.exe\__main__.py", line 5, in <module>
  File "c:\users\afarbos\desktop\airflow\env\lib\site-packages\gunicorn\app\wsgiapp.py", line 10, in <module>
    from gunicorn.app.base import Application
  File "c:\users\afarbos\desktop\airflow\env\lib\site-packages\gunicorn\app\base.py", line 12, in <module>
    from gunicorn import util
  File "c:\users\afarbos\desktop\airflow\env\lib\site-packages\gunicorn\util.py", line 9, in <module>
    import fcntl
ImportError: No module named fcntl

It seems that fcntl does not work on windows (http://stackoverflow.com/questions/1422368/fcntl-substitute-on-windows). Is that normal ? does airflow support windows ?

@hevy-CC4477,
Unfortunately, our shift to gunicorn as the application server made airflow incompatible with windows :
http://stackoverflow.com/questions/11087682/does-gunicorn-run-on-windows
I do not think we plan on supporting windows at this point, and since we do not have machines that run windows would have a hard time testing against it.

Does that only impact the web server? Or other functionality are also impacted?

NT4 support is on the roadmap, we'll then attack Windows Server 2000 and work our way up.

just kidding

It would impact the web server, as well as the way we serve/visualize the logs currently. The main issue is that the webserver is baked into the tool, but I do not think that the worker and scheduler are affected by this. Then again, I have not tested it, so I cannot vouch for compatibility.

I tried to get just an airflow worker to run on windows and hit a lot of issues (log naming incompatible with the file system, relying on shebangs, ... ). I ended up creating a winrm operator. I hope this helps ...

Yes, you answer to my question thanks.


[Modding Tools] Add Tacent View

https://github.com/R2Northstar/ModdingDocs/pull/187

the developer also quickly added support for some DDS files from Titanfall 2 that couldn't be opened.

what does this mean? can all dds files be opened with it? do they need to be extracted from vpks?

do they need to be extracted from vpks?

It supports viewing DDS files, not VPK.


output has hard spaces which are rejected in pandoc

Hi, I really appreciate this project. I've just had some trouble when using the output. When I put my text files through pandoc, I get a complaint about hard spaces which have been inserted. I think it's latex which is rejecting them. Let me know if you want more details. Some representations of the spaces are \20.

I'm not sure what the cause of this issue could be. It may be the text in the clipboard has these characters in which are respected by the markdown conversion. It could also be the library I used to actually convert the HTML to markdown.
Someone previously contributed a patch that added a lot of support for pandoc and I notice there are a lot of replacements done on the stream. Perhaps you'd like to add one that replaces this \20 with a space in a pull request?

Wow. What a fast response. I'm not a programmer, so I can't write a patch, unfortunately. Let me find another example, and post it here, just so we have a clear test. thanks for your prompt response.

Hi, I've tested this again. This is the latest web page which caused problems:
https://www.quora.com/What-is-the-best-textbook-for-Category-theory
thanks, Frank

HI Frank,
I'll see what I can do. This project is pretty much unmaintained so I'll need to find some spare time to look into this. I'll see what I can do

Hi Euan, just noticed another related bug. When a text as italics, the space before the first asterisk is a hard space. I've just looked at the javascript, and I don't see where it returns a single asterisk in replacement for italics. I see that it would return an underscore. But I haven't seen that in my results. Is most of the conversion using to-markdown?
When I look around, I see that Dom Christie has updated his project to-markdown to turndown
https://github.com/domchristie/turndown
It looks as if he is maintaining it. I don't see a project which uses that code in a manner which is as easy to use as yours.
I wish I could make the changes myself. kind regards, Frank
{
filter: ['em', 'i'],
replacement: function (content) {
return '' + content + ''
}
},

@colcord, try replacing this line:
              .replace(/[ ]+\n/g, '\n')

with:
              .replace(/[\u00a0 ]+\n/g, '\n')


Add NA as a Threat Level value

Summary
Add NA to the Threat Level selector for STRIDE/LINDDUN/CIA threats
Description for the changelog
Add NA as a Threat Level value, issue #195
Other info
This can also be forward ported to version 2.0

Merging in as we need this for the version 1.5 release


pycocotools starts with index 1

Hi guys! Thanks for your great job!
I have evaluate my custom one-class (pedestrian) dataset (visdrone format) and have -1 COCO metrics values, because pycocotool class indexes starts with 1. Index 0 means no-object.
I fix it locally, and now it works fine for me.
But  may be all the pedestrians are not included in your COCO evaluation?
Add this line:
coco_evaluator.py   242:    logger.info(f'cocoGT {cocoGt.anns[1]} CatIds: {cocoGt.cats}')
And get result:

cocoGT {'segmentation': [], 'area': 598.0, 'iscrowd': 0, 'image_id': 0, 'bbox': [440.0, 248.0, 13.0, 46.0], 'category_id': 0, 'id': 1} , ...
CatIds: {1: {'supercategory': 'pedestrian', 'id': 1, 'name': 'pedestrian'}, ...

thanks, we do make a mistake converting to coco category ids, now it starts with index 0 and gets the correct results.


(Bug) Minted, Dutch: Whitelisted addresses are not initialized if list length > 60

Steps:

Start creating Minted (or Dutch) crowdsale, decimals =18, 1 tier, whitelisted
In Step 3: add 61 whitelisted addresses from *. csv file:
https://drive.google.com/open?id=1XpOw_lqxZE6G5k0qAwWbhT2MTcTxFsWm
Complete deployment, check if Register whitelisted addresses transaction is skipped in Step 4

Expected result :

user should be able to create crowdsale with more than 61 whitelisted addresses
OR
should be restriction of length of whitelisted list  in Step 3

Actual result:

Whitelisted  addresses are not initialized if list length > 60 (for both strategy)

If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
Ropsten
Proxy address: 0xbbe7f8062c2d6214af0451d8b4c3526ad88986ba
ExecID: 0x116fea137db6e131133e7f2bab296045d8f41cc5607279db17b218cab0929a51
If you were able to create it, what is the URL of your crowdsale?
http://localhost:3000/contribute?addr=0xbbe7f8062c2d6214af0451d8b4c3526ad88986ba&networkID=3
Do you have screenshots showing the problem?

Do you see errors in the dev console? If yes, please include a screenshot
No

@dennis00010011b do you have the Etherscan link to the failed transaction to add a big number of items into the whitelist in Ropsten?