Error thrown when install using Docker-Compose

Description
Error thrown when install using Docker-Compose,
Stoped at bellow logs:
nakama         | {"level":"info","ts":"2019-04-22T09:26:48.933Z","msg":"Found runtime modules","count":0,"modules":[]}
nakama         | {"level":"info","ts":"2019-04-22T09:26:48.933Z","msg":"Starting Console server for gRPC requests","port":7348}
nakama         | {"level":"info","ts":"2019-04-22T09:26:48.933Z","msg":"Starting Console server gateway for HTTP requests","port":7351}
nakama         | {"level":"info","ts":"2019-04-22T09:26:48.933Z","msg":"Starting API server for gRPC requests","port":7349}
nakama         | {"level":"info","ts":"2019-04-22T09:26:48.934Z","msg":"Starting API server gateway for HTTP requests","port":7350}
nakama         | {"level":"info","ts":"2019-04-22T09:26:49.177Z","msg":"Startup done"}
^CGracefully stopping... (press Ctrl+C again to force)
Steps to Reproduce
install using Docker-Compose
Your Environment

Nakama:2.4.0
Cockroach: v2.1.4
Operating System and version: CentOS7.6

docker-compose version 1.24.0

This is normal server operation, seems like you’ve stopped the server manually yourself.
I don’t see any errors being thrown here. What are you referring to here?
(Ps please only comment on one issue, not multiple)

It stopped at this log, and didn't move on to the next step.
nakama         | {"level":"info","ts":"2019-04-22T09:26:49.177Z","msg":"Startup done"}
It means the installation was successful？

@gucheng117 I think you're confused. "Startup done" means the server has fully started and all subsystems have initialized. I think it will be quickest to ask any more questions in the community channel: https://gitter.im/heroiclabs/nakama

@novabyte OK, thank you.

Adding tty: true under nakama services fixes the issue


Can not assemble release build after upgrading environment

Hi, I'm not newbie for android development.
After upgrading environment of react native, especially putting "org.gradle.configureondemand=true" in gradle.properties, it stop compiling release build.
app/build.gradle
compileSdkVersion 27 ( originally was 23 )
buildToolsVersion "27.0.2" ( originally was 23.0.2 )
build.gradle
classpath 'com.android.tools.build:gradle:3.0.1' ( originally was 2.2.3  )
gradle.properties
org.gradle.configureondemand=true
android.enableAapt2=false ( < same results )
used command
./gradlew assembleRelease
error code
/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values-v26/values-v26.xml:9:5-12:13: AAPT: resource android:attr/colorError not found.

/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values-v26/values-v26.xml:13:5-16:13: AAPT: resource android:attr/colorError not found.

/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values-v26/values-v26.xml:17:5-93: AAPT: style attribute 'android:attr/keyboardNavigationCluster' not found.

/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values/values.xml:252:5-69: AAPT: resource android:attr/fontStyle not found.

/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values/values.xml:252:5-69: AAPT: resource android:attr/font not found.

/.gradle/caches/transforms-1/files-1.1/appcompat-v7-27.0.2.aar/93c2a1d353f8f315d0e501836fdfab5d/res/values/values.xml:252:5-69: AAPT: resource android:attr/fontWeight not found.

error: resource android:style/TextAppearance.Material.Widget.Button.Borderless.Colored not found.
error: resource android:style/TextAppearance.Material.Widget.Button.Colored not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:7: error: resource android:attr/colorError not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:11: error: resource android:attr/colorError not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:15: error: style attribute 'android:attr/keyboardNavigationCluster' not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values/values.xml:163: error: resource android:attr/fontStyle not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values/values.xml:163: error: resource android:attr/font not found.
./node_modules/react-native-audio/android/build/intermediates/res/merged/release/values/values.xml:163: error: resource android:attr/fontWeight not found.
error: failed linking references.

Is there any technique to avoid this error?
Thanks in advance.
Tell us which versions you are using ( you can see the versions in your package.json ):
react-native-audio :  4.0.0
react-native :0.55.4
react :  16.3.1
using react-native-sound ? Yes: git+https://github.com/zmxv/react-native-sound.git#fd89265133963b6914d292bdc9c7f8478440f9ba

After clean install with react-native init AwesomeProject,  the error was gone.


Make !wait its own command instead of being part of the parser logic

What part of Adonis is this related to?
Command
What are you suggesting?
Make !wait it's own command instead of being part of the parser logic

There is a problem
\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: 1000; position: fixed; inset: 0; opacity: 100%; background-size: 100% 100%; background-image: url('https://github.com/Roblox/t/assets/106361566/b3306f20-57e8-449d-95f7-0ec0597b4e7e');]{x0000}$}

How would that work tho?

Also, why


BUG: Update vtkRenderingLookingGlass to fix support with the "Portrait"

Updates vtkRenderingLookingGlass to include recent fixes, which adds support for the Looking Glass Portrait.
Fixes #17

Closing. This pull request is superseded by https://github.com/KitwareMedical/SlicerLookingGlass/pull/25


[WIP] Add capability to serialize and de-serialize dice-ml explainers

Signed-off-by: Gaurav Gupta<EMAIL_ADDRESS>

Codecov Report

Merging #289 (eb4de88) into master (195b638) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

:exclamation: Current head eb4de88 differs from pull request most recent head e56562a. Consider uploading reports for the commit e56562a to get more accurate results

@@            Coverage Diff             @@
##           master     #289      +/-   ##
==========================================
- Coverage   71.26%   71.20%   -0.07%
==========================================
  Files          26       26
  Lines        3438     3448      +10
==========================================
+ Hits         2450     2455       +5
- Misses        988      993       +5

Flag
Coverage Δ

unittests
71.20% <100.00%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

dice_ml/explainer_interfaces/explainer_base.py
88.73% <100.00%> (-0.53%)
:arrow_down:

dice_ml/explainer_interfaces/dice_random.py
91.79% <0.00%> (-1.50%)
:arrow_down:

Continue to review full report at Codecov.

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


make install should be named something else

Overview
Our build system pervasively uses make install to mean something like "download and locally install the build dependencies."
This, unfortunately, conflicts with the conventional meaning of make install, which is "install the program we just built into the standard system directories." Or, as the GNU Make manual puts it, to "compile the program and copy the executables, libraries, and so on to the file names where they should reside for actual use."
For the sake of reducing surprises, we should rename make install to make dev-deps or something.
(This might be more intrusive than it is beneficial, but hey.)
Considerations

We should agree on a good new name. I'm not aware of any conventional ones.
All instances of the install target will have to be updated.
Readmes and other documentation will have to be updated.
There should be a deprecation period in case there's a hidden CI script somewhere that's using make install.

Work
If there are no objections in principle, I can give it a shot, as a vehicle for familiarizing myself with the breadth of the build system.

Yeah, this one was a complete brain fart by me. I had npm install in my head when I set them up, despite the fact that I read and tried to follow the GNU conventions.
In Opentrons/opentrons-modules#50 we ended up going with setup and teardown. I don't have strong feelings on the task name itself, but any consistency is good

Cool.
@mcous Could you clarify the scope of make install as it currently exists? I see several kinds of dependencies:

Actual code dependencies, like libraries.
Development dependencies, like pytest.
Incidental dependencies just for the build system, like shx.

Does make install cover all of these?
I ask because there might be a more precise name we can use. (Otherwise, make setup sounds good.)

@SyntaxColoring it covers all three of those. Everything you need to build, test, and run any project in the monorepo.
Ignoring the task names, the tasks are configured in such a way to allow the setup steps for JS and Python to be run in parallel via make install -j. Please avoid touching any task structure for this reason


Accessibility: Unable to edit/delete date using 'Delete' or 'Backspace' button after first use

Expected behavior
In datepicker, the date should be cleared on use of 'Delete' or 'Backspace' button.
Actual behavior
While using react-datepicker with redux-form, unable to clear the date after a valid date is selected / entered through textbox.
Steps to reproduce

Create a react form with redux-form and create react-datepicker field as one of the fields.
After loading the form, select a valid date.
Try to edit/delete the date using 'Delete' or 'Backspace' buttons and observe.
Unable to edit/delete the date after first use.

Are you able to reproduce the problem on https://reactdatepicker.com/ ? It seems to be working as expected for me...

Was this ever solved?

the issue is reproducible when we use the reactdatepicker along with redux-form. Is there suggested approach/way to make them work together

I found the issue is reproducible when we try to make DatePicker a controlled component. Instead, use it as an uncontrolled component and it will work. This means simply avoiding having value as an attribute in your DatePicker.
I think DatePicker has its own state management internally.
Hope this helps anyone. Thanks!

thank you @Swastikyadav . This solution helped me

But this doesnt help when you want to hold the date value and display it

But this doesnt help when you want to hold the date value and display it

Sorry for not being responsive here @vilasinimodem
I hope you have resolved this by now. But in case you haven't or anyone else may need this.
You should try to use some combination of defaultValue, refs, and onChange handler.


Customization of XArray Columns

Problem description
Hello,
I created a custom Series in pandas' that has function on it not normal to a normal pd.Series.  Can you create custom columns in xarray?  Are there any examples of that?
Thanks

@achapkowski - can you take a look at our documentation on Extending xarray and let us know if that is sufficient to have us close this issue?


How do I get out of this?

Describe your problem here.

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

I figured out that it's "", but I need it to not appear when the song first loads. I don't know if it's still a Flixel problem though.


[1.3.0 beta] Text box placeholder label weirdness

When a chat is opened via selecting a notification, if Use Chat Name As Placeholder Label is enabled, it behaves oddly. Sometimes it will just say

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @electronika in #android-bugs.

full text: When a chat is opened via selecting a notification, if Use Chat Name As Placeholder Label is enabled, it behaves oddly. Sometimes it will just say "Bluebubbles" instead of the contact name, and sometimes it will be the phone number instead of the contact name. The issue goes away by exiting the chat and re-entering it

Update: I can no longer reproduce this currently. Might have just been a fluke

This is intended, it is just nullsafety catching null exceptions. It will first check if it can find the contact & if so it will display the contact name, otherwise it will try to display the "address" it got from the mac (so a phone number), and finally it will fallback to just "BlueBubbles".


🐛 Bug Report: Users not found

👟 Reproduction steps
Hi,
This code "Users users = Users(client);" does not work with flutter SDK. Is there a difference between dart and flutter SDK? Since this same chunk of code is working with dart sdk
👍 Expected behavior
Dart or flutter normally share same code
👎 Actual Behavior
Users not defined in flutter appwrite package
🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
Linux
🧱 Your Environment
I am using digital ocean
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Users API is basically something that would be found on server side. so you won't find this API class in the flutter_appwrite . And yes there is a difference between [flutter_appwrite](https://pub.dev/packages/appwrite) and [dart_appwrite](https://pub.dev/packages/dart_appwrite) . Flutter appwrite SDK contains all the APIs for the client side while the Dart appwrite SDK is used for performing server side functions.  If you look at the docs you can notice that some functions are different in server and client side SDK.
Also if you look at the docs, you will see it only on the server side only.

Actually I was trying to undestand the code bellow which by the way found in the flutter sdk
Users users = Users(client);

try {
  final response = await users.create(userId: '[USER_ID]', email: ‘email@example.com’,password: ‘password’, name: ‘name’);
  print(response.data);
} on AppwriteException catch(e) {
  //show message to user or do other operation based on error as required
  print(e.message);
}

This creates a new user on the server side.  And you will find this code in the dart package .

@2002Bishwajeet, thanks for chiming in on this!
@pixeluvw, is there anything else you need for this or can it be closed?

That's fine for me thanks

Thanks again


Grid Resize Column does not work properly in RTL

Hello I Used SlickGrid in RTL Theme and  When I resize the column width it wont resize the column in right way.

thi repo is dead. use: https://github.com/6pac/SlickGrid


Extract column lineage from indirect dependencies

The current implementation of column lineage extraction does not address real world applications as far as I can tell.
The two most common applications I can think of are:

Impact analysis when changing definition of columns or considering deletion
Understanding definition of columns

Both of these applications require extracting indirect column dependencies from e.g. WHERE, GROUP BY, IF and CASE WHEN clauses. As far as I can tell this is not possible at the moment (unless I'm missing a configuration option).
Example 1) (this is actually from the ExtractColumnLevelLineage.java examples):
UPDATE `bigquery-public-data.samples.wikipedia` W
   SET title = S.corpus, comment = S.word
FROM (SELECT corpus, UPPER(word) AS word FROM `bigquery-public-data.samples.shakespeare`) S
WHERE W.title = S.corpus;

extracts:
Lineage:
bigquery-public-data.samples.wikipedia.comment
                <- bigquery-public-data.samples.shakespeare.word
bigquery-public-data.samples.wikipedia.title
                <- bigquery-public-data.samples.shakespeare.corpus

when I would like to see:
Lineage:
bigquery-public-data.samples.wikipedia.comment
                <- bigquery-public-data.samples.shakespeare.word
                <- bigquery-public-data.samples.shakespeare.corpus*
                <- bigquery-public-data.samples.wikipedia.title*
bigquery-public-data.samples.wikipedia.title
                <- bigquery-public-data.samples.shakespeare.corpus
                <- bigquery-public-data.samples.wikipedia.title*

The * indicates an indirect dependency (of course the output is generated by the user, so zetasql would have to provide some attribute for indirect relationships). Both columns indirectly depend on corpus and title. The definition of comment changes, if we make changes to either corpus or title in upstream tables. I would like to be aware of that when I make changes to those columns.
Another two made up examples:
Example 2) GROUP BY:
Query:
CREATE TABLE foo.bar AS
SELECT
    SUM(word_count) words,
    corpus,
FROM `bigquery-public-data.samples.shakespeare`
GROUP BY corpus;

Lineage:
foo.bar.corpus
                <- bigquery-public-data.samples.shakespeare.corpus
foo.bar.words
                <- bigquery-public-data.samples.shakespeare.word_count

where I would like to see:
Lineage:
foo.bar.corpus
                <- bigquery-public-data.samples.shakespeare.corpus
foo.bar.words
                <- bigquery-public-data.samples.shakespeare.word_count
                <- bigquery-public-data.samples.shakespeare.corpus*

Example 3) IF:
Query:
CREATE TABLE foo.bar AS
SELECT
    SUM(IF(word_count > 10, 1, 0)) word_count_gt_ten,
    corpus,
FROM `bigquery-public-data.samples.shakespeare`
GROUP BY corpus;

Lineage:
foo.bar.word_count_gt_ten
foo.bar.corpus
                <- bigquery-public-data.samples.shakespeare.corpus

where I would like to see:
Lineage:
foo.bar.word_count_gt_ten
                <- bigquery-public-data.samples.shakespeare.word_count*
foo.bar.corpus
                <- bigquery-public-data.samples.shakespeare.corpus

Please add configuration options for detecting these indirect dependencies, otherwise I don't see anyone adapting column level lineage which could be extremely powerful.

You bring up a very good point, thank you for reporting this!
I originally envisioned the column lineage feature to focus only on columns that were used to write to other directly. But now that you bring this discussion up; I agree that we should have visibility on filters, groups, etc.
I'll need to look into it a bit to give you a timeline. My first impression is that it'd require decent refactor of how lineage is currently implemented. But I'd like to have this as well!

Thanks, would be amazing to have that feature!


Update react-native.md

Specify that the docs are talking about React Native 0.18 rather than React 0.18 to avoid confusion.

LGTM thanks!


added deep-copy functions tosc_copy_message and tosc_copy_bundle

Added two simple deep copy functions.
As you can see the memory allocation is completely in charge of the caller (as warned within the function comments), which results in the functions being very simple, which I guess might make them quite light to maintain in the future.
Anyways please feel absolutely free to close if you don't find them useful in the API.
(I can move this feature in the client)
Please also feel free to return any feedback or demand for any change or modify it.
Cheers again  👍

Hi @neonsoftware, thanks a lot for the PR! I can certainly see the usecase for a deep copy function. In order to simplify what you've proposed, what do you think of something like:
int tosc_copy_message(tosc_message *d_o, char *d_buffer, int d_len, tosc_message *src_o) {
  if (d_len < src_o->len) return -1;
  memcpy(d_buffer, src_o->buffer, src_o->len);
  tosc_parseMessage(d_o, d_buffer, src_o->len);
  return 0;
}

Hi @mhroth.
calling the parser ? Even better !

let me know if the PR is to be re-done or the change will be on your side

I realise that this PR is dragging on, I'm sorry for that. Could you write a code snippet for how you intend to use this function? This function is now only saving you two lines of code (one to copy the buffer, one to parse the buffer). I'm thinking that the usecase is to copy the OSC buffer away from the networking code and onto some other queue. To me it feels like if that's what you are trying to accomplish, then, it seems to me, you wouldn't need this kind of a deep copy function. You could just call memcpy(d_buffer, src_o->buffer, src_o->len) manually?
I hope that you don't misunderstand my intentions. I really appreciate the PR, and I'd like to balance that with keeping the library, well, tiny ;)

No problem at all ! 👍
Please always take all the time it takes to defend quality.
It's a fast world, they say, but it's also wrong and broken.
It's ready when it's ready. 😄
Thanks to you for taking the time to maintain.
But here is the current usage context, absolutely, please feel free to see where they are used, here in this repo, for example, search toss_copy in the file.
kian_next_message() looks in a pump to check if a message has arrived.
The caller of kian_get_next_message is going to stack the message up in an array to use them after, so it needs to strictly deep-copy.
int kian_get_next_message(tosc_message *dst)
{
	tosc_message *next_msg = NULL;

	if (!kian_bag.is_initialized)
		kian_init();

	next_msg = kian_next_message();
	if (next_msg != NULL) {
		tosc_copy_message(dst, next_msg);
		return 1;
	}
	return 0;
}

if I substitute I would still need also a tosc_parseMessage, please feel me if I'm wrong
int kian_get_next_message(tosc_message *dst)
{
	tosc_message *next_msg = NULL;

	if (!kian_bag.is_initialized)
		kian_init();

	next_msg = kian_next_message();
	if (next_msg != NULL) {
                memcpy(dst->buffer, next_msg-> buffer, dst->len);
                tosc_parseMessage(dst, dst->buffer, dst->len);
		return 1;
	}
	return 0;
}

Two aspects :

I actually did not, even in my code which must improve, verify the return of the buffer length check(-1). In that case I would have, in the second version, have to also add the length check (if (d_len < dst->len) return -1). But let's keep this apart, and the number of code lines would have been the same.
Looking at the code, the indirections and access to internal data structure are quite explicit (->buffer, ->len), are white-box, no encapsulation or abstraction as in the east of the API, the user needs to know about about the exact internals. You would not be able to change the namings (you want to rename len to buflen) in tosc_message without breaking deep copies. Here the motivation for the addition of the deep-copy API.


RFC: BC Break - CMS to have it's own route

Hey guys,
Routing through the event listener is quite an issue for existing ZF 2 apps.  It also adds unneeded configuration options.   In order to assist me going forward to make this less intrusive, I'd like to suggest the following change:
Currently the CMS routes are defined like the following:
        'contentManager' => [
                'type' => 'Zend\Mvc\Router\Http\Segment',
                'options' => [
                    'route' => '/rcm[/:page][/:revision]',
                    'defaults' => [
                        'controller' => 'Rcm\Controller\IndexController',
                        'action' => 'index',
                    ]
                ],
            ]

I'd like to change this to:
        'contentManager' => [
                'type' => 'Rcm\Route\Cms',
                'options' => [
                    'route' => '/rcm',
                    'defaults' => [
                        'type' => 'n',
                    ]
                ],
            ]

Reason:  This will allow me to fix or remove many of the attached event listeners and use the Route Manager for what's it designed for.  In addition, this will allow the normal 404 error messages to be handled by the default 404 error handler in Zend.

I agree RCM should use its own route type rather than the old index controller method. @jerv13 James what do you think?

I am OK with it, submit some code :)

I would like to checkout your code and test it and see the impact before I merge it.

Ok will do.

Change added to reliv/Rcm  Pull request #247.  Please see comments for BC break and migration notes.

@jerv13  - The unit tests are failing, but you should be able to checkout that PR and test against your app.  I'll fix the unit tests and add one for the route, while you're checking this out.


Request is not going upto app container.

Hello Team,
I am new to Kamal.
My Kamal Version: 1.3.0
I am exploring kamal to deploy our ruby app. I am able to create my app container (As health check is passing) and traefik container is also created which is exposing port 80 on host node.
Below is my kamal config/deploy.yml file:
# Name of your application. Used to uniquely configure containers.
service: sf-app

# Name of the container image.
image: sf-app
# Deploy to these servers.
servers:
  web:
    hosts:
      - <IP_ADDRESS>
    port: "8080:8080"
#    traefik: false
# Credentials for your image host.
registry:
  # Specify the registry server, if you're not using Docker Hub
  server: xyz-docker.pkg.dev/devops/kamal
  username: _json_key_base64
  password:
    - KAMAL_REGISTRY_PASSWORD

builder:
  multiarch: false

# Configure custom arguments for Traefik (commented out)
# traefik:
#   args:
#     accesslog: true
#     accesslog.format: json

# Configure a custom healthcheck (commented out)
healthcheck:
   path: /cloud/health-status
   port: 8080
   max_attempts: 100
   interval: 60s

on my target host <IP_ADDRESS> i can see my app conatiner and treafik is running fine. But when i checked treafik container logs i can see 502 bad gateway error means request is reaching upto treafik but its unable to forward to app container.

But i am unable to understand how the treafik will forward the request to my app container.
Can you please point me in right direction which configuration i am missing here. So i can test my app functionality.
Can you please help me here?
Thank You

Hi Team,
Can you please guide me on above issue?
Thank You

@Tekchanddagar if you don't have anything else in your deploy.yml, than it looks like a pretty default config except to two things:

port 8080
healthcheck

I suggest reset the to default, make sure that everything works and do any changes only after this.

@igor-alexandrov , Thank You for your response.
As i am new to kamal. Was making one mistake. Inside kamal config/deploy.yml i was using below config:
servers:
  web:
    hosts:
      - <IP_ADDRESS>
    port: "8080:8080"

But traefik by default listen on port 80 and my app was running on port 8080.
So I have changes the host port from 8080 to port 80 inside my kamal config/deploy.yml file i.e
servers:
  web:
    hosts:
      - <IP_ADDRESS>
    port: "80:8080"

And after making this change my site is up.
Thank You

@Tekchanddagar I am glad it helped. Please close the issue.


[Refactor]: remove slug segment from DELETE comment API URL endpoint

Description
The current API URL to delete a comment is /articles/{slug}/comments/{id}.
The slug segment is the slug of the related article.
To delete a comment, this slug isn't required.
Solution
Change the URL to /articles/comments/{id}.

can i work on this issue please?

discontinued task


Chat sample build error. firebase_options.dart missing file

I cannot build the chat sample app.
Target of URI doesn't exist: 'firebase_options.dart'.
Can you please update your samples so that they can be successfully built and run out of the box?

No, it is the config file related to your firebase account. See this short guide how to generate it


How to pass a custom list of value in the component ?

Hi !
Can we do something like this ?
<jaspero-chips [listOfItems]="myList"></jaspero-chips>

Thanks in advance

Sorry about that, i used reactiveForm finally, it's better ^^


GPU Particle Attractor has no effect on stationary particles (GPUParticle3D)

Tested versions
v4.2.1.stable.official [b09f793f5]
System information
4.2 stable, Windows 10 - Vulkan Forward+ - Nvidia GeForce RTX 2070 Super
Issue description
I'm trying to use a particle attractor to shoot away particles that have landed (collided) on a surface. The attractor works fine as long as they are moving, but when they land on the surface and become still the attractor don't have any effect on the particles.
I have set the Collision to Rigid and Friction to 0. I've tried Bounce from 0 and above (with a bounce of 1 the attractor work as the particle has bounced off the surface and is in the air again).
Steps to reproduce
Create a GPU Particle 3D
Create a GPU Particle Collision Box
Create a GPU Particle Attractor Box 3D
Assign a sphere shape to the Particle and turn Collision on, set to Rigid and Friction to 0 and Bounce to 0
Have the particles land on the Collision box and become still
Move the Attractor over the particles to have them move. They are not affected by the Attractor
Minimal reproduction project (MRP)
ParticleTestProjectX.zip

Please provide a minimum project to make this easier to test 🙂

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
If the reproduction steps are not project dependent (e.g. the bug is visible in a brand new project), you can write "N/A" in the field.
Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.

@AThousandShips I've added a test project

I did some testing. It seems what happens is that one of the "collided" states of a particle sets it velocity to 0 unless there is a massive change in velocity. The force the attractor applies to the particle is not enough to push it out this state causing the particle to look stuck.

I think I have a fix but it is definitely going to change existing behavior. Doing some more testing.


Temporal Alignment

Fixes #61.
See example file: aligned-reinforcement-photometry-b814a426-7ec9-440e-baaa-105ba27a5fa6.nwb

@pauladkisson
How does this look to you? w.r.t. the experiment setup

Personally, one question I have is the 38.7 shift on all the processed ophys when the raw photometry data starts from 0; also how the raw photometry only goes up to 1607s whereas the processed ones go up to 1835s

Temporal alignment bugs should be fixed.  Ready for re-review.
Note: For velocity modulation experiments, optogenetic stimulation starts halfway through the session per Methods: Closed-loop velocity modulation experiment.

Beautiful!


There is a bug when reinstalling Langflow1.0.0a37 through a local folder when Langflow1.0.5 is already available.

How to reinstall version 1.0.0a37 of Langflow1.0.0a37 when there is already version 1.0.5 of Langflow1.0.5?
I encountered a bug after trying the following
When there is already version 1.0.5  of Langflow1.0.5, reinstall Langflow1.0.0a37 through a local folder.

After installation, there is an error message stating that the frontend file is missing.

Move the frontend of the local file to the running path directory and try running it again
An error occurred while running.

After uninstalling the current version, reinstall the local Langflow 1.0.37 version, allowing for no folder loss error but still encountering errors.

@dosu After clearing the cache and deleting files, run migration to resolve the issue with the following error message.

Afterwards, attempting to run langflow directly resulted in the following error message.

@dosu I hope to use the old version Langflow 1.0.0a37. How to install it directly.

Install Langflow 1.0.0a37 directly using instructions

The same error message still appears after running

@zzleaning is there a specific reason why you want to use a deprecated and unmaintained version of langflow?
in any case, I suggest you to remove the entire langflow directory in the conda environment and try with a fresh install.
Also setting LANGFLOW_LOG_LEVEL=debug in the env variable might help understanding the actual problem

@zzleaning is there a specific reason why you want to use a deprecated and unmaintained version of langflow?
in any case, I suggest you to remove the entire langflow directory in the conda environment and try with a fresh install. Also setting LANGFLOW_LOG_LEVEL=debug in the env variable might help understanding the actual problem

Thanks for your answer. I am using this version only because the previously installed version was missing many components. Perhaps there was an issue during the first configuration, but I overlooked it. At present, I am still a beginner in learning how to use Langflow, and I have not fully understood many things, so I am trying to switch to the version that my leader is currently using. Yesterday at the end, I created a new conda environment and reinstalled Langflow, and now it can be used normally. Thank you again!


Patch 1

This seems to be based on a really old PR, do you mind updating it? Should
make the commit summary much more condensed :)
On Mon, Feb 3, 2020 at 2:47 AM IDigle1<EMAIL_ADDRESS>wrote:

Fixed typo
You can view, comment on, or merge this pull request online at:
https://github.com/pcottle/learnGitBranching/pull/632
Commit Summary

Resolves #476
Resolves #477 -- scope binding issue with refresh
Resolves #479 -- switch to https for everything
Fix french word
Merge pull request #481 from MartinGoulet/patch-1
Update french translation
Merge pull request #482 from joachimstalder/master
Resolves #483 case sensitivity
handle the ' too
Fix typo in french
Merge pull request #485 from danielleberre/patch-1
Resolves #484 change solution command
Resolves #484 change solution command
Resolves #484 change solution command
Resolves #486 -- easier to understand button labels when interactive
rebasing
Typo fix
Merge pull request #490 from moskdev/typo_fix
Resolves #487
Resolves #488 -- make https-y things links in the console
Set html lang and meta http-equiv="content-language" attr on
language change.
Generate alternate url for different locales so search engine could
find them all.
Set html lang, remove unused import
Small fix - replace regex with string split
Merge pull request #492 from PanAeon/feature/change-lang-meta-attr
Requested changes - removed underscore and sorted out duplicates in
locales
Merge pull request #493 from PanAeon/feature/generate-alternate-urls
Merge pull request #471 from PHPirates/typos
Followup to PR #471 -- json issue
Fix typo
Merge pull request #495 from paikwiki/fix-typo
Resolves #497 -- fix unescaping random content from terminal (more)
fixed typo in german translation
Merge pull request #501 from CookieCompiler/master
update zh_cn translation in describe.js
corrected grammatical error in readme.md
Fixed typos in comments and strings
Fixed typos in comments and strings
Merge pull request #505 from Hongarc/master
Merge pull request #504 from fillerInk/master
Merge pull request #503 from RogerLiNing/zh_cn_translation
Remove module object-assign
Fix more typo, ' and some word
Merge pull request #508 from Hongarc/typo
Merge pull request #507 from Hongarc/object-assign
change '_.extend' to 'Object.assign'
change '_.clone(..args)' to 'Object.assign({}, ..args)'
Replace some '_.each' with 'Array.prototype.forEach'
Replace '_.map' to 'Array.prototype.map'
Replace '_.reduce' to 'Array.prototype.reduce'
Replace '_.filter' to 'Array.prototype.filter'
Replace '_.keys' to 'Object.prototype.keys'
Use 'util/escapeString' instead of _.escape
Use 'Object.values' and 'Object.keys' to get list 'keys' and 'values'
Use 'Array.prototype.forEach' instead of '.each' and '.forEach'
Use 'Object.values' and 'Object.keys' instead of '_.each(object)'
Use 'Array.prototype.includes' instead of '_.include'
Remove 16 underscore requires
Fix space-group in
No join, no split
Merge pull request #509 from Hongarc/simple
Merge pull request #510 from Hongarc/args
Fixed scroll 125% or higher
Fixed don't show all of #commandLineBar
Avoid display 900px in small screen
remove forgot in 'no more native' a9dd27c
Merge pull request #514 from Hongarc/package
Merge pull request #511 from Hongarc/css
Restore src/levels in Gruntfile.js
Add some info about this repository
Merge pull request #515 from Hongarc/package
Change npm to yarn
Merge pull request #517 from Hongarc/master
Remove module unuse
Add yarn.lock
Create simple debounce and throttle instead of _.
Use Object.values instead of _.each : 96ddb50
fix a little typo in cn
Merge pull request #520 from jasonqu/patch-1
Merge pull request #518 from Hongarc/module
fix(css): fix offset top of select level (in firefox)
Merge pull request #522 from Hongarc/css
Merge pull request #519 from Hongarc/underscore
chore(git): remove some line is covered by other line
chore(git): add yarn-error.log to .gitignore
Merge pull request #523 from Hongarc/gitignore
refactor(html): don't use underscore.min.js
Merge pull request #524 from Hongarc/dependencies
fix chinese translate
Update interactiveRebase.js
Merge pull request #529 from labixiaoshuai/master
update french spelling
Fix french translation
Yet another small french typo fix
Merge pull request #533 from LeBezout/fix-french-translation
Merge pull request #535 from danielleberre/patch-2
Merge pull request #536 from danielleberre/patch-3
pick -> Omit/Pick
Merge pull request #538 from LeBezout/fix-toggle-button-helperText
Merge pull request #527 from wasd845/master
Make button text unselectable
Merge pull request #542 from nikitavbv/fixBtnSelect
Resolves #540
see #543 improved git describe
German translation fix
Merge pull request #545 from mrclrchtr/patch-1
Merge pull request #544 from bwl21/bwl21/543
Make contributions easier
Merge pull request #546 from jankeromnes/master
Update German translation
Use 'grunt fastBuild' in Gitpod to build the app faster
Merge pull request #547 from MichaWiedenmann/patch-1
whitespace for travis
Merge pull request #548 from jankeromnes/patch-1
Print helpful welcome message in Gitpod
Merge pull request #549 from jankeromnes/master
Refactor show commands to extract keys from the object
Merge pull request #550 from grocky/fix-#541
Add configuration for Galician language
Merge pull request #552 from viticlick/gl-language
Fix: file remoteBranches.js
Merge pull request #553 from toofff/fix-file-remote-branches
Resolves #554
Update grunt version
Merge pull request #555 from Hongarc/patch-1
Resolves #557 -- add contributor faces
fix(readme): hide comment in README.md
chore(deps): contributor-faces to devDepen
chore(readme): remove blamk line
Merge pull request #559 from Hongarc/patch-3
Merge pull request #558 from Hongarc/patch-2
remove Node.js v7 in travis-ci
Merge pull request #560 from Hongarc/patch-4
use every instead of _.uniq
remove unused underscore
Explicitly fail when unsupported range operator is specified
Add tests for currently supported log arguments
Implement rev-list
Implement log using RevisionRange
chore: add PRs wellcome to README.md
Merge pull request #566 from Hongarc/prs-welcome
Merge pull request #563 from eatdrinksleepcode/no-range-operator
Merge pull request #564 from Hongarc/unused
Merge pull request #565 from eatdrinksleepcode/revision-range
Use Object.assign instead of module assign
Remove all white space at end of line
Update package
Merge pull request #567 from Hongarc/trim
Merge pull request #568 from Hongarc/package
Add https: to cdn file, can test with open file
Use uglify-es instead of uglify
migrating old version react to last version
Convert revision range processing to pipeline model
Support range operator in revision range (log and rev-list)
Revert "Update package" PR #568
Merge pull request #569 from eatdrinksleepcode/range-operator
Update test in travis-ci
Merge pull request #572 from Hongarc/patch-5
fix: correct module instead of react
feat: up to date dependencies , migrate react
Change esversion to 6
Fix resize width and height to -1
Resolves #574 -- move npm to yarn everywhere else
Merge pull request #573 from Hongarc/package
Update yarn.lock file
Update README reference from npm to yarn
Merge pull request #575 from
eatdrinksleepcode/update-yarn-lock-for-grunt-update
Merge pull request #576 from eatdrinksleepcode/yarn-README
Check that there are no source file changes before building
Merge pull request #577 from eatdrinksleepcode/verify-no-changes
Use babelify instead of grunt-react
Remove @babel/preset-env
Merge pull request #579 from Hongarc/react
Make Gitpod use yarn grunt instead of the global grunt
Prefix grunt with yarn in README.md as well
Merge pull request #580 from jankeromnes/patch-1
Set line height of icons bar icons
Merge pull request #582 from kimsey0/patch-1
Resolves #583 -- fix function binding
feat: make es_ES available from the languages menu
Merge pull request #584 from DevIntent/enableEsEs
add favicon
add link with icon in head
Merge pull request #586 from luciancic/favicon
rampup relativeRefs translate corrections
Merge pull request #587 from hisbvdis/ru_translate_corrections
Small mistake in previous commit
Merge pull request #588 from hisbvdis/ru_translate_corrections#2
fixed a typo of fetchRebase.js
Merge pull request #597 from wuzh07/fixTypo-from-wuzh07
Added support for git tag -d  and fixed a bug where a duplicate
tag name wouldn't show in the error-msg
Merge pull request #599 from LukasSchmid97/deleteTags
Test coverage for deleting tags, PR #599
remove random file
Fixed typo in error message displayed
Merge pull request #600 from Retucex/master
Change upper value in 'git-error-args-few' string to lower
Merge pull request #602 from mexanga/commandTimeout
Update index.js
Update index.js
Update contributor
Merge pull request #606 from Hongarc/update-contributor
Merge pull request #605 from Zabari/patch-1
Resolves #608 -- enforce word boundary
fix: get ls and cd with right way
Merge branch 'master' into fix/command
Merge pull request #610 from Hongarc/fix/command
Disable "git fakeTeamwork" in push level (remote6)
Disable "git branch" and "git checkout" in source nothing level
(remoteAdvanced7)
Merge pull request #612 from PhilipEnchin/fix-source-nothing-level
Merge pull request #611 from PhilipEnchin/fix-push-level
german text corrected
increase readability of german text
Merge pull request #615 from cyper85/master
Change where HEAD points to match objective
Merge pull request #616 from dzampino/typoFix
Resolves #618 -- remove todo
Add Vietnamese language switcher to helperbar.
Add translation of index page.
translate commits.js
Translated 'intro' levels to Spanish 'es_ES'
Translated 'advanced' levels to Spanish 'es_ES'
Writing typos
Translated 'mixed' levels to Spanish 'es_ES'
Translated index.js to Spanish 'es_ES'
Translated 'rampup' levels to Spanish 'es_ES'
Translated 'rebase' levels to Spanish 'es_ES'
es_AR Typos fixed
Merge pull request #619 from flyingbot91/es_AR_translation_typos
Bump mixin-deep from 1.3.1 to 1.3.2
Merge pull request #620 from
pcottle/dependabot/npm_and_yarn/mixin-deep-1.3.2
Translated 'remote' levels to Spanish 'es_ES'
Added es_ES translation to levelBuilder.js
es_ES translation typos
Translated src/js/dialogs to Spanish 'es_ES'
'es_ES' translation typos
Merge branch 'master' into es_ES_translation
Various 'es_AR' translation typos
Update src/levels/remote/clone.js
Merge pull request #623 from flyingbot91/es_AR_translation_typos_v2
Merge pull request #622 from flyingbot91/es_ES_translation
Other version of PR #624 -- map header directly from browser
Merge pull request #625 from pcottle/addLocaleHeader
fix(typo): fix a typo in Chinese
Merge pull request #626 from normal-coder/fixTypo
Update pullArgs.js
Merge pull request #627 from parksjin01/master
complete translate to Vietnamese
Merge https://github.com/pcottle/learnGitBranching
Merge pull request #628 from duongtiendat1990/master
Update detachedHead.js

File Changes

M .gitignore
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-0
(12)
A .gitpod.yml
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-1
(9)
M .travis.yml
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-2
(15)
M Gruntfile.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-3
(44)
D LICENSE
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-4
(9)
A LICENSE.md
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-5
(21)
M README.md
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-6
(86)
M tests/base.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-7
(28)
M tests/git.spec.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-8
(170)
M tests/remote.spec.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-9
(24)
M tests/treeCompare.spec.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-10
(4)
D assets/emoji_table.rtf
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-11
(2523)
A checkgit.sh
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-12
(6)
D iOS/AppDelegate.h
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-13
(16)
D iOS/AppDelegate.m
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-14
(51)
D iOS/Base.lproj/LaunchScreen.xib
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-15
(50)
D iOS/Images.xcassets/AppIcon.appiconset/Contents.json
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-16
(38)
D iOS/Images.xcassets/test.png
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-17
(0)
D iOS/Info.plist
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-18
(42)
D iOS/main.jsbundle
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-19
(5)
D iOS/main.m
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-20
(18)
D lib/underscore-min.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-21
(32)
M package.json
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-22
(40)
M src/js/app/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-23
(55)
M src/js/commands/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-24
(37)
D src/js/constants/AppStyles.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-25
(16)
D src/js/constants/Routes.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-26
(19)
M src/js/dialogs/confirmShowSolution.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-27
(52)
M src/js/dialogs/levelBuilder.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-28
(81)
M src/js/dialogs/nextLevel.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-29
(45)
M src/js/dialogs/sandbox.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-30
(231)
M src/js/git/commands.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-31
(157)
M src/js/git/headless.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-32
(7)
M src/js/git/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-33
(448)
M src/js/graph/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-34
(16)
M src/js/graph/treeCompare.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-35
(57)
M src/js/intl/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-36
(9)
M src/js/intl/strings.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-37
(657)
M src/js/level/builder.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-38
(15)
M src/js/level/disabledMap.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-39
(2)
M src/js/level/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-40
(48)
M src/js/level/parseWaterfall.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-41
(19)
M src/js/mercurial/commands.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-42
(2)
M src/js/models/commandModel.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-43
(31)
M src/js/react_views/CommandHistoryView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-44
(42)
M src/js/react_views/CommandView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-45
(92)
M src/js/react_views/CommandsHelperBarView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-46
(27)
M src/js/react_views/HelperBarView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-47
(24)
M src/js/react_views/IntlHelperBarView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-48
(44)
M src/js/react_views/LevelToolbarView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-49
(44)
M src/js/react_views/MainHelperBarView.jsx
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-50
(25)
M src/js/sandbox/commands.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-51
(26)
M src/js/sandbox/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-52
(16)
M src/js/stores/CommandLineStore.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-53
(4)
M src/js/stores/GlobalStateStore.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-54
(4)
M src/js/stores/LevelStore.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-55
(22)
M src/js/stores/LocaleStore.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-56
(22)
M src/js/util/constants.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-57
(2)
A src/js/util/debounce.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-58
(17)
M src/js/util/errors.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-59
(2)
M src/js/util/eventBaton.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-60
(6)
M src/js/util/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-61
(3)
A src/js/util/throttle.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-62
(13)
M src/js/views/builderViews.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-63
(10)
M src/js/views/commandViews.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-64
(74)
M src/js/views/gitDemonstrationView.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-65
(17)
M src/js/views/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-66
(24)
M src/js/views/levelDropdownView.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-67
(18)
M src/js/views/multiView.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-68
(15)
M src/js/views/rebaseView.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-69
(7)
M src/js/visuals/animation/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-70
(2)
M src/js/visuals/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-71
(91)
M src/js/visuals/tree.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-72
(12)
M src/js/visuals/visBase.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-73
(18)
M src/js/visuals/visBranch.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-74
(23)
M src/js/visuals/visEdge.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-75
(3)
M src/js/visuals/visNode.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-76
(19)
M src/js/visuals/visTag.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-77
(20)
M src/js/visuals/visualization.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-78
(18)
M src/levels/advanced/multipleParents.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-79
(324)
M src/levels/index.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-80
(112)
M src/levels/intro/branching.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-81
(304)
M src/levels/intro/commits.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-82
(190)
M src/levels/intro/merging.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-83
(277)
M src/levels/intro/rebasing.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-84
(255)
M src/levels/mixed/describe.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-85
(253)
M src/levels/mixed/grabbingOneCommit.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-86
(161)
M src/levels/mixed/jugglingCommits.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-87
(169)
M src/levels/mixed/jugglingCommits2.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-88
(1161)
M src/levels/mixed/tags.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-89
(1372)
M src/levels/rampup/cherryPick.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-90
(222)
M src/levels/rampup/detachedHead.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-91
(298)
M src/levels/rampup/interactiveRebase.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-92
(269)
M src/levels/rampup/relativeRefs.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-93
(285)
M src/levels/rampup/relativeRefs2.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-94
(279)
M src/levels/rampup/reversingChanges.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-95
(244)
M src/levels/rebase/manyRebases.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-96
(84)
M src/levels/rebase/selectiveRebase.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-97
(92)
M src/levels/remote/clone.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-98
(235)
M src/levels/remote/fakeTeamwork.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-99
(218)
M src/levels/remote/fetch.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-100
(301)
M src/levels/remote/fetchArgs.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-101
(564)
M src/levels/remote/fetchRebase.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-102
(0)
M src/levels/remote/mergeManyFeatures.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-103
(0)
M src/levels/remote/pull.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-104
(0)
M src/levels/remote/pullArgs.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-105
(0)
M src/levels/remote/push.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-106
(0)
M src/levels/remote/pushArgs.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-107
(0)
M src/levels/remote/pushArgs2.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-108
(0)
M src/levels/remote/pushManyFeatures.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-109
(0)
M src/levels/remote/remoteBranches.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-110
(0)
M src/levels/remote/sourceNothing.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-111
(0)
M src/levels/remote/tracking.js
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-112
(0)
A src/style/favicon.ico
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-113
(0)
M src/style/main.css
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-114
(0)
M src/style/rainbows.css
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-115
(0)
M src/template.index.html
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-116
(0)
D todo.txt
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-117
(0)
A yarn.lock
https://github.com/pcottle/learnGitBranching/pull/632/files#diff-118
(0)

Patch Links:

https://github.com/pcottle/learnGitBranching/pull/632.patch
https://github.com/pcottle/learnGitBranching/pull/632.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pcottle/learnGitBranching/pull/632?email_source=notifications&email_token=AAIVDH3T3JBNOWXT5Q6CN33RA7Y5RA5CNFSM4KPC6REKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IKRU2BA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIVDHZKGGF25XYZHELA36LRA7Y5RANCNFSM4KPC6REA
.

--
Peter M Cottle
UC Berkeley 2012
UC San Diego 2011

It is my first commit in not my own project. I just wanted to help fix bug,
but something went wrong :)


Special symbols not allowed? colons, trailing whitespaces, starting quotation marks...

Hi BADR team!
we're delighted with this tool, it has boosted our translation speed by a long shot, but we've run into a really weird issue: it would seem the translations are not escaped when stored in the DB.
What I mean is, I can add News but not News:, nor "News" as a translation. Same thing happens with leading and trailing whitespaces, leading quotation marks...
This forces us to modify these entries manually after exporting them to YAML, which beats the purpose of the TC. Here you are a sequence of screenshots for improved clarity:
What we want to save:

What is saved instead:

What is actually displayed:

Are we missing something? Is there something we're doing terribly wrong? If that's not the case, is it a bug, a missing feature?
Thank you again for this great gem, keep up the good work!
Sergio

@helsayed Check this.

In this line
params[:value].strip # => "Board:"
but
YAML.load(params[:value].strip) # => {"Board"=>nil}
so it would appear that YAML.load is the culprit, but why is this happening?
Thanks!
Sergio


Sinch User registration failing in sinch-android-rtc-3.17.6

Hi,
I'm trying to explore SInch App to App calling using sinch-android-rtc-3.17.6 SDK push sample and I'm always getting a User registration failed message. while trying to register user using Usercontroll API from sdk sample.
Http request: POST  https://clientapi.sinch.com/V2/Instance body: {"ApplicationKey":"#######","Capabilities":["ice-restart.1","p2p","push","push.2","push.3","push.4","srtp.1","voip.1"],"DeviceId":"45dd-475f-95be-9c4ca8d101ff","DeviceType":2,"PushData":"","SdkVersion":"3.17.6","Seed":"1624126802","Signature":"4wBJcJE+OEQSVdUL/abLr+xRcXE=","UserId":"*******"}
2021-06-19 23:50:02.553 26380-28225/com.ondhaspot.app D/HttpClient: Scheduling request: {id='9fc45137-2c59-4dcc-8fa9-559b480e9181', url='https://clientapi.sinch.com/V2/Instance', method='POST', headers={Accept=text/json, Content-Type=application/json; charset=utf-8}}
Always getting response as
{
"Message": "internal Server Error"
}
Can someone let me know anything I'm missing here?

Did you find any solution?


Hover state on the "resend email confirmation" button is white

Hard to see from this screenshot, but there is a second button to the left that is invisible on hover

This has been fixed:


Add related images check

This check verifies that all images referred to in the CSV are actually
in the relatedImages section of the CSV.
Currently, it just logs a warning, but still passes. It will only fail
if there is an error.
Fixes #740
Signed-off-by: Brad P. Crochet<EMAIL_ADDRESS>

Coverage increased (+0.2%) to 84.14% when pulling 4bd5cf37b5164a85bd86779dcef42a4e5d60c390 on bcrochet:related-images into 12e69d68b3b1cc98bc34d8438b628bfdf4441e9f on redhat-openshift-ecosystem:main.


Change App bottom tab bar to the solid theme color

https://ionicframework.com/docs/api/tabs

@NatalieWilson19 would this fit with the redesign? #598


main.py file generates different sized .txt files

I have run this file successfully. For videos in a folder, it sometimes generates files with dict format and sometimes tuple. What is the reason for it?  I tested this issue on Arrest030_x264.mp4 video.

Earlier I got 14.3 MB file with tuple format and later got 3.3 MB file with dict format.
This tuple format (14.3 MB file) had only 213 vectors(each with 512 dim) while dict format (3.3 MB file) had 540 vectors(each with dim 512) which was as expected (= no. of frames / 16)
I got to know about the format by writing this code in ipython2:-
a = open('Arrest030_x264.txt', 'r').read()  		a = a[1:-1]  		a = ast.literal_eval(a)                      print type(a)
Also, by running this code on same file again gives different values. Is this randomness due to ffmpeg?
Also, in this main.py line18, what's the significance of 112 in opt.sample_size = 112 ?

The following change need to be done:-
In main.py file, you should put the outputs = [] line inside the for loop which goes for all the input_files.
Earlier if this not done, was causing to store the previous video's features along with the current ones and thus the succeeding generated files had increasing file size. Thus, one need to empty the outputs variable.
Thank You


Error: Cannot find module "." (in production build)

Hello,
I'm having an issue trying to make this module work in production mode.
Let's take by example this simple configuration:
FileUploader = ElectronRemote.requireTaskPool(require.resolve('../workers/uploadWorker'));
...
export class UploadManager {
    ...
    private async doUpload(file) {
        await FileUploader.doUpload(file);
    }
}

with uploadWorker.js being:
async function doUpload(file) {
    console.warn('uploading ' + file.name);
    // async code here
}

module.exports = { doUpload };

This configuration works like a charm when trying it in dev mode; while it seems to be failing in production build.
In particular, I get this exception:
Error: Cannot find module "."
    at webpackMissingModule (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3879:84)
    at /Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3879:163
    at Generator.next (<anonymous>)
    at step (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3991:191)
    at /Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3991:437
    at /Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3991:99
    at rendererRequireDirect (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:3926:17)
    at getOrCreateWindow (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:4019:49)
    at DeferSubscriber._Observable.Observable.defer [as factory] (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:4031:16)
    at DeferSubscriber._callFactory (/Users/giovanni/Documents/my-electron-project/release/mac/Secret app name.app/Contents/Resources/app.asar/dist/main.js:24407:27)

At first I thought it was something caused by the async function, but even using a built in helper from this same library (FileUploader = ElectronRemote.requireTaskPool(require.resolve('electron-remote/remote-ajax'));) I get the same error.
A few already explored caveats:

asar packaging is turned on; turning it off does not help
The exception is thrown in the moment the code is called (FileUploader.doUpload(file);), not when the module is imported
The built main.js seems to correctly reference the module containing the remote code FileUploader = ElectronRemote.requireTaskPool(/*require.resolve*/(110));, where module 110 is defined and well-shaped:

...
function doUpload(file) {
    return __awaiter(this, void 0, void 0, function () {
        return __generator(this, function (_a) {
            console.warn('uploading ' + file.name);
            return [2 /*return*/];
        });
    });
}
module.exports = { doUpload: doUpload };

Any pointer on other things I should check?

1

We found that our problem was basically caused by the code at this line: https://github.com/electron-userland/electron-remote/blob/master/src/renderer-require.js#L43
In particular, in the development environment (using webpack-dev-server) the require was correctly managed as path, while in the production build the resolve tried to reference the module using the webpack-assigned ID, which was then not available to be used in renderer-require-preload.js.
We finally managed to find our way around it by loading the module in the appropriate way (in our case, using a path) before passing it to ElectronRemote.requireTaskPool, and then removing the incriminated module.resolve call inside rendererRequireDirect.
Do you see other possible solutions to this issue? I'm quite curious on how other people make it work in production environments or to find out if it's just an issue of our configuration. 😉
More generally, I think this could be helpful to more people, as one could decide its own module loading method (using a relative/absolute path or require.resolve). I will shortly create a PR for this.

Yeah, this probably doesn't work with Webpack, you probably need to use regular-ass require


VSHA-503 modify tests for use on vshasta

Signed-off-by: Jacob Salmela<EMAIL_ADDRESS>Summary and Scope
Add vshasta support to some existing tests by adding a conditional.
Adds a is_vshasta_node function.
Issues and Related PRs

Partially resolves VSHA-503
Works with https://github.com/Cray-HPE/livecd-gcp-infrastructure/pull/174

Testing
Tested on:

#redbull
Virtual Shasta

Test description:
Executed the tests on a vshasta environment and saw the tests were skipped.
The function works on a vshasta pit node:
pit:~ # is_vshasta_node ; echo $?
+ [[ -f /etc/google_system ]]
+ return 0
+ echo 0
0
pit:~ #

a metal image booted to vshasta:
ncn-m002:~ # is_vshasta_node ; echo $?
+ [[ -f /etc/google_system ]]
+ grep --color=auto Google
+ lsblk --noheadings -o vendor
+ return 0
+ echo 0
0

and a metal node:
redbull-ncn-m001-pit:~ # is_vshasta_node ; echo $?
+ [[ -f /etc/google_system ]]
+ grep Google
+ lsblk --noheadings -o vendor
+ return 1
+ echo 1
1

Risks and Mitigations
Low
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

In addition to creating the is_vshasta function in the common function library, it seems like you'd also want to add code to the add_local_vars function in that library to handle any new variables you want to have set.

Pulled it in

Pulled it in
Perfect. I've approved, but looks like you may need to squash the commits now because of the merge commit that snuck in there.

Removed the merge commit.  I think we're good now

Removed the merge commit. I think we're good now

Cool. I think you need someone on PET team to approve this before it can merge. Or anyway, I don't have authority to do it without that. Maybe go hit up #casm-pet channel and beg. :)

Looks like I cannot merge it yet either


Update installation page to include istio-demo-auth story

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: wattli
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
Assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Nvm. Yeah I remember we infer the verify San based on mesh config flag
value .
On Tue, May 29, 2018, 11:23 AM Tao Li<EMAIL_ADDRESS>wrote:

@wattli commented on this pull request.
In content/docs/setup/kubernetes/quick-start.md
https://github.com/istio/istio.github.io/pull/1374#discussion_r191525832
:

@@ -268,11 +268,19 @@ customize Istio to your needs.

 _**OR**_

b)  Render Kubernetes manifest with Helm and deploy with kubectl.

b) Install Istio and enable mutual TLS authenticaiton globally between sidecars. This option is only recommended for new clusters, and all applications are installed with sidecars. Otherwise, we recommend to choose option a) and incrementally adopt Istio mutual TLS later on.

Not sure if I understand you correctly. If mTLS is turned on here
globally, authn will happen.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/1374#discussion_r191525832,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABlbhyji0YDdsH_yJfYF7T3iS7ZRqv17ks5t3ZIogaJpZM4UR7Ts
.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: incfly, wattli
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
Assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@geeknoid , could you help to approve?

New changes are detected. LGTM label has been removed.

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: incfly, myidpt, wattli
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
Assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, incfly, myidpt, wattli
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Could not open file /opt/dvtb/models/caffenet-yos/caffenet-yos-weights

Really eager to run your tool on my model/data.
I installed with Docker using the link you gave: https://github.com/fishcorn/dvtb-container
When I launch the container i get this prompt: developer@d6c8b1d52a74:/opt/dvtb$
So then I supposed I had to run your tool with: ./run_toolbox.py
But that gives me this error: RuntimeError: Could not open file /opt/dvtb/models/caffenet-yos/caffenet-yos-weights
Complete error message is:
got module <module 'caffevis.app' from '/opt/dvtb/caffevis/app.py'>
got app <class 'caffevis.app.CaffeVisApp'>
Got settings <module 'settings' from '/opt/dvtb/settings.py'>
/opt/caffe/python/caffe/pycaffe.py:13: RuntimeWarning: to-Python converter for boost::shared_ptr<caffe::Net<float> > already registered; second conversion method ignored.
  from ._caffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, \
/opt/caffe/python/caffe/pycaffe.py:13: RuntimeWarning: to-Python converter for boost::shared_ptr<caffe::Blob<float> > already registered; second conversion method ignored.
  from ._caffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, \
/opt/caffe/python/caffe/pycaffe.py:13: RuntimeWarning: to-Python converter for boost::shared_ptr<caffe::Solver<float> > already registered; second conversion method ignored.
  from ._caffe import Net, SGDSolver, NesterovSolver, AdaGradSolver, \
h
CaffeVisApp mode (in main thread):     GPU
Traceback (most recent call last):
  File "./run_toolbox.py", line 33, in <module>
    main()
  File "./run_toolbox.py", line 23, in main
    lv = LiveVis(settings)
  File "/opt/dvtb/live_vis.py", line 62, in __init__
    app = app_class(settings, self.bindings)
  File "/opt/dvtb/caffevis/app.py", line 53, in __init__
    raw_scale = self._range_scale,
  File "/opt/caffe/python/caffe/classifier.py", line 26, in __init__
    caffe.Net.__init__(self, model_file, pretrained_file, caffe.TEST)
RuntimeError: Could not open file /opt/dvtb/models/caffenet-yos/caffenet-yos-weights

I've managed to dowload the .gz file and extract them, so i could go a bit further, the tool runs for a while then ends up with:
CaffeVisApp mode (in CaffeProcThread): GPU
JPGVisLoadingThread.run called
F0818 09:45:28.533731    28 pooling_layer.cu:212] Check failed: error == cudaSuccess (8 vs. 0)  invalid device function
*** Check failure stack trace: ***

I run it in a docker container this way:
sudo NV_GPU=0 nvidia-docker run -ti \
--name dvtb \
-e DISPLAY \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-v /path/to/a/workspace:/home/developer/work \
fishcorn/dvtb-container
Then at the prompt : ./run_toolbox.py

I managed to bypass the message above by setting this line to False in opt/dvtb/setting.py
caffevis_mode_gpu = locals().get('caffevis_mode_gpu', False)
now i get to the user interface and it seems to work fine.


Feat: Support Versioned releases.

The following does the following.

Rolls back Formula/wave-cli-jar.rb & Formula/wave-cli.rb to the last stable v4 release.
Adds a v4 formula
Adds a RC formula

Users will now be able to run any of the following commands to install an appropriate version of the wave-cli note there is no official v1.5 tap created at the moment.
brew install seqeralabs/tap/wave-cli
brew install<EMAIL_ADDRESS>brew install seqeralabs/tap/wave-cli@rc

Style & Linting fixes.
There were a number of legacy brew / ruby syntax issues which have also been addressed in this PR.
The output of the audit was as follows.
brew audit --strict wave-cli-jar
seqeralabs/tap/wave-cli-jar
  * line 6, col 99: Use the new Ruby 1.9 hash syntax.
  * line 17, col 5: Use `File.write`.
  * line 17, col 15: Use `bin/"wave-cli-jar"` instead of `"#{bin}/wave-cli-jar"`
  * Stable: version 1.5.0-rc.3 is redundant with version scanned from URL

The issues were auto-fixed using the following command in the root of the formula repo.
brew style --fix .

We should not include rc


maintaining

Your PR has made me feel that I'm not maintaining this project, and this is kind of true. There are things I have planned for it. like: (redesigning the UI, migrating to flutter 2.0). Currently I'm focusing on my other projects. I'll get back to StarBook near December. Therefore I'm closing it.


feat: support clone to sub dir for repo

Prow and its library are quite friendly to CI infrastructure, and we have been using them extensively.
This PR aims to enhance the customization capability of its code workspace, similar to Jenkins's checkout to sub-directory feature. This way, within the same workspace, there will be opportunities to accommodate more repositories to address complex scenarios.

/test all
/hold

This PR aims to enhance the customization capability of its code workspace, similar to Jenkins's checkout to sub-directory feature. This way, within the same workspace, there will be opportunities to accommodate more repositories to address complex scenarios.

👋 can you describe what kind of scenarios are you interested in? The client library is able to checkout multiple repositories (via multiple ClientForWithRepoOpts calls), just not under the same temporary directory (but the location under the temporary directory is supposed to be an irrelevant internal detail. I'm not sure I see the benefits of having them in the same directory.

Hi @petr-muller, thanks for your feedback.
In this project, we utilize prow git library to prepare a clean code workspace for PR in order to do all kinds of linters check.
The need for this capability arises from our utilization of replace in go.mod to reference certain private repositories, for example:
replace github.com/qiniu/log.v1 => ../kodo/src/github.com/qiniu/log.v1
replace github.com/qiniu/errors => ../kodo/src/github.com/qiniu/errors

In this context, kodo represents another private repository. Consequently, we need organize these distinct repositories and position them at the same directory level for compiling.
Another, our project has config like this. so with this functionality, I can address this scenario like the following:
- |
  cd .. && git clone xxx && cd -
  golangci-lint xxx

It will be very straightforward.

but the location under the temporary directory is supposed to be an irrelevant internal detail

Seems that this is the actual code directory, the real workspace. i am thinking It would be more elegant with such capability.

/test all
/hold cancel

/ok-to-test

After deeper reflection and practice, I am considering the possibility of directly supporting "Copy to custom directory," which might be more elegant. This approach should be able to accommodate a wider range of use cases.
Please help review @petr-muller @krzyzacy

I'm still catching up on the latest Prow changes, previously we leverage path_alias for repo dest locations Prow jobs, but seems you are only referencing the Prow git client instead of the actual Prow jobs?

Yes, The background context is that I am building a unified linters runner to standardize engineering practices across multiple orgs and numerous repositories. Compared to configuring Prow jobs for each repository, a centralized, low-configuration, and observable service would be more convenient for me.
Of course, I still choose to use some of Prow's foundational packages, as they are indeed very useful.

Where do we set this option? From your own controllers? I would suggest open an issue with the descriptions or your use case, and then associate your PR to the issue :-)
Could you also add a unit test to assert the behavior?


markdown cant render when i use json api

hi guys
i use json api on markdown but pkg cant render markdown and return this error:
ERROR TypeError: Cannot read property 'replace' of null
Please report this to https://github.com/chjj/marked.
    at Lexer.webpackJsonp.../../../../marked/lib/marked.js.Lexer.lex (marked.js:138)
    at Function.webpackJsonp.../../../../marked/lib/marked.js.Lexer.lex (marked.js:129)
    at marked (marked.js:1219)
    at MarkdownService.webpackJsonp.../../../../angular2-markdown/markdown/markdown.service.js.MarkdownService.compile (markdown.service.js:47)
    at MarkdownComponent.webpackJsonp.../../../../angular2-markdown/markdown/markdown.component.js.MarkdownComponent.onDataChange (markdown.component.js:32)
    at MarkdownComponent.set [as data] (markdown.component.js:25)
    at updateProp (core.es5.js:11122)
    at checkAndUpdateDirectiveInline (core.es5.js:10814)
    at checkAndUpdateNodeInline (core.es5.js:12357)
    at checkAndUpdateNode (core.es5.js:12296)

article component html
<markdown  [data]="article?.content">

</markdown>

app component ts
  ngOnInit() {

    let id =this.route.snapshot.paramMap.get('id');
    this.tJs.getArticle(id).then(data => {
    this.article = data;

  }, (err) => {

    console.log('errorrrr',err);
    alert(err.status)

    });

  }

also i tested without json api and works fine !

ERROR TypeError: Cannot read property 'replace' of null
Means that the data isn't available yet. Maybe subscribe to it and then use markdown.

@muffinrecon is right.
Just appending a *ngIf will solve it. This will make the markdown component load only when your data is already loaded.
<markdown  [data]="article?.content" *ngIf="article?.content">
</markdown>


Updates javascript dependencies in efforts to kill security warning

node-growl is flagged, and indirectly required by some test infra.
To squash that implied a rediculous amount of dependency updates :P

double-checked minification. looks a bit better than before due to things inherited by moving up a bit:
1784	./zipkin-ui/target/zipkin-ui-2.10.5-SNAPSHOT.jar
2112	/Users/acole/.m2/repository/io/zipkin/java/zipkin-ui/2.10.4-SNAPSHOT/zipkin-ui-2.10.4-SNAPSHOT.jar


Ubuntu/Debian compatibility ?

Before I start messing with my system installing all dependencies and such, is the script compatible with both Ubuntu/Debian ?
I have been looking for a decent management script and google lead me here <3

Hi - should be completely fine - it's pure python -  ( python versions 3.9 or newer)  - so as long your python satisfies that then it should be completely fine.
The dependencies are listed in README.   You can test it by cloning the repo and running from there. Easy way to try it out.
Aside from some convenience python modules, it uses wireguard tools and nftables - both are needed to run vpn anyway  (or iptables if thats your thing) with or without wg-tool.
Feel free to tag me if I can help.

Thank you for the fast reply.
I installed the dependencies using pip, now I am confused how to set things up... From the readme, I am not sure where to run this (already cloned the project, it has no dist folder):
    rm -f dist/*
    poetry build --format wheel
    ./scripts/do-install /

testing:
You can run out of the cloned repo for testing by running wg-tool.py  - try ./wg-tool.py -h
build and installing:

poetry build creates a python wheel (which holds all the code) and saves it in ./dist/xxx.whl
the install script would then install to destination directory prefix (/ above) - the code would then be installed in something like  /usr/lib/python3.10/site-packages/wg_tool .
a sym link would also be installed  in /usr/bin/wg-tool pointing to the installed module wg-tool.py.

once its installed and available in /usr/bin then it would be in your path.
let me know how it goes.

to keep the repo clean probably better to create a test directory and run in there.
mkdir ../test
cd ../test
ln -s ../wg_tool/wg-tool.py wg-tool
./wg-tool -h

be nice if someone made a .deb package for wg_tool

A docker image would be better given all the dependencies I think...

good idea on docker  ... i forgot to answer your question fully- you run poetry build in the top level of repo - and ditto for installer script which takes one arg which is the destination prefix. Those to things (build/install) are normally done by the package builder tool.
packages take care of the dependencies - so installing a package makes it simple too.

I broke my system as I feared... I only had python 3.8 and meant to add 3.10... There was some conflict which was suggested to run apt purge python3 (dumb me)...
I've been trying to fix it for the last 30 minutes in vain... I will try again tomorrow as I am useless after midnight... A docker package is certainly the way to go xD

geez so sorry - thats really annoying - :(

hope you can things back to normal

the only need for 3.9 is using match() instead of if else ... there are a few places but it would be possible to make a version without match() statements I would think.

again - so sorry

Really, no worries... It probably will be less hassle installing the system from scratch (it's a remote server), it will just need some extra configs (FW, SSH, some other custom packages, ...)...
I just hope it is worth it :P as I am still in the "testing phase" xD

remote machine ... ug .. thats a lot of work.

would be doable to make copies of the 2 files using match() and change them to use if else - those quite likely would work okay with python 3.8.

I added 2 files in lib38 which use if/else instead of match(). These should work on python 3.8. Simply copy them over the regular ones. Hope this helps.

Some feedback:

I started from a fresh system Ubuntu 22.04 with python 3 preinstalled Python 3.10.6
sudo apt install wireguard will install tools as well
pip install tomli_w netaddr qrcode tomli build installer wheel poetry => adding a requirements file would've been useful maybe ?
export PATH="/home/ubuntu/.local/bin:$PATH" make sure installed packages are in path => warning will show correct path to add if not
git clone https://github.com/gene-git/wg_tool.git
cd wg_tool
poetry build --format wheel
./scripts/do-install /
It fails if not ran using sudo... further in the script it spits WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Not sure what is the best path here...

$ ./scripts/do-install /
rsync: [Receiver] mkdir "//usr/share/wg_tool" failed: Permission denied (13)
rsync error: error in file IO (code 11) at main.c(787) [Receiver=3.2.3]
rsync: [Receiver] mkdir "///usr/share/licenses/wg_tool/LICENSE" failed: Permission denied (13)
rsync error: error in file IO (code 11) at main.c(787) [Receiver=3.2.3]
chmod: changing permissions of '///etc/wireguard/': Operation not permitted
rsync: [Receiver] ERROR: cannot stat destination "////etc/wireguard//scripts/": Permission denied (13)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(768) [Receiver=3.2.3]

Got an error as python not found, so updated manually to python3
Further as well I got pip no such option: --root-user-action which I have removed to finish the install
Then the last step:

$ cd src/wg_tool/
$ mkdir ../test
$ cd ../test
$ ln -s ../wg_tool/wg-tool.py wg-tool
$ ./wg-tool -h
-bash: ./wg-tool: /usr/bin/python: bad interpreter: No such file or directory
$ vim ../wg_tool/wg-tool.py    # update to python3
$ ./wg-tool -h
usage: wg-tool [-h] [-wkd WORK_DIR] [-i] [-add] [-mod] [-dnsrch] [-dnslin] [-int] [-uuk] [-usk] [-all] [-act] [-inact] [-imp IMPORT_USER] [-keep KEEP_HIST] [-keep_wg KEEP_HIST_WG] [-l] [-rpt SHOW_RPT]
               [-rrpt] [-det] [-sop] [-v]
               [users ...]

WgTool : Manage wireguard Server & User/Profiles

positional arguments:
  users                 user_1[:prof1,prof2,...] user_2[:prof_1,prof_2]

options:
  -h, --help            show this help message and exit
  -wkd WORK_DIR, --work_dir WORK_DIR
                        Set the working dir. If unset, use dir path : /etc/wireguard/wg-tool:./
  -i, --init            Initialize: create server config - please edit. Can also set --work_dir
  -add, --add_users     Add user(s) and/or user profiles user:prof1,prof2,...
  -mod, --mod_users     Modify user(s) profiles (with -dnsrch, -dnslin)
  -dnsrch, --dns_search
                        Add/Mod user with dns search list from server config DNS_SEARCH
  -dnslin, --dns_linux  Linux. profile resolv.conf managed using PostUp/Down scripts
  -int, --int_serv      With --add_users uses internal wireguard server
  -uuk, --upd_user_keys
                        Update existing user(s) keys.
  -usk, --upd_serv_keys
                        Update server keys - affects all users
  -all, --all_users     Some opts (e.g. upd_user_keys) may apply to all users/profiles
  -act, --active        Mark users/profiles user[:profile,...] active
  -inact, --inactive    Mark users/profiles user[:profile,...] inactive
  -imp IMPORT_USER, --import_user IMPORT_USER
                        Import a user profile : --imp user.conf user_name:profile_name
  -keep KEEP_HIST, --keep_hist KEEP_HIST
                        Keep config history
  -keep_wg KEEP_HIST_WG, --keep_hist_wg KEEP_HIST_WG
                        Keep wg-config history
  -l, --list_users      List users/profiles
  -rpt SHOW_RPT, --show_rpt SHOW_RPT
                        Output of "wg show" (file, "stdin") -> connected users report
  -rrpt, --run_show_rpt
                        Run "wg show" -> connected users report (see also -rpt)
  -det, --details       Adds details to rpt and list output
  -sop, --save_opts     Save defaults for keep_hist/keep_hist_wg
  -v, --verb            Be more verbose

Finally, I went through the readme and updated the needed values. Then tried to add a test user and got the below error:

$ ./wg-tool --add_user enissay:pixel
Normal Mode: using existing setup
Adding enissay:pixel
    config:   updating - server
    config:   updating - enissay
 wg-config:   updating - enissay:pixel
Traceback (most recent call last):
  File "/home/ubuntu/.local/lib/python3.10/site-packages/qrcode/image/pil.py", line 5, in <module>
    from PIL import Image, ImageDraw
ModuleNotFoundError: No module named 'PIL'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ubuntu/wg_tool/src/test/./wg-tool", line 26, in <module>
    main()
  File "/home/ubuntu/wg_tool/src/test/./wg-tool", line 22, in main
    wgtool.doit()
  File "/home/ubuntu/wg_tool/src/wg_tool/lib/class_wg.py", line 385, in doit
    write_wg_users(self)
  File "/home/ubuntu/wg_tool/src/wg_tool/lib/wg_users.py", line 131, in write_wg_users
    okay = text_to_qr_file(prof_str, actual_file,)
  File "/home/ubuntu/wg_tool/src/wg_tool/lib/utils.py", line 23, in text_to_qr_file
    img = qr.make_image(fill_color="black", back_color="white")
  File "/home/ubuntu/.local/lib/python3.10/site-packages/qrcode/main.py", line 296, in make_image
    from qrcode.image.pil import PilImage
  File "/home/ubuntu/.local/lib/python3.10/site-packages/qrcode/image/pil.py", line 7, in <module>
    import Image
ModuleNotFoundError: No module named 'Image'

Several things clearly including needing root to install in system area.
When the python qrcode module was installed, it should have installed its own dependencies - including pillow - which is misssing - can you please install pillow and maybe let whoever packaged qrcode that it missed the pillow dep.

I did assume that python points to python3 since python2 is long ago dead/deprecated.

The install script should work as non-root if you do something like:
mkdir  ~/tools
./scripts/install ~/tools
then it will install everything under ~/tools and you should be able to run from there
(other issues aside for a moment)

my todo

change python to python3
remove pip option from install script
add requirements  file

 can you please install pillow and maybe let whoever packaged qrcode that it missed the pillow dep.
Pillow solved it.
Now getting his:
$ sudo wg-quick up wg-configs/server/wg0.conf
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add XXXX.1/24 dev wg0
[#] ip -6 address add YYYY::1/64 dev wg0
[#] ip link set mtu 8920 up dev wg0
[#] /usr/bin/nft -f /etc/wireguard/scripts/postup.nft
/usr/bin/wg-quick: line 295: /usr/bin/nft: No such file or directory
[#] ip link delete dev wg0

I will have to install nft and try again, but I am having internet issues... Will try again tomorrow...

nft is nftables runtime -

$ whereis nft
nft: /usr/sbin/nft /usr/share/man/man8/nft.8.gz

Ah gotcha - - we need to change the script  to just 'nft' (many distros have /sbin sym link to bin) -

for now can you simply edit the wg0.conf and change /usr/bin/nft to /usr/sbin/nft
I can change it to just 'nft' - that should work everywhere

Yes, that's what I did.
Sadly I have no internet... I will look further tomorrow... I am of no use past 3am xD
$ sudo wg show
interface: wg0
  public key: E25nseQ6GEg2oyyyyyyyyyyywSKz8HHPJEx4=
  private key: (hidden)
  listening port: 60xxx

peer: JwOgjMki5c4ljeq6vxxxxxxxxxxxxxxxxxxxIulUeZGhM=
  preshared key: (hidden)
  endpoint: XXXX.154:33338
  allowed ips: YYYY.3/32
  latest handshake: 12 seconds ago
  transfer: 2.54 KiB received, 124 B sent

also please try instead of wg show:
sudo wg-tool -rrpt

If no traffic then (assuming vpn server itself has internet / local access) - the nftables config is likely not right for your setup

I will push the python3 change and the pip option fix to gh repo -

Still on my todo list - create requirements file.
Please Let me know if you got the postup script working.  Thanks!

requirements.txt added in commit 7a548d2

Please Let me know if you got the postup script working. Thanks!

Sadly not. Sorry for my disappearance but I am on holidays (since over a week actually)... I'll be back home later this week and will dig deeper to find a fix

Sorry to hear that - happy to help where I can. I assume vpn server has internet access so when the vpn clients get nat'ed their traffic should get to internet as well (and would appear to come from vpn server of course). Have wonderful rest of holidays and very merry christmas !

May be worth double checking that the  network settings look right in your postup nftables script.

No worries, last time I checked, server had internet and handshake was successful, yet no internet on the client...
I admit some of the options I just winged (I was not sure)... When back, I will try again from scratch which will allow me also to try all the changes you generously implemented... I will get back with questions to set things right...

ok that sounds good  - have fun day :)

(it really does sound like the postup script is worth looking over)

one more thought occurred to me - please make sure ip forwarding is turned on
sysctl -w net.ipv4.ip_forward=1
and add line to /etc/sysctl.d/systctl.conf (or whatever name you prefer for file) :
net.ipv4.ip_forward = 1

Hi any updates from your side?


Create tr.js

Hi @secalsecal!
Thank you for your interest but there's unfortunately only an empty file in your pull request. Could you please check it if you actually meant to submit a translation?

Hi again @secalsecal!
We've just received a Turkish translation, so you may use. If you wish to modify it feel free to do it: https://github.com/punarinta/xroom.app-translations/blob/master/tr.js


Complete implementation of TS stream generator

For our integration tests, we have a stream generator that generates DASH-style streams of Mp4 files. With the recent integration test for CEA-708 captions, a stream generator was created for HLS-style streams of TS files, but the implementation is very stripped-down. It makes a "stream" with a single segment.
A more complete implementation would be useful, as it would allow for the creation of new integration tests for TS content.

Resolved with https://github.com/shaka-project/shaka-player/commit/f904583d0653c6b651eaf20514e8954f8a88b53d


config: extended warnings on v2 API usage.

config: extended warnings on v2 API usage.
The earlier PR #10964 added in validation that we're not using v2 xDS
transport, but we didn't have any warning on v2 bootstraps, v2
extension configs inside a v3 config and also for v2 resource types.
This PR adds support for these validations by warning and incrementing
the deprecated feature use stat. The following notifications are added:

Rate limited warning log
Trace-level log
The runtime.deprecated_features is bumped, but only after server
initialization, so this doesn't apply to bootstrap. This is consistent
with how other deprecated features are treated today.

Risk level: Medium (it's possible that this will cause monitoring to
alert, the boosting logic is also quite complex).
Testing: Unit tests and server bootstrap tests added.
Fixes #10815
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

Note that this depends on #13223 merging first.

LMK when this is ready for review.
/wait

@mattklein123 ready for review.

Sorry needs one more main merge.
/wait

Needs main marge and looks like tidy is still failing.
/wait

Still needs main merge.
/wait


Jumpstart ArcBox - Overview

I'm trying to deploy the Azure ArcBox template from here : https://azurearcjumpstart.io/azure_jumpstart_arcbox/
But it is always failing at the point of implementing custom script as VM extension to the 2 Linux machines.
I tried to deploy it to North Europe region , then to East US region >> but same errors occured.
I'm afraid the error messages are not descriptive enough to spot the root cause.

Screenshots attached for more info.

Hi @ekramyelnaggar, I'm able to reproduce this issue when the Service Principal is not assigned as a contributor on the target subscription. Please make sure you're following the prerequisites which can be found here:
https://azurearcjumpstart.io/azure_jumpstart_arcbox/#prerequisites
Verify that the proper IAM role is assigned, and let me know the results. Happy to assist further if your issue continues after verifying the permissions. Thanks!

Due to the release of ArcBox 2.0 I will go ahead and close this for now. Please comment if further assistance is required.


Custom Template Documentation

When you get a chance, having an entry in the Wiki for how to add your own custom themes would be awesome.

Documentation added with some basic examples, more on the way.
https://github.com/blogifierdotnet/Blogifier/blob/master/docs/CustomThemes.md


Loading large numbers

Hi.
When i try to load user id which is a large integer cookie.load will drop the last 4 digits of the id.
Expected value:  "108858650188719526842"
Cookie.load output:<PHONE_NUMBER>88719520000
Any ideas how to fix this ?

I just had to set the do not parse flag to true -> Cookie.load("cookie name", true) .


Release Google.Cloud.Bigtable.V2 version 2.6.0

Changes in this release:
New features

Add WarmAndPing request for channel priming (commit 263af4c)
Add explicit routing header annotations for bigtable/v2 (commit 53d712e)

Created release for Google.Cloud.Bigtable.V2-2.6.0


Enhancement/Alignment for import data format and export data format

Currently, the annotated file exported from doccano cannot be imported back into doccano for further validation or annotation because of a misalignment in the import and export formats described here (https://github.com/chakki-works/doccano/issues/113).
This PR addresses this by adding a new export option that allows the users to export the annotated file with text labels that allows for this to be re-imported into doccano. The feature preview is shown below:

The original export functionality is maintained as it contains user details for each annotation that is used in inter-annotator analyses.

@Hironsan , @c-w :I'd really appreciate feedback on this PR. If I've missed something in the submitting process, please do let me know.
PS: I'm new to the project and would love to contribute. (@c-w: Thanks for introducing me to this project!)

Messed up some git history. See https://github.com/chakki-works/doccano/pull/217 for the updated PR.