Print some logs on errors. Override entrypoint with our command.

Closes #147

This change is

Codecov Report

Merging #152 into master will decrease coverage by 0.25%.
The diff coverage is 2.85%.

@@             Coverage Diff              @@
##             master     #152      +/-   ##
============================================
- Coverage     21.13%   20.88%   -0.26%
- Complexity      204      205       +1
============================================
  Files            55       55
  Lines          2266     2298      +32
  Branches        201      201
============================================
+ Hits            479      480       +1
- Misses         1732     1763      +31
  Partials         55       55

Impacted Files
Coverage Δ
Complexity Δ

...ostyasha/yad/DockerDescriptorVisibilityFilter.java
42.85% <ø> (ø)
3 <0> (ø)
:arrow_down:

...yasha/yad/launcher/DockerComputerJNLPLauncher.java
20.86% <0%> (-1.98%)
14 <0> (ø)

...ain/java/com/github/kostyasha/yad/DockerCloud.java
12.57% <0%> (-1.54%)
9 <0> (ø)

...om/github/kostyasha/yad/utils/DockerFunctions.java
42.85% <100%> (+2.85%)
3 <1> (+1)
:arrow_up:

Continue to review full report at Codecov.

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


Can't install Plugin System on Windows

Hi, I would love some assistance on how to install the community plugin system for Typora on Windows:
I followed these steps, but ended up with no change to my Typora interface. No ribbon or anything:

I opened PowerShell and executed "install.ps1." It seems to have worked given that certain files/folders were created, as seen in the image below
Then, I opened Typora but, again, there weren't any visible changes to my interface, no "Settings" Model, no "Plugin Markeplace," nothing

All this to say, any help would be appreciated

Here's the log:

why core.js and core.css are in .typora/community-plugins?
It should be:
╰─ .typora/community-plugins/
  ├─ 2.3.32/
  │  ├─ locales/
  │  ├─ core.css
  │  ╰─ core.js
  ├─ install.ps1
  ├─ loader.js
  ╰─ loader.json

Ahh, this was the issue! I've got it working now. I don't think the PowerShell script created the folder "2.3.32" to place the core files in. Thanks for the help


Jaclyn taroni/451 citation in readme

⚠ This is stacked on #464, but I've merged in dev because I'll also need to update the AnnData README simultaneously.
Issue Number
#451 and specifically: https://github.com/AlexsLemonade/scpca-portal/issues/451#issue-1924741351
Purpose/Implementation Notes

Here, I'm adding an initial draft of citation language to one of the READMEs included in downloads (api/scpca_portal/templates/readme.md). If @jashapiro and @dvenprasad are okay with this language, I'll propagate those changes to the other READMEs. I will mark this as a draft for now since it should not be merged before #451 is addressed in all READMEs, but please review changes to api/scpca_portal/templates/readme.md in the draft @jashapiro and @dvenprasad.
Types of changes
What types of changes does your code introduce?

Bugfix (non-breaking change which fixes an issue)

Functional tests
List out the functional tests you've completed to verify your changes work locally.
Checklist

