Bug: Read input is ignored for template comments

Is there an existing issue for this?

[X] I have searched the existing issues

Is this a regression?
Yes
Current behavior
I have a "pricing" scope and inside it I have code like this
`

<custom-title
[title]="t('title')">

    ....

`
When it extracts the translations the "title", "investors" and such are put properly inside pricing/en.json.
These:
 <!-- t(title,basic_calculator,detailed_implementation_plan,connect_with_investorst) -->
are just poot in the root en.json file as if they have no parent.
I tried even removing the other read like this:
`

<custom-title
[title]="t('title')">

    ....

`
But it still didn't put them in proper file.
With this I'm basically forced to write all prefixes manually which is what I've been doing untill now but no I had like 20 of these at once an putting prefixes on the will look really ugly and unreadable.
Module provider looks like this:
providers: [{provide: TRANSLOCO_SCOPE, useValue: {scope: 'pricing', alias: 'pricing'}}],
Expected behavior
Expected that translations are put inside the pricing/en.json with proper parent file and not the root translation file.
Please provide a link to a minimal reproduction of the bug
None
Transloco Config
keysManager: {
    input: ['common', 'services', 'app'],
    unflat: true,
    defaultValue: "{{key}}",
  }

Debug Logs
I tried this but it just said

> DEBUG=* transloco-keys-manager extract

'DEBUG' is not recognized as an internal or external command,
operable program or batch file.

Please provide the environment you discovered this bug in
Transloco: ^4.2.2
Transloco Keys Manager:^3.7.0
Angular: 15.2.4
Node: 18.13.0
Package Manager: npm 8.19.3
OS: win32 x64

Additional context
No response
I would like to make a pull request for this bug
No

@zsimuno Please provide a reproduction link as I don't fully understand your issue.
The comments and all the other keys are not affected by the fact that you are providing a scope, it just allows the keys manager to map the keys prefixed with the scope alias to the correct files.
You pasted 2 identical template snippets:
<custom-title
[title]="t('title')">

So it's hard to understand.
Note that the debug logs didn't work as you are trying to set an environment variable using the Linux syntax

@zsimuno Feel free to reopen this with a reproduction link 👍


Fixes some misspellings, typos, grammar, and punctuation

"PubSab" bothered me. I put a little more effort into cleaning up some of the rest, too.

@colindean thanks a lot for fixing this!


How to implement DatePickerIOS in TextInput to select the date for DOB .

How to implement DatePickerIOS in TextInput to select the date for DOB .
Need help I posted same as on Stack Overflow but i did't get any response.

Sorry, GH Issues is only for bugs. You can post the link to your Stack Overflow question here in case people stumble upon it.
I would also recommend looking for help via these others forms:

Chat on Reactiflux in #react-native
Start a thread on the React Discussion Board
Join #reactnative on IRC: chat.freenode.net
Join the Facebook React Native Community and ask there.

@facebook-github-bot close


command a exported file bug

in exported file i have

and i use

and i have a error

That command would be for removing a permission set with world="true". Just don't include "true" at the end.

Thanks @creator3
The fail messages in the latest versions should make this more obvious. :)


BUG: Mac M1 (arm) ODE solver incorrect results conda installation

Describe your issue.
Using scipy.integrate.ode I notice many errors and warnings on Mac M1, compared to running the same code on an Intel chip, e.g.
UserWarning: zvode: Excess work done on this call. (Perhaps wrong MF.), with then resulting incorrect output of the solver.
The easiest example is if I copy and paste from the website.
In the below example, it does not give the same output as the website (note here, the output itself is incorrect, as well as producing the warning). The correct output should be as on the website above which prints 10 time-steps before quitting the loop, which is what I find on an Intel terminal.
This is just a simple example, I find issues like this quite persistent on Mac M1. I installed scipy using the Apple Silicon version of conda (at 4.13). I assume this is somehow to do with the installation, though I was under the impression scipy was compatible with M1 via conda? Is there an install guide for Mac M1?
Reproducing Code Example
from scipy.integrate import ode

y0, t0 = [1.0j, 2.0], 0

def f(t, y, arg1):
    return [1j*arg1*y[0] + y[1], -arg1*y[1]**2]
def jac(t, y, arg1):
    return [[1j*arg1, 1], [0, -arg1*2*y[1]]]

r = ode(f, jac).set_integrator('zvode', method='bdf')
r.set_initial_value(y0, t0).set_f_params(2.0).set_jac_params(2.0)
t1 = 10
dt = 1
while r.successful() and r.t < t1:
    print(r.t+dt, r.integrate(r.t+dt))

Error message
/opt/miniconda3/lib/python3.9/site-packages/scipy/integrate/_ode.py:1011: UserWarning: zvode: Excess work done on this call. (Perhaps wrong MF.)
  warnings.warn('{:s}: {:s}'.format(self.__class__.__name__,
1 [-9.75447932e-05+9.99902455e-01j  1.96095143e+00+7.77841228e-04j]

SciPy/NumPy/Python version information
1.9.0 1.22.4 sys.version_info(major=3, minor=9, micro=13, releaselevel='final', serial=0)

Hi @jsmarsha11 thank you for reporting. Indeed I can reproduce this locally with a M1. On main it is working just fine though. Not sure if we did something wrong on the dist.

So installing using pip works just fine. I think it's an issue with our conda packaging then. cc @rgommers @h-vetinari

Unlikely it's packaging related, more it's just bad code that happens to be sensitive to the exact build config used.

@jsmarsha11 you said you observed other issues. Are they also related to this function or other functions?

Yes indeed, there is nothing in the conda-forge recipe that would cause this. It's also not even clear that this differs between PyPI and conda-forge packages, my guess would be that we ship the wheel on PyPI with OpenBLAS 0.3.18 but when installing from conda-forge you get 0.3.20. That's a known bad version for macOS M1.

my guess would be that we ship the wheel on PyPI with OpenBLAS 0.3.18 but when installing from conda-forge you get 0.3.20. That's a known bad version for macOS M1.

Indeed conda-forge is on 0.3.20 for openblas. I was not aware it was seriously broken for osx-arm (or it could be marked as such, so it cannot be installed anymore; though it's been published so long now that I'd be worried about breaking the reproducibility of a lot of environments).[^1]
We have the issue that conda-forge cannot directly test the osx-arm binaries, because there's no native hardware in public CI for that yet (though scheduled to arrive in GHA/Azure 2022Q4), otherwise I'd already be running the test suite also on osx-arm.
[^1]: luckily, 0.3.21 is scheduled to arrive soon.

Wow, thanks for this, and glad it wasn't just me!
And I can also confirm the pip install has correct output on the original post.

@jsmarsha11 you said you observed other issues. Are they also related to this function or other functions?

And regarding this, let me get back to you. I have a more complex code which is unfortunately still failing, and I expect it is the scipy integration. I'm actually surprised it is still not working given the above now works after installing with pip (I assumed it would be the same issue, as the error messages were the same). Of course, it's possible the other code is breaking for some other reason. When I get time I will try to get a minimum working example, or i'll let you know if I no longer believe the issue to be with scipy.
Thanks, this is appreciated.

Update:
Everything working on my end. The pip install works, and I was eventually able to resolve all the issues I was having. So I think it was simply this openblas problem as mentioned above.
Thanks!

Great, thanks for confirming.


Defining a policy for support for old TypeDoc versions

As much as I'd like people to always upgrade to the newest TypeDoc version when it's released, or shortly after, this isn't always feasible for some projects, which are either stuck on old TypeScript versions or don't have enough dedicated time to resolve any breaking changes.
My policy for support for old versions has always been "upgrade or perish", but despite that, there are a significant number of projects using an old version of TypeDoc. Here's the data from npm for this past week.

In the interest of not totally leaving old projects to die, lots of projects will do security updates for older versions for some period of time. I've said before that I don't have the time to maintain old versions, which remains true, but I'm open to creating a branch for one or maybe two prior minor versions, which will accept patches to fix security vulnerabilities only.
My concerns:

Continuing to support older versions will lead to an increase of bug reports for unsupported versions.
Accepting patches for security issues will be construed to mean that vulnerabilities will be fixed on discovery for old versions by a maintainer.
Partial support for old versions will encourage people to remain on older versions even when an upgrade is available.

It is also worth mentioning here that TypeDoc is (almost always) a development dependency. A vulnerability in it will not affect a production version of your application. A "high severity" vulnerability in Marked (https://github.com/markedjs/marked/security/advisories/GHSA-rrrm-qjm4-v8hf) can only actually cause you problems if you're running TypeDoc on code which re-exports elements from modules not under your control.
Comments? Mitigation strategies? Things I've missed?
Ref: #1854, cc @bennycode

Thank you for taking care of my issue. It's super cool that you take it as an example to develop a process for upcoming security fixes. I suggest that you do it like the Node.js team which supports fixes for their latest major version (currently v17.x) and the one prior (currently v16.x).
I suggest that TypeDoc should also make a v1.0 and signal breaking changes by bumping the major version to v2.0 because I was not expecting to see breaking API changes between v0.21 & v0.22. Having this concept of major version / breaking changes would also make it easy to distinguish which versions to get security patches: the latest major & the one from before.

I was not expecting to see breaking API changes between v0.21 & v0.22.

SemVer says:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

TypeDoc is somewhat stricter than this - I avoid breaking changes for patch versions, and only plan to make them for minor versions.
I've avoided going to 1.0 so far because basically everything I've wanted to do has been a breaking change... and am still rather unhappy with the public API. It's getting a lot closer though, probably two to three more rounds of breaking changes and it'll be at a state where breaking changes should become far less necessary to make new features.


fix: publish config

:tada: This PR is included in version 0.8.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Utterly Lost

I don't know if I should have started someplace else, but a search landed me here. However, I can't make it past the 2nd sentence of the Simple Histograms section. I have no idea what's being references with the use of the "Reference option for the query". In fact, you don't even tell me to work in Power Query - I finally figured out that's where you are.

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

ID: 414d2796-4f3f-8ebe-c9b9-0445c4523b82
Version Independent ID: d6906e43-5f47-9712-f08c-27ad5e2c2b82
Content: Histograms - Power BI
Content Source: powerbi-docs/service-histograms.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

@Scott-Phoenix  - sorry for the confusion with that article. Let me see if I can provide more clarity in that article and improve it. Thanks for your feedback, and sorry for the inconvenience.


Expose diff editor options to access and update them

The following options should be covered: https://github.com/Microsoft/monaco-editor/blob/e52655e4681f9d2ed4e39bf1832d3ac67c62bdf5/monaco.d.ts#L3100

Also, there is no onDidChangeConfiguration event for the diff editor.

Also, there is no onDidChangeConfiguration event for the diff editor.

I am also in need of this onDidChangeConfiguration event.
@alexdima It is almost 3 years, Can you please update us on the time frame in which can we expect this feature in the Monaco editor


fix: allow apple pay shipping events to emit

Summary
onDidSetShippingMethod & onDidSetShippingContact events will again send data back to the useApplePay hook listeners as well as by using the standard const eventEmitter = new NativeEventEmitter(NativeModules.StripeSdk); listeners
What happened was that the:
if let callback = self.shippingMethodUpdateJSCallback { ... }

Would never be set in any place other than using the ApplePayButton component from Stripe, meaning that if you were using the useApplePay hook or needed to listen to the shipping changes, it would skip and never trigger the sendEvent function
Motivation
I needed to listen to the shipping address changes programatically because the app we use has shipping available to different countries which require different tax calculations and currencies.
Testing

[ ] I tested this manually
[x] I added automated tests

Documentation
Select one:

[ ] I have added relevant documentation for my changes.
[x] This PR does not result in any developer-facing changes.

hey @p-sebastian , thanks for the contribution!
So you're using the useApplePay hook without using the ApplePayButton component? Apple requires using their specific button for this (otherwise your app will be rejected), so can I ask what you're using for the button then?

hey @charliecruzan-stripe , Apple allows you to create the button as long as it follows the guidelines, so it is an ApplePay button but created normally by me in react-native.  (it is already running in production so it has been approved by apple)
Difference is that in the onPress handler I call the presentApplePay like the docs in stripe say
const { presentApplePay } = useApplePay({
    onShippingMethodSelected,
    onShippingContactSelected,
});

const onApplePayPress = async () => {
  const { error, paymentMethod } = await presentApplePay({
    ...
  });

  // Handle confirmation
};

While the button exported by stripe -> ApplePayButton that uses the ApplePayButtonNative contains these functions as props, even though the Props type doesn't define them.
export interface NativeProps {
  ...
  onShippingMethodSelectedAction?: (
    ...
  ) => void;
  onShippingContactSelectedAction?: (
    ...
  ) => void;
  onCouponCodeEnteredAction?: (
    ...
  ) => void;
}

The ApplePayButtonView.swift has the following mapping where the self.shippingMethodUpdateJSCallback is supposed to get set.
 @objc func handleApplePayButtonTapped() {
        if onPressAction != nil {
            onPressAction!(["true": true])
            // JS Callbacks are all no-ops since in legacy code (useApplePay hook),
            // this behavior is controlled via the onDidSetShippingMethod and onDidSetShippingContact
            // events
            stripeSdk?.shippingMethodUpdateJSCallback = doesNothing
            stripeSdk?.shippingContactUpdateJSCallback = doesNothing
            stripeSdk?.couponCodeEnteredJSCallback = doesNothing
        } else {
            stripeSdk?.shippingMethodUpdateJSCallback = onShippingMethodSelectedAction
            stripeSdk?.shippingContactUpdateJSCallback = onShippingContactSelectedAction
            stripeSdk?.couponCodeEnteredJSCallback = onCouponCodeEnteredAction
        }
    }

On a side note, I noticed that you will be switching to start using the:
const { error, paymentMethod } = await createPlatformPayPaymentMethod({ applePay: {...} })

But that doesn't have the 2 event listeners and the manual eventEmitter setup also doesn't work, it only works if it runs with the useApplePay hook, probably because of the self.hasLegacyApplePayListeners that doesn't get set.

Apple allows you to create the button as long as it follows the guidelines

Interesting, I didn't know that. FWIW, as Apple changes the design requirements, I would imagine it's easier to just use their PKPaymentButton rather than having to update your custom component every now and then to re-follow their guidelines. But maybe that doesn't happen often enough to be an issue for you!

Apple allows you to create the button as long as it follows the guidelines

Interesting, I didn't know that. FWIW, as Apple changes the design requirements, I would imagine it's easier to just use their PKPaymentButton rather than having to update your custom component every now and then to re-follow their guidelines. But maybe that doesn't happen often enough to be an issue for you!

Hasn't happened to me yet, but they can get very picky when it comes to approving it, it the same for the signing with apple button

Gotchya, and just out of curiosity, why do you prefer using your own custom component then? Do you do the same thing for the Google Pay button component? Is there something i could add to our pre-provided components?

@charliecruzan-stripe It allows you a bit more flexibility on the style and it is not that difficult to make. Also if you are using reanimated you could check RectButton for cancelling pan handlers when a button is inside, which I am not sure you can do with the stripe implemented one
Stripes version:

Our version:
Font size is the same as the checkout next to it (an SVG), as well as borderRadius (although that is editable on the stripe one)

I see, Apple does not recommend altering the icon or text size in the Apple Pay button, so that is not something we would offer since it would open up the possibility of app rejections 😞

Merging to fix since this affected existing behavior, but I do want to mention that we design the Apple and Google Pay APIs to be used with our components (specifically, the PlatformPayButton), so your mileage may vary if you're using your own component. My biggest concern would probably be app review in that case, but we also do not test using our APIs with 3rd party apple/google pay button components


Exception is being thrown: 'The space 'CSSpace' has no associated collection'

Description
When trying to do bulk delete as following:
public DbSet<DevicePackageHistory> DevicePackageHistories { get; set; }
DbContext _unitOfWork = new DbContext();
_unitOfWork.DevicePackageHistories.Where(dph => dph.ID == 3).Delete();`

Exception
Exception message:
The space 'CSSpace' has no associated collection.
Stack trace:
at System.Data.Metadata.Edm.MetadataWorkspace.GetItemCollection(DataSpace dataSpace, Boolean required)
at System.Data.Metadata.Edm.MetadataWorkspace.GetItems(DataSpace dataSpace)
at Z.EntityFramework.Plus.Internal.Model.GetModelNames(DbContext this)
at Z.EntityFramework.Plus.Internal.Model.GetDatabaseFirst(DbContext context)
at Z.EntityFramework.Plus.InternalExtensions.GetModel(DbContext context)
at Z.EntityFramework.Plus.BatchDelete.Execute[T](IQueryable1 query)    at Z.EntityFramework.Plus.BatchDeleteExtensions.Delete[T](IQueryable1 query, Action1 batchDeleteBuilder)    at Z.EntityFramework.Plus.BatchDeleteExtensions.Delete[T](IQueryable1 query)
But when I run this:
        DbContext _unitOfWork = new DbContext();
	if (_unitOfWork.DevicePackageHistories.Where(dph => dph.ID==0).Count() == 0)
	{
		_unitOfWork.DevicePackageHistories.Where(dph => dph.ID==0).Delete();
	}

Everything works fine.
What am I doing wrong?
Further technical details

EF version:5.0.0
EF Plus version:1.9.3
Database Provider:MS SQL

Hello @mikehac ,
Could you provide a runnable solution with this issue?
It happens when we try to read your model. Without a project, this kind of issue is a way to hard to reproduce.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Hi @JonathanMagnan
Here is my repository which contains runnable solution and sql script to create a ms db. We have checked this issue on 3 machines with windows 10x64, Microsoft SQL server 2012 r2. It fails when you run the exe file directly, not in debug mode.
The exceptions is:
Unhandled Exception: System.InvalidOperationException: The space 'CSSpace' has no associated collection.
at System.Data.Metadata.Edm.MetadataWorkspace.GetItemCollection(DataSpace dataSpace, Boolean required)
at System.Data.Metadata.Edm.MetadataWorkspace.GetItems(DataSpace dataSpace)
at Z.EntityFramework.Plus.Internal.Model.GetModelNames(DbContext this)
at Z.EntityFramework.Plus.Internal.Model.GetDatabaseFirst(DbContext context)
at Z.EntityFramework.Plus.InternalExtensions.GetModel(DbContext context)
at Z.EntityFramework.Plus.BatchDelete.Execute[T](IQueryable`1 query)
at EntityFrameworkPlusTest.Program.Main(String[] args) in C:\Users\user\Desktop\EntityFrameworkPlusTest-master\EntityFrameworkPlusTest\Program.cs:line 14

Thank for the project, we will look at it this week.

Hello @mikehac ,
The v1.9.5 has been released.
Could you try it and let me know if that's working.

Hi @JonathanMagnan ,
Thank you so much for trying to help me, I'll check it tomorrow at work and inform you with the results.
Best regards,

Hi @JonathanMagnan
It seems working, no exceptions.
Good work!!


Add state dump to create and delete shoot

What this PR does / why we need it:
Add state dump to create-shoot and delete-shoot.
The delete-shoot test prints the dump also when it runs as cleanup test (os.Getenv("TM_PHASE") == "Exit").
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

Thanks for the clarification. Could you please also resolve the conflict?


Vertical alignment support for text schema

implements #190
Example:
https://github.com/pdfme/pdfme/assets/7068515/6cbad2ce-fa7b-4248-9f4d-daa6192bdf48
Notes & Caveats
Vertical aligning in edit mode in the designer is surprisingly challenging. You cannot vertically align textarea, so we had to dynamically resize it after any change to ensure it's set to the height of it's content and position it within the parent container (credit to @steffancarrington).  This does lead to some minor side-effects - sometimes, with certain fonts, the scrollbar is visible when it should not be. Also, there's occasionally a 1 pixel shift between edit and view mode due to the rounding of textarea.scrollHeight.
In implementing this we spotted an issue with dynamic font sizing not properly considering line-height which I'll log separately and look into.

Released as 2.2.0 !!!


Format code

An exciting project you got here. But no offense, main.py looks like spaghetti code. I tried to clean it up a bit, I can't say it's the best it can be but it's a lot better than before.
A quick review of what I changed:

Turned the comment at the top of the file into a doc string
Made all in-line comments have a consistent spacing
Made string literals have " instead of '
Spacing with blank lines

These changes make the code a lot clean and readable.

😅 thx!


Challenge 2 - As a Developer, I am able to Create a User & Login as a User using a Login provider integrated with PlayFab

Styling to Login Form
Allow ability to Create a User through PlayFab.

closed styles with #28 . can create and login through playfab


ensure builder.cleanup() waits on pending work

Prior to this, if cleanup was invoked while the build was cancelling, it would begin to do cleanup prior to the current step completing. Which would typically result in "missing directory" or "missing file" errors, which would then result in the build crashing and not completing it cleanup rather then exiting cleanly.

[ ] debug OOM which becomes apparent during mid-build cancellations (issue with: aggregateTime)
[x] confirm
[ ] test

@oligriffiths this is likely the solution to the problem we spoke about on Wednesday. I finally had some time to debug it...

Looks sane. Fix tests and we’re good I think.

@oligriffiths aggregateTime seems to OOM when we don't crash during mid-build cancellation.
I'm investigating why, and see if I can fix...

Although this is green, I haven't been able to fix the OOM issue (or add a test here that demonstrates it) So we should hold-off until i, or someone else, has a chance to look into that.

@stefanpenner got a repo to demo the OOM?

Ok so I reproduced the issue:
ember build
Environment: development
cleaning up...
cleaning......
Cannot stop: not the current node.

<--- Last few GCs --->

[68590:0x102801000]    13909 ms: Mark-sweep 998.5 (1045.1) -> 828.5 (875.1) MB, 450.2 / 0.0 ms  allocation failure GC in old space requested
[68590:0x102801000]    14610 ms: Mark-sweep 828.5 (875.1) -> 828.4 (838.6) MB, 701.4 / 0.0 ms  last resort GC in old space requested
[68590:0x102801000]    15083 ms: Mark-sweep 828.4 (838.6) -> 828.4 (838.1) MB, 472.2 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x38b802e0427d]
Security context: 0x15b0e6c206a9 <JSObject>
    1: aggregateTime(aka aggregateTime) [/Users/goli/Projects/broccoli/lib/builder.js:~448] [pc=0x38b803389be9](this=0x15b0095022e1 <undefined>)
    2: buildHeimdallTree [/Users/goli/Projects/broccoli/lib/builder.js:400] [bytecode=0x15b0a04faca9 offset=21](this=0x15b0b9f13439 <EventEmitter map = 0x15b02a42ed51>,outputNodeWrapper=0x15b05fa22971 <NodeWrapper m...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Note the Cannot stop: not the current node. line, it's important.
During cleaning, heimdall is being messed with as it is being started/stopped in the wrong order. What happens is a node starts being build, and heimdall.start() is called from beginNode fire in Broccoli. Then cleanup() is called and https://github.com/ember-cli/ember-cli/blob/master/lib/models/builder.js#L250 starts a new heimdall node, and then the endNode is fired for the currently building node, then the cleanup heimdall node is stopped.
So for now, I've added a _isCleaning flag to skip doing the heimdall doing the aggregate time.
➜  ember build
Environment: development
cleaning up...
cleaning......
Cannot stop: not the current node.
Built project successfully. Stored in "dist/".

So the same Cannot stop: not the current node. is output (issue still exists) but the OOM is gone.

So, I added some debug statements to beginNode and endNode. Even when cancelling the ember-cli build, the broccoli build doesn't get cancelled. Example: ember-cli-build.js
'use strict';

const Plugin = require('broccoli-plugin');

class Sleep extends Plugin {
  build() {
    return new Promise(resolve => {
      console.log('Going to sleep');
      setTimeout(() => {
        console.log('Waking up');
        resolve();
      }, 2000);
    });
  }
}

module.exports = function(defaults) {
  return new Sleep([
    new Sleep([], { name: 'Sleep 1' })
  ], { name: 'Sleep 2' });
};

➜  ember-test git:(master) ✗ ember build
Environment: development
START Sleep 1
Going to sleep
cleaning up...
Waking up
DONE Sleep 1
Cannot stop: not the current node.
START Sleep 2
Going to sleep
Waking up
DONE Sleep 2
Built project successfully. Stored in "dist/".

CMD+C was initiated after the first Going to bed, see cleaning up....
It completes after, but then the next node continues to build, this doesn't seem right...

@oligriffiths ya, looks like something else is fishy...

@stefanpenner yeah so broccoli-builder did call cancel() https://github.com/ember-cli/broccoli-builder/blob/0-18-x/lib/builder.js#L212
However Broccoli 2 does not, and if you do call cancel, you get an exception due to https://github.com/broccolijs/broccoli/blob/master/lib/builder.js#L109 and https://github.com/broccolijs/broccoli/blob/master/lib/builder.js#L119
I don't know what the intention behind those 2 lines are, can you shed some light? Seems like we need to do some refactoring.

@oligriffiths I've fixed it

@oligriffiths updated, mind re-reviewing?

@stefanpenner something is still off. Trying with a new ember install, hitting CMD+C after building... is printed to console:
Environment: development
cleaning up...
Cannot stop: not the current node.
BUILD CANCELLED

Stack Trace and Error Report: /var/folders/v0/v1xr03j523d3py2sp5m4_gsm0000gn/T/error.dump.210e83fb537b3243555bd0c7f3062c40.log

// log
ERROR Summary:

  - broccoliBuilderErrorStack: [undefined]
  - code: [undefined]
  - codeFrame: [undefined]
  - errorMessage: BUILD CANCELLED
  - errorType: [undefined]
  - location:
    - column: [undefined]
    - file: [undefined]
    - line: [undefined]
  - message: BUILD CANCELLED
  - name: Cancelation
  - nodeAnnotation: [undefined]
  - nodeName: [undefined]
  - originalErrorMessage: [undefined]
  - stack: Cancelation: BUILD CANCELLED
    at CancelationRequest.throwIfRequested (/Users/goli/Projects/broccoli/lib/cancelation-request.js:17:13)
    at promiseFinally.then (/Users/goli/Projects/broccoli/lib/builder.js:115:48)
    at process._tickCallback (internal/process/next_tick.js:68:7)

@oligriffiths ya we explicitly fail the build, as the build was not successful so the "BUILD CANCELLED" is expected. That being said, i cannot replicate the Cannot stop: not the current node message myself.

Adding a log to startNode and endNode you get this:
➜  ember-test git:(master) ember build
Environment: development
Start: EMPTY_MERGE_TREE
End: BroccoliMergeTrees
Start: ProcessedTemplateTree
End: Funnel
Start: /Users/goli/Projects/ember-test/app/styles
End: UnwatchedDir
Start: Funnel (styles)
End: Funnel
Start: /Users/goli/Projects/ember-test/tests
End: WatchedDir
Start: broccoli-persistent-filter:EslintValidationFilter
cleaning up...
End: broccoli-persistent-filter:EslintValidationFilter
Cannot stop: not the current node.
BUILD CANCELLED

@oligriffiths we should likely make BUILD CANCELLED less screaming case.

@oligriffiths are you sure the heimdall warning is from broccoli, and not something in ember-cli?

kill logging: https://github.com/heimdalljs/heimdalljs-lib/commit/baac3fe53972afccab18aa1643f65dd56161ef22

released as v2.2.0 🎉

👏


DDIM sampler training parameters

Hi, thanks for your great work in implementing the DDPM baseline.
I'm curious about the changes in numberOfSteps, betas start and end, when changing the sampler from DDPM to DDIM. could you please provide me with the DDIM sampler training parameters.
Thank you in advance.

Hi, regarding the parameters for the DDIM sampler, you can refer to the original DDIM paper. For faster inference speed, I would consider a $S$ of 10 or 20; for better generation quality, I would suggest a $S$ no less than 50. You can specify $S$ by setting the subseq-size parameter.

In terms of time skipping schedule, according to the paper, they recommend the linear schedule for most datasets except for CIFAR10. To do this, simply setting skip-schedule as linear (or quadratic).

Thank you very much


Statiq.Web upgrade to 1.0.0-beta.44 seems breaking

I use Devlead.Statiq in my blog because I have made some modifications to the Cleanblog theme in a fork and your library is a very easy way to use that fork, so thanks for the idea and implementation.
I tried to update my blog to the latest Statiq.Web (1.0.0-beta.44) and ran into some problems.
My guess is that the problem started with Statiq.Web 1.0.0-beta.38 which included a version of Statiq.Framework that made a number of breaking changes that affected Devlead.Statiq
I forked Devlead.Statiq and made a branch where I tried to isolate the problem by adding a project that only uses the theme functionality. The main reason I did this was that I had problems running the existing test project because of a file getting locked, so you might also need to fix some stuff for the tabgroup functionality
https://github.com/henrikrxn/Devlead.Statiq/tree/Update-to-Statiq-Web-1-0-0-beta-44
Did not think it was worth doing a PR at this point.
The branch fixes the compile errors introduced by the breaking changes from Statiq.*
That could of course be the source of the problems, but I do not think so.
I tried to investigate on the simple repro, but my knowledge about the inner workings of Statiq  is not sufficient to understand and fix the problem and make a PR.
When I run the DevLead.Statiq.TestThemes project I added this way:
dotnet run --framework net6.0 -- preview --clean-mode Full --Verbose
I get the following errors as part of the verbose output
[INFO] [Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager] User profile is available. Using 'C:\Users\Henrik\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
[ERRO] Content/PostProcess » RenderContentPostProcessTemplates » ExecuteIf » ExecuteIf » ExecuteIf » ExecuteConfig » RenderRazor » [E:/MyGithub/Devlead.Statiq/src/DevLead.Statiq.TestThemes/input/posts/HelloWorld.md => posts/helloworld.html] The layout view '/_layout.cshtml' could not be located. The following locations were searched:
/_layout.cshtml
[INFO] ========== Execution Summary ==========

and later a "follow-up"
[INFO] - Analyzer Before Engine Execution Events in 1 ms
[INFO] - Engine Execution in 3150 ms
[CRIT] The layout view '/_layout.cshtml' could not be located. The following locations were searched:
/_layout.cshtml
[INFO] To get more detailed logging output run with the "-l Debug" flag

After this when put a comment // in DevLead.Statiq.TestThemes\Program.cs at the beginning of the .AddThemeFromUri line then things build just fine (provided the theme folder has content)
That is why I think the breaking Statiq.Framework changes affected, at least, the theme part of your library.

Fixed by #4


[omnibus] add internal attribute for sever api version in use

Just like it says on the label.  This is currently used for pedant config, and will also be used once we move the reindex script into a template, since it needs to be version-aware.
ping @chef/lob

:+1:


Update neutron api doc with horizon notes.

Alright @neiljerram, I've made those changes. =)

Thanks.


Fix encrypt helper

fixes #92
The decrypt_helper is doing the right thing while the encrypt_helper is walking down the line for whatever reason. So this behaviour is now changed and at least locally for me it works.

@savar thanks for your contribution! I've tested locally and your patch seems to fix the issue.


missing sw-toolbox.js since 3.5

I install the sw-toolbox with bower and refer the path bower_components/sw-toolbox/sw-toolbox.js in my importScripts. However the file does not exists in the latest release. When I check the previous releases, the file exists in the 3.4, but has disappeared since 3.5.

Apologies—we've made some changes to our build/publishing process, and it does look like the bower end of things is not working as expected since v3.4.0.
@gauntface, is there any accommodation in the current build process for getting the bundled sw-toolbox.js file checked in to GitHub in a tagged release, to make Bower happy?
(Or is Bower a lost cause at this point?)

will talk a look at this today. Sorry for the issues :(

If my understanding is correct. Bower will use the github releases to use as it's "download". The issue with this is that tagging a release will "tag" the source of the project, but the build file sw-toolbox.js is not included because it's in .gitignore.
Going to see if there is a way around this, but I'm not hopeful.

Yeah anything we do to fix this is going to be horrible.
Sadly I'd vote dropping bower support (Addy is in favor of this) or we just allow build versions back in to master - this will allow it to be in a tag to include the required files.

@e111077 I just noticed platinum-sw adding some commits related to this issue :) Do you know whether the plan is to continue using that anywhere? Over on Fizzle, we (incl Taylor) were of the opinion platinum-sw should be deprecated in favor of directly using sw-toolbox and sw-precache.
Would us dropping Bower support here cause any issues for y'all? If so, we can probably keep supporting it for a while longer but are actively trying to focus on npm/yarn support as much as possible otherwise.

We have decided to deprecate platinum-sw but the team has also decided to port all deprecated elements to the 2.0 "hybrid" mode at the very least. Support will stop there.

@addyosmani @jeffposnick shall we just commit the build to master? When I contested the build in master a long time ago, no one called out that bower was using it this way and it happened by chance to work with the old build process. This would at least get Bower running while we finish off sw-helpers.

Apologies for this issue; I've tagged v3.6.1 which includes the built library, so hopefully bower will be happy. It looks okay when I ran bower install sw-toolbox just now.
(@gauntface, I had to manually tag it in GitHub because the publish process won't complete due to https://github.com/GoogleChrome/selenium-assistant/issues/87)


[Add] Awesome-Design-Tools

Fixes Issue
closes #2424

Changes proposed

Screenshots

Note to reviewers

@JuanPabloDiaz could you please enhance the description a bit


Display vault name in the open tab title

Please Select if your Request is Either something new or an Enhancement

[x ] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[x] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
With many tabs open and titles potentially identical across vaults it is easy to type into a wrong note.
Describe the solution you'd like
Show the vault name in brackets after the note title as in the Lookup

Great suggestion! adding it to our queue of CROP candidates

I'm not sure if this is possible. @kevinslin Do you know of any APIs to achieve this? I combed through the VSCode APIs but I can't find anything relevant. I'd also be happy for a link to an extension that does something like this, I'm happy to read through it's source code to figure this out.

Nor am I, there is some discussion here

Looks like the VSCode API has been finalized! We can finally add this to Dendron, I'll see if the feature is out on Insiders and start the implementation.

I tried implementing this, but it actually doesn't seem to be possible yet. The VSCode Tab API only gives you read access to tabs, all tab properties are read only. The most you can do is close an open tab, or look at which tabs are currently open.

@SeriousBug maybe we can still keep the crop label just in case it become possible in the future.

Oh I just dropped it so we don't re-pick it accidentally. Sure, I can add it back.

I can see my vault names next to the file names on the tabs if I select 'medium' for Workbench>Editor: Label Format settings in VSCode.


Fix broken links for input/output formats in data file

Some projects contained links in the input/output fields, pointing to sites where the supported file formats had been listed. These have been broken during the conversion, and resulted in things like
"inputs" : [ "[Multiple](https:", "", "blackthread.io", "gltf-converter", "#supported-formats)" ],

(see https://github.com/KhronosGroup/glTF-Project-Explorer/blob/master/public/data/glTF-projects-data.json#L1225 )
Assuming that input/output should not contain markdown, these links should be fixed, and where applicable, the link should be added to the description.
(I'll tackle this ASAP, this issue is rather a reminder)

@weegeekps The input/output fields should probably at least state the glTF version. But thinking about this, the string Multiple may not be so sensible: When someone is looking for a converter from FBX to glTF 2.0, it will not be found...
Maybe there should be some sort of wildcard, e.g. using "*" to indicate multiple formats? (I'd have to take a closer look at how something like this could be aligned with the current implementation of the search+filter functionality...)
Do you have an idea what could be the best approach here?

If we can, I think the best approach would be to explicitly list out the file formats since the field supports a list of strings. This should allow us to add filters for both the Input and Output methods in the future. I've noticed some other places where we can do this separation, for example FBX2gltf (ClayGL), where we currently have a string with multiple comma separated values.
"inputs" : [ "FBX, COLLADA, OBJ" ],

In this case, we show only one entry and using our existing filtering logic, we'd have "FBX, COLLADA, OBJ" filter tag created at init. Breaking these out into individual options allows better tags to be created.
"inputs" : [ "FBX", "COLLADA", "OBJ" ],

Now we have 3 tags created for the Input Methods field, so users could filter on any one of these and get the results they expect. Using the Blackthread.io example from https://github.com/KhronosGroup/glTF-Project-Explorer/blob/master/public/data/glTF-projects-data.json#L1225, we'd list out the list similar to this:
"inputs": [ "3MF", "AMF", "FBX", "OBJ", "glTF 2.0", "glTF 1.0", "COLLADA", "Three.js JSON format", "PCD", "PLY", "STL" ],
"outputs": [ "glTF 2.0" ]

That said, we have 45 entries of "Multiple" at the moment, and only about eight of these have links. I think maybe you and I following the links that are provided and listing out the formats and then leaving "Multiple" where we don't have a good link is a decent start. When we broadcast the existence of this tool, we may want to also ask maintainers of the projects listed by us to at least drop by and update their entries, and explicitly provide guidance asking them to flesh out their list of inputs and outputs.

The fact that some strings had "Not, been, split" could be considered a bug in my initial conversion process. Generally, they should all have been stored as arrays of strings.

I went through the data file (no PR yet), and the result of the first pass is at https://github.com/javagl/glTF-Project-Explorer/commit/f53c3eec184eb68e042b6dcd73043527f7b7bf11

Split inputs/outputs strings:

things like "OBJ, FBX" into "OBJ", "FBX"
"glTF 1.0 and 2.0" into "glTF 1.0", "glTF 2.0"
"Multiple, glTF 2.0" into "Multiple", "glTF 2.0"

Fixed broken links for formats that had been behind "Multiple"
Replaced some "Multiple" entries with lists of file extensions

In some cases, I did not list the supported file formats, but kept the "Multiple" entry, because the information was hard to find, or too long and detailed. The latter refers to cases where the website mentions file format version numbers, or claims a "partial" support, sometimes even mentioning the supported features. (I added links in the description in some cases, but not systematically...)
Many entries had "?" listed as their supported formats. This has mostly been the case for plugins for applications like Maya/Cinema4D/...etc. I replaced the "?" with "Multiple" in these cases, because the file formats will there generally be "all that the application supports".
I'm not sure what's the best solution here. We could gather the supported formats for the "large 3D applications" at some point, and then Copy+Paste them for the importer plugins. Alternatively, we could say that it is an importer/exporter for glTF 2.0, regardless of which formats the application supports. But then, people might not find the plugin when looking for a way to convert their models.
Another question is whether we should differentiate between glTF and GLB somehow. (GLB is sometimes listed explicitly, but usually not...)

Minor other things:

Fixed some input/output mixups
Removed duplicate entry for blackthread.io
Simplygon Cloud seems to no longer exist - should it be removed?

Should I create a PR for that already, so that we can tackle the questions mentioned above in another pass?

Yeah, I'd say lets go ahead and create another PR. Couple thoughts:
Once the announcement goes out, we may have some decent success reaching out the the glTF community at-large and asking them to come update their entries. My hope is that would do a decent job at cleaning up those "Multiple" entries. At least far better than we can do ourselves.
Re: glTF and GLB, I'm torn. I think there's a fair argument to be made that GLB is glTF but it's definitely true that not all tools out there support both. This may be an ask to bring up to the wider group on the weekly call.

This somehow got buried. The changes done in https://github.com/javagl/glTF-Project-Explorer/commit/f53c3eec184eb68e042b6dcd73043527f7b7bf11 seem to basically made their way into the data file (although admittedly, I couldn't find "the" commit where they have been added in the "blame" view).
I'll open another issue for the specific point of glTF vs. GLB


Respawning players after death

We should probably do this since we just implemented PVP

So

http://wiki.vg/Protocol#Client_Status
something like in login.js : I think sendInitialPosition , and spawn but possibly not all of it

So it's needed to make these function available (no copy-pasting !)


test-network-k8s: chaincode deploy step fails on k3s environment

Hello,
I cannot get through chaincode deploy step using test-network-k8s. I was able to do all the steps up to then: cluster init, up, channel create...but when I issues ./network chaincode deploy ... command it got stuck Launching chaincode container "asset-transfer-basic"... and eventually errored exceeding progress deadline.
I tried to diagnose further using k9s tool and as seen from the screenshot below it looks like that the pod failed trying to pull nonexistent image url "docker.io/library/asset-transfer-basic:latest".
My k8s environment is built using k3s. Should that be a problem?
Any help troubleshooting this is appreciated.
Thanks.
[1]

[2]

[3]

note: I have experienced similar error on using sample-network from fabric-operator: https://github.com/hyperledger-labs/fabric-operator/issues/94

relevant bits from network-debug.log:

Content
+ sleep 0.5
+ [[ 4 -lt 1 ]]
+ MODE=chaincode
+ shift
+ '[' chaincode == kind ']'
+ '[' chaincode == unkind ']'
+ [[ chaincode == \c\l\u\s\t\e\r ]]
+ [[ chaincode == \k\8\s ]]
+ [[ chaincode == \k\u\b\e ]]
+ '[' chaincode == up ']'
+ '[' chaincode == down ']'
+ '[' chaincode == channel ']'
+ [[ chaincode == \c\h\a\i\n\c\o\d\e ]]
+ chaincode_command_group deploy asset-transfer-basic ../asset-transfer-basic/chaincode-java
+ COMMAND=deploy
+ shift
+ '[' deploy == deploy ']'
+ log 'Deploying chaincode'
+ echo -e Deploying chaincode
+ deploy_chaincode asset-transfer-basic ../asset-transfer-basic/chaincode-java
+ local cc_name=asset-transfer-basic
+ local cc_label=asset-transfer-basic
++ absolute_path ../asset-transfer-basic/chaincode-java
++ local relative_path=../asset-transfer-basic/chaincode-java
+++ cd ../asset-transfer-basic/chaincode-java
+++ pwd
++ local abspath=/root/fabric-samples/asset-transfer-basic/chaincode-java
++ echo /root/fabric-samples/asset-transfer-basic/chaincode-java
+ local cc_folder=/root/fabric-samples/asset-transfer-basic/chaincode-java
++ mktemp -d
+ local temp_folder=/tmp/tmp.KGrFsMH6Dk
+ local cc_package=/tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ prepare_chaincode_image /root/fabric-samples/asset-transfer-basic/chaincode-java asset-transfer-basic
+ local cc_folder=/root/fabric-samples/asset-transfer-basic/chaincode-java
+ local cc_name=asset-transfer-basic
+ build_chaincode_image /root/fabric-samples/asset-transfer-basic/chaincode-java asset-transfer-basic
+ local cc_folder=/root/fabric-samples/asset-transfer-basic/chaincode-java
+ local cc_name=asset-transfer-basic
+ push_fn 'Building chaincode image asset-transfer-basic'
+ echo -ne '   - Building chaincode image asset-transfer-basic ...'
+ nerdctl build --namespace k8s.io -t asset-transfer-basic /root/fabric-samples/asset-transfer-basic/chaincode-java
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 1.02kB done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.0s

#3 [internal] load metadata for docker.io/library/gradle:jdk11-alpine
#3 DONE 1.7s

#4 [internal] load metadata for docker.io/library/openjdk:11-jre
#4 DONE 1.6s

#5 [internal] load build context
#5 transferring context: 1.20kB done
#5 DONE 0.0s

#6 [stage-1 1/6] FROM docker.io/library/openjdk:11-jre@sha256:356949c3125c4fa8104745e7ea92bd995da4567634e6599b470d2f972d13e0e2
#6 resolve docker.io/library/openjdk:11-jre@sha256:356949c3125c4fa8104745e7ea92bd995da4567634e6599b470d2f972d13e0e2 0.0s done
#6 DONE 0.0s

#7 [gradle_build 1/4] FROM docker.io/library/gradle:jdk11-alpine@sha256:235ce49c53047d8a049e39e89e694639e8fa34096621206acc7bec6c3c630903
#7 resolve docker.io/library/gradle:jdk11-alpine@sha256:235ce49c53047d8a049e39e89e694639e8fa34096621206acc7bec6c3c630903 0.0s done
#7 DONE 0.0s

#8 https://github.com/krallin/tini/releases/download/v0.19.0/tini
#8 DONE 0.7s

#9 [gradle_build 3/4] COPY build.gradle ./
#9 CACHED

#10 [stage-1 2/6] ADD https://github.com/krallin/tini/releases/download/v0.19.0/tini /tini
#10 CACHED

#11 [stage-1 5/6] COPY --chown=javauser:javauser --from=GRADLE_BUILD /home/gradle/build/libs/chaincode.jar /chaincode.jar
#11 CACHED

#12 [stage-1 3/6] RUN chmod +x /tini
#12 CACHED

#13 [stage-1 4/6] RUN addgroup --system javauser && useradd -g javauser javauser
#13 CACHED

#14 [gradle_build 2/4] COPY src/ src/
#14 CACHED

#15 [gradle_build 4/4] RUN gradle --no-daemon build shadowJar -x checkstyleMain -x checkstyleTest
#15 CACHED

#16 [stage-1 6/6] COPY --chown=javauser:javauser docker/docker-entrypoint.sh /docker-entrypoint.sh
#16 CACHED

#17 exporting to docker image format
#17 exporting layers done
#17 exporting manifest sha256:2ec7c9f00f2f325d53bb66e3db7ad1a8be643c6bcc7686c24180fc795d742cb9 done
#17 exporting config sha256:37df60b77385de7a4017634937cbdc99ca14d1385eca4b7428ef24b2eebe8238 done
#17 sending tarball
unpacking docker.io/library/asset-transfer-basic:latest (sha256:2ec7c9f00f2f325d53bb66e3db7ad1a8be643c6bcc7686c24180fc795d742cb9)...
#17 sending tarball 3.1s done
#17 DONE 3.1s
Loaded image: docker.io/library/asset-transfer-basic:latest
+ pop_fn
+ '[' 0 -eq 0 ']'
+ echo -ne '\r✅'
+ echo ''
+ return
+ '[' k3s == k3s ']'
+ export CHAINCODE_IMAGE=asset-transfer-basic
+ CHAINCODE_IMAGE=asset-transfer-basic
+ package_chaincode asset-transfer-basic asset-transfer-basic /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ '[' ccaas == k8s ']'
+ '[' ccaas == ccaas ']'
+ package_ccaas_chaincode asset-transfer-basic asset-transfer-basic /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ local cc_name=asset-transfer-basic
+ local cc_label=asset-transfer-basic
+ local cc_archive=/tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
++ dirname /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ local cc_folder=/tmp/tmp.KGrFsMH6Dk
++ basename /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ local archive_name=asset-transfer-basic.tgz
+ push_fn 'Packaging ccaas chaincode asset-transfer-basic'
+ echo -ne '   - Packaging ccaas chaincode asset-transfer-basic ...'
+ mkdir -p /tmp/tmp.KGrFsMH6Dk
+ local 'cc_default_address={{.peername}}-ccaas-asset-transfer-basic:9999'
+ local 'cc_address={{.peername}}-ccaas-asset-transfer-basic:9999'
+ cat
+ cat
+ tar -C /tmp/tmp.KGrFsMH6Dk -zcf /tmp/tmp.KGrFsMH6Dk/code.tar.gz connection.json
+ tar -C /tmp/tmp.KGrFsMH6Dk -zcf /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz code.tar.gz metadata.json
+ rm /tmp/tmp.KGrFsMH6Dk/code.tar.gz
+ pop_fn
+ '[' 0 -eq 0 ']'
+ echo -ne '\r✅'
+ echo ''
+ return
+ '[' ccaas == ccaas ']'
+ set_chaincode_id /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
+ local cc_package=/tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
++ shasum -a 256 /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz
++ tr -s ' '
++ cut -d ' ' -f 1
+ cc_sha256=353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a
++ tar zxfO /tmp/tmp.KGrFsMH6Dk/asset-transfer-basic.tgz metadata.json
++ jq -r .label
+ cc_label=asset-transfer-basic
+ CHAINCODE_ID=asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a
+ launch_chaincode asset-transfer-basic asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a asset-transfer-basic
+ local org=org1
+ local cc_name=asset-transfer-basic
+ local cc_id=asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a
+ local cc_image=asset-transfer-basic
+ launch_chaincode_service org1 peer1 asset-transfer-basic asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a asset-transfer-basic
+ local org=org1
+ local peer=peer1
+ local cc_name=asset-transfer-basic
+ local cc_id=asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a
+ local cc_image=asset-transfer-basic
+ push_fn 'Launching chaincode container "asset-transfer-basic"'
+ echo -ne '   - Launching chaincode container "asset-transfer-basic" ...'
+ cat kube/org1/org1-cc-template.yaml
+ sed 's,{{CHAINCODE_NAME}},asset-transfer-basic,g'
+ sed 's,{{CHAINCODE_ID}},asset-transfer-basic:353334bac2ad1c949c9ad48a62940feeebad9a6a0cb17522d23c5812e6cca99a,g'
+ sed 's,{{CHAINCODE_IMAGE}},asset-transfer-basic,g'
+ exec kubectl -n test-network apply -f -
+ sed 's,{{PEER_NAME}},peer1,g'
deployment.apps/org1peer1-ccaas-asset-transfer-basic created
service/org1peer1-ccaas-asset-transfer-basic created
+ kubectl -n test-network rollout status deploy/org1peer1-ccaas-asset-transfer-basic
Waiting for deployment "org1peer1-ccaas-asset-transfer-basic" rollout to finish: 0 of 1 updated replicas are available...
error: deployment "org1peer1-ccaas-asset-transfer-basic" exceeded its progress deadline
+ exit_fn
+ rc=1
+ set +x

I must have been mistaken; I was able to run past chaincode deployment and query/invoke when I reinitialized environment with k3s this time specifying to use docker runtime.
I thought using the below configuration should suffice to make the script compatible with default k3s(containerd runtime), but I must have been wrong.
export TEST_NETWORK_CLUSTER_RUNTIME="k3s"
export TEST_NETWORK_CONTAINER_NAMESPACE="--namespace k8s.io"
export CONTAINER_CLI="nerdctl"

Closing the issue as I was able to get past the problem albeit with a different configuration.


Put area before resource in Invoke-VSteam Request, add completers and give allow it expand values

Area comes first on the URL path and it's confusing to have it suggested first.
It would be nice if -area tab completed and if -area was present the -resource was also tab completable . At least 50% of the time the value property of the output is required so a switch which says give me the values would be helpful.

do you see an API for the completion or do you mean hard coded?

As far as I can see there is no API to find out what available, so wrote have a script  (generate-areaClasses.ps1) which  re-writes the completer classes and adds everything the module knows about. I know "wiki" is missing, and there are probably others which need to be typed. I might read down the documents for any more, it's just a time saver, not a validator. I was doing other completers and just got tired of (a) Having the parameters in a different order from how the URI got build , and (b) typing them all the time. 30 minutes writing which is paying itself back 2 or 3 seconds at a time!

We can get the areas and resources from Get-VSTeamOption. I am working on this now. I have it where you can tab complete Area. Will create the resource completer next. The order of the parameters does not mater in the definition of the function just the order passed to the function.

This was a great idea! I am close to being done.

This will be in next release.

Glad you like the idea. The reason for having area before resource is when you tab complete the parameters it makes more sense to them in the order they appear in the URL . Having resource first leads to putting "teamsettings" first and "work" second and building a broken URL. After doing it for the 100th time I just swapped the parameter order on my version.


Test result pane: rerun/debug doesn't work

On leaf nodes in the test result pane, right click offers rerun and debug as expected, but they do nothing:

And for higher level nodes, no such option is shown at all:

The corresponding gutter icons in the code do show both buttons, but they only work for top and leaf nodes
My testst use FreeSpec
IntelliJ IDEA 2022.3.1
kotest plugin 1.2.63-223.4884.69-EAP-SNAPSHOT (and earlier)

It's a limitation of how intellij handles junit sources. Despite providing the link back it doesn't work for parent tests.

But it works for junit tests


module go version

It's possible for you to downgrade the version inside your go.mod to go1.20?
the new way to handle the module and go version is strict.
https://github.com/golangci/golangci-lint/actions/runs/5893637045/job/15985603630?pr=4023
https://go.dev/blog/toolchain
https://github.com/golangci/golangci-lint/pull/4021

@ldez Hi! Done.
It's my bad – these linters are simple and do not require 1.21 API.
But what about the new ones?


Add hans.gerwitz.com

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[x] This site is not an ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: hans.gerwitz.com
  url: https://hans.gerwitz.com
  size: 347
  last_checked: 2023-11-20

GTMetrix Report: https://seirdy.one/posts/2023/05/02/fediverse-blocklists/

Looks like you pasted the wrong link. Do you mind providing a GTMetrix link?


"How to compile PDFKit for use in the browser" fails with "Cannot find module"

Bug Report
Description of the problem
Hi everyone.
I'm following this wiki page to use PDFKit in the browser.
However, when I run the last command, I get:
Error: Cannot find module 'C:\path\to\folder\node_modules\pdfkit\lib\document.coffee' from 'C:\path\to\folder'
    at C:\path\to\folder\node_modules\browser-resolve\node_modules\resolve\lib\async.js:55:21
    at load (C:\path\to\folder\node_modules\browser-resolve\node_modules\resolve\lib\async.js:69:43)
    at onex (C:\path\to\folder\node_modules\browser-resolve\node_modules\resolve\lib\async.js:92:31)
    at C:\path\to\folder\node_modules\browser-resolve\node_modules\resolve\lib\async.js:22:47
    at FSReqWrap.oncomplete (fs.js:152:21)

I'm trying other ways to make PDFKit work in the browser, but none was successful so far.
Thanks in advance.
Code sample

Your environment

pdfkit version: 0.9.0
Node version: 8.9.1
Browser version (if applicable):
Operating System: Windows 10 x64

This wiki doesn't work since v0.9.0. I wrote it when pdfkit was written in coffeescript. Unfortunately I don't know how to make the single-file bundle for the browsers with the current pdfkit version.
It would be great if someone could update this wiki page...

I will update Wiki. For now look at demo folder and browser-demo npm script

I fixed the wiki: https://github.com/foliojs/pdfkit/wiki/How-to-compile-standalone-PDFKit-for-use-in-the-browser and added a complete example at https://github.com/blikblum/pdfkit-webpack-example


Add home button

Adds a check to the AddToHome button to see if the widget is already added to the layout

Contributor License Agreement adherence:

[X] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

📓 Note 📓
Conventional commits supports including ticket information as well.
for example, in Jira style commit messages the format is
MUMUP-2580 Adding layout checks to messages filter

in conventional commit format it would be written
fix(messages): conditionally check if "add to home" is in layout

add conditional check to message's angular filter

MUMUP-2580


Adding initial code

Good to be merged @danharvey ?

One comment on the config, otherwise looks good.


[Low Priority] Accordion weird behaviour

When in responsive display, there is a weird behaviour when clicking on the accordion items, the whole sections gets highlighted.
Everything works well, but only the highlight is done for a second on the whole container

This is just a product of the chrome dev tools to make it easier for the user to understand what has been clicked. On the actual mobile device this does not happen


test: Cypress | Firestore added validations + CI Stabilize

Description

This PR fixes the flaky /ClientSide/OtherUIFeatures/Omnibar_spec.js
Adds validation for Firestore Ds
Removed added parameter from CreateDataSource()
Fixed MsSQL to use same DS thruout
Trial fix on StubWindowNAssert() to check the external link navigation related issues
using TS Refresh() in Onboarding.skipSignposting() + Added timeout for #sidebar visibility to check app load empty toast issue
Trial fix cypress/e2e/Regression/ClientSide/Binding/Button_Text_WithRecaptcha_spec.js

Type of change

Script fix (non-breaking change which fixes an issue)

Testing
How Has This Been Tested?

[X] Cypress CI runs

Checklist:
QA activity:

[X] Added Test Plan Approved label after Cypress tests were reviewed

/ci-test-limit

/ci-test-limit runId=6246910177

/ci-test-limit runId=6246910177

/ci-test-limit runId=6246910177

/ci-test-limit runId=6246910177

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6248359328

/ci-test-limit runId=6250895461

/ci-test-limit runId=6250895461

/ci-test-limit runId=6250895461

/ci-test-limit runId=6250895461

/ci-test-limit runId=6250895461


enable GL errors in tests via commandLine argument, and fix a test

Now we can enable GL errors logging when running tests, helpful for debugging.
i also fixed the VertexBufferObjectShaderTest :

VertexBufferObjectWithVAO must be used when gl30 is enabled
gl.glEnable(GL20.GL_TEXTURE_2D) is only valid with fixed function pipeline (which is not the case with libGDX).

We usually don't format tests. If this is something we want to do from now, i could format my changes in tests, not a problem, just tell me.

Dunno, I think it would make sense. But tbh it doesn't really matter.


adding color parameter to heatmap function

I was asked by a user to render a heatmap table using green instead of red! Because "red" is hard-coded, I was forced to create a new version of the heatmap function.

Thanks for the PR! I will likely expand it a bit before merging so that it uses the rendererOptions mechanism.

You can now specify a custom color scale function, see the example here: http://nicolas.kruchten.com/pivottable/examples/montreal_2014.html


530 duplicate year

Changed logic in duplicate public grouping to allow the year to pass as long as it's within +/-2 years
fixes #530

This should be good once the conflict is resolved.


Error: manifest does not contain minimum number of descriptors (2), descriptors found: 1

What are the causes for this error?  The charts are being built with helm = 3.8 but still I see this error on  Helm upgrade.

Can you share your template?

parameters:
DEPLOY_SP: ''
DEPLOY_PASSWORD: ''
DEPLOY_TENANT_ID: ''
AKS_CLUSTER_NAME: ''
AKS_RESOURCE_GROUP: ''
REGISTRY_SERVER_NAME: ''
REGISTRY_LOGIN: ''
REGISTRY_PASSWORD: ''
RELEASE_TAG: ''
HELM_PUSH_TIMEOUT_SECONDS: '45'
steps:

bash: |
az login --identity
az aks get-credentials
-n ${{ parameters.AKS_CLUSTER_NAME }}
-g ${{ parameters.AKS_RESOURCE_GROUP }}
--overwrite-existing
echo "************ HELM PACKAGING ********"
for package_name in $(system.defaultWorkingDirectory)/src/Services/Auth/Auth/charts/auth $(system.defaultWorkingDirectory)/src/inkling/compiler-service/charts/compiler $(system.defaultWorkingDirectory)/src/backend/converter/charts/converter $(system.defaultWorkingDirectory)/src/Services/ControlPlane/ControlPlane/charts/controlplane $(system.defaultWorkingDirectory)/src/Services/DataManagement/DataManagement/charts/datamanagement $(system.defaultWorkingDirectory)/src/Services/DataService/charts/dataservice $(system.defaultWorkingDirectory)/src/Services/Orchestration/charts/orchestrationengine $(system.defaultWorkingDirectory)/src/Services/TickTock/charts/ticktock $(system.defaultWorkingDirectory)/src/Services/OfflineCleanup/charts/offlinecleanup $(system.defaultWorkingDirectory)/src/Services/BillingJob/charts/billingjob $(system.defaultWorkingDirectory)/src/Services/InklingLighthouseJob/charts/inklinglighthousejob $(system.defaultWorkingDirectory)/src/Services/Prober/Prober/charts/prober $(system.defaultWorkingDirectory)/src/Services/GenericWorkflowService/GenericWorkflowService/charts/genericworkflowservice $(system.defaultWorkingDirectory)/src/Services/SimControl/SimControl/charts/simcontrol $(system.defaultWorkingDirectory)/src/Services/SimulatorGateway/SimulatorGateway/charts/simulatorgateway $(system.defaultWorkingDirectory)/src/Services/ManagedSimService/ManagedSimService/charts/managedsimservice  $(system.defaultWorkingDirectory)/src/Services/WatsonagentVerifier/WatsonagentVerifier/charts $(system.defaultWorkingDirectory)/infrastructure/kube/external_charts/consul-inject; do
helm package --version ${{ parameters.RELEASE_TAG }} --destination $(build.artifactStagingDirectory) $package_name
done
continueOnError: false
displayName: 'helm package auth, compiler, converter, controlplane, datamanagement, dataservice(DAS), orchestrationengine, ticktock, offlinecleanup, billingjob, inklinglighthousejob, prober, genericworkflowservice, simcontrol, simulatorgateway, managedsimservice, watsonagentverifier, consul-inject'

bash: |
timeout=${{ parameters.HELM_PUSH_TIMEOUT_SECONDS }}

How does this helm registry login work -
1. We provided Contributor Role to VMSS Managed Identity (this step is done in azure portal)
2. We then login using MSI of the VMSS (az login --identity)
3. We then login into the helm registry using a password and a username.
Here we get password using az acr login as we already have provided contributor role to VMSS MSI
Used guidelines from : https://docs.microsoft.com/en-us/azure/container-registry/container-registry-helm-repos#authenticate-with-the-registry

USER_NAME="00000000-0000-0000-0000-000000000000"
PASSWORD=$(az acr login --name $(registryName) --expose-token --output tsv --query accessToken)
helm registry login $(registryName).azurecr.io  --username $USER_NAME  --password $PASSWORD
echo "Helm registry login done"
echo "************ PUSHING HELM PACKAGES INTO ACR REPO "
for chart in auth compiler converter controlplane datamanagement dataservice orchestrationengine ticktock offlinecleanup billingjob inklinglighthousejob prober genericworkflowservice simcontrol simulatorgateway managedsimservice watsonagentverifier consul-inject; do
retries=8
pushExitCode=''
echo "**** PUSHING HELM PACKAGE ${chart}-${{ parameters.RELEASE_TAG }}.tgz INTO REPO "
while [ $retries -gt 0 ]; do
# timeout function exits with code 124 when inside command 'helm push' times out
echo "Starting helm push for ${chart}"
timeout $timeout helm push $(build.artifactStagingDirectory)/$chart-${{ parameters.RELEASE_TAG }}.tgz  oci://$(registryName).azurecr.io/bonsai
pushExitCode=$?
retries=$((retries-1))
if test $pushExitCode -ne 0; then
# Something went wrong during helm push command, potentially it timed out.
if test $pushExitCode -eq 124; then
echo "**** HELM PUSH TIMED OUT AFTER ${timeout}s ... ********"
fi
    # Sleep to give it time to populate then check if helm package still got pushed successfully.
    # Scenario could be that on first try helm push timed out due to known bug in Azure CLI or that the package already exists due to a previous successful run.
    sleep 3
    helm show chart $chart --version ${{ parameters.RELEASE_TAG }}
    showExitCode=$?
    if test $showExitCode -eq 0; then
      # This means helm push actually succeeded earlier, despite Azure CLI not behaving as expected.
      echo "************ HELM PUSH SUCCEEDED, DESPITE AZURE CLI CLIENT TIMING OUT OR REPORTING ERROR. MOVING TO NEXT PACKAGE... ********"
      break
    fi

    if [ $retries -eq 0 ]; then
      echo "************ HELM PUSH FAILED FOR PACKAGE ${chart}-${{ parameters.RELEASE_TAG }}.tgz WITH EXIT CODE ${pushExitCode}. NO MORE RETRIES... ********"
      exit $pushExitCode
    else
      # Package did not get pushed which means helm push failed. Retry
      echo "************ HELM PUSH FAILED WITH EXIT CODE ${pushExitCode}, RETRYING ${retries} MORE TIMES... ********"
    fi
  else
    # Helm push succeeded
    break
  fi
done
echo "************ COMPLETED PUSHING HELM PACKAGE ${chart}-${{ parameters.RELEASE_TAG }}.tgz INTO REPO ********"

done
continueOnError: false
displayName: 'az acr helm push auth, compiler, converter, controlplane, datamanagement, dataservice(DAS), orchestrationengine, ticktock, offlinecleanup, billingjob, inklinglighthousejob, prober, genericworkflowservice, simcontrol, simulatorgateway, managedsimservice, watsonagentverifier, consul-inject'

Error I get:
helm.sh/helm/v3/pkg/getter/ocigetter.go:53

helm.sh/helm/v3/pkg/getter.(*OCIGetter).Get
helm.sh/helm/v3/pkg/getter/ocigetter.go:36
helm.sh/helm/v3/pkg/downloader.(*ChartDownloader).DownloadTo
helm.sh/helm/v3/pkg/downloader/chart_downloader.go:100
helm.sh/helm/v3/pkg/action.(*ChartPathOptions).LocateChart
helm.sh/helm/v3/pkg/action/install.go:753
main.newUpgradeCmd.func2
helm.sh/helm/v3/cmd/helm/upgrade.go:135
github.com/spf13/cobra.(*Command).execute
github.com/spf13/cobra@v1.3.0/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/cobra@v1.3.0/command.go:974
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/cobra@v1.3.0/command.go:902
main.main
helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
runtime/proc.go:255
runtime.goexit
runtime/asm_amd64.s:1581
************ HELM UPGRADE FAILED WITH EXIT CODE 1, RETRYING 3 MORE TIMES... ********
history.go:56: [debug] getting history for release auth
Error: manifest does not contain minimum number of descriptors (2), descriptors found: 1
helm.go:84: [debug] manifest does not contain minimum number of descriptors (2), descripto

Im getting this error while I trying to helm pull from dockerhub when I put ~ as a version:
~5.0.0-helm

I found that this error occurs when I have not authenticated to the helm repository I have pushed my chart to. Once I authenticate, push my chart, then the error is gone when using the chart.

I found that this error occurs when I have not authenticated to the helm repository I have pushed my chart to. Once I authenticate, push my chart, then the error is gone when using the chart. For some reason I dont get a 403, just this particular error on using the chart.

Would you be able to provide more context into the issues that you experienced?

I am using an artifactory repo. This error occurs when pushing as anon


MuckRock request 17046-17143

via muckrock
I requested 17046 - 17143 without the 8500 which i believe are Lexus Nexus checks

🐈


ENYO-5967: Cleanup and refactor pattern-list-details

This poor thing just needed some ❤.

At least one of those should be possible.

@webOS101 Updated the position of the city name in zoomed mode.


Optimize dynamicImports of native calls

As discussed in https://github.com/scala-js/scala-js/pull/4262#issuecomment-738698144

To optimize the imports, I need to retrieve the load spec (if any) for classes referenced in a specific method body (in computeNewAttributes). But that makes the attributes depend on other things than the method body itself. Options I see:

Mark the method attributes as "dirty" in this case and always recalculate them (even if the method's version didn't change).
Defer retrieval to the optimization stage (and abort inlining if the referenced class isn't native or not an import).
Track method/class dependencies and introduce a pre-UPDATE UPDATE pass.
Do not do this and wait for somebody to complain.

@sjrd ideas, opinions?

To optimize the imports, I need to retrieve the load spec (if any) for classes referenced in a specific method body (in computeNewAttributes). But that makes the attributes depend on other things than the method body itself. Options I see:

Mark the method attributes as "dirty" in this case and always recalculate them (even if the method's version didn't change).
Defer retrieval to the optimization stage (and abort inlining if the referenced class isn't native or not an import).
Track method/class dependencies and introduce a pre-UPDATE UPDATE pass.
Do not do this and wait for somebody to complain.

@sjrd ideas, opinions?

IMO this:

Defer retrieval to the optimization stage (and abort inlining if the referenced class isn't native or not an import).

is the best way to deal with this. Always dirty could have weird consequences. I'm not sure exactly what your third suggestion means.
Having the optimizer ask for that info and backtrack sounds reasonable.

IMO this:

Defer retrieval to the optimization stage (and abort inlining if the referenced class isn't native or not an import).

is the best way to deal with this. Always dirty could have weird consequences. I'm not sure exactly what your third suggestion means.
Having the optimizer ask for that info and backtrack sounds reasonable.

I'm not sure exactly what your third suggestion means.

What I meant by that is recording which methods (when calculating attributes) needed information about which classes. If these classes change, invalidate the method attributes. So an overall pass would look like:

Diff class changes / invalidate method attributes
Re-calculate method attributes (currently called UPDATE pass)
Re-optimize tagged methods (currently called PROCESS pass)

My concern with the defer retrieval is that we need to duplicate some tree matching between update and optimize :-/

I'm not sure exactly what your third suggestion means.

What I meant by that is recording which methods (when calculating attributes) needed information about which classes. If these classes change, invalidate the method attributes. So an overall pass would look like:

Diff class changes / invalidate method attributes
Re-calculate method attributes (currently called UPDATE pass)
Re-optimize tagged methods (currently called PROCESS pass)

My concern with the defer retrieval is that we need to duplicate some tree matching between update and optimize :-/

My concern with the defer retrieval is that we need to duplicate some tree matching between update and optimize :-/

To me it seems that that concern would be dwarfed by the added complexity (and impact on performance) of another entire pass.

My concern with the defer retrieval is that we need to duplicate some tree matching between update and optimize :-/

To me it seems that that concern would be dwarfed by the added complexity (and impact on performance) of another entire pass.

Well, to be clear, the additional pass would only be on classes, not on the methods. But maybe that is fair. I'll fiddle with it more once I fixed the other mess :P

Well, to be clear, the additional pass would only be on classes, not on the methods. But maybe that is fair. I'll fiddle with it more once I fixed the other mess :P

would that be a viable option? I can recognize thunks by the common superclass (compiler runtime lib specific name, but we have a lot of precedent for runtime / optimizer collaboration like that).

Yes, that's a possibility. The optimizer can recognize shapes and references to stdlib stuff to do its job. However, it must not assume anything about the semantics of non-stdlib code. It can assume that scala.scalajs.runtime.DynamicImportThunk is what it is in the stdlib; but it may not assume that any class extending DynamicImportThunk is necessarily emitted for a js.dynamicImport and therefore follows the shape and semantics currently emitted by the compiler.

We need to be extremely careful with these, since they might pull in lots of types too eagerly (depending on the exact usage site).

I don't think this is an issue in practice. Any type t appearing in this .asInstanceOf[t] will also appear at the call site of the js.dynamicImport, if it is actually used. In the above example, this doesn't happen because the result of dynamicImport is thrown away, but if you follow it with .then[Unit](z => println(z)), then the .asInstanceOf[int] also appears in the lambda passed to then, which is in the calling module.
So any practical use of js.dynamicImport will have the same cast in the calling module than in the called module.


Feature request: Word count in dialogue and quest boards

Hello!
Best wishes for 2021! I come again today with a proposal, which I hope can be added to the base product.
What I come to propose today is a small feature to add a word count on quest (text boxes) and dialogue boards. Allow me to explain the use case, as I can imagine that this doesn't seem very useful at first glance.
When building a game, one may hire contractors to do small parts of the game. For example, side quests. These contractors are commonly paid on a per-word basis. When someone, as a contractor, builds a side quest, then the payout of this is done based on the amount of words in that quest and/or dialogue. Currently, we didn't find an easy or straight forward way to simply count the words, hence why I'd like to propose this improvement. Alternatives, such as ArcWeave, do have this functionality (but are in return missing a lot of functionality that GoNorth does offer).
Please refer to the below user story if this adds further clearance;
As a project manager / team lead, I would like to be able to see a word count on quest and dialogue boards, so that I can easily calculate contractor payouts for quests/dialogue that this person worked on.
Please share us your thoughts.

Hi,
thanks for the idea and best wishes to you too!
Your idea sounds reasonable in the context you outlined. I will include statistics in general (amount of nodes, words and so on) in an upcoming release. Since I am currently finalizing the current release (christmas and new years eve took some time where I could not continue to work on it), this will not be included in that release.

Hi,
thanks for the idea and best wishes to you too!
Your idea sounds reasonable in the context you outlined. I will include statistics in general (amount of nodes, words and so on) in an upcoming release. Since I am currently finalizing the current release (christmas and new years eve took some time where I could not continue to work on it), this will not be included in that release.

Implemented with the release v<IP_ADDRESS>. Statistics are supported for dialogs, quests and wiki.


Add Kaushikdey647

What changes does this PR do?
Adds my username to the README.md
Screenshots (If any)
Questions

Changes Reflected in commit 7334e3ed5ce43323e503dca9247ee33983467293

So how is the Pull Request Completed?

So how is the Pull Request Completed?

Soon some maintainer will merge (adding the changes) this Pull Request to the main branch,:)


Document the file naming scheme

See https://github.com/google/skywater-pdk-sky130-raw-data/issues/1#issuecomment-1202386286
@miesli inferred that the naming scheme could be something like:
sky130_fd_pr__nfet_01v8_w0p36u_l0p15u_m1(8701_9_10_IDVD).mdm
               ^- Device name
                         ^-  width in m
                                 ^- length in m
                                       ^- metal contact
                                            ^- Here is 8701_9_10 and 8701_11_12. What is the difference ?
                                                     ^- measurement curve (either IDVD or IDVG)

@akinakturk can you confirm that this is the case?
I'd be good to add it to the README and/or the docs directory.

I tried to document the naming scheme for the base level primitives at http://bit.ly/open-source-pdks-naming and https://bit.ly/sky130-names

I believe that the numbers in brackets are connected to the test point names on the test tile.
At the moment we don't have permission to publish publicly the test tile documentation. I'm working with SkyWater to change that and there is a public effort to recreate the documentation from scratch at http://bit.ly/sky130-mpw1-testtile-notes

You are mostly right about the naming scheme:
sky130_fd_pr__nfet_01v8_w0p36u_l0p15u_m1(8701_9_10_IDVD).mdm
^- Device name
^-  width in microns => 0 point 36
micrometers (u is commonly used for microns)
^- length in microns => 0 point 36 micrometers
^- multiplication factor =>
shows how many devices are in parallel, m=1 corresponds to a single device
^- Here is 8701_9_10 and
8701_11_12. What is the difference ?
These numbers come from the skywater chip. The first is the module
number (each module has 12 pads associated with it). The following are
some of the pad numbers.
Pads 9 and 10 correspond to the source and drain pad numbers of one of
the discrete MOSFETs (gate and body are shared within this module.
Module number, source and drain
pads describe the location of this device on the chip)
                                                 ^- measurement

curve (either IDVD or IDVG)
Akin
On Tue, Aug 2, 2022 at 10:29 AM Johan Euphrosine @.***>
wrote:

See #1 (comment)
https://github.com/google/skywater-pdk-sky130-raw-data/issues/1#issuecomment-1202386286
@miesli https://github.com/miesli inferred that the naming scheme could
be something like:
sky130_fd_pr__nfet_01v8_w0p36u_l0p15u_m1(8701_9_10_IDVD).mdm
^- Device name
^-  width in m
^- length in m
^- metal contact
^- Here is 8701_9_10 and 8701_11_12. What is the difference ?
^- measurement curve (either IDVD or IDVG)
@akinakturk https://github.com/akinakturk can you confirm that this is
the case?
I'd be good to add it to the README and/or the docs directory.
—
Reply to this email directly, view it on GitHub
https://github.com/google/skywater-pdk-sky130-raw-data/issues/9, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPNITQENKXVA2IXGUSVLSDVXEWDRANCNFSM55LMF4GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

Akin Akturk
CoolCAD Electronics LLC
5000 College Avenue, Ste. 2105
College Park, MD 20740

Thank you for the clarification (I attributed the "u" to the number of the length and width and not as a unit. So in the end we both arrive at the same value).
In my new example, how to read the data using DMT, we encountered an unexpected behavior. The plot shows the charateristic ID(VG) for all nfet_01v8 with length 0.5um. The device from the module 2602 really differs from the other ones. Do you have an explanation for that?

The documentation for these test structures do not provide much
information, but I believe the difference is due to some stress effects
(assuming that these are the same type of devices). See below.
2602: "nfet w/ sep sb ; w=1.000; l=0.500;"
8436 9 10: "w=0.42; l=0.5; m=1;sa=2.5;sb=2.5;prox_count=0"
8436 10 11: "w=0.42; l=0.5; m=1;sa=1.11;sb=1.11;prox_count=0"
8436 11 12: "w=0.42; l=0.5; m=1;sa=0.68;sb=0.68;prox_count=0"
8701 7 8:"w=0.65; l=0.5; m=1; contact-gate=0.050um"
8701 5 6:"w=0.42; l=0.5; m=1; contact-gate=0.050um"
The main differences between these are w and sa/sb (stress parameters). By
the way, currents do scale with w; however, they do not always scale
linearly with w. Especially for "narrow" devices, the narrow width effects
are pronounced.
Another and probably the most important difference is the device name used
in device descriptions. Modules 8436 and 8701  are labeled as "nshort"
devices. This is the name skywater uses. These are "standard" thin oxide
n-channel FETs.
Mismatch module such as 2602 is labeled as "fet mismatch nfet". Based on w
and l values, and other mismatch module labels, nshort is the best name to
describe this device. Mismatch modules 2602, 2605, 2607, 2608, 2611, 2612,
2618, 2622, 2624, 2627 have these generic device names, as opposed to
standard device names such as nshort. Based on w and l, and the device name
used, you need to guess what each of these devices corresponds to.
Hope this helps.
Akin
On Wed, Aug 3, 2022 at 4:59 PM miesli @.***> wrote:

Thank you for the clarification (I attributed the "u" to the number of the
length and width and not as a unit. So in the end we both arrive at the
same value).
In my new example, how to read the data using DMT, we encountered an
unexpected behavior. The plot
https://dmt.semimod.de/examples/readin_dut_lib.html#the-generated-files
shows the charateristic ID(VG) for all nfet_01v8 with length 0.5um. The
device from the module 2602 really differs from the other ones. Do you have
an explanation for that?
—
Reply to this email directly, view it on GitHub
https://github.com/google/skywater-pdk-sky130-raw-data/issues/9#issuecomment-1204477355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPNITSYUG6U2DDZO5RECU3VXLMTRANCNFSM55LMF4GA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

Akin Akturk
CoolCAD Electronics LLC
5000 College Avenue, Ste. 2105
College Park, MD 20740


Error installing ext_metrics on Kibana 5.0.0 using bin/kibana-plugin install https://github.com/ommsolutions/kibana_ext_metrics_vis/releases/download/0.1.0/extended_metric_vis.zip

Installing the plugin i'm getting this error :
ERROR in ./plugins/area3d_vis/public/area3d_vis_controller.js
Module not found: Error: Cannot resolve module 'vis' in /usr/share/kibana/plugins/area3d_vis/public
@ ./plugins/area3d_vis/public/area3d_vis_controller.js 19:11-25

area3d_vis is a different plugin - this should have nothing to do with the extended_metric_vis in fact this plugin (when using the plugin-installer) does not even have access to the folder ./plugins/area3d_vis/
Have you checked with https://github.com/JuanCarniglia/area3d_vis yet ?

You're right sorry for disturbance. It works correctly, thank you for this plugin 👍


total_heart_rate_zone_durations  data isn't correct

I'm trying to figure out where this data is coming from or how it's getting generated.
Comparing the effort_zones data I pulled out of inspector vs what shows up in the JSON are very different.
For my recent 15 minute ride here's the data I get.
From Peloton performance_graph.json. The numbers here correlate to seconds.
{
	"effort_zones": {
		"total_effort_points": 29.4,
		"heart_rate_zone_durations": {
			"heart_rate_z1_duration": 0,
			"heart_rate_z2_duration": 94,
			"heart_rate_z3_duration": 187,
			"heart_rate_z4_duration": 617,
			"heart_rate_z5_duration": 0
		}
	}
}

From pylotoncycle I get the following. I can't tell what the numbers correlate to, and taken to percentages it's still not comparable to the peloton data.
"total_heart_rate_zone_durations": {
            "heart_rate_z1_duration": 299,
            "heart_rate_z2_duration": 505,
            "heart_rate_z3_duration": 1766,
            "heart_rate_z4_duration": 1112,
            "heart_rate_z5_duration": 0
        },

I checked my rides and it's not a one off it's consistently very different data.
Is this intentional? If so, what units are being used for the heart rate zones? Is there a way to convert or just get the raw data?
Thanks!

I have an idea here. I'll throw together a PR and we'll see how you feel about it.


Build / Run Scripts don't end up in generated project

Attempting to generate a project with run scripts, and finding that they aren't ending up in the generated project.
Version: 2.0.0 and 1.11.2
example.yml
name: iOSApp
options:
  bundleIdPrefix: ios.app.test.1234512345
targets:
  - name: The-App-iOS
    type: application
    platform: iOS
    deploymentTarget: 10.0
    preBuildScripts:
      - name: ExampleA
        script: ls
    postCompileScripts:
      - name: ExampleB
        script: ls
    postBuildScripts:
      - name: ExampleC
        script: ls
      - name: ExampleB
        path: ls

Running xcodegen --spec example.yml
I've tried many things, such as adding / removing sources / trying a different script. It just doesn't seem to work. Any idea what is going on?
Thanks!

All of those names are only for the master branch, since they haven't been released yet. Use prebuildScripts and postbuildScripts for now (postCompileScripts isn't supported before master).

Ah thanks for the clarification.
But should prebuildScripts and postbuildScripts exist in version 2.0.0?

Yes, both the prebuildScripts and preBuildScripts versions should work in master, but only prebuildScripts will work in 2.0.0.

Yeah there was a backwards compatible change in the casing of ‘Build` if that wasn’t clear.
Use lowercase B for 2.0.0

Hehe, this took me way too long to track down today 😄
Any ETA on when we can release a 2.1.0 with this feature in it? ❤


doc: reformat README.md

reformat for better readability

no longer necessary. The issue is the prow CI config was not moved to ubi9, so the binaries failed to start for linking error, so the subscription never completes, so the lane fails.


Logout doesn't work after login if user has not navigated to another page before clicking the button (AntiForgery issue)

This seems to be an issue with Asp.Net anti forgery tokens not working with HTMX OOB updates.
If the user navigates to another page or refreshes the browser then the button works.

A temp fix was committed here 70044a7
To fix properly maybe we can try having HTMX do a full page swap if login success and swap only the form on error?


Fix/tx history updates

#85ztrxnyf
Status was not updating becouse of PayloadDiffer finding difference for amountWithDetails and thus updating amountWithDetails in resolvePayload, ignoring updates of statusAppearance

Task linked: CU-85ztrxnyf Android. Fix EVM transactions status realtime update


Api

What is currently broken for sure is the userExists function in AddUser.php

Oh and the last one, I forgot to mention, but I think hash function will return password that is longer than the one that is allowed in our database. Possible solution is to increase the length of the password stored in the database to something like 256 characters.

w.r.t. the hashed password length issue it looks like md5 creates hashed passwords that are 32 chars long, so we should be ok there.

w.r.t. the hashed password length issue it looks like md5 creates hashed passwords that are 32 chars long, so we should be ok there.
good to know


Add processor fees amount on the "Mark as unpaid" modal

Follow up on https://github.com/opencollective/opencollective-frontend/pull/4394
Mark as unpaid modal currently looks like in the screenshot below. Adding the processor fees in the checkbox label could add some clarity:

Also refund payment processor fees ($2.36)

If the processor fees are 0, we shouldn't display the checkbox.

Specs
API

[ ] On GQLV2, add a field to retrieve the transactions linked to the expense

Frontend

[ ] Fetch the transaction, and use the paymentProcessorFeeInHostCurrency to display the label

I would like to work on this Issue


Use isort black profile

What does this PR do?

Use https://timothycrosley.github.io/isort/docs/configuration/profiles/#black
Then run isort <check> on all checks.
Refs #7060
Motivation

Use defaults to reduce configuration options.
Additional Notes

Used this script to apply isort (using ddev test -fs <check> would have taken too long):
from pathlib import Path
from subprocess import call

from tqdm import tqdm

checks = [
    path for path in Path('.').iterdir()
    if path.is_dir() and not path.name.startswith(('.', '_')) and path.name != 'venv'
]

for check in tqdm(checks):
    command = ['isort', check]
    call(command)

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Closing in favor of #7445


[#31] resolve dynamic url mapping

Closes #31

Coverage decreased (-2.4%) to 83.028% when pulling 4c326c5a97637a594e362ebf71172dbd3b92428c on feature/31_resolve_dynamic_url_path into 03530526bca090d904dc9af8a86677858dc299da on develop.


Does orchid generate rest endpoints?

I think it does, just making sure before I use it. If I create a field or a model, would it have a rest endpoint?

No package generates any REST.  This is not a CRUD solution.


Put a word-wrap property for the => | errorMessage & isUserInputBlank | text which appear when either of both States are true.

Description
When we put wrong slang or slang that is not present or the search bar is empty, we get a msg telling us the real problem like
this
1.  When slag is not present
- This entry does not exist in our records as of yet :(

  1. You can help us add this by creating a [github issue](https://github.com/Njong392/Abbreve)

  2. Or, you could fill out this [feedback form](https://t.co/mp86BLYBhq) and we will address the issue

2.  When SearchBar is Empty
- Search bar 🔍 is Empty!. Please put abbreviation in search bar

But when either of these messages appears, the content on its left gets displaced slightly to the left. it will more clear from the SS I have added below.
Screenshots

Additional information
No response

Sounds great, @PriyansuMaurya do you want me to assign this to you?

No, I didn't put it to get this assigned to me, bcoz I don't know much about tailwind. it's for the general public, if it doesn't get solved this month, then definitely I will learn tailwind and try to solve it in the next month.

Thank you for raising this Priyansu! If no one takes this on, I'll try to go over it and see what I can do 💙

Gonna try to tackle this! Assigning to myself. :)

@adropofilm are you still on this?

Hi friends, passing this on to anyone who wants to take it up. Been assigned to me for a while, sorry!

I think it's safe to close this. Since we moved the search bar to the top, we don't have much of this problem anymore. What do you think @adropofilm

The bug has not been fixed till now although the search bar has been moved to the top. you can see this in the video 👇
Abbreve Word Wrap Bug

Ooof... I somehow missed this issue. Thanks for the video @PriyansuMaurya I'll set out to fix some stuff this weekend.

Hi. Can I be assigned to this issue? I have experience with tailwind CSS.

Hi there! Yes, sure. I'll assign you.

@Njong392 I've made a PR for the issue

I saw. Thank you. I think replied to the pull request and suggested some changes.

@Njong392 I checked and this issue has not been resolved.....Can i be given the permission to work on this so we could close this issue.

@newdydx i think the issue that the site has now is that the text near the search bar doesn't align with the content below it. It's shifted inward. And then continuously shifts outward as described by this issue.
Should I assign you still?

@Njong392 of course you can assign me...After going through the site I discovered the second issue had been resolved and the only issue left is the issue of the word wrap and I would love to work on the issue.....thanks

Assigning you. Thank you for taking it on.

Oh wait. This issue is assigned to @TropicolX Would you still be interested in working on this?

@Njong392 still waiting to be assigned

If by the weekend, the originally assigned person doesn't respond, I'll assign you then. All good?

@Njong392 no problem

@newdydx assigning you to this now.

@Njong392 I made the pull request

Has it been resolved?

Yes...
Also, I've added a fancy scrollbar that matches the color. Supposed to be merged but you haven't.
May I know why?

@devodii I already reviewed your pull request. Please check the comments I made.

The caret in the search field seems to be hiding when it's focused but shows after the field is not null.
Should i work on this?
https://user-images.githubusercontent.com/113144477/234280397-60116fef-8539-4e7e-9315-f46a8fda0e52.mp4

This looks like an issue totally different from this one.It should be created separately. And I assigned you to this issue already btw

Oh...
The one you assigned to me, i don't understand it.
I guess it's the fact that the notFound message moves to the left when it has no record for the value inputed.
Correct?

This is what we want, don't  we? @Njong392
Before

After Filling and Clicking SUBSCRIBE button

Here nothing moves (stays as it was except message appears)
Here is the code for the same

@PriyansuMaurya sorry, but i am a little bit lost. how does your reply relate to this issue? Just asking because i seem to be confused

Ah, it took me a minute to see what u meant. But yeah. That is the expected reaction

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!heythisisvivek, @giocompany, @blackhu0804, @raj03kumar, @hicodersofficial, @vucenovic, @cagev, @j1mehta, @uniyalabhishek, @Saptaktdk, @gstru, @msboffl, @drjova, @jettzhang95, @prasanthkuna, @marcopestrin, @hyduez, @verkit, @LDuncAndroid, @priyank003