HttpUnhandledException

World Creator throws this exception when I try to create Base Class Info/Merged Class Info new entry in the Persistent Class Info screen in General Tab.
The error occurred:
Type:       HttpUnhandledException
Message:    Exception of type 'System.Web.HttpUnhandledException' was thrown.
Data:       1 entries
		'ASPIMPERSONATING'		''
Stack trace:

at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.default_aspx.ProcessRequest(HttpContext context) in c:\Users\Vaas\AppData\Local\Temp\Temporary ASP.NET Files\vs\54e5db1e\48e4861d\App_Web_gon4xl1e.0.cs:line 0
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
----------------
InnerException:
		Type:       NullReferenceException
		Message:    Object reference not set to an instance of an object.
		Data:       0 entries
		Stack trace:

at Xpand.ExpressApp.WorldCreator.System.WCExtensions.Init(IPersistentTemplatedTypeInfo persistentTemplatedTypeInfo, Type codeTemplateType) in D:\a\1\s\Xpand\Xpand.ExpressApp.Modules\WorldCreator\System\WCExtensions.cs:line 59
at Xpand.ExpressApp.WorldCreator.Controllers.InitializeTemplatedTypeInfoController.OnViewControlsCreated() in D:\a\1\s\Xpand\Xpand.ExpressApp.Modules\WorldCreator\Controllers\InitializeTemplatedTypeInfoController.cs:line 13
at DevExpress.ExpressApp.ViewController.view_ControlsCreated(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at DevExpress.ExpressApp.View.OnControlsCreated()
at DevExpress.ExpressApp.View.CreateControls()
at DevExpress.ExpressApp.Web.Controls.ViewSiteControl.SetView(View view)
at DevExpress.ExpressApp.Web.Templates.BaseXafPage.SetView(View view)
at DevExpress.ExpressApp.Frame.SetTemplateView(View view)
at DevExpress.ExpressApp.Frame.SetTemplate(IFrameTemplate val)
at DevExpress.ExpressApp.Web.WebWindow.CreateControls(Page page, Boolean checkRequestParams)
at DevExpress.ExpressApp.Web.WebApplication.CreateControlsCore(Page page)
at DevExpress.ExpressApp.Web.WebApplication.CreateControls(Page page)
at DevExpress.ExpressApp.Web.Templates.BaseXafPage.CreateControls()
at DevExpress.ExpressApp.Web.Templates.BaseXafPage.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
InnerException is null

a sample will help resolving the issue

Gave sample project in #535 called Solution1.zip contains sample project.

I cannot reproduce this case, however it does not look direct related to the WorldCreator module. I suggest you try the solutions suggested from google
https://www.google.com/search?q=Loading+this+assembly+would+produce+a+different+grant+set+from+other+instances.&rlz=1C1CHBF_enGR824GR824&oq=Loading+this+assembly+would+produce+a+different+grant+set+from+other+instances.&aqs=chrome..69i57j0l4j69i60.2215j0j7&sourceid=chrome&ie=UTF-8

eXpand.lab release 19.1.602.6 includes commit that relate to this task:

WorldCreator: PersistentClassInfo base should be selected only from preexisting classinfo #534

Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
Thanks a lot for your contribution.

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


how to save ckpt  on each epoch end or N batches instead of N minutes?

As title describled,I want to save ckpt on epoch end or N batches,but I only find "ckpt_interval_minutes",thks!

Only time interval intra-epoch checkpoints are implemented in Brain. If you need to base it on number of steps, you gotta implement it yourself. You can override fit() - probably just copy the basic implementation and change the one if statement that looks at the time since last ckpt. You can access the number of batches seen with self.step.

I'll add some context for the choice of minutes over number of batches. We felt that basically minutes is the most relevant measurement here, since cluster compute is really reserved in wall clock time.

Lastly, if you want to base epochs on numbers of updates rather than seeing the full data, you can passlooped_nominal_epoch=<num_updates_per_epoch> in the training data loader options. See this documentation as well.

I'll add some context for the choice of minutes over number of batches. We felt that basically minutes is the most relevant measurement here, since cluster compute is really reserved in wall clock time.

Unfortunately not the most stable / reproducible one. E.g. if later on you want to resume from a checkpoint from a given iteration / epoch without checking what that should be. Working with checkpoint filenames on disk is also a bit simpler when they are stable. From the reproducibility standpoint, it might make sense to also support traditional checkpointing based on number of iterations or epochs.

Unfortunately not the most stable / reproducible one. E.g. if later on you want to resume from a checkpoint from a given iteration / epoch without checking what that should be. Working with checkpoint filenames on disk is also a bit simpler when they are stable and follow some simple pattern. From the reproducibility standpoint, it might make sense to also support traditional checkpointing based on number of iterations or epochs.

Thanks, the ease of working with predictably named checkpoints is worth considering. Even now, I think basically any workflow is possible, it's more a question of what methods are made most obvious and immediate. The epoch based checkpointing is actually the one that all the SpeechBrain examples and recipes offer as the default. The checkpointer allows the user to provide the name of the checkpoint, I would recommend using that for reproducible checkpoint names. If we want to base an experiment around number of updates, I think the LoopedLoader (looped_nominal_epoch argument) is a good tool, but I have only used it without caring about seeing every sample an equal number of times - would be nice to hear about experiences with both considerations simultaneously.
In some recipes I use a Checkpointer instance just to find a suitable checkpoint - that workflow could be made easier and documented a bit better. I think also making it easier to provide a direct path to a checkpoint and getting a Checkpoint namedtuple would be a simple but helpful addition.

Closing here. Please feel free to re-open.


export SelectQueryBuilderImpl

this is useful for users extending the library. I'm trying to add a method that allows the user to easily subquery a table, but I need access to the SelectQueryBuilderImpl class.
declare module "kysely/dist/cjs/query-builder/select-query-builder" {
  interface SelectQueryBuilder<DB, TB extends keyof DB, O> {
    ... patch types here
  }
}

SelectQueryBuilderImpl.prototype.selectNested = function (
  this: SelectQueryBuilder<any, any, any>,
  from: string,
  fromCol: string,
  toCol: string
) {
  return this.select((eb) =>
    jsonObjectFrom(
      eb.selectFrom(from).selectAll().whereRef(fromCol, "=", toCol)
    ).as(from)
  );
};

SelectQueryBuilderImpl.prototype.selectNestedArray = function (
  this: SelectQueryBuilder<any, any, any>,
  from: string,
  fromCol: string,
  toCol: string
) {
  return this.select((eb) =>
    jsonArrayFrom(
      eb.selectFrom(from).selectAll().whereRef(fromCol, "=", toCol)
    ).as(from)
  );
};

const res = await ky
  .selectFrom('user')
  .selectNested('role', 'user.roleId', 'role.id')
  .execute();
// returns User & { role: Role }

The class is an implementation detail and should not be exported. We're probably going back having SelectQueryBuilder as a class instead of an interface soon because of typescript performance issues.


[cxx-interop] Fix friend operators that come from class template specializations.

This is kind of related to: rdar://100021897 as it'd mean we don't have to use [] but just could use the find

@swift-ci please test

@swift-ci please smoke test


Sorted set inconsistencies.

SortedSetGetRank, SortedSetGetScore, and SortedSetRemove all reference elements by their value. However they all take those values in different ways...

SortedSetGetRank takes ElementName Value
SortedSetGetScore takes ElementNames []Value
SortedSetIncrement takes ElementName Value
SortedSetRemove takes ElementsToRemove which is SortedSetRemoveNumElements which is a struct containing just Name (not Value).

We're still referring to the "element name" rather than "element value" in these functions.

[ ] SortedSetGetScore takes Values []Value
[x] Rename SortedSetGetScore -> SortedSetGetScores
[ ] SortedSetGetRank takes Value Value

The request only takes a single value, because that's how Redis does it.
Chris says not to loop inside the method because something something concurrency.

[ ] SortedSetIncrement takes Value Value
[ ] SortedSetRemove takes Values []Value.

Remove the option to remove all. We can add it back later if necessary. Deleting a SortedSet can be done with client.delete(collectionName).

@schwern In case this isn't on your radar, it looks like sorted sets are inconsistent from the other types in that their Hit responses are using public properties instead of methods to expose values. All of the other CDT store their values as private data members and expose them to users as methods.

@pgautier404 In almost (dictionaryIncrement being an exception) every other case there's some need to convert the value. SortedSets largely return numbers (score or rank). The plan was to change them to simple type conversions and avoid having the user jump through an accessor. For example, type SortedSetRank uint64.

SortedSetFetch* needs String and Bytes methods. ✅
SortedSetGetRank returns a number.
SortedSetGetScores returns an array of numbers.
SortedSetIncrement returns a number.

I could add an accessor method for consistency 🤷 but I'd like to keep the single value types.

@pgautier404 I thought about it some more.
Because we're so inexperienced with Go, I think it's best to make all the struct members private and provide an accessor. We can always change it to a simple type conversion later.

@pgautier404 ...except responses are in a different package now, so we can't access private members.


Consumer to receive messages for new topic

Hello. If a consumer starts before a topic is created then it will never receive any messages. My scenario is:
1.Topic X does not exist
2.Consumer starts
3.Producer starts some time later and creates X
Consumer's log indicates that eventually the returned metadata includes the name of the new partition X. My guess is that OnPartitionsAssigned should trigger and make a new assignment.
So far i tried reducing "topic.metadata.refresh.interval.ms" this did not help. Setting "auto.offset.reset" in the Consumer's config throws. Is this expected?
What is the correct way for the consumer to start receiving messages? On a related note, is there any reason the consumer has to retrieve the whole list of topics? It is a consideration in case the list is large and the consumer needs to retrieve all that data for no reason.

I think that' one for upstream librdkafka.

Thanks you for the speedy reply. I have forwarded on the question.


Short solution needed: "Convert GD output to base64" (php-gd)

Please help us write most modern and shortest code solution for this issue:
Convert GD output to base64 (technology: php-gd)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments explain solution.
Link to this issue in comments of pull request.

Convert GD output to base64


license?

do you have a license for this?

MIT license

close w/ https://github.com/yusugomori/DeepLearning/commit/6b8af8891a94a1a25c15b5d5151f4bb59d0dab5f


Intent to add support for more Ubuntu versions

Hi, I'm planning to create a pull request that would add support for newer Ubuntu versions, at the very least Zesty. My current plan is to modify the Xenial patching script to download the proper kernel version (maybe rather with "apt source" than git), then create several versions of the *.patch files, i.e. uvcvideo-<kernel-version>.patch and apply them based on the kernel version.
Does this plan sound OK to you?
May I merge the 0001*.patch and 0002*.patch files together so they can be versioned easier?
Also, there is a script called patch-uvcvideo-ubuntu-mainline.sh that seems rather old and doesn't really work...should that be deleted?

Hello @mkollaro
We are planning to support more target Kernel versions with 4.8 being first on the list.
If you would be willing to contribute patches, scripts and documentation for any new configuration they will be gladly accepted. You can combine the patches as long as you keep the attributions in the header.
patch-uvcvideo-ubuntu-mainline.sh is in fact rather old. @ev-mp, could you take a look please?


Updating troubleshooting #1

Following convention that the license at the time the code was made available, is the license that applies to that code at that point in time, even if the license is changed later.

@fossygirl - This has two thumbs up, can we merge this PR?


Proposal for efficient shape_type

The shape_type for pyarray should be a friend class to pyarray that takes a reference to that pyarray, being a proxy on the numpy array shape buffer and dimensionality (by reference).

Implemented in #29.


feat: Decouple staking logic from the tier module

Description
This PR streamlines the Tier module by removing all interactions with the staking keeper (e.g., Delegate, Undelegate, BeginRedelegation, etc.) and introduces several fixes and improvements.
As a result, the developer stake will remain stored in the Tier module, so that it is no longer affected by slashing and won't be eligible for rewards.
Tasks

[x] Refactor Lock, Unlock, Redelegate, and CancelUnlocking.
[x] Get rid of unbondTime and only rely on unlockTime to complete the unlocking.
[x] Return error if no unlocking lockup found in SubtractUnlockingLockup.
[x] Expect unlockTime and completionTime to be nil instead of time.Time{} to reduce ambiguity.
[x] Add creation_height to  MsgUnlockResponse.
[x] Update and fix corresponding tests.

Codecov Report
Attention: Patch coverage is 95.16129% with 3 lines in your changes missing coverage. Please review.

Project coverage is 27.88%. Comparing base (24c0f5c) to head (50e8c29).

Files with missing lines
Patch %
Lines

x/tier/keeper/keeper.go
93.10%
1 Missing and 1 partial :warning:

x/tier/keeper/lockup.go
96.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              dev      #11      +/-   ##
==========================================
- Coverage   28.53%   27.88%   -0.65%
==========================================
  Files         148      148
  Lines        6225     6119     -106
==========================================
- Hits         1776     1706      -70
+ Misses       4336     4312      -24
+ Partials      113      101      -12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Don't know how to build task 'spec:models' (see --tasks)

When running rake spec:models I get the error:
"Don't know how to build task 'spec:models' (see --tasks) "
Even though rake -AT produces:
...
rake spec                               # Run all specs in spec directory (excluding plugin specs)
rake spec:controllers                   # Run the code examples in spec/controllers
rake spec:features                      # Run the code examples in spec/features
rake spec:helpers                       # Run the code examples in spec/helpers
rake spec:models                        # Run the code examples in spec/models
rake spec:prepare                       #
rake spec:statsetup                     #
...
Rails 5.0.1/Ruby 2.4/rspec-rails 3.5.1
I don't know if this is an rspec-rails issue, or a rake issue perhaps, or my own config issue??

I'd say somehow the rake task file isn't being detected by rake, what happens if you manually require 'rspec/rails/tasks/rspec.rake' in your Rakefile?

Here's what my Rakefile looks like after the change:
require_relative 'config/application'
require 'rspec/rails/tasks/rspec.rake'

Rails.application.load_tasks

But then just running the rake command gives:
LoadError: cannot load such file -- rspec/rails/tasks/rspec.rake
I'm using rvm and my gems are in a gemset, does that change what the path should be?  Thanks for the help!

Drat, you probably need the full path to include the file as it's not a ruby file. I'm pretty sure this is an issue with how Rake and Rails are interacting to include the file though.

@alexbrinkman did you add rspec-rails to your :development environment as well in your gem file? or just your :test environment?
If I have rspec-rails only in the :test group, then the rake tasks do not work.  But if I move it to :development, :test they work correctly.

@urkle - Thanks for the information, that worked.  I added rspec-rails to my development group too.  Previously it was just in test.  Thanks so much!


Genotyping multiple samples fails when RG ids are not unique (was "genotype multi samples.")

when i run freebayes on multi-samples which has different SM in @RG. The out of freebayes seems not to genotype every sample rather just give  genotype info for first sample.

Hi @kongdeju they need to have unique IDs and SMs in @RG. If you have the same ID then freebayes will treat them as the the same sample.
To verify that this is the issue please post the @RG lines from the BAM header.
You can fix this issue by running your files through bamadrg. Please report here if this does not fix the problem.
There should also be a check for this to avoid this particular type of corruption of the read groups, where multiple samples are defined within one read group. Is there not a warning message?
@AlistairNWard we need to find some way to check for these problems. Right now this seems to be the most common issue people are running into.

@ekg Thanks a lot for your reply. I will have a try.

@ekg  Yes,you are right. Thank you very much!


Mqtt enabled to properties

Provides the enabled property in the MqttProperties.
Question: Is this change necessary? If the MqttProperties bean is not provided this flag is set to false; if the property bean is provided the flag is true. So it somehow might not be necessary.

Question: Is this change necessary? If the MqttProperties bean is not provided this flag is set to false; if the property bean is provided the flag is true. So it somehow might not be necessary.

Hmm, you are right I think. Let's revert the change then and only go with the doc and dependency updates.


Initializers are not allowed in ambient contexts

- [x] bug report
- [ ] feature request

Versions.

@angular/cli: 1.0.0
node: 6.10.0
os: darwin x64
@angular/common: 4.0.0
@angular/compiler: 4.0.0
@angular/core: 4.0.0
@angular/forms: 4.0.0
@angular/http: 4.0.0
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 4.0.0
@angular/platform-browser-dynamic: 4.0.0
@angular/router: 4.0.0
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.0

Repro steps.

After migrating to 1.0 and doing ng serve I obtain the error: Initializers are not allowed in ambient contexts.
The log given by the failure.

ERROR in<EMAIL_ADDRESS>(9,33): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(10,43): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(11,42): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(12,43): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(13,35): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(34,33): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(12,33): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(1,33): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(15,37): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(8,42): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(9,41): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(10,45): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(11,44): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(14,41): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(6,28): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(10,30): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(15,30): Initializers are not allowed in ambient contexts.
<EMAIL_ADDRESS>(20,31): Initializers are not allowed in ambient contexts.

ERROR in<EMAIL_ADDRESS>(8,36): Initializers are not allowed in ambient contexts.

ERROR in AppModule is not an NgModule

Your TypeScript version is out of date. This is not a bug. Install the latest and if you get other errors, downgrade by point release until you get a working build.

It's a good idea to just destroy your node_modules folder and just do a clean install.

@aluanhaddad thanks for the feedback. I had already updated to the recent version (2.2.1), but I think I forgot to do a clean install.
Problem solved. Thanks.

They should but, from what I have read on the Angular blog, certain Angular features didn't work correctly correctly with<EMAIL_ADDRESS>I have not encountered any issues, and I have been running against the latest TypeScript  available, updating all major dependencies, including Angular and TypeScript within 2 days of a release on a production app using a continuous delivery model, with no issues.
Perhaps it works that scenario because the app does not use AOT.
AOT is a break from all standards. It deviates from the TypeScript specification, via ngc, in such a way that it violates the ECMAScript spec, meaning you are no longer writing standard or future standard compliant programs, you are writing Angular specific programs where syntax (decorators) has been redefined by ngc to mean something they never will in JS or TS.
AOT is a bad thing and it needs to die.

Thanks for the insight @aluanhaddad .

still have the same problem. i have TS 2.2.2.

@AbdelMonnem can you post the line that's raising the error?
The error experienced by the OP was likely caused by something like:
some-dependency.d.ts
export declare const value = 5;

This is illegal in TypeScript 2.0 but became legal in TypeScript 2.1 with the introduction of literal type inference for const declarations.

I tried to add material to a current project. Because I got some errors and I am new to Angular I started with a clean installation. I am using TS 2.2.2, but still have the above issue.
I used the following commands to create the project:
ng new material // using latest angular-cli version
cd material
npm install --save @angular/material
npm install --save @angular/animations
I then added the following line to app.module.ts:
import { MdButtonModule, MdCheckboxModule } from '@angular/material';
Executing"ng serve" I get a lot of errors, starting with the following one:
--> ERROR in<EMAIL_ADDRESS>(9,42): Initializers are not allowed in ambient contexts.
According to your getting-started.md I additionally added the following line to app.module.ts:
import {BrowserAnimationsModule} from '@angular/platform-browser/animations';
-->  A directory named @angular/platform-browser/animations does not exist in my node_modules directory. Even class BrowserAnimationsModule does not exist in any of the files in node_modules directory.
Have I missed anyting?
Best regards
Christian

I had the same error and fixed it by typing:
npm install --save typescript@latest
package.json now has the latest ts version and ts compiler is 2.2.2.
By the way: I used angular-cli to install a new angular based project. The version in package.json was something like 2.0.3.

That is why I don't think people should rely on scaffolders. They are handy but it is a must to know how to do things from first principles like @hbsts did.

I get an 'unmet peer dependency' for<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS> when I try to install<EMAIL_ADDRESS>However, when I look at package.json, all three of those are at ^2.4.10.
Any ideas?
PS: I saw the same initializers error as the OP in the exact same situation.

Closing as this doesn't seem to be an Angular CLI bug, but rather expected behaviour based on TypeScript versions.
@AneelaBrister Angular version 2 does not support the latest TS versions, you must stay in 2.1.x.

@filipesilva I don't know about the CLI, but I've ran npm:@angular/*@^2 against TypeScript dev builds that were well into typescript 2.3. Again, I don't use the CLI but it certainly works with the framework itself.

I had same issue, clearing and re installing node_modules helped.

while i'm using typescript:2.0.3,
it produces initializers are not allowed in ambient contexts.
the after upgrading to 2.1.4
it produces cannot read property 'exclude' of undefined typescript in main.ts
pls someone help to fix this

Why not use the latest stable TypeScript version? 2.1.4 is a fairly arbitrary place to start and it has been out of date for a while.

This is so much why using a pre-processor language for Angular 2 and greater was a bad idea. Native JavaScript is always best.
The Angular io docs for webpack, specifically the package.json, needs to be updated.

@dman777 You are complaining about transpilers when you have adopted a monolithic framework and a framework specific CLI on top of that. Transpilers do not restrict you.
Consider, that TypeScript is by default perfectly happy to emit code irrespective of any TypeScript errors including this one. These are tooling level errors, more like warnings, and thus non-blocking unless other tools get in the way (ex: ngc)

Right now, you have production documentation that is wrong with breakage. The package.json needs to be fixed.  Any newcomer, as myself, will do the walk through the docs and hit this error. That should be of greater importance than anything else.

What TypeScript version works? What's the command to change it?

Just use the latest 2.3.4

I updated typescript to 2.3.4 but I still have the error Initializers are not allowed in ambient contexts. here the gist : https://gist.github.com/rbinsztock/1da21750458133a29f7bfe114ff02417

I still have this problem. I have the latest typescript 2.4.1. I deleted node_modules and reinstalled all the packages, but I still have the same error - Initializers are not allowed in ambient contexts.
Here is my package.json:
{
"name": "webapplication2",
"version": "1.0.0",
"description": "",
"scripts": {
"test": "echo "Error: no test specified" && exit 1"
},
"author": "",
"license": "ISC",
"dependencies": {
"@angular/common": "~4.0.0",
"@angular/compiler": "~4.0.0",
"@angular/core": "~4.0.0",
"@angular/forms": "~4.0.0",
"@angular/http": "~4.0.0",
"@angular/platform-browser": "~4.0.0",
"@angular/platform-browser-dynamic": "~4.0.0",
"@angular/router": "~4.0.0",
"@types/node": "7.0.7",
"angular-in-memory-web-api": "~0.3.0",
"core-js": "^2.4.1",
"rxjs": "5.0.1",
"systemjs": "0.19.40",
"typescript": "^2.4.1",
"zone.js": "^0.8.4"
},
"devDependencies": {}
}
Here is my tsconfig.json:
{
"compilerOptions": {
"target": "es6",
"module": "es6",
"moduleResolution": "node",
"sourceMap": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"lib": [ "es7", "dom" ],
"noImplicitAny": true,
"suppressImplicitAnyIndexErrors": true
}
}

I solved my problem. It turns out VS2015 project file using TS2.0. After changed it to 2.2, the errors are gone.

Use the latest 2.4.2. VS tools version 2.4. You can download the latest tools from www.typescriptlang.org

for version 2.1.6 it throws error project requires version above 2.7.2 and after install 2.7.2 I get error ERROR in node_modules/@angular/core/core.d.ts(214,21): error TS1039: Initializers are not allowed in ambient contexts.
Fix this.


📜 Rolling logs and /log folder

As the title says, quite straightforward.
This is basically to stop our VPS dying from too many logs...!

watch out, the logs might roll away

;preview

;preview


example code missing .storage in package line

I think
package com.<your-resource-group>.<your-artifact-name>;

should be
package com.<your-resource-group>.<your-artifact-name>.storage;

given that BlobController.java is placed within a new subfolder "storage"
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ac19ce1b-2184-5487-67c9-22c4ff97336d
Version Independent ID: ecc6b6cf-73e4-1575-add0-cb44d7aa4fcf
Content: How to use the Spring Boot Starter for Azure Storage
Content Source: articles/java/spring-framework/configure-spring-boot-starter-java-app-with-azure-storage.md
Service: storage
GitHub Login: @KarlErickson
Microsoft Alias: karler

Hi, @KarlErickson
Could you please assign this issue to @backwind1233 ?

@asherk-kxs thanks for reaching out.
Below code snippets show all package names of Spring Cloud Azure docs:
package com.contoso.ssltest;
package com.wingtiptoys.servicebus;
package com.<your-resource-group>.<your-artifact-name>;
package com.example.demo;
package yourGroupId.yourGroupId.controller;
package com.wingtiptoys.security;
package com.contoso.eventhubs.sample;
package com.example.servicebus;
....

We will discuss how to improve it.


Main file error

@KrisKasprzak @CloudHead84 @luni64 downloaded the main file but arduino ide gives error of -
(Specified folder/zip file does not contain a valid library)
Later when i manually placed that file in my libraries folder the ide gave error-
(Invalid library found in C:\Users\Vaibhav Pandey\OneDrive\Documents\Arduino\libraries\TeensyStep4: no headers files (.h) found in C:\Users\Vaibhav Pandey\OneDrive\Documents\Arduino\libraries\TeensyStep4)

What Version of the IDE are you using?

@luni64
Arduino IDE - 1.8.19
Teensyduino - 1.56
Windows 10

I added the required manifests to make the Arduino IDE happy and fixed some other issues. Downloading the zip file and adding it with the IDE should work now. I tested building the examples with the Arduino IDE, both compile and work as expected
Hope that helps

@luni64
Much appreciated. It works now just need to see to if the stepper works accordingly.
Thanks.


docs(README): improve https and proxy agent documentation

🔗 Linked issue
#379, #215, #316
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
agent setting only applies to older versions of node.
As of version 18 node fetch is native and depends on undici, which uses a dispatcher option instead
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

https://undici.nodejs.org/#/docs/api/ProxyAgent?id=example-basic-proxy-request-with-local-agent-dispatcher


Add a rule using the maven-enforcer plugin that requires Maven 3.6.3

@madhukarbharti ,
The username under which you're committing and pushing to Github seems to be mis-configured. You will have to look into how to configure your git settings properly, amend the author of the commits and then force push back to the branch. (When your user is properly set up, you see your avatar when against your commits in the commit history, otherwise it's a default grey avatar).

Raised New PR: https://github.com/strongbox/strongbox-parent/pull/99 so closing duplicate one


Add ability to customize font size

Added an ability to customize font sizes. This is set at a new section in the settings.
The controler for this sets a number of css variables which are used in css rules that
override tailwind's text- to use the font size and line spacing contained in the
variable. The control itself is a simple logarithmic slider that controls a "scale
factor" by which all the text sizes in a resume are scaled by.
Fixes #379 #325 #256

One thing this is currently missing is localizations for the setting name is called outside of the English version.

@rpolley thanks for the PR. I was waiting for this for a long time.
@AmruthPillai Can you merge this PR. This is a feature we all really need. BTW will checkout and try to run the application from this PR.

Reviewing it now :)

Reviewing it now :)

@rpolley @AmruthPillai I can see the font size slider and it is changing size on UI. But while exporting the resume the font size is still the same. Not changing in the final exported PDF. Am I the only one facing this issue?

@rpolley @AmruthPillai I can see the font size slider and it is changing size on UI. But while exporting the resume the font size is still the same. Not changing in the final exported PDF. Am I the only one facing this issue?

@vijay-yadav-3 @AmruthPillai from what it looks like none of the settings currently get serialized at all when exporting the resume.

@vijay-yadav-3 @AmruthPillai from what it looks like none of the settings currently get serialized at all when exporting the resume.

I actually added the serializing into JSON portion of the code in a subsequent commit after @rpolley's PR. That should be a part of it, and from what I can wee, it does preserve font size when refreshing the page too. Is the font size even when they are on the /r/:resumeId page? That is the page used to export PDFs too, so it should be visible there.

I actually added the serializing into JSON portion of the code in a subsequent commit after @rpolley's PR. That should be a part of it, and from what I can wee, it does preserve font size when refreshing the page too. Is the font size even when they are on the /r/:resumeId page? That is the page used to export PDFs too, so it should be visible there.

Fixed in v2.5.2 :)

Fixed in v2.5.2 :)


value of type 'Self' has no member 'hopped'

/Users/jimmyhoughjr/vapor-auth-template/Sources/App/Jobs/EmailJob.swift:47:14: Value of type 'Self' has no member 'hopped'
I ran swift package update then swift build in command line. Then built in Xcode with the same error.

I wonder if         // Mailgun         .package(url: "https://github.com/vapor-community/VaporMailgunService.git", .branch("mads-updates")) is related?

Hey! Yea sorry about that, made some changes to that Mailgun branch which I forgot to update here. This has been fixed in #2 - basically you need to use .delegating(to: EventLoop) instead of hopped(to: )

thanks for the quick fix. I'll pull again and test soon.

works.


[Enh]: Consider adding __slots__

We would like to learn about your use case. For example, if this feature is needed  to adopt Narwhals in an open source project, could you please enter the link to it below?
n.a.
Please describe the purpose of the new feature or describe the problem to solve.
To keep the overhead introduced by narwhals objects as low as possible (both in memory and access speed), we could consider using __slots__ since:

we don't have dynamic attributes
everything falls back to be attribute access and manipulation

If for some use case a library needs to dynamically add attributes to a narwhals object, we can suggest to inherit from the original narwhals implementation.
Suggest a solution if possible.
No response
If you have tried alternatives, please describe them below.
No response
Additional information that may help us understand your needs.
Hard to figure out how to benchmark this

Added this locally and diff is less than expected. All tests are passing. If there is interest I will open a PR

sure - I don't really know what it does but if there's no regression and it improves things, sounds like a good idea

Hi all! I saw this issue, which reminded me of some investigation I did myself for my team a few months back. Our conclusion was that __slots__ really only make sense if you expect to create many instances of a class in the same code (e.g. you would create many Car objects in a simulation of traffic flow). Otherwise, it introduces additional overhead (e.g. with child classes) and complexity. Slots are not a concept that many people are familiar with and also blocks access of the __dict__ attribute, which does have its uses. In the end, we concluded that using __slots__ was not worth all the trouble.

Hey @mikeweltevrede thanks for your input. This is very valuable.
My main concern is regarding both creating new instances and accessing attributes - as the layer Narwhals adds one or more attributes access for each method, and returns a new instance most of the time.
While in most cases this overhead is neglectable, I would like to make sure that it is as low as possible and it does not add up to something significant in cases of a complex series of steps.


fixed panic in isAllowed

Coverage decreased (-0.01%) to 86.409% when pulling fb6b25045da39e87bbcffaac5b1ad84d0c3590ad on dissoupov into 379b55432863573548b8fda865de8a590d13b1f3 on main.


Support the MSVC and GCC

Closes: #431

The default CXXCompiler is Clang
If you want to use a compiler other than Clang, please use --CXXCompiler gcc or --CXXCompiler msvc
If you want to use MSVC, be sure to use Visual Studio Developer Command Prompt or Visual Studio Developer PowerShell

I finished this PR, btw

Does the description of the repository need to be changed
And why aren't Github discussions in the main repository?

I finished this PR, btw

Thanks, I'll look at the changes later today.

Does the description of the repository need to be changed

Why would the description have to change?

why aren't Github discussions in the main repository? Wouldn't that make easier to access(jump)?

We thought it would be best to keep all discussions not related to the compiler implementation in a separate repository. You can easily access them by hoping through the organization's page.

I simply thought we would have the Library in this repository, so I just mention it

After we got the LLVM back end, wasn't it difficult to support interoperability support for multiple versions of CXXCompiler?
As far as I know, Carbon only plans to interoperate with Cpp when using the Clang compiler
Or maybe you're not talking about the LLVM back end?
@kyouko-taiga

After we got the LLVM back end, wasn't it difficult to support interoperability support for multiple versions of CXXCompiler?

Yes and no.
Currently, the transpilation story is completely orthogonal to LLVM. That's because the transpiler just walks Val ASTs and generate C++ text. We can continue to operate that way as long as we can afford a second-class interoperability from C++ to Val, i.e., use a C++ API inside a Val program.
In that picture, LLVM is just another backend and generating LLVM IR is no different than generating Javascript sources.
Once we want C++ to Val interoperability, however, we'll need a way to read C++ sources to generate the corresponding Val APIs and necessary glue code. I plan on using clang to do that, meaning there's a connection to LLVM at this point. I have almost no idea how we'll deal with ABI, but I suspect that's the point where we'll diverge more and more from other compilers.

@kyouko-taiga

I think this PR can be merge @kyouko-taiga

I think that's all done @kyouko-taiga


[Chip] Chip with onDeleted but without onPressed has no ripple when tapping delete button.

Description
On a chip with a delete button but without onPressed, there is currently no ripple on the delete button when it is pressed.
Behavior before merging #42779

Tapping on a chip with only onPressed creates one ripple;
Tapping on a chip with onPressed and onDeleted on the delete icon creates two ripples, one for the whole chip and one for the delete icon; (unexpected)
Tapping on a chip with only onDeleted creates one ripple;
Tapping on a chip with neither onPressed nor onDeleted creates no ripples.

(Highlights are not counted as ripples.)
The pull request #42779 fixes the issue b/140930220; after #42779, there is only one ripple when the delete icon is tapped on a chip with onPressed and onDeleted. But this pull request creates the following behavior:
Behavior after merging #42779 (current master)

Tapping on a chip with only onPressed creates one ripple;
Tapping on a chip with onPressed and onDeleted on the delete icon creates one ripple for the delete icon only;
Tapping on a chip with only onDeleted creates no ripples; (unexpected)
Tapping on a chip with neither onPressed nor onDeleted creates no ripples.

(Tapping the delete button still calls onDeleted as expected. Holding down the delete button still shows a tooltip.)
Expected behavior

Tapping on a chip with only onPressed creates one ripple;
Tapping on a chip with onPressed and onDeleted on the delete icon creates one ripple for the delete icon only;
Tapping on a chip with only onDeleted creates one ripple for the delete icon only;
Tapping on a chip with neither onPressed nor onDeleted creates no ripples.

Clarifications are needed for the following behavior:

When a chip with a delete button is pressed (on the delete button), should the whole chip be highlighted?
When a chip with a delete button is pressed (on the delete button), should the whole chip be elevated?

Related issues

b/140930220
This issue is blocking PR #41463 (has caused #41463 to be reverted).

Steps to reproduce

Create a new flutter project and save the following code as main.dart.
Run the project (with flutter on branch master).
Press and hold different parts of each chip to see how the ripples behave.

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RawChip(
                label: Text('Chip with onPressed'),
                onPressed: () {},
            ),
            RawChip(
                label: Text('Chip with onPressed and onDeleted'),
                onDeleted: () {},
                onPressed: () {},
            ),
            RawChip(
                label: Text('Chip with onDeleted only'),
                onDeleted: () {},
            ),
            RawChip(
                label: Text('Inactive chip'),
            ),
          ],
        ),
      ),
    );
  }
}

Screenshots

Test app

Tapping first chip

Tapping second chip

Tapping delete icon on second chip (master)

Tapping delete icon on second chip (previous version)

Tapping delete icon on third chip (previous version)

Issue still exist
[✓] Flutter (Channel dev, v1.18.0, on Mac OS X 10.15.4 19E266, locale en-GB)
    • Flutter version 1.18.0 at /Users/taha/Code/flutter_dev
    • Framework revision de1e572916 (13 hours ago), 2020-04-06 16:15:07 -0700
    • Engine revision df257e59c2
    • Dart version 2.8.0 (build 2.8.0-dev.20.0 1210d27678)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.0.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.43.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.9.1

[✓] Connected device (5 available)
    • SM M305F      • 32003c30dc19668f          • android-arm64  • Android 10
      (API 29)
    • Taha’s iPhone • 00008020-001059882212002E • ios            • iOS 13.4
    • macOS         • macOS                     • darwin-x64     • Mac OS X
      10.15.4 19E266
    • Chrome        • chrome                    • web-javascript • Google Chrome
      80.0.3987.149
    • Web Server    • web-server                • web-javascript • Flutter Tools

• No issues found!

multiple flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale
    en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (12 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.17.0

[✓] Connected device (2 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64 • Android
      10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios           • iOS
      14.3

! Doctor found issues in 1 category.

[✓] Flutter (Channel dev, 1.26.0-1.0.pre, on macOS 11.1 20C69 darwin-x64, locale
    en-GB)
    • Flutter version 1.26.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision 63062a6443 (9 days ago), 2020-12-13 23:19:13 +0800
    • Engine revision 4797b06652
    • Dart version 2.12.0 (build 2.12.0-141.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Applications/Android/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Android Studio not found at /Applications/Android/Contents
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.17.0

[✓] Connected device (4 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS
      14.3
    • macOS (desktop)      • macos                     • darwin-x64     • macOS
      11.1 20C69 darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google
      Chrome 87.0.4280.88

! Doctor found issues in 1 category.


AWS provider should default to use itsown storage service

Hi,
When running the following command:
./pkb.py --cloud=AWS --benchmarks=object_storage_service
it deploys a VM on AWS and then from the VM, it  runs this particular  benchmark on Google storage. I am assuming this is a bug or maybe it's by design?
One should expect AWS provider uses S3 instead of Google storage.

It is by design, but I agree that the more intuitive behavior would be to run on the storage service from the same provider as the VM. I'm assigning this to myself, but I don't know how quickly I will have time to work on it. If you want to implement it yourself in the mean time, I would be glad to help.

@noahl
Hi, thanks! No hurry.
It works with explicit "--storage=AWS" just seem redundant.

This is by design so I'm going to close this.  Really it should just default to Azure Blob storage :)


Enable OIDC extension in Provisioner

Description
The Gardener OIDC extension is important for several important customers of Kyma. Caused by some delays in the rollout of KIM, we decided to enable this extension already in the Provisioner to unblock our customers in their goals.
Related line is:
extensions:
   - type: shoot-oidc-service  #this line enables OIDC extension

We will enable this OIDC extension in all new created Gardener clusters. Shoot-Specs of existing clusters will NOT be updated!
AC:

[ ] Enable GArdener's OIDC extension per default in all shoot-specs of new created clusters

Appendix:

Gardener Docs: https://github.com/gardener/gardener-extension-shoot-oidc-service/blob/master/docs/usage/openidconnects.md

Hi @tobiscr , is there some documentation added / planned in help.sap.com to let SKR users know how they can use it?

This is actually not the official feature we want to deliver. We enabled the OIDC extension in Provisioner only because we had customers who were blocked in their go-live.
The official feature is https://github.com/kyma-project/kyma/issues/18305. But we need first to migrate KIM on Production and also KEB has to make additional OIDC-providers configurable via BTP cockpit.
The documentation will happen for the the feature is fully supported.


Update Cleave 1-5 (6  is seperate PR)

Why is 6 a seperate pr

idk something went wrong and it auto pr'd cleave 6


Workflow not starting when the manifest is uploaded from Litmus-Portal

Details
What happened: While uploading the manifest from Litmus Portal, the workflow is not getting started.
What you expected to happen: While uploading the manifest, the workflow name should be updated in the manifest.
Anything else we need to know?:  While uploading the manifest from Litmus Portal, there was no provision to update the workflow name.

Workaround
Current work-around is to update the name manually using the YAML editor provided in the Tune Workflow screen.
With the fix, the workflow name will be updated in the manifest while uploading:

This issue has been resolved and added to master branch with PR: https://github.com/litmuschaos/litmus/pull/2487

@AmitKumarDas Can we close this issue?

Yes @rajdas98 . Closing this issue.


Discrepancies in time fields precision between Admin API responses and Webhook requests for Posts

Issue Summary
Time values in updated_at field and other time fields also are different in API responses and Webhook requests.
API response nullifies milliseconds while Webhook request includes milliseconds.
Example API response:
{
  "posts": [
    {
      "uuid": "39c42a38-5c4a-4405-981f-ff3f84b86568",
      "created_at": "2021-03-14T15:02:26.000Z",
      "updated_at": "2021-03-14T15:02:26.000Z",
      "published_at": "2021-03-14T15:02:26.000Z",

"Post published" Webhook request for this post:
{
  "posts": [
    {
      "uuid": "39c42a38-5c4a-4405-981f-ff3f84b86568",
      "created_at": "2021-03-14T15:02:26.033Z",
      "updated_at": "2021-03-14T15:02:26.033Z",
      "published_at": "2021-03-14T15:02:26.034Z",

You can see milliseconds included into latter request but missing in former. I've encountered this during writing sync engine between Ghost and other sources. Since I use same server for updating ghost and receiving webhooks, I use updated_at field do determine, if post was edited by my system or by user.
To Reproduce

Create POST via admin API.
Recieve webhook for created post.
Notice difference in milliseconds.

Excepted result: datetime fileds are same.
Technical details:

Ghost Version: 3.41.3
Node Version: v12.19.0
Browser/OS: Linux
Database: SQLite

Thanks for the report! I can see why that would be an issue.
We'll try to take a look at this soon but in the meantime a PR would be welcome!


deeply nested relations do not inherit context

functions from an inherited Model don't have context
return Model
.join({athlete: 'user'})
.get(invId)
.exec()
.then((result) => {
  account = result;
  console.log(account.context); //HAS CONTEXT
  console.log(account.athlete.context); //HAS CONTEXT
  console.log(account.athlete.user.context); //DOES NOT HAVE CONTEXT
  return user = account.athlete.user;
})

I fixed the original issue, just to run into the same problem with "new" records.  My latest pull request will fix both issues

I have discovered that deeply nested new records are not saving unless I explicitly save it's parent


Speed up GetSkillDamage

Speed up by creating versions of the method specific to each Comp so we don't have to search for the Comp. Also use less variables since this is called on CompTick.

Accepted


Overhaul PrepJSInterop to be simpler, more uniform, with less code paths.

PrepJSInterop was a huge bag of spaghetti code, with more checks added on top of the existing checks as the years passed, without ever reconsidering the code paths.
This commit is a major overhaul of that phase, which several advantages.
First, we clearly separate the handling of a) member defs, b) templates and c) statements/expressions.
Second, checks are structured hierarchically so that each check is performed at exactly one place, rather than being repeated for every kind of member def that requires the checks. This makes it much easier not to forget obscure combinations of features that would be missing checks. As a "proof" of that claim, each non-helper method is called from exactly one call site. (A helper method only inspects some properties of a symbol, as opposed to performing real checks, reporting errors, mutating the symbol table and/or transforming the tree.)
Exceptions are:

validateJSConstructorOf, called both from the transformation of js.constructorOf[T] and that of js.ConstructorTag.materialize[T]. This could be avoided by re-transforming the tree generated by the materialization, but that would perform useless work.
checkSetterSignature, called both for setters in JS types and exported setters in Scala types.
checkRHSCallsJSNative, called both for concrete members in native JS types and for native JS vals and defs.

It's worth pointing out that, due to correctly centralizing everything, there is a possibility that, after this commit, errors will now be reported for incorrect code that was slipping through the cracks before. According to our versioning policy, this is supposed to warrant a minor release.

It's worth pointing out that, due to correctly centralizing everything, there is a possibility that, after this commit, errors will now be reported for incorrect code that was slipping through the cracks before. According to our versioning policy, this is supposed to warrant a minor release.

IMO that just means we fixed bugs. Especially if the definition of incorrect code didn't change.
But it is true that the versioning policy does not distinguish these two things. Personally, I think it crucial it does. Further, we seem to have applied this reasoning, the fix to #3976 being a recent example.

I don't see the link with #3976. There was no code that would compile before its fix and wouldn't compile anymore after the fix.

IMO that just means we fixed bugs. Especially if the definition of incorrect code didn't change.

Yes, in the case of this PR it would only be fixing bugs. Yet despite that, in the 0.6.x series we used to introduce warnings instead of errors when we deliberately added checks that we had not thought about before.

I don't see the link with #3976. There was no code that would compile before its fix and wouldn't compile anymore after the fix.

The link is in the wording of VERSIONING.md: #3976 would be considered "a backward incompatible change" if "backward incompatible" would include bugs. This is because an alternative implementation of System.identityHashCode would be replaced.
In that case, this change would be a

Backward source incompatible change at the language level or at the standard library level (including any addition of public API in the stdlib)

indeed warranting a minor version bump.

Yet despite that, in the 0.6.x series we used to introduce warnings instead of errors when we deliberately added checks that we had not thought about before.

Fair enough. I'm willing to attribute this to the ambiguity of specification itself.
In any case, all things considered, I do not think we should bump minor for this PR. However, I do not feel very strongly about it.

In any case, all things considered, I do not think we should bump minor for this PR. However, I do not feel very strongly about it.

OK, let's keep it as is, as a patch version.


Undefined variables included in query string

Variables with a value of undefined are included in the query string.
For example:
var url = new Url();
var url2 = new Url();
url2.clearQuery();
url2.query["var"] = url.query["var"];
ur2.query.toString()
If "var" doesn't exist in the query string, this will print out "var=undefined".  Could undefined variables be ignored?

fixed in v2.2.0


invalid or unknown key: server_side_encryption

variable "region" {
  default = "ap-southeast-1"
}

provider "aws" {
  region = "${var.region}"
}

module "terraform_state_backend" {
  source = "git::https://github.com/cloudposse/terraform-aws-tfstate-backend.git?ref=master"
  namespace = "master"
  stage = "master"
  name = "mediapop"
  region = "${var.region}"
}

gives:

Error: module.terraform_state_backend.aws_dynamodb_table.default: : invalid or unknown key: server_side_encryption

@kitsunde
thanks for testing!
what Terraform version are you using?
they just recently (in March) added DynamoDB server-side encryption to the AWS provider
https://github.com/terraform-providers/terraform-provider-aws/pull/3303
https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#1110-march-09-2018
can you update to the newest TF version and retest?

I’m using the latest available on macOS 0.11.5. It’s possible it’s because I’m trying to do it in SG, I switched to a different module.

From: Andriy Knysh<EMAIL_ADDRESS>Sent: Tuesday, April 3, 2018 9:04:19 PM
To: cloudposse/terraform-aws-tfstate-backend
Cc: Kit Sunde; Mention
Subject: Re: [cloudposse/terraform-aws-tfstate-backend] invalid or unknown key: server_side_encryption (#2)
@kitsundehttps://github.com/kitsunde
thanks for testing!
what Terraform version are you using?
they just recently (in March) added DynamoDB server-side encryption to the AWS provider
terraform-providers/terraform-provider-aws#3303https://github.com/terraform-providers/terraform-provider-aws/pull/3303
https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#1110-march-09-2018
can you update to the newest TF version and retest?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudposse/terraform-aws-tfstate-backend/issues/2#issuecomment-378242404, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAC_RbCXXpMFuTMXTn3Ygxbo4b4koIl-ks5tk3NTgaJpZM4TEqj-.

Will close this for now. Please reopen if you're still having trouble.


Added fix so rheostat won't break in React v15

We should probably drop support for 0.13.x

I don't think we should drop support for 0.13 at least until Facebook has released 16. In other words, I think we should always support "latest + 2 versions back".

Shall I wait until there is a final call, if you want to drop or keep support for 0.13.x?

Why 2 versions? +1 seems good enough especially since deprecations usually happen between version.
https://facebook.github.io/react/blog/2016/02/19/new-versioning-scheme.html#avoiding-the-major-cliff

We can discuss it offline, but that's the policy enzyme is maintaining already, and it's also the policy that node itself maintains. 2 versions because providing an upgrade path is critical, and just because 16 comes out doesn't mean everybody will have stopped using 0.14.

Yeah but node follows a different version scheme.
You could also say the same case about people and React 0.13 when v16 comes out. I think most people are on v15 whenever 16 comes out and if they're not then they can just use an older version of this package (we can even backport bug fixes if we need to).
Enzyme is also doing that weird package.json hack so that's probably why it's maintaining a -2 version path. I'm not necessarily tied to keeping that hack around throughout versions.

That version scheme stopped applying once io.js/node 4 came out.
Enzyme is explicitly maintaining support for "latest minus 2", and will continue to do so. We'll drop 0.13 once v16 comes out. I strongly prefer rheostat to do the same.

Would you describe what is broken? I am new to using this component (I am using React 15.1.0).

Since my last comment, I see what is broken. Any ideas as to when the pull request will be merged in?

Closing this in favor of #26.


Release Process

Considerations:

Lead time for downstream projects/platforms to consume
Versioning (as detailed in #4)
Prep branches and deploy previews (either as interim releases for acceptance testing or, for sites/sandboxes, Netlify)
Tagging, release to repos and distribution
Security vulnerabilities (and dependency scanning)
Coverage?
Static analysis?
API Docs

These will likely look different for platforms (ie. tbDEX, Web5) and component projects (where fewer guidelines will apply and project leads take more autonomy).

I wanna add that JSDocs should be required for the release process where applicable. I also feel like we can be making use of GitHub Actions to automate or make reports on some of the things listed here.


Add new forex support

Closes https://github.com/zackurben/alphavantage/pull/81 and adds the remaining support for the other new forex endpoints.

Coverage decreased (-1.05%) to 93.548% when pulling b502b61d29553c681e0cc74286ac9e7da470adaa on add-new-forex-support into 1aaed0e2e1eeea1a7c1d376993bc08cb0b79f124 on master.


How to freeze an account

when i use eos to set up private network, how can me freeze an account like eos?

To disable an account, set the keys of the account to null, as described in the documentation.
From the documentation:
$ cleos push action eosio updateauth '{"account": "eosio", "permission": "owner", "parent": "", "auth": {"threshold": 1, "keys": [], "waits": [], "accounts": [{"weight": 1, "permission": {"actor": "eosio.prods", "permission": "active"}}]}}' -p eosio@owner
$ cleos push action eosio updateauth '{"account": "eosio", "permission": "active", "parent": "owner", "auth": {"threshold": 1, "keys": [], "waits": [], "accounts": [{"weight": 1, "permission": {"actor": "eosio.prods", "permission": "active"}}]}}' -p eosio@active

I want to using eosio permission to freezing other common account, like BP nodes

像报道里面的一样作为超级节点冻结其他账户和恢复其他账户 应该怎么办

The same procedure applies to any account.  Just change the account name in the command to the desired account.


Improve docs layout

Changes navbar layout:

Change docs sidebar layout and add index cards:

I think the docs look better this way, @fargito WDYT ?

This is great, thanks a lot!


No DFU capable USB device available

After flashing the Renesas MCU with the bootloader using the latest version of Renesas Flash Programmer, the serial port still display as RA USB Boot(CDC) and I get No DFU capable USB device available (exit status 74).
I have a Arduino Uno R4 WiFi but I soldered the RA4M1 USB bridge under the board. I have tried both bootloader for the Uno R4 WiFi and Minima and none of the works. In each case I've got operation completed and the flashing is successful when I flash the bootloader.
My goal is to flash Tasmota on the ESP32S3 of the Arduino Uno R4 WiFi (which works) and communicate with the Renesas chip by having Firmata installed on it and communicate via the shared UART.

ok, I found the solution. There is a unlabeled pin just beside IOREF (boot in the pinout or MD in schematic). When you put a jumper on that pin to ground and reset the board, you end up in RA USB Boot with a VID 0x045B and PID 0x0261. When you put that pin to 5V and reset the board, you end up with the correct minima USB Serial port with VID 0x2341and PID 0x0069.


I should be able to boot from a volume rather than local storage

We had a user on slack that was attempting to deploy a VM with a flavor set to 0GB root and ephemeral disks. They referenced this bug as the rational.
Looking at the code, there appears to be a boot_from_volume property that looks promising. However, the size of this volume is still determined by the disk size defined in the flavor. It seems like making the boot volume size independently configurable and listing the boot_from_volume property on the main CPI doc on bosh.io should solve the user's use case.

cc @voelzmo

Thanks for the highlighting, @cppforlife :) I was a few days out of office, sorry for the delay.
I guess it makes sense to have the root disk size adjustable. I'll adjust the linked story in our backlog and put in something similar to AWS's ephemeral disk in the resource_pool. Does that sound reasonable?

Marking as open-for-contributions as we've got different priorities for now. For anyone who likes to take shot at this: I've added more detailed tasks and background info in the corresponding tracker story

Implemented in release v25.


V3/turbine grid visualization

This adds a visualization package to plot the turbine grid across all atmospheric conditions.
Note This is a work in progress.
Dependencies

#8

@rafmudaf I think I missed a dimension when expanding this out originally. My latest commit should do the trick though. In case you want to test it out, you can run a simple script i pasted below based off the jensen/jiminez regression test.
import numpy as np

from src import Floris
from src.tools.visualization.values_at_rotor import plot_rotor_values

from tests.conftest import SampleInputs

DEBUG = False
VELOCITY_MODEL = "jensen"
DEFLECTION_MODEL = "jimenez"

sample_inputs_fixture = SampleInputs()
sample_inputs_fixture.floris["wake"]["properties"]["velocity_model"] = VELOCITY_MODEL
sample_inputs_fixture.floris["wake"]["properties"]["deflection_model"] = DEFLECTION_MODEL

floris = Floris(input_dict=sample_inputs_fixture.floris)
floris.go()

n_turbines = len(floris.farm.turbine_id)

test_results = []

velocities = floris.flow_field.u[:]

# 1 Wind directions, 3 Windspeeds, 3 Turbines
titles = [
    [
        f"wd: {sample_inputs_fixture.farm['wind_directions'][0]}, ws: {ws}, T: {t}"
        for t in range(1, 4)
    ]
    for ws in sample_inputs_fixture.farm["wind_speeds"]
]
titles = np.array(titles).reshape(1, 3, 3)
res = plot_rotor_values(velocities, titles, return_fig_objects=True, max_width=3, save_path="sample_image.png")
res = plot_rotor_values(velocities, return_fig_objects=True, max_width=3, save_path="sample_image_no_titles.png")

And this has immediately proved to be super helpful. Thanks @RHammond2!


chore: remove println call when flipping state changed

I propose to remove this line:
println("Flip Controller $it")
This is some debug information that might not be interesting to keep in production.

@wajahatkarim3 Any chances that this P.R could be merged ? :)


Remove exception handling ssh

Codecov Report

Merging #733 (da37bb2) into master (576abac) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #733      +/-   ##
==========================================
- Coverage   41.41%   41.40%   -0.02%
==========================================
  Files         341      341
  Lines       25337    25331       -6
==========================================
- Hits        10494    10488       -6
  Misses      14843    14843

Flag
Coverage Δ

unittests
41.40% <100.00%> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

dbaas/physical/ssh.py
79.38% <100.00%> (-1.21%)
:arrow_down:

Continue to review full report at Codecov.

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


mingw error on devel because of too big of a file

Description
C:/rtools40/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/as.exe: test/unit/math/mix/fun_30_test.o: section .pdata$_ZN4stan4test8internal12test_hessianIZZNS1_16expect_ad_helperIZN19lub_constrain_tests10expect_vecISt6vectorIN5Eigen6MatrixIdLin1ELin1ELi0ELin1ELin1EEESaIS9_EES9_SB_EEvRKT_RKT0_RKT1_EUlSE_SH_SK_E_ZNS1_13expect_ad_vvvISL_SB_S9_SB_EEvRKNS0_13ad_tolerancesESE_SH_SK_RKT2_EUlSE_E0_JSB_S9_SB_EEEvSP_SE_SH_RKNS8_IdLin1ELi1ELi0ELin1ELi1EEEDpT1_ENKUliE_clEiEUlSE_E_EEvSP_SE_SW_db: string table overflow at offset 10000302

C:\Users\Administrator\AppData\Local\Temp\ccXJOQze.s: Assembler messages:

C:\Users\Administrator\AppData\Local\Temp\ccXJOQze.s: Fatal error: can't close test/unit/math/mix/fun_30_test.o: file too big

Do we need to break up the tests more for mingw?

Do we need to break up the tests more for mingw?

No, this is due to jumbo tests that are used for RTools 4.0. We need to descrease jumbo size again for Windows, though I did that just a few days ago https://github.com/stan-dev/math/pull/2394 and am now inclined to just turn it off for windows.
No tests will pass right now as both machines that could run OpenCL are offline. @bgoodri will not be on premises for a while so I am guessing the only reasonable thing is to turn off OpenCL tests for awhile which is really really bad but at least wont halt other development. The Linux machine sometimes comes back up on its own but hasnt in the 16 hours now so that seems less and less possible now.

Okay in the interlude @t4c1 if you want another machine to run the opencl tests lmk and I can run them on my gpu/cpu locally at least as a spot check


Add support for segmented representations

This adds support for segmented representations, which are homogeneous "chunks" of fixed-length "sub-vectors", or lists within lists.  These are commonly used for Pitt Approach systems, among others.

[ ] initializer
[ ] decoder
[ ] mutate
[ ] jupyter notebook
[ ] test harness
[ ] documentation

Merged into develop, though I still need to add real-valued equivalent in real_ops and in the jupyter notebook.

To do for today:
[ ] Add example of real-value use to jupyter notebook (which will also be a test of the code)
[ ] Add unit tests
Will still need to work on ReadTheDocs documentation for segmented representations, but given the spate of meetings I have in the afternoon, I probably won't have time.

Continuing work today

Finished updating real-valued mutation to accommodate segmented representations, which had the nice side-effect of simplifying real-valued mutation.  Jupyter notebook updated to demonstrate this capability.
Now to put in at least some primitive unit tests for segmented representation.

Going to close this out since the actual coding is done.  Need to merge into develop as I don't want the code to continue getting out of sync with other changes, and we're planning on doing a release today, if possible.

Going to close this out since the actual coding is done.  Need to merge into develop as I don't want the code to continue getting out of sync with other changes, and we're planning on doing a release today, if possible.


In the hosting window, the 'free' amount interferes with the 'max' amount

you might just need to make the window larger, at some point I think we can't support tiny resolutions in the UI.


Apply bootswatch theme to narrative col and sticky col

One thorny thing that needs to be sorted out: right now the addition of bg-light by default screws with the nytimes demo. What's the best way to sort that out so that the nytimes styling takes precedent?
Perhaps by requiring that any secondary theme specify all of the style attributes specified by the bootswatch theme otherwise it's fine to use bootswatch?

If you feel like you've gotten this to a good place as of our call, I'm happy to keep it as is, but I feel like we might benefit from guidance from the Quarto team on this one, since we're essentially guessing at some of the stuff about how SCSSfiles are merged in. Happy to file an issue/discussion if you think it's worth it!
What I do know is that SCSS files get interleaved: they have sections like /*-- scss:defaults --*/ (to set up variables) and /*-- scss:rules --*/, and those get individually combined across all SCSS files before the end result is collated (so all the defaults sections stay together, all the rules sections stay together, etc.)
I think ideally our rules would just touch layout in the CR sections, and we'd set a few CR-specific variables in the defaults that fall back to the existing theming. Then people could set a base Quarto theme, and if they wanted to they could provide additional overrides. For example:
$cr-narrative-font: $font-family-sans-serif !default

What I don't know is:

The order SCSS files are merged in across extension, file and project
How the array vs string works (it seems like you have a better idea of this!)

@andrewpbray Also interesting to note that you can provide format variants... seems like this might be a good way to provide some extra theming out of the box without having to copy those additional styles with a template!

I'll revert https://github.com/qmd-lab/closeread/commit/e1a503828af56aa3c3a9f4bc838f66d0289f0fb7 in main in just a sec — I wanted to test whether there was a Quarto bug with _metadata.yml. Dang it, GitHub Pages needs branch previews so we don't have to do this in main!

Thanks for putting together that discussion post on this. Seeing it all laid out is good validation that...yeah, its kinda complicated!
Good catch about format variants. I hadn't heard about that!
Amen about the branch preview thing. I could set up a netlify workflow for that... 🤔

Just for the sake of documentation, this conversation turns a bit on the outcome of convos with the devs: https://github.com/quarto-dev/quarto-cli/issues/10383

@jimjam-slam you can now access the PR site at closeread.netlify.app (for all the good it does while these style sheets aren't merging!)


add nanopore to ebi submissions

Now the table looks like this:

Coverage increased (+0.008%) to 91.171% when pulling c115750b471422201ee735b2bd6a38cb956b4c79 on antgonza:add-nanopore-ebi into d97a99ccd99ee849429d560072b745f2d658262b on qiita-spots:dev.


Use a table plugin to render the data asset table

Right now the data asset table is unstyled.  Find a react table plugin (e.g. react-table), use it to render your table and apply one of the standard themes.

Currently exploring Material UI as an alternative to react-table
Planning to work on styling on top of Material UI after it's been implemented

Implemented table of datasets with Material UI
Currently working a table that shows both datasets and results


Registration page nits

[ ] The Admin/Registrations page doesn't provide any way to remove a registration that was entered in error
[ ] The instructions for the .csv upload format are not clear
[ ] No error messages seem to be generated for poorly formatted csv files
[ ] Affiliation and country are apparently optional in the CSV format; they should then be optional in the form too
[ ] The "Send" button should be colored red (only when it says "Send", not "Re-send" -- see #91)
[ ] The "Send" button appears to do nothing until the page is refreshed

This was my attempt, based on the popover instructions:
     email, name, affiliation, country
<EMAIL_ADDRESS>Stephanie Weirich, University of Pennsylvania, USA

But it did not work well.

No errors were reported, though.

@bcpierce00
The format you tried above works. Maybe your cloud functions and dependencies need to be updated, eg: papaparse.min.js.

Some applications put quotes around values in CSVs, which @bcpierce00 might have used. @anniejingchen can you try again with quoting?

It works for contents but not for the header. But it will have quotes in each item except for email.
email,name,affiliation,country
<EMAIL_ADDRESS>"Foo Bar", "UC Irvine", "CHN"

But the header cannot be quoted. In which case, there is no result.

@anniejingchen then would you please change the parser to accept quotes on the header?

What seems to work is no quotes / no spaces.  This is good enough for the moment — we can leave it if you like, Jing.  We just have to document it (in the Conference Organizers Manual and in the popover text for the upload button).

On Aug 11, 2020, at 7:46 PM, Jonathan Bell<EMAIL_ADDRESS>wrote:
@anniejingchen https://github.com/anniejingchen then would you please change the parser to accept quotes on the header?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/clowdr-app/clowdr-web-app/issues/110#issuecomment-672367720, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVQQC3H7KFSBFVGG52RDVDSAHJ4PANCNFSM4P2R24UQ.

After we enter the Send button, it will not be changed to Re-send button automatically. I believe it is caused by the code below (Fig.1). For some reason, in the re-rendered component, the new record (we just sent) has not yet got the invitationSentDate property. So the button will not change.
In my opinion, the best way to solve it is to figure out how to get the invitationSentDate prop. Because if we use other ways to change Send button to Re-send button and leave the  invitationSentDate to be undefined, such as creating a new state prop called alreaySend, the date still won't display (Fig.2). The invitationSentDate may come from the antd table. I may need more time to figure it out.
Would you like to leave it for now?
Do you have any suggestions? Thanks.

What seems to work is no quotes / no spaces. This is good enough for the moment — we can leave it if you like, Jing. We just have to document it (in the Conference Organizers Manual and in the popover text for the upload button).
…
On Aug 11, 2020, at 7:46 PM, Jonathan Bell @.***> wrote: @anniejingchen https://github.com/anniejingchen then would you please change the parser to accept quotes on the header? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVQQC3H7KFSBFVGG52RDVDSAHJ4PANCNFSM4P2R24UQ.

I'd like to leave it there currently. I will add more rules about the format in the tooltip/popover for uploading.

@jon-bell @bcpierce00
After we enter the Send button, it will not be changed to Re-send button automatically. I believe it is caused by the code below (Fig.1). For some reason, in the re-rendered component, the new record (we just sent) has not yet got the invitationSentDate property. So the button will not change.
In my opinion, the best way to solve it is to figure out how to get the invitationSentDate prop. Because if we use other ways to change Send button to Re-send button and leave the  invitationSentDate to be undefined, such as creating a new state prop called alreaySend, the date still won't display (Fig.2). The invitationSentDate may come from the antd table. I may need more time to figure it out.
Would you like to leave it for now?
Do you have any suggestions? Thanks.

After sending the invitation for a single registration, you should fetch the updated registration object (something like this.setState((prevState)=>({ Registrations:prevState.Registrations.map(reg => reg.id == updatedReg.id ? updatedReg : reg) })); - note the use of the state updater that will be event-race safe compared to using this.state.Registrations). The “send all” button should return the list of impacted registration id’s, and then the frontend should fetch the updated registrations.

Already fixed!
   - Benjamin

On Aug 11, 2020, at 21:44, anniejingchen<EMAIL_ADDRESS>wrote:

What seems to work is no quotes / no spaces. This is good enough for the moment — we can leave it if you like, Jing. We just have to document it (in the Conference Organizers Manual and in the popover text for the upload button).
…
On Aug 11, 2020, at 7:46 PM, Jonathan Bell @.***> wrote: @anniejingchen https://github.com/anniejingchen then would you please change the parser to accept quotes on the header? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#110 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVQQC3H7KFSBFVGG52RDVDSAHJ4PANCNFSM4P2R24UQ.
I'd like to leave it there currently. I will add more rules about the format in the tooltip/popover for uploading.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@jon-bell @bcpierce00
After we enter the Send button, it will not be changed to Re-send button automatically. I believe it is caused by the code below (Fig.1). For some reason, in the re-rendered component, the new record (we just sent) has not yet got the invitationSentDate property. So the button will not change.
In my opinion, the best way to solve it is to figure out how to get the invitationSentDate prop. Because if we use other ways to change Send button to Re-send button and leave the  invitationSentDate to be undefined, such as creating a new state prop called alreaySend, the date still won't display (Fig.2). The invitationSentDate may come from the antd table. I may need more time to figure it out.
Would you like to leave it for now?
Do you have any suggestions? Thanks.

After sending the invitation for a single registration, you should fetch the updated registration object (something like this.setState((prevState)=>({ Registrations:prevState.Registrations.map(reg => reg.id == updatedReg.id ? updatedReg : reg) })); - note the use of the state updater that will be event-race safe compared to using this.state.Registrations). The “send all” button should return the list of impacted registration id’s, and then the frontend should fetch the updated registrations.

Thanks~

Also see #116 for some related small issues.

Some of this may be relevant in the new UI but we have separate issues (some internal) tracking such. Closing for now.


Feature Request: Expose option to use a specific font for unicode range.

I couldn't find another issue where this was suggested/discussed (forgive me if the topic has already been brought up), but it would be great if terminal supported something like the symbol_map option in kitty.
For some, it would be an alternative to nerd fonts (if your preferred font does not have the extra glyphs).

I think issue #2664 is what you're asking for.

It is. Thanks for pointing it out.
Duplicate of #2664.


Organizations installing the app should define what DSN to submit to

Currently, we can only install the app in getsentry and all events are sent to a specific Sentry DSN (defined as an env variable).
This will enable other orgs being able to install the app and we submit events on their behalf.

@asottile-sentry I think we could solve this by having the companies interested on this opening a PR and declaring the mapping between their org and which DSN to report to.
Thoughts?

it would probably be better if they committed the DSN to a config file in their repository and then it was read from there?  otherwise we're going to get hundreds of PRs here and acting as a central authority doesn't sound fun

json / ini is simple enough!

The plan as of now:

Create app that can only be installed under the orgs: armenzg & armenzg-dev
Create .sentry repo with configured DSN
Install GH App under armenzg-dev and run some CI

I need to change the permission to have access to the single file sentry_config.ini.


Deliver cropping results as coordinates in PAGE XML

We performed a first brief testing of the cropping procedure which worked pretty well. However, the output is by now only the cropped image. For the integration with the subsequent processing steps, it is necessary to deliver the cropping results as coordinates in PAGE XML.
<PrintSpace>
    <Coords points="101,232 932,232 932,1794 101,1794"/>
</PrintSpace>

Cf. https://ocr-d.github.io/gt//pagexml_documentation/pagecontent_xsd_Complex_Type_pc_PrintSpaceType.html#PrintSpaceType_Coords

Pls. note that in the mean time, ocrd_tesserocr implements a very naïve solution for cropping which may nevertheless serve as an orientation for docanalysis. The coordinates are stored in the element Border rather than in PrintSpace since it is more appropriate to reflect the semantics of the cropping operation.

Thank you very much. We were looking for some reference for the full PAGE XML.

Just run the cropping procedure and you should be ready to go.

In addition, you do not have to write the XML directly. There is a full fledged API to PAGE XML integrated with the OCR-D core module.

Cropping results are now saved in pageXML 5095877c6566a4ffdbce6ee499405dfb8144c44c

Given the commit you linked above, I strongly doubt that the cropping results (or the binarization results) are actually saved in PAGE XML. You have to create a PAGE instance and modify the border element. Cf. https://github.com/OCR-D/ocrd_tesserocr/blob/4a69ba1f899659d00dc8bf21756ff72bf63bad60/ocrd_tesserocr/crop.py#L159

Sorry, that was a wrong commit url. Please check this commit b6c983662dba7ba959b0ab4ed27b8047d70649a3.
Cropping results are saved in Page XML and we are using border element save the crop coordinates.


Vendor in files for runc/libcontainer

vndr was previously removing .go files in runc/libcontainer since they weren't used anywhere in cri-o, but kpod stats will use them
Signed-off-by: Ryan Cole<EMAIL_ADDRESS>

@rhatdan @mrunalp

LGTM

LGTM

This should come in as part of the kpod stats PR so we don't have to work around vndr.

It looks like libcontainer has some dependencies not listed in cri-o's vendor.conf.  If I vendor them in, is there a particular version I should specify or can I just stick with HEAD?

vndr should pull in whatever we are importing in the code. Are we missing any libcontainer vendors right now?

libcontainer wasn't used in the code previously, so the code wasn't pulled in.  kpod stats, which I am working on now though, does import libcontainer

I can vendor it in as a part of kpod stats, but I thought that vendors were supposed to go in separate PRs

Let us vendor it with the PR that needs it otherwise it breaks vndr.


Provide a little advice on how to get the ActiveDirectory module into…

… the computer. Fixes #211

Thanks!


Too slow scripts to add references

The scripts to add references is very unoptimised and slow because in each iteration it opens a new query for finding the ID of related tuple,
a much faster way is to have a Get All query once and then make a dict out of it and using in memory data to find IDs instead of making new query to server on each pass,
This need to be optimised for future users and contributors
Thanks
Hare Krishna

a much faster way is to have a Get All query once and then make a dict out of it and using in-memory data to find IDs instead of making a new query to the server on each pass,

yup! i was worried about the speed. this is a great solution. what if we save the data in json in that format ? I mean the json files would contain the ids.

we may write script to take the old json and convert to the new format. so that, the referencing scripts are not needed anymore
we reference using the smarter way @Gupta-Anubhav12 suggested.

1 or 2 ? which one should we do ?

as planned in meeting today we can have choice 1 as so let's close this issue and merge the PR


bug: v4.6.2 dependency problem

Overview
It seems that with upgrade v4.6.2 some internal dependency are broken.
In particular I've seen that requests v2.24.0 is installed that needs idna < 3, but idna 3.2 is installed.
Below you can see the pipdeptree output command:

Steps to reproduce

Current behavior

The installation of the covmatic-stations package fails because pip tries to uninstall idna v3.2 and install idna v2.10.
Expected behavior

The dependency between requests and idna should be consistent, and installing a package which rely on requests shoud not trigger an upgrade or downgrade of already installed packages (in this case idna)

The opentrons package does not depend on requests. It has a deep dependency on idna >= 2.8
opentrons==4.6.2
  - aionotify [required: ==0.2.0, installed: 0.2.0]
  - anyio [required: ==3.3.0, installed: 3.3.0]
    - idna [required: >=2.8, installed: 3.2]
    - sniffio [required: >=1.1, installed: 1.2.0]
    - typing-extensions [required: Any, installed: <IP_ADDRESS>]
  - jsonschema [required: ==3.0.2, installed: 3.0.2]
    - attrs [required: >=17.4.0, installed: 21.2.0]
    - pyrsistent [required: >=0.14.0, installed: 0.18.0]
    - setuptools [required: Any, installed: 57.4.0]
    - six [required: >=1.11.0, installed: 1.16.0]
  - numpy [required: >=1.15.1,<2, installed: 1.15.1]
  - opentrons-shared-data [required: ==4.6.2, installed: 4.5.0]
    - jsonschema [required: ==3.0.2, installed: 3.0.2]
      - attrs [required: >=17.4.0, installed: 21.2.0]
      - pyrsistent [required: >=0.14.0, installed: 0.18.0]
      - setuptools [required: Any, installed: 57.4.0]
      - six [required: >=1.11.0, installed: 1.16.0]
  - pydantic [required: ==1.8.2, installed: 1.8.2]
    - typing-extensions [required: >=<IP_ADDRESS>, installed: <IP_ADDRESS>]
  - pyserial [required: ==3.5, installed: 3.5]
  - typing-extensions [required: ==<IP_ADDRESS>, installed: <IP_ADDRESS>]

Given that covmatic-stations does not spec any of its dependencies' versions, and given that<EMAIL_ADDRESS>can be installed successfully on its own, I'd say this is probably an issue with covmatic-stations

Great! @mcous
I can confirm that upgrading requests to 2.26 before the installation of covmatic-stations solved the problem.
Since as you said the opentrons system does not depend on request this "old" package is from our previous installation and it is not related to opentrons.
Thanks for the time you spent on that: your help has been very useful!


Deprecate auto_mkdir default value

Currently we're still falling back to the current behavior of auto_mkdir=True if auto_mkdir is not specified. I'm not sure how quickly we can move to setting auto_mkdir=False by default. Is doing that in this PR too soon, or should we wait for a release with a FutureWarning?
Closes #212

I think let's do a release with a warning first.

Thanks!


HW 1 Errors

Hello, the following are errors I have found in your first homework assignment:

The link you have included to the course webpage does not work.
Your links to the quiz and exam folders do not work.
You have not answered question 4.
You have not answered question 5.

Since this is the first assignment, you have the opportunity to earn some points back on these mistakes if you resolve these issues by the start of class on Monday.

Is it possible if I can get it done today that it can count? I just had a lot of work today this week.
Sorry for the inconvenient.
Get Outlook for iOShttps://aka.ms/o0ukef

From: NicholasAsirvadam @.>
Sent: Tuesday, February 20, 2024 12:31:45 AM
To: Lillyrives/IDS2024S @.>
Cc: Subscribed @.***>
Subject: Re: [Lillyrives/IDS2024S] HW 1 Errors (Issue #2)
[External]
Closed #2https://github.com/Lillyrives/IDS2024S/issues/2 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/Lillyrives/IDS2024S/issues/2#event-11857221209, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFSZ5E5OAD5MOAX3RMFHP4LYUQ7NDAVCNFSM6AAAAABDN2KZ32VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHA2TOMRSGEZDAOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Sorry, it is too late to earn points back now.
-Nicholas Asirvadam
Get Outlook for iOShttps://aka.ms/o0ukef

From: Lillyrives @.>
Sent: Tuesday, February 20, 2024 8:01:12 AM
To: Lillyrives/IDS2024S @.>
Cc: Asirvadam, Nicholas Ravi @.>; State change @.>
Subject: Re: [Lillyrives/IDS2024S] HW 1 Errors (Issue #2)
[External]
Is it possible if I can get it done today that it can count? I just had a lot of work today this week.
Sorry for the inconvenient.
Get Outlook for iOShttps://aka.ms/o0ukef

From: NicholasAsirvadam @.>
Sent: Tuesday, February 20, 2024 12:31:45 AM
To: Lillyrives/IDS2024S @.>
Cc: Subscribed @.***>
Subject: Re: [Lillyrives/IDS2024S] HW 1 Errors (Issue #2)
[External]
Closed #2https://github.com/Lillyrives/IDS2024S/issues/2 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/Lillyrives/IDS2024S/issues/2#event-11857221209, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFSZ5E5OAD5MOAX3RMFHP4LYUQ7NDAVCNFSM6AAAAABDN2KZ32VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRHA2TOMRSGEZDAOI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHubhttps://github.com/Lillyrives/IDS2024S/issues/2#issuecomment-1954277611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFSZ7AWUOR6KT4IWGHBLWJDYUSUCRAVCNFSM6AAAAABDN2KZ32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJUGI3TONRRGE.
You are receiving this because you modified the open/close state.Message ID: @.***>


Error in atoti.UserContentStorageConfig

Hi! I've been looking at this issue: https://github.com/atoti/atoti/issues/716
I don't know if it's the same problem, but it happens to me in both Oracle and MySQL. I have tried setting the database URL with JDBC and not setting it.
If it's the same problem...In the other issue you commented that this problem will be solved in the next release, correct?
¿This problem affects all types of databases?
Important: The connection to the database works, doing a read_sql()

Steps to reproduce

Actual Result
Attached error logs: server.log
We inform the values corresponding to the parameters of the url, but due to security policy we cannot give them:

Expected Result
Session is created and connects to the remote DB via JDBC
Environment

atoti: 0.7.1
Python: 3.9.12
Operating System: Windows 10 Enterprise x64

Logs (if relevant)

Hi,
Can you share some code to reproduce the issue?
Otherwise, it indeed looks similar to #716 which is going to be fixed in the next release (around end of November) so you could wait for that and try again.

Hi!
The code is this:

import atoti_sql as atoti_sql
import atoti as tt
session = tt.Session(
user_content_storage = tt.UserContentStorageConfig(
url="jdbc:oracle:thin:[/]@[:]:",
driver=atoti_sql.drivers.ORACLE
)
)

We inform the values corresponding to the parameters of the url, but due to security policy we cannot give them

Hi!
This issue is already resolved. It was solved with the new release 0.7.2...
Thanks!


Support separate keydown/keyup event for hotkey

Is this possible to do? I've seen this in Swift before.
Here it is implemented for macOS: https://medium.com/@avaidyam/building-a-better-registereventhotkey-900afd68f11f but seems to be a lot more than that lol.

I think this maybe be possible on Linux(X11) and maybe Windows too (I have an idea but haven't tested it yet).
As for macOS, I see in the article that they are using private APIs which will result in your app getting rejected by The App Store so we can't use that. Since I am not a macOS dev, I will have to leave it to someone else to contribute.

I see in the impl we have kEventHotKeyPressed. Is there a reason kEventHotKeyReleased wouldn't work?

@morajabi thanks for looking into this, the API should be straight forward, you would need to just add a field in GlobalHotKeyEvent
pub enum HotKeyState {
	Pressed,
	Released,
}

pub struct GlobalHotKeyEvent {
    /// Id of the associated [`HotKey`]
    pub id: u32,
	pub state: HotKeyState,
}

+1 on this


Unexpected token } on files with get in ES6 object literal

I'm attempting to use flow on a project, and ran across a really confusing error message. The simplified test case is:
/* @flow */
function get () {
}
module.exports = { get };

The error is Unexpected token }, on the module.exports line.
I also get a similar error if get isn't the only thing in the object, e.g.:
/* @flow */
function get() {}
function add() {}
module.exports = { get, add };

In this case, the error is:
Unexpected token ,
The workaround is pretty straightforward (rename the 'get' function and use get: _get, or similar), but seemed worth reporting.

Thanks for the report and the simpler repro than we had before! We're tracking this in #528 (gonna change that issue's name...)