[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots
Please attach any screenshots that illustrate these changes.

Could you please update the target of this PR to davidsmejia/451-add-readme-file-dates from #469 and add Generated on: {date} to the top of the readme files.

Could you please update the target of this PR to davidsmejia/451-add-readme-file-dates from #469 and add Generated on: {date} to the top of the readme files.

Done, please see https://github.com/AlexsLemonade/scpca-portal/pull/467/commits/7f4339b9bf55ff9e6ee10cf6650bc3cea1c66e02


Release 1.2.0

Signed-off-by: Joe Adams<EMAIL_ADDRESS>

Does this fix the problem with pulling metrics from elasticsearch 7.13? I don't see the notes in the changelog and I'd recommend pulling in that PR before the next release.

Maybe we could update the repo settings to accept only squash on merge to make it easier to create the changelogs (basically git log previous_tag...version)?


ProjectToTypeAsync?

Is Mapster.Async available only for Adapt(), and not for projections?
What I would like is something like this
public async Task<List<SomeDto>> GetProjectionAsAsync(SomeRequest request)
{
    var data = _db.SomeData.AsQueryable();

    // Database operation should be async
    return await data.ProjectToTypeAsync<List<SomeDto>>();
}

I'm not sure if I understand the inner workings correctly, but wouldn't this still execute the database call + projection synchronously, and just the ToList() operation asynchronously?
return await data.ProjectToType<List<SomeDto>>().ToListAsync();

Mapster already has some underlying issues that can cause problems when using ProjectToType() in certain situations that involve async code. These issues will need to be resolved first. It is advisable to materialize queries with ToList() first before calling ProjectToType().

@andrerav I know this is a relatively old and already closed issue, but what are you specifically referring to when it comes to async issues in relation to Mapster? I noticed I'm still using ProjectToType in an async context in many places, but was unaware of it causing any issues.


Update scripts to use cabal v2-* commands

We used to have cabal new-run in the scripts, until somewhat recently.

https://github.com/input-output-hk/cardano-node/tree/serge/new-run replaces all uses of cabal run with cabal new-run.


Name resolution does not work without filesystem access

At the moment DNS lookups seem to require filesystem access. Is that intended behavior?
Steps to reproduce:
package main

import (
	"fmt"
	"log"
	"net"

	_ "github.com/stealthrocket/net/wasip1"
)

func main() {
	ips, err := net.LookupIP("example.org")
	if err != nil {
		log.Fatal(err)
	}

	fmt.Println(ips)
}

❯ GOOS=wasip1 GOARCH=wasm gotip build -o dnstest.wasm dnstest.go
❯ gotip version
go version devel go1.21-5c15498 Fri Jul 7 22:02:26 2023 +0000 linux/amd64
❯ wasirun --version
wasirun v0.7.2

Result:
❯ wasirun --dir=/ dnstest.wasm
[2606:2800:220:1:248:1893:25c8:1946 <IP_ADDRESS>]
❯ wasirun --dns-server <IP_ADDRESS>:53 dnstest.wasm
2023/07/10 08:37:11 lookup example.org on [::1]:53: Connection refused

Without docs saying otherwise I'd expect the last invocation to work as well

@chriso pointed out that another option could be to add a lookup functions in the wasip1 package such as wasip1.LookupIP, which would bypass the Go resolver when building with -tags=getaddrinfo.


The environment

Hello, we use cuda-11.4 and it works well. What is your error messages? How about installing a cuda 11.4?


Remove unused imports

Summary
Somehow the scheduled CI run from last night caught some unused imports which previously went unnoticed. This PR removes those imports.

I did notice that on Linux the unused-import errors do not always get caught properly. I am not familiar with an issue on the side of pylint itself tracking this, however.


Crash on iOS simulator

Hi! I created an app and tested it on android. It works nice! But there is a problen with iOS Simulator. On real iOS device app doesn't crash, but has unexpected behavior too. The app starts good, but when I open the screen with flutter_gl usage, it crashes with the following error.
Flutter console:
flutter_gl/CustomRender.swift:149: Fatal error: Unexpectedly found nil while unwrapping an Optional value
Apple report:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Incident Identifier: 2F5134DA-6D29-4E98-B79A-50684C15E747
CrashReporter Key:   93229631-22EE-58BF-A374-D0E230E9F06B
Hardware Model:      MacBookPro16,1
Process:             Runner [3048]
Path:                /Users/USER/Library/Developer/CoreSimulator/Devices/AA3D36EC-D618-4093-BDC9-2BFBB5DA22BF/data/Containers/Bundle/Application/1FF1FE9A-B859-41C5-86C4-C2ABF2A482FC/Runner.app/Runner
Identifier:          absolutely.correct.identifier
Version:             1.0.0 (1)
Code Type:           X86-64 (Native)
Role:                Foreground
Parent Process:      launchd_sim [1951]
Coalition:           com.apple.CoreSimulator.SimDevice.AA3D36EC-D618-4093-BDC9-2BFBB5DA22BF [1340]
Responsible Process: SimulatorTrampoline [1561]

Date/Time:           2022-08-04 06:44:56.4980 +0300
Launch Time:         2022-08-04 06:44:10.9655 +0300
OS Version:          macOS 12.5 (21G72)
Release Type:        User
Report Version:      104

Exception Type:  EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: SIGNAL 4 Illegal instruction: 4
Terminating Process: exc handler [3048]

Triggered by Thread:  0

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libswiftCore.dylib            	    0x7fff30740c17 closure #1 in closure #1 in closure #1 in _assertionFailure(_:_:file:line:flags:) + 391
1   libswiftCore.dylib            	    0x7fff3074097c closure #1 in closure #1 in _assertionFailure(_:_:file:line:flags:) + 300
2   libswiftCore.dylib            	    0x7fff30740655 closure #1 in _assertionFailure(_:_:file:line:flags:) + 117
3   libswiftCore.dylib            	    0x7fff307402aa _assertionFailure(_:_:file:line:flags:) + 314
4   flutter_gl                    	       0x1028a3fa8 CustomRender.initGL(context:) + 1976 (CustomRender.swift:149)
5   flutter_gl                    	       0x1028a36fd CustomRender.initEGL() + 3101 (CustomRender.swift:126)
6   flutter_gl                    	       0x1028a1f86 CustomRender.setup() + 54 (CustomRender.swift:53)
7   flutter_gl                    	       0x1028a1e92 CustomRender.init(options:renderToVideo:onNewFrame:) + 1954 (CustomRender.swift:48)
8   flutter_gl                    	       0x1028a16e6 CustomRender.__allocating_init(options:renderToVideo:onNewFrame:) + 70
9   flutter_gl                    	       0x1028b11bf SwiftFlutterGlPlugin.handle(_:result:) + 2255 (SwiftFlutterGlPlugin.swift:43)
10  flutter_gl                    	       0x1028b2fd6 @objc SwiftFlutterGlPlugin.handle(_:result:) + 118
11  Flutter                       	       0x1062b5a21 __45-[FlutterMethodChannel setMethodCallHandler:]_block_invoke + 104
12  Flutter                       	       0x105cf4712 invocation function for block in flutter::PlatformMessageHandlerIos::HandlePlatformMessage(std::__1::unique_ptr<flutter::PlatformMessage, std::__1::default_delete<flutter::PlatformMessage> >) + 86
13  libdispatch.dylib             	    0x7fff2011265a _dispatch_call_block_and_release + 12
14  libdispatch.dylib             	    0x7fff2011383a _dispatch_client_callout + 8
15  libdispatch.dylib             	    0x7fff20120c88 _dispatch_main_queue_callback_4CF + 1075
16  CoreFoundation                	    0x7fff2036c84d __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
17  CoreFoundation                	    0x7fff203670aa __CFRunLoopRun + 2772
18  CoreFoundation                	    0x7fff203660f3 CFRunLoopRunSpecific + 567
19  GraphicsServices              	    0x7fff2c995cd3 GSEventRunModal + 139
20  UIKitCore                     	    0x7fff25059f42 -[UIApplication _run] + 928
21  UIKitCore                     	    0x7fff2505eb5e UIApplicationMain + 101
22  Runner                        	       0x1024bc11f main + 63 (AppDelegate.swift:5)
23  dyld_sim                      	       0x1026d6ee9 start_sim + 10
24  dyld                          	       0x10eb6f52e start + 462

Thread 1:
0   libsystem_pthread.dylib       	    0x7fff6da2ef48 start_wqthread + 0

I copied the aar for android setup, but did nothing for iOS setup. Is there anything that needs to be done?

As I mentioned in issue, it works on the real device

@L3odr0id  Something I tried was in CustomerRenderer.swift in the flutter_gl package in ios was to add a texture null check like below:
if(texture == nil) {
    return;
}
glBindTexture(CVOpenGLESTextureGetTarget(texture!), CVOpenGLESTextureGetName(texture!));

This stopped the unwrapped optional error but then got a new error:
'cyclone' is not a recognized processor for this target (ignoring processor)
I read that this error is an issue running opengl in a simulator. So not sure how to fix this error. To put apps on iTunes really need screenshots from multiple devices which is difficult without a simulator.

@Medicmind , thanks for your attention to this problem. I needed screenshots for the AppStore as well. I think the actual workaround here is to upload layouts from Figma or just screenshot other pages of the app.
Also this package is unmaintained. There is an idea for a better solution and so I'm going to create my own 3D renderer package

There is a fork which is maintained at:
https://github.com/Knightro63/three_js
which I use instead of this one. I've found the 3D animation example work with knightro63 version while they  don't with the wasabia version. But the knight63 version still has an issue with not working on iOS simulators.


Balance without considering load

I was wondering if there is a plugin or feature that instead of just doing the distribution of request between services in order, it analyze the workload or delay of them.
For example:
base send to S1 and S2, one request for each every time. Instead, if S1 is delaying too much, it send two to S2 before sending again to S1.

check out https://github.com/dgonzalez/visigoth /cc @dgonzalez


[Improvement][Worker] Task load

Describe the question
Now we can get the cpu、memory usage of works and masters, but sometimes we also want to get the waiting task number of each worker.
What are the current deficiencies and the benefits of improvement
Help us monitor the load of the cluster.
Which version of DolphinScheduler:
-[1.3.6]
-[dev]
Describe alternatives you've considered
Store the taskSize on zk by heart beat info

Everyone is welcome to discuss.


configurable parameters

slightly formatting
configurable number_of_judgment_attempts
configurable baseline_model in show_result.py

Thanks for you contribution. The code looks good to me. I like that you allow the baseline to be configured in show_result.py when generating all the battles. If we configure a model as the baseline we should also configure the model as the anchor when compute the bradley terry coefficients and win-rates. Could you add the code to configure that as well? I can merge it once you do. If not, I can do it instead.

@CodingWithTim Hope I understood you correctly. I've added this part

Thanks you got the right idea. This is great! I think one last thing is get_bootstrap_result also need to be able to support configurable baseline as well. Inside get_bootstrap_result it also calls compute_mle_elo. Could you add support for this as well? Thanks!

@CodingWithTim yeah, overlooked that part, sorry. Now it's there

@dmitrysarov Sorry about the late review, was busy with upcoming releases. This code works wonderfully for me. We really appreciate your contributions!


Task: split category and status

Fixes the bug where marking a task as completed in the overview page removes it from the tasks page
Description

Create a new category property in stores/task.js
replace all uses of task.status with task.category in components/task.js

Related Issue

How Has This Been Tested?

I looked at it with my eyes
Checklist

[ ] All automated tests have been passed locally (unit / e2e / linter / coverage)
[ ] New unit and E2E tests have been added to address the changes made
[ ] Manual testing has been performed according to the provided instructions
[ ] Code follows team's coding style, convention and standards
[ ] Documentation has been updated to reflect relevant changes (if applicable)

Screenshots (if applicable):

Addressed in another PR so we won't proceed with this implementation


add deploy script starter

Coverage remained the same at 81.818% when pulling 3c3d45bfa036b52366b006451bd8ad4d7e2bd37d on deploy-scripts into 183d3ccb057259b82ce7b476f0c6ecda7f8699de on master.

You still need to figure out the deploy script to digital ocean

Current Problem is that we can't generate certificates


chore(package): update css-loader to version 0.28.0

Closes #133
https://greenkeeper.io/

Summary

Test plan

Coverage remained the same at 93.698% when pulling 4f266cf1ae70f56a07b9d9bad50a2bbd30b3ba49 on greenkeeper/css-loader-0.28.0 into e7ad5acbf408d7675f5d14c2f91db54953d5855a on master.

Coverage remained the same at 93.698% when pulling 4f266cf1ae70f56a07b9d9bad50a2bbd30b3ba49 on greenkeeper/css-loader-0.28.0 into e7ad5acbf408d7675f5d14c2f91db54953d5855a on master.

Coverage remained the same at 93.698% when pulling 4f266cf1ae70f56a07b9d9bad50a2bbd30b3ba49 on greenkeeper/css-loader-0.28.0 into e7ad5acbf408d7675f5d14c2f91db54953d5855a on master.


Create Panel for Details Desktop View

The Work Item Details view should be in a panel that slides out from the right side of the screen (desktop), rather than it's own page (mobile).
See InVision Prototype for details: https://redhat.invisionapp.com/share/UV8W6AEHX#/screens/193330600_Panel_Edit

@mindreeper2420 How much width we are targeting for panel? And How it should come from 768px to 992px?

@smahil @joshua it should take about about 1/3 of the screen on desktop views. There are no defined pixel widths at the moment. If you'd like, I can review on a branch, once you have a rough stage of it.

PR #263 merged with master hence closing this task.


Not working in launcher

I am currently using the LauncherFenix for minecraft. I have tried to find the problem to not loading the seedcracker.jar being in the mods carpet or in the Fabric loader carpet (inside the mods carpet). I used the seedcracker version for 1.14, but every time I create a new world to try the Cracking it doesn´t work. It open the game with the Fabric loader version of 1.14.4.
Sorry my English, I am a Latin American. This is the page of the Launcher: (https://launcherfenix.com.ar/wope/)

Buy the game


'name' attribute for index

Addition of an additional 'name' attribute to indexes will simplify their identification and make it easier to know what exactly the index means when printing a data structure.
MultiIndex should support having separate names for each level (might be related to https://github.com/v0dro/daru/issues/150).

How to display with Index name in irb :
right now it is coming like this :
irb(main):005:0> Daru::Index.new [100, 99, 101, 1, 2], name: "index_name"
=> #<Daru::Index(5): {100, 99, 101, 1, 2}>

I want this :
irb(main):005:0> Daru::Index.new [100, 99, 101, 1, 2], name: "index_name"
=> #<Daru::Index: index_name(5) {100, 99, 101, 1, 2}>


Core Data Retention and Persistent Caps implementation

🚀 Feature Request
Relevant Package [REQUIRED]

 This feature request is for Core Data
Description [REQUIRED]
Approved UCR: https://docs.edgexfoundry.org/3.0/design/ucr/Core-Data-Retention/

@jpwhitemn @lenny-intel  According to the UCR and ADR, we consider do the following implementation, could you please help review?
Add the configurations to toml file,
Retention:
  Enabled: false
  Interval: 30s          # purging interval defines when the database should be rid of readings above the high watermark.
  MaxCap: 10000    #  The maximum capacity defines where the high watermark of readings should be detected for purging the amount of the reading to the minimum capacity.
  MinCap: 8000     # The minimum capacity defines where the total count of readings should be returned to during purging.

If the Retention.Enabled set to true,

Core data will create a schedule to trigger the reading purging
When the reading amount reaches the MaxCap, Core data should purge the amount of the reading to the minimum capacity.
For example,

If MaxCap is 10000 and MinCap is 8000, and the amount of readings is greater than 10000, the core data
should purge the amount of the reading to 8000.
the core data will use the 8001st reading to find the related event's origin time, and reusing the DeleteEventsByAge function to purge readings. (If we only remove readings and related events, some readings might lose the related event)


feat: adapt starter yml workflow (#343)

Summary
Created workflow based on the given starter https://github.com/rrd108/vue-mess-detector/blob/main/release-docs.sh
Description

Added yml file

Related Issues
Fixes #343
Type of Change

[X] Documentation update

Screenshots (if applicable)
N/A

so should I set up the ssh secret, right?


webhook: Add RunAsUser functionality within copy-vault-init and containers

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #663

License
Apache 2.0

What's in this PR?
Attempting to address the situation where PSPs are being enforced for running containers without a root user.  This takes a slightly different approach than other PRs.  Instead of introducing a new annotation, it relies on the user just leveraging the Pod Spec.
Additional context
The PodSecurityContext (https://godoc.org/k8s.io/api/core/v1#PodSecurityContext) and SecurityContext (https://godoc.org/k8s.io/api/core/v1#SecurityContext) types share some attributes, but not all.  One such attribute is the RunAsUser, which is fairly important for PSP policies.
Checklist

[ ] Error handling code meets the guideline
[ ] Logging code meets the guideline (TODO)
[ ] User guide and development docs updated (if needed)
[ ] Related Helm chart(s) updated (if needed)

To Do
I'm not clear how far we want to take this - I don't see an acceptance test exercising the current SecurityContext within the webhook managed containers for AllowPrivilegeEscalation, but we might want to add a PSP policy, service account, and ClusterRole/RoleBinding (for the SA) to exercise the complete flow here.  Any advice around this would be welcome.

[] Add a specific acceptance test

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

Thank you @Z3r0Sum !


How to fail NodeTask

I am unable to fail a build in order to get my gradle build to fail and stop execution.
My fail.js file:
return false;

The task in my build.gradle:
task fail (type: NodeTask) {
    script = file('fail')
    ignoreExitValue = false
}

What do I need to do in my js NodeTask to get gradle to not successfully run?

I was able to accomplish what I wanted by throwing an error in my js file.
throw new Error("FAILED!");


BoundedVariance & BoundedCovariance

Closes #68.

BoundedVariance transformation
BoundedCovariance transformation
Use higher ranked trait bounds to clean up extra clones in aggregators

Covariance doesn't really have a way to call it from FFI at this point, because of a lack of data loaders.

For posterity- an explanation of HRTB's.
I want to be able to use traits like Sub, Sum, etc in situations where the data is behind a reference. Otherwise we'll have to clone. So lets say I specify a trait bound Sum<&T>. But this isn't specific enough- all references have lifetimes, but in most situations the lifetimes are elided.
In a typical situation, if you do this:
let my_struct = MyStruct;
let my_struct_ref = &my_struct;

The compiler can infer my_struct_ref has some anonymous concrete lifetime that captures how long my_struct lasts from the context.
When specifying a trait bound, there is no context to elide the lifetime, so it must be explicitly stated. So I'll update my trait bound-- Sum<&'static T>... but this won't work either- when I try to use that bound in the code, I'm using it on a non-static reference, so the compiler complains. It also doesn't make sense to add a new lifetime on the constructor function, because the lifetime we'd want to specify the trait bound for doesn't yet exist at the time we call the constructor.
So what we need is a way to specify a trait bound with a generic lifetime parameter Sum<&'a T>, as well as an impl for Sum<&'a T> (any generic lifetime). Indeed, there is such an impl:
macro_rules! float_sum_product {
    ($($a:ident)*) => ($(
        #[stable(feature = "iter_arith_traits", since = "1.12.0")]
        impl<'a> Sum<&'a $a> for $a {
            fn sum<I: Iterator<Item=&'a Self>>(iter: I) -> Self {
                iter.fold(0.0, Add::add)
            }
        }
    )*)
}
integer_sum_product! { i8 i16 i32 i64 i128 isize u8 u16 u32 u64 u128 usize }

Now, we just need a way to specify the trait bound-- we want to say that for any lifetime 'a, there exists Sum<&'a T>. With a HRTB you can say just that: for<'a> Sum<&'a T>


Added chat-app example

Added code from chat-app tutorial Chat app tutorial

Coverage remained the same at 100.0% when pulling 274090e9a4fe3e5c813a24c3ef01a427d40e07dd on coffee-mug:socketio-example into 2ebba8bed648fa0fe5c66184f9c4cc34d8dbc976 on zeit:master.

Coverage remained the same at 100.0% when pulling f2e923abeeb897bfef4cd80258568214abbe608f on coffee-mug:socketio-example into 58efd96ad0e226f52cd0180161eecbd9c393674b on zeit:master.

Coverage remained the same at 100.0% when pulling f2e923abeeb897bfef4cd80258568214abbe608f on coffee-mug:socketio-example into 58efd96ad0e226f52cd0180161eecbd9c393674b on zeit:master.

Sweet, thanks!


bug: characters with accents supplied through surveys lead to wrong updates

Describe the problem
Non-alphabetical characters of the ASCII table supplied through a template survey are not properly supported when using copier update.
Template

Unfortunately, I'm not able to share a private template from my organization.
To Reproduce

Use a copier template and answer a question with a non-alphabetical characters of the ASCII table, for example é
Later on, update the project with copier update
See é being displayed as Ã© for the same question

Change Ã© to é in the prompt and complete the survey
See .rej files being created, caused by a mismatch between Ã© and é :

@@ -3,3 +3,3 @@ name = "u-iris.robotframework-courses-u-webapp"
 version = "0.1.0"
-description = "Projet Courses U automatisÃ©"
+description = "Projet Courses U automatisé"
 packages = [

Expected behavior

Unicode characters are correctly handled.
Environment

OS: Windows 10
Copier version: 6.0.0a7.post1.dev0+b8ff4d8
Python version: 3.9.7
Installation method: pipx+git

What happens if you export PYTHONIOENCODING=UTF8 in your shell first? And PYTHONUTF8=1?

Ah, I was able to replicate. First project generation is OK (accent written in copier answers file), but during the update the prompt shows Ã© just like @fdaguin said. I had PYTHONIOENCODING=UTF-8 exported. I'll try with PYTHONUTF8 now.

export PYTHONUTF8=1 fixed it 🎉 !

Thanks a lot for your investigation @pawamoy, I'm closing this issue!


Add Workflow for closing old PRs

This feature aims to automate the management of open PRs in a repository, ensuring that outdated or abandoned PRs are closed in a timely manner. By doing so, it helps maintain repository hygiene, improves workflow efficiency, and provides a better experience for both maintainers and contributors.

@Akshat111111 Please assign me this issue under gssoc'24


Can't run paraphraser in bulk or interactive mode

I've tried running the paraphraser in both modes, but I'm getting the following error:
Traceback (most recent call last):
  File "run_paraphraser.py", line 136, in <module>
    run(args)
  File "run_paraphraser.py", line 68, in run
    run_bulk(model, args)
  File "run_paraphraser.py", line 39, in run_bulk
    all_paraphrases = model.generate_paraphrases(
AttributeError: 'NMTParaphraser' object has no attribute 'generate_paraphrases'

From running:
docker run --rm -it \
>     -v $PWD/run_paraphraser.py:/home/run_paraphraser.py \
>     dakshvar22/paraphraser_cpu:latest \
>     python run_paraphraser.py \
>     --interactive \
>     --language en

@dakshvar22 I deleted the image downloaded locally, and then run:
docker run --rm -it \
>     dakshvar22/paraphraser_cpu:latest \
>     --interactive \
>     --language en

However, I got the following error:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: exec: "--interactive": executable file not found in $PATH: unknown.

It might be related to the image's entry point?
I tried running instead:
docker run --rm -it \
>     dakshvar22/paraphraser_cpu:latest

And then, once inside the container, I ran python run_paraphraser.py --interactive --language en. However, I got the same error again:
2021-05-03 13:15:22.161433: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'libcudart.so.10.1'; dlerror: libcudart.so.10.1: cannot open shared object file: No such file or directory
2021-05-03 13:15:22.161483: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
| [src] dictionary: 65400 types
| [tgt] dictionary: 65400 types
| loaded 1 examples from: test_bin/test.src-tgt.src
| loaded 1 examples from: test_bin/test.src-tgt.tgt
| test_bin test src-tgt 1 examples
Enter a sentence to be paraphrased: Hello, I would like to purchase a toaster
Traceback (most recent call last):
  File "run_paraphraser.py", line 136, in <module>
    run(args)
  File "run_paraphraser.py", line 66, in run
    run_interactive(model, args)
  File "run_paraphraser.py", line 23, in run_interactive
    paraphrases = model.generate_paraphrases(
AttributeError: 'NMTParaphraser' object has no attribute 'generate_paraphrases'

@federicotdn I just ran this locally after deleting the image (you can see that the image is downloaded):
(rasa_master) daksh (main) paraphraser $ docker run --rm -it \
> dakshvar22/paraphraser_cpu:latest \
> --interactive \
> --language en
Unable to find image 'dakshvar22/paraphraser_cpu:latest' locally
latest: Pulling from dakshvar22/paraphraser_cpu
345e3491a907: Pull complete
57671312ef6f: Pull complete
5e9250ddb7d0: Pull complete
0ebfab80d990: Pull complete
76bad59340cc: Pull complete
9421e072bfe5: Pull complete
5cd7644590c8: Pull complete
f9e225ad5ad1: Pull complete
57d6116c0fe2: Pull complete
c24286bd1ae7: Pull complete
9cdb94ea2d0a: Pull complete
6422c62ce372: Pull complete
3a522c00d3c7: Pull complete
f7a0b03db663: Pull complete
Digest: sha256:2d208429ae0c36fc54e35ffe0303f30a760e3ac4dbf997dad02e8dba420fb6f6
Status: Downloaded newer image for dakshvar22/paraphraser_cpu:latest
2021-05-03 14:15:46.887511: W tensorflow/stream_executor/platform/default/dso_loader.cc:59] Could not load dynamic library 'libcudart.so.10.1'; dlerror: libcudart.so.10.1: cannot open shared object file: No such file or directory
2021-05-03 14:15:46.887641: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
/root/miniconda3/lib/python3.7/site-packages/gensim/similarities/__init__.py:15: UserWarning: The gensim.similarities.levenshtein submodule is disabled, because the optional Levenshtein package <https://pypi.org/project/python-Levenshtein/> is unavailable. Install Levenhstein (e.g. `pip install python-Levenshtein`) to suppress this warning.
  warnings.warn(msg)
| [src] dictionary: 65400 types
| [tgt] dictionary: 65400 types
| loaded 1 examples from: test_bin/test.src-tgt.src
| loaded 1 examples from: test_bin/test.src-tgt.tgt
| test_bin test src-tgt 1 examples
Enter a sentence to be paraphrased: Hello I am looking for a toaster.
| loaded 1 examples from: test_bin/test.src-tgt.src
| loaded 1 examples from: test_bin/test.src-tgt.tgt
| test_bin test src-tgt 1 examples
1. Hello I am looking for a toaster.
2. "Hello I'm looking for a toaster".
3. Please I am looking for a toaster.
4. "Hello I'm looking for a toast".)"
5. Hail me to a toaster.
6. Hallow I’m looking for a toaster.
7. Salute that I’m looking for a toaster.
8. Here's a toast.
9. Hola is looking for a toaster. ...
10. It looks for an outlet.
Generation completed in 16.362245321273804

Not sure what's the problem on your side 😅

I don't think the image got deleted at your end. Maybe you had some layers which it skipped downloading (but it would have skipped only if there wasn't a difference in that layer. Weird 😅 )

Tried again, now it's working for some reason 🤔  (the hash digest hasn't changed between runs). Thanks!


Support WebGPU to eliminate torch dependency

https://github.com/burn-rs/burn/issues/243

burn-wgpu is too immature to handle models as large of SDXL. Hopefully one day...

Any thoughts on this with the latest release of Burn? :) I'm curious what you think is missing these days. @Gadersd


Slightly refactor store request packet call-tree

Packets should use SW, but this required passing sz to the function that set the op. This seemed to break an abstraction so I merged hb_mc_manycore_format_store_request_packet into its single callsite and set SW/STORE there.
Also, refactored to use HB_MC_SUCCESS instead of 0.

(I have not run regression on this yet, but will post when I have)


unmanaged-cluster: Downloading TKR re-prints log message rather than showing progress . characters

Bug Report
From a comment in another PR (https://github.com/vmware-tanzu/community-edition/pull/2822#issuecomment-1012618133)

Expected Behavior
For a carriage return \r to replace this line, giving the visualization of progress.
Steps to Reproduce the Bug
Remove the locally downloaded TKR then run a cluster create.

Nice to have for alpha release v0.10.0; but not required until v0.11.0.

Hmmm I'm having trouble reproducing this.
@garrying, it'd be helpful to get a dump of information on:

the terminal you're using / OS / environment
the output of echo $SHELL
the output of echo $TERM
if you're using 256 term colors
maybe your shell .rc file

And just to confirm, this is only happening for the download step?

macOS 11.6.2, iTerm 2 (3.4.15)

.zshrc

Ubuntu 20.04.3 LTS, Hyper (3.1.5)
on both:

/bin/zsh, /usr/bin/zsh
xterm-256color

Yeah, it's only happening on download step. Interesting, I'm not seeing the issue on macOS 12.1 and I have a similar setup on it.

Hmmmm still not able to reproduce on mac with iTerm or the default terminal, in different shells, on my linux desktop, or in a virtual machine.
Just so we're all working off the same binary here (since it's yet released), let's connect on K8s slack and I can drop you a newly built binary to try

Ahhhhh I think I see what's happening. Here's how I've been able to reproduce it:

First, remove the existing bom so it initiates a download again
$ rm -rf ~/.config/tanzu/unmanaged

Run a create which should end the download logging animation loop:
unmanaged-cluster create my-cluster

In a wide terminal window, this is the expected result:

In a more narrow terminal, the terminal prompt is wrapping to the next line ... so it has no line to replace:

This is probably why I couldn't reproduce it ... my monitor is too wide 😂
This is especially troublesome since we pad the carriage return in RepalceLinef with a bunch of empty spaces. I'm not sure there's a great solution here (or why this was necessary to do in the first place) but it might be worth exploring removing that extra space.
https://github.com/vmware-tanzu/community-edition/blob/826f80e75acec4dda039cc489d06e35d89fbc49f/cli/cmd/plugin/unmanaged-cluster/log/log.go#L271-L273


[FEAT]: Disable playing the next video, until the current video lesson has been played

closed in #134


chore:correct some quick links

Hello.
new to mina and found some expired documents to correct

Explain your changes here.
correct quick links to the right location

Explain how you tested your changes here.
just click it.

Checklist:

This section of the readme no longer exists. Closing.


Document the Vaporpad Protocol (VPP)

In progress on the reconnection branch.

@djahandarie suggests:

Clarify that the rebased ops are what is retransmitted.
Clarify that writes are accepted by servers.
Explain why C_WRITE_RESP contains ops.
Explain hashing.

(Slightly buggy) protocol documentation is available in docs/protocol.adoc.


Loosen label and annotation validation and related tests

From #4486
Proposed:

label values: restrict to [A-Za-z0-9_-.]*

annotation values: no restriction

qualified names (label and annotation keys, resource names, volume plugins): loosen restrictions to ([A-Za-z0-9_-.]+/)?[A-Za-z0-9_-.]+ - this should be a strict superset of
what we allow today.  We can say that convention is to use dns-compatible
domain + label, but still allow things like FOO/B_A.R.  This DOES NOT allow for foo.com/bat/bat - is that an important affordance to anyone?  We could allow that, but we need to be clear that "bar/bat" means (bar, bat) while "foo.com/bar/bat" means (foo.com, bar/bat).

@smarterclayton does that give you enough freedom?
@bgrant0607 does that give you enough consistency?
@quinton-hoole-google does this make the qualified name type now viable for your use case in kube-proxy?

Yes on the freedom question.  I assume we will spec case-sensitivity?
----- Original Message -----

From #4486
Proposed:

label values: restrict to [A-Za-z0-9_-.]*

annotation values: no restriction

qualified names (label and annotation keys, resource names, volume
plugins): loosen restrictions to ([A-Za-z0-9_-.]+/)?[A-Za-z0-9_-.]+ - this
should be a strict superset of
what we allow today.  We can say that convention is to use dns-compatible
domain + label, but still allow things like FOO/B_A.R.  This DOES NOT allow
for foo.com/bat/bat - is that an important affordance to anyone?  We could
allow that, but we need to be clear that "bar/bat" means (bar, bat) while
"foo.com/bar/bat" means (foo.com, bar/bat).

@smarterclayton does that give you enough freedom?
@bgrant0607 does that give you enough consistency?
@quinton-hoole-google does this make the qualified name type now viable for
your use case in kube-proxy?

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628

You mean "yes, it is case sensitive"?  Yes, sure.
On Thu, Feb 19, 2015 at 2:45 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Yes on the freedom question. I assume we will spec case-sensitivity?
----- Original Message -----

From #4486
Proposed:

label values: restrict to [A-Za-z0-9_-.]*

annotation values: no restriction

qualified names (label and annotation keys, resource names, volume
plugins): loosen restrictions to ([A-Za-z0-9_-.]+/)?[A-Za-z0-9_-.]+ -
this
should be a strict superset of
what we allow today. We can say that convention is to use dns-compatible
domain + label, but still allow things like FOO/B_A.R. This DOES NOT
allow
for foo.com/bat/bat - is that an important affordance to anyone? We
could
allow that, but we need to be clear that "bar/bat" means (bar, bat) while
"foo.com/bar/bat" means (foo.com, bar/bat).

@smarterclayton does that give you enough freedom?
@bgrant0607 does that give you enough consistency?
@quinton-hoole-google does this make the qualified name type now viable
for
your use case in kube-proxy?

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-75155018
.

Thanks. Yes, I'm happy with this.
Do we auto-lowercase label keys today?

We do not, we fail validation (in master at right now)
----- Original Message -----

Thanks. Yes, I'm happy with this.
Do we auto-lowercase label keys today?

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-75157257

Yes, I'm reasonably happy with that, from my as yet limited perspective. My personal preference would be to ultimately support both hierarchical names and hierarchical namespaces, somehow  (e.g. something like "subdept.dept.acme.com/workgroup/product/user/resource" means (subdept.dept.acme.com, workgroup/product/user/resource), as this makes for convenient ACL's and the like.  So I support your "We could allow that..." part, and associated semantics.

I'm not sure we want to zoom in to do ACLs or things on segments of the
name, but it's plausible anyway.
On Thu, Feb 19, 2015 at 3:27 PM, Quinton Hoole<EMAIL_ADDRESS>wrote:

Yes, I'm reasonably happy with that, from my as yet limited perspective.
My personal preference would be to ultimately support both hierarchical
names and hierarchical namespaces, somehow (e.g. something like "
subdept.dept.acme.com/workgroup/product/user/resource" means (
subdept.dept.acme.com, workgroup/product/user/resource), as this makes
for convenient ACL's and the like. So I support your "We could allow
that..." part, and associated semantics.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-75161172
.

I can write this change, but there's a couple of things to decide:

do we allow comma in label values (we did until now, but in this proposal we don't)? [I guess we do]
do we really want to allow Qualified Names to end with dash/period/underscore? [I guess we don't]
what max length of Qualified Names we allow? [I guess 253]
do we want to allow completely arbitrary annotations, and do we want to enforce some length limit?

On Feb 26, 2015, at 6:56 AM, gmarek<EMAIL_ADDRESS>wrote:
I can write this change, but there's a couple of things to decide:
do we allow comma in label values (we did until now, but in this proposal we don't)? [I guess we do]
do we really want to allow Qualified Names to end with dash/period/underscore? [I guess we don't]
Is there a disadvantage?
what max length of Qualified Names we allow? [I guess 253]
It should be defined in the identifiers section, but if not should be predictable to our other names.
do we want to allow completely arbitrary annotations, and do we want to enforce some length limit?
We should set a maximum to limit abuse, but it should probably be total size of all annotation values and keys, not any particular one (I don't see a reason any individual annotation can't be large).  50K total as a straw man.
—
Reply to this email directly or view it on GitHub.

On Thu, Feb 26, 2015 at 8:24 AM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

On Feb 26, 2015, at 6:56 AM, gmarek<EMAIL_ADDRESS>wrote:
I can write this change, but there's a couple of things to decide:
do we allow comma in label values (we did until now, but in this proposal we don't)? [I guess we do]
do we really want to allow Qualified Names to end with dash/period/underscore? [I guess we don't]
Is there a disadvantage?

I don't think this is a big deal, but I agree - given that DNS names
don't allow trailing punctuation, it's not unreasonable to assume this
shouldn't.  It's a marginally more complex regex is all.

what max length of Qualified Names we allow? [I guess 253]
It should be defined in the identifiers section, but if not should be predictable to our other names.

Previously it was max(dns_label + max(dns_subdomain) + 1.  I think
making this be the same as dns subdomain is fine.

do we want to allow completely arbitrary annotations, and do we want to enforce some length limit?
We should set a maximum to limit abuse, but it should probably be total size of all annotation values and keys, not any particular one (I don't see a reason any individual annotation can't be large). 50K total as a straw man.

by 50, Clayton obviously means 64.

SGTM

Obviously

On Feb 26, 2015, at 11:35 AM, Tim Hockin<EMAIL_ADDRESS>wrote:
On Thu, Feb 26, 2015 at 8:24 AM, Clayton Coleman
<EMAIL_ADDRESS>wrote:

On Feb 26, 2015, at 6:56 AM, gmarek<EMAIL_ADDRESS>wrote:
I can write this change, but there's a couple of things to decide:
do we allow comma in label values (we did until now, but in this proposal we don't)? [I guess we do]
do we really want to allow Qualified Names to end with dash/period/underscore? [I guess we don't]
Is there a disadvantage?

I don't think this is a big deal, but I agree - given that DNS names
don't allow trailing punctuation, it's not unreasonable to assume this
shouldn't. It's a marginally more complex regex is all.

what max length of Qualified Names we allow? [I guess 253]
It should be defined in the identifiers section, but if not should be predictable to our other names.

Previously it was max(dns_label + max(dns_subdomain) + 1. I think
making this be the same as dns subdomain is fine.

do we want to allow completely arbitrary annotations, and do we want to enforce some length limit?
We should set a maximum to limit abuse, but it should probably be total size of all annotation values and keys, not any particular one (I don't see a reason any individual annotation can't be large). 50K total as a straw man.

by 50, Clayton obviously means 64.
—
Reply to this email directly or view it on GitHub.

There's a small issue with label values: they were not checked until now. E.g. in guestbook example there's a comma used in label value, which is forbidden both in current implementation and Brendans suggestion, but it was OK, as it was never checked. I don't know how many things will brake when we'll turn the value validation on.
In addition current implementation allows backslashes and Brandans suggestion does not - is this a mistake, or is it by design?

@gmarek. By design, @smarterclayton suggested to 'preserve' backslash for future uses. I translated it in 'admit it'.

I'm sorry, but I don't understand. Is Brendans suggestion by design omit backslash, or originally it was there by design? (I guess you meant the former, but I don't know here the original discussion was)

@gmarek as far as I remember during the discussion someone (guessing @smarterclayton) raised the point about unicode and char to be esacped. But I cannot find anymore asked me to reserve backslash for future uses. That's why I modified the regexp and I specifically added an entry in unit test for this.
The starting discussion was here: https://github.com/GoogleCloudPlatform/kubernetes/issues/341
Then https://github.com/GoogleCloudPlatform/kubernetes/pull/4486

For label queries, reserving backslash for escaping values we might use in the future.  For values themselves I don't believe we need any escaping.

On Feb 27, 2015, at 10:47 AM, Salvatore Dario Minonne<EMAIL_ADDRESS>wrote:
@gmarek as far as I remember during the discussion someone (guessing @smarterclayton) raised the point about unicode and char to be esacped. But I cannot find anymore asked me to reserve backslash for future uses. That's why I modified the regexp and I specifically added an entry in unit test for this.
The starting discussion was here: #341
Then #4486
—
Reply to this email directly or view it on GitHub.

PR for this #4898

Oh, I missed those updates. I'll add a backslash on Monday.

wait wait.
I do not think that adding backslash to the allowed set is what was
suggested.  Backslash MAY be needed when parsing strings but as yet it has
not been demonstrated.  Let's please try to keep it as minimal as possible
and expand when we have demonstrated reasons.
Let's discuss comma - I don't want it in the set, but is it worth a
breakage risk?
On Fri, Feb 27, 2015 at 8:43 AM, gmarek<EMAIL_ADDRESS>wrote:

Oh, I missed those updates. I'll add a backslash on Monday.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76425890
.

Well, comma is only a special case because it's used in Guestbook example (frontend-controller.json). Because this example is the most visible one (at least for us in Warsaw), my feeling is that it was copied a lot of times as a framework, hence making it invalid may be problematic...
Generally adding any nontrivial validation can break something, but I guess we'll need to live with it.

If we have to add comma, it's not the end of the world, but we could also
just fix the example and say "yeah, we broke it".  Adding any sort of
restriction is likely to break someone.
I'm open to arguments either way with comma.  I'd rather not do it, but
I'll accept it.
On Fri, Feb 27, 2015 at 10:09 AM, gmarek<EMAIL_ADDRESS>wrote:

Well, comma is only a special case because it's used in Guestbook example
(frontend-controller.json). Because this example is the most visible one
(at least for us in Warsaw), my feeling is that it was copied a lot of
times as a framework, hence making it invalid may be problematic...
Generally adding any nontrivial validation can break something, but I
guess we'll need to live with it.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76442562
.

I don't like commas in values of labels.  It's a natural separator.

On Feb 27, 2015, at 1:15 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
If we have to add comma, it's not the end of the world, but we could also
just fix the example and say "yeah, we broke it". Adding any sort of
restriction is likely to break someone.
I'm open to arguments either way with comma. I'd rather not do it, but
I'll accept it.
On Fri, Feb 27, 2015 at 10:09 AM, gmarek<EMAIL_ADDRESS>wrote:

Well, comma is only a special case because it's used in Guestbook example
(frontend-controller.json). Because this example is the most visible one
(at least for us in Warsaw), my feeling is that it was copied a lot of
times as a framework, hence making it invalid may be problematic...
Generally adding any nontrivial validation can break something, but I
guess we'll need to live with it.
--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76442562
.

—
Reply to this email directly or view it on GitHub.

I'm inclined to fix the example and take the hit on this one, while we
can.  Once v1beta3 becomes v1, we're locked in.
On Fri, Feb 27, 2015 at 10:25 AM, Clayton Coleman<EMAIL_ADDRESS>wrote:

I don't like commas in values of labels. It's a natural separator.

On Feb 27, 2015, at 1:15 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
If we have to add comma, it's not the end of the world, but we could
also
just fix the example and say "yeah, we broke it". Adding any sort of
restriction is likely to break someone.
I'm open to arguments either way with comma. I'd rather not do it, but
I'll accept it.
On Fri, Feb 27, 2015 at 10:09 AM, gmarek<EMAIL_ADDRESS>wrote:

Well, comma is only a special case because it's used in Guestbook
example
(frontend-controller.json). Because this example is the most visible
one
(at least for us in Warsaw), my feeling is that it was copied a lot of
times as a framework, hence making it invalid may be problematic...
Generally adding any nontrivial validation can break something, but I
guess we'll need to live with it.
--
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76442562>

.

--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76445240
.

Comma is out. I don't really want to think about escaping right now.

BTW, I think "reserving for future use" means that we have to DISALLOW such characters now, lest people start using them in ways that are incompatible with our future plans. We can add flexibility in the future, but it's impossible to take away.

Right

On Feb 27, 2015, at 4:05 PM, Brian Grant<EMAIL_ADDRESS>wrote:
BTW, I think "reserving for future use" means that we have to DISALLOW such characters now, lest people start using them in ways that are incompatible with our future plans. We can add flexibility in the future, but it's impossible to take away.
—
Reply to this email directly or view it on GitHub.

Let's all make a pact to challenge anyone who adds a "string" type to the
API to document the validation rules for it.  Or even move away from string
as a literal type and encourage typedefs to capture semantics.
On Fri, Feb 27, 2015 at 2:14 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Right

On Feb 27, 2015, at 4:05 PM, Brian Grant<EMAIL_ADDRESS>wrote:
BTW, I think "reserving for future use" means that we have to DISALLOW
such characters now, lest people start using them in ways that are
incompatible with our future plans. We can add flexibility in the future,
but it's impossible to take away.
--
Reply to this email directly or view it on GitHub.

--
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76482631
.

On Feb 27, 2015 2:18 PM, "Tim Hockin"<EMAIL_ADDRESS>wrote:

Let's all make a pact to challenge anyone who adds a "string" type to the
API to document the validation rules for it. Or even move away from string
as a literal type and encourage typedefs to capture semantics.

+100 !  I'd be in favor of systematically getting rid of string as a
parameter type internally too, not just in the API. Strings are
just too prone to misunderstanding and subtle bugs. E.g. does this "name"
string include the namespace prefix or not? The code I've been working on
recently is riddled with these types of latent bugs, both in core code and
in unit and system tests.
Q

On Fri, Feb 27, 2015 at 2:14 PM, Clayton Coleman<EMAIL_ADDRESS>wrote:

Right

On Feb 27, 2015, at 4:05 PM, Brian Grant<EMAIL_ADDRESS>wrote:
BTW, I think "reserving for future use" means that we have to DISALLOW
such characters now, lest people start using them in ways that are
incompatible with our future plans. We can add flexibility in the
future,
but it's impossible to take away.
--

Reply to this email directly or view it on GitHub.

--

Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/issues/4628#issuecomment-76482631

.

—
Reply to this email directly or view it on GitHub.

As @thockin suggested, we're changing regexp for label values. Tim suggested to have the same rules for values and qualified names (i.e. '.' should not be correct label value), with the difference that we allow empty values. Are everyone OK, with the new regexp:
([A-Za-z0-9][-A-Za-z0-9_.] *[A-Za-z0-9])?"

Sorry, two mistakes; 'qualified name pieces' not 'qualified names' and regexp should be:
"((" + kubeChar + extendedKubeChar + "*)?" + kubeChar + ")?"

I think this is done.


Allow skipping normalization for certain words

New functionality idea to be considered in the future: Skip certain words or fragments from normalization, to allow capturing the exact input especially since we're trying to catch not only the information that is entered by the user. Some examples:
+ I !really like *
- OK, I see you're serious about that!

Other possible syntaxes that could make sense:
+ I +really like *
+ I "really" like *

Okay, this is next on my list of things to improve.


vs-code debugging with jest

Using the latest version of react-boilerplate, are there instructions on how to run tests with jest with a debugger?
I've tried a lot of different configurations but none seem to hit the breakpoint I specify.

This is directly in the docs-- did you even look :)?

Yes I did. My question is related to using vs-code. Surely someone has an example of the config required for vscode to start debugging tests directly in the IDE.

You might want to actually open the docs.


Support RenderLayers and multi-camera rendering

The stock Bevy render pipeline allows cameras with the RenderLayers component to ignore entities without a matching layer mask (encoded with the same RenderLayers component). This allows multiple cameras to be used to construct a wide range of visual effects.
Particles currently render on all cameras, ignoring the RenderLayers component. This can result in conflicts between effects that use particles and effects that use multiple cameras. To support this Bevy feature, the particle rendering pipeline must detect the RenderLayers component on camera entities and allow layer-specific emitters or effect assets.

I looked at RenderLayers and as I understand it a render pipeline shouldn't really care about this, but rather about the per-view VisibleEntities, which admittedly we also ignore currently. This is because the combination of the render layers of entities vs. the render layers of cameras are baked into VisibleEntities already, alongside the per-entity Visibility. But respecting VisibleEntities in Hanabi requires a tiny bit of refactor because:

for particle spawning and update, this is view-independent, and we can aggressively batch compatible effects together, which is what we do now (more or less; there's room for improvement).
for rendering, sorting (not implemented), and some related effects like billboarding, this is view-dependent and the current batching doesn't work anymore, we need to do a separate per-view batching.

See the new multicam example for multiple viewports/cameras and render layers support.


Null value in a non-null field

Open the creator
Start setting the age

select gestational age
type 9 to weeks
type 6 to days
delete 6 (change my mind, I actually do not know what to put here, so I'm leaving it blank)

I expect this sets the text field to an empty string or null, and marks the field as "tampered with"

Go to Validate section and hit complete

Issue
I get the following:

The validator in the backend correctly points out the issue - an int field is null. The corresponding (errorneous) phenopacket would look like:
{
  "id": "whatever-phenopacket-id",
   "subject": {
      "taxonomy": {
         "id": "NCBITaxon:9606",
         "label": "Homo sapiens"
      },
      "id": "jimmy",
      "timeAtLastEncounter": {
         "gestationalAge": {
            "weeks": 9,
            "days": null
         }
      }
   },
  ...

Note the null in subject > timeAtLastEncounter > gestationalAge > days

The issue can be "fixed" if the user types a value into the field. However, this is undesirable because gestational age of e.g. P22W and P22W0D have different interpretation.
DOD
Clearing optional field won't result in a null field.
Note - this likely applies to other fields as well. See #293 for a similar issue

Looks fine


Card in Card Transition

Detailed description

Describe in detail the issue you're having.
Card in Card Transition is different. The Image does have the correct transition and the card in the card (text card) does not have a transition.

Is this a feature request (new component, new icon), a bug, or a general
issue?
Bug

Is this issue related to a specific component?
http://ibmdotcom-web-components.mybluemix.net/?path=/story/components-card-in-card--default

What did you expect to happen? What happened instead? What would you like to
see changed?
http://ibmdotcom-web-components.mybluemix.net/?path=/story/components-card-in-card--default should have a transition in the text card: transition: 150ms cubic-bezier(0.2, 0, 0.38, 0.9);

What browser are you working in?
Firefox latest version

What version of the NextJS template are you using?

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Steps to reproduce the issue

Step one
Go to card in card section in storybook
Step two
Hover
Step three
See the glitch
etc.

Additional information

Screenshots or code
Notes

More information received
What one sees
https://user-images.githubusercontent.com/48327647/112834634-e4a33380-90a0-11eb-86e8-06bd1eba1a9b.mov
What one should see
https://user-images.githubusercontent.com/48327647/112834656-ebca4180-90a0-11eb-812c-050555fbb153.mov
What seems to be missing


Update minimum rustc version to 0.11.0

Update minimum stable rustc version tested by Travis CI to 0.11.0.

Also need to update the Requirements section of the README.md

Right, forgot. Updated.


add "install azure cli" command

should we also change line 320 to 322?
run: () => {
   opn('https://aka.ms/GetTheAzureCLI');
}

to be:
run: installAzureCLI

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

Yes, sounds good.

I missed that: Maybe that command should also go in the activationEvents in the package.json.

@chrmarti fixed command activation in master


Scope Underscore Not Working

Using an underscore in a scope wont send the SQL query correctly.
Example :
RequestedScopes": "profile email webApi offline_access openid",
AND the SQL query sent.
SELECT [api.UserClaims].[Id], [api.UserClaims].[ApiResourceId], [api.UserClaims].[Type]
FROM [cjii].[ApiClaims] AS [api.UserClaims]
INNER JOIN (
    SELECT [api3].[Id]
    FROM [cjii].[ApiResources] AS [api3]
    WHERE EXISTS (
        SELECT 1
        FROM [cjii].[ApiScopes] AS [x3]
        WHERE [x3].[Name] IN (N'profile', N'email', N'webApi', N'openid') AND ([api3].[Id] = [x3].[ApiResourceId]))
) AS [t3] ON [api.UserClaims].[ApiResourceId] = [t3].[Id]
ORDER BY [t3].[Id]

If I change to "offlineaccess" it works fine.

Moved: https://github.com/IdentityServer/IdentityServer4/issues/1867


"\n" in property value is transformed to a new line in the result

From
ldap.group.mappings.0=groupName=cn\ndescription=description\nuser=uniqueMember
It creates
ldap.group.mappings.0=groupName=cn
description=description
user=uniqueMember

I released a new version yesterday, take a look at the online version if it fixes the issue.

It works correctly, I can no longer reproduce the issue.
Thanks, Thiago!


linux: add extraBuildInputs and extraNativeBuildInputs

Motivation for this change
Create a way to add extra BuildInputs into buildLinux, so linux forks which need extra tools to build linux can use those
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I removed extraBuildInputs, as the probably are not needed, and renamed it to nativeBuildInputs

I removed extraBuildInputs, as the probably are not needed, and renamed it to nativeBuildInputs

@ofborg eval

@ofborg eval

not sure why this fails.

not sure why this fails.

rebased, so OfBorg no hopefully can eval

rebased, so OfBorg no hopefully can eval

Rebasing makes no difference. I think staging eval is broken right now.

Rebasing makes no difference. I think staging eval is broken right now.


feat: 7200 cloud login

Opening draft to get feedback and collaborate with @edgarrmondragon in resolving conflicts in the client code.
Still have some TODOs:

[x] Tests
[x] Finish logout command
[x] Update/correct docs
[ ] General cleanup
[x] Incorporate @edgarrmondragon's changes from #7324

Resolves https://github.com/meltano/meltano/issues/7200

@cjohnhanson I've changed the base branch from main to cloud. Feel free to close and re-create the PR if you'd rather make it clean.

@cjohnhanson - does this pr also include the logout capability?
I linked to the issue but want to make sure I'm not messing anything up if this isn't 1:1 with that.

@cjohnhanson - does this pr also include the logout capability?
I linked to the issue but want to make sure I'm not messing anything up if this isn't 1:1 with that.

@aaronsteers yes, this has logout capability as well -- though there will be a one-line Pulumi update that needs to go out to before this, I realized in testing that you have to provide a redirect URI for the logout and we'll need to add it as an allowed URI in Cognito.

The first time I try to login, I get the following error in my browser (Firefox) console:
Scripts may not close windows that were not opened by script.

It closes as expected on all other attempts.
After authentication the CLI hangs.

@cjohnhanson I've left my review suggestions in another PR:

https://github.com/meltano/meltano/pull/7380

They're mostly small stuff, but a few things I consider important have change there too (e.g. restricting the file permissions on the config file which contains the secret tokens). I've also addressed all of the lint issues.

The first time I try to login, I get the following error in my browser (Firefox) console:
Scripts may not close windows that were not opened by script.

It closes as expected on all other attempts.

@WillDaSilva good callout. I've added a You may close this window. message to the login/logout pages for any browsers that won't run that window.close() call for whatever reason.

@aaronsteers I went ahead and just removed the settings section for the docs. Users shouldn't be configuring any of those configurable options (but we should still keep them around for testing purposes), with the one exception of MELTANO_CLOUD_PROJECT_ID which isn't actually used anywhere in this PR. The meltano cloud run command has --project-id as its own flag, and I think it's reasonable to stick to that pattern in the short term until we settle on a top-level "default" project to use when one isn't provided to subcommands that need it, maybe with an associated env var like MELTANO_CLOUD_DEFAULT_CLOUD_PROJECT


[bug] Gulp test wasn't running server tests [closes #873]

This PR fixes #873. The models were never getting loaded in the gulp tests so it was freezing on mongoose errors. This loads the models before running the server tests.

@mikepc

I can confirm this fixes the issue.
@codydaig It looks like the behavior between the Grunt & Gulp test tasks is slightly different. Using Gulp, it appears that the karma task is started before the Mocha task completes. This ends up skewing the reporting output from the tests. Whereas, using Grunt, the Karma task doesn't start until the Mocha task is complete.

@codydaig It looks like the Gulp test task is running both the Karma & Mocha tests in parallel.. The task defined here https://github.com/meanjs/mean/blob/master/gulpfile.js#L222, can be updated to this
// Run the project tests
gulp.task('test', function (done) {
  runSequence('env:test', 'mocha', ['karma'], done);
});

This will run the Mocha task first, and then run the Karma task. Learned something new about run-sequence :) anything that you want to run in parallel, you just group them within an array param of runSequence() But for this case, I think we want Mocha to run first; to be consistent between Grunt & Gulp.

@mleanos I'm working on refactoring the gulp file to be more inline with the grunt file. This was just a bug fix in the meantime. I'm happy to make the change if thats desired in this PR as well.

@codydaig I think making that change in this PR is appropriate. Just so that this particular Gulp task outputs the results in a readable manner.

@mleanos Change has been made.

Perfect. LGTM. Thanks @codydaig

@rhutchison Any comments on this PR? I think you we're one of the guys pushing for gulp.

@codydaig regarding what were you looking for feedback from @rhutchison?

@ilanbiala I'm pretty sure it was @rhutchison that was pushing for the gulp change, and had made some improvements in the gulp file in the past. But I've tested this and it makes it so you can run the tests with gulp, so since ryan doesn't have any feedback, then I think it's good to merge.


zxfer does not handle writing its metadata to unmounted file systems

Such as:
Writing backup info to location none/.zxfer_backup_info.tank
sh: cannot create none/.zxfer_backup_info.tank: No such file or directory
Error writing backup file. Is filesystem mounted?

Perhaps it could temporarily mount the filesystem path that it needs and the unmount after writing out the metadata.

I have the same problem.