Show what the different colour in the calandar mean

Some color blob or something

How?: Set the colour of each event passed to FullCalendar with the backgroundColor attribute. See more here: https://fullcalendar.io/docs/event-object


dispose of subscription when component is unmounting

gets pretty messy for me, where the profiler shows something like 2-3MB more memory usage when not disposing of these streams.
i guess RxJS cleans these up by using a ref counter or something so it doesn't just leak? still seems like disposing would be a nice thing to do.

this looks good. I will merge it


View entity frames from the GUI

🎉 New feature
Needs https://github.com/ignitionrobotics/ign-rendering/pull/486
Summary

View entity frames from the context menu. This is similar to Gazebo classic's functionality.
This is an alternative to https://github.com/ignitionrobotics/ign-gui/pull/182
Test it

Right-click an entity
View
Frames

TODO

[ ] View frames for entities other than links
[ ] Scale frames to reasonable sizes w.r.t. their parents

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

I wasn't able to turn off frame visualization.

Fixed, it needs https://github.com/ignitionrobotics/ign-rendering/pull/486

Would it be possible to show a frame name when the mouse hovers over the axis?

I made it always show the name, but it only works with Ogre 1. Do you think that's enough for a 1st iteration?


TDS/SC ratio output

Please add this enhancement when you get a chance.
Thanks.
tds_sc_ratio385011108225401.txt

Putting me to work with the issues!
I have a graphical way of evaluating TDS/SC ratios in the sum vs sc plot. I can add a tabular output of that data as well. I think what I would do is add it to the automated chemical checks so that it flags a new min/max in Anions or cations/SC or a > 99 percentile and < 1 percentile, like it does for the individual result checks.I like breaking out the TDS into sum of cations and sum of anions / SC because it gives you a little more info on group of analytes might be off.
I am out in the field all this week and next but I will get to these when I return. #99 #98 #97


Add is_building to sc2::Unit

Extend sc2::Unit class with boolean property named is_building. The property should be calculated at creation of a new sc2::Unit object e.g. via a special unit filter isBuilding.

Done.


Reword

Reworded because it sounded like ALM Toolkit is the only options - nowadays we have Tabular Editor etc.

@matt40k : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


when will 4.3.1 be available on npm?

It's still 4.2.1

+1

+1 @MinaSamir11

Help @MinaSamir11

done 4.3.1


Don't show error text for thumbnail errors

Displaying the error text for an image load error clogs of the view; don't show the error text.

This looks good so far, looks like it has the rename changes in it.

ha ha, thanks. It's ready now! No name changes...


Undocumented isPrePostEQ boolean in AOIS operator

I cannot understand the reason for this variable. What was the reason for using this?

Hi Haoyuan,
I am not sure about it, either. It seems to set whether adding ++ or -- on both sides or only one side.
Best regards,
Lin
On Feb 4, 2017, at 8:53 PM, Haoyuan Sun <notifications<EMAIL_ADDRESS>wrote:
I cannot understand the reason for this variable. What was the reason for using this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/jeffoffutt/muJava/issues/8, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEaWnwC1ZRsPP5DJGwmfJx4eeb8y7yk4ks5rZSu0gaJpZM4L3Wxr.


Cannot view PipelineRuns if current user only has "Pipeline Viewing" permission

What happened?
Cannot view PipelineRuns if current user only has "Pipeline Viewing" permission.

Logs in ks-apiserver:
 E1125 21:32:09.550954       1 am.go:985] role.rbac.authorization.k8s.io "anonymous" not found

 E1125 21:32:09.551000       1 utils.go:76] /workspace/pkg/kapis/iam/v1alpha2/handler.go:1093 role.rbac.authorization.k8s.io "anonymous" not found

 I1125 21:32:09.551052       1 apiserver.go:599] undefined - "GET /kapis/iam.kubesphere.io/v1alpha2/namespaces/test-projectl82l5/roles/anonymous HTTP/1.1" 404 53 0ms

 E1125 21:36:25.500093       1 am.go:985] role.rbac.authorization.k8s.io "test" not found

 E1125 21:36:25.500136       1 utils.go:76] /workspace/pkg/kapis/iam/v1alpha2/handler.go:1093 role.rbac.authorization.k8s.io "test" not found

 I1125 21:36:25.500181       1 apiserver.go:599] undefined - "GET /kapis/iam.kubesphere.io/v1alpha2/namespaces/test-projectl82l5/roles/test HTTP/1.1" 404 48 0ms

 E1125 21:36:27.148624       1 am.go:985] role.rbac.authorization.k8s.io "test" not found

 E1125 21:36:27.148666       1 utils.go:76] /workspace/pkg/kapis/iam/v1alpha2/handler.go:1093 role.rbac.authorization.k8s.io "test" not found

 I1125 21:36:27.148709       1 apiserver.go:599] undefined - "GET /kapis/iam.kubesphere.io/v1alpha2/namespaces/test-projectl82l5/roles/test HTTP/1.1" 404 48 0ms

Steps to reproduce

Create a Workspace, DevOps Project and a simple Pipeline using admin account
Create a test account
Create a role naming anonymous with permission Pipeline Viewing
Invite the test account into Workspace and DevOps Project created before and assign a role created before
Login into test account and go into that Pipeline
See error

/kind bug

/priority high
/milestone v3.2

Hi @LinuxSuRen , I have verified this problem in KubeSphere 3.2.1-rc.2, and the result is that this issue has not been fixed. Please see the screenshots below, which Pipeline Viewing permission doesn't depend on Pipeline Run Record Viewing:


SW_VERS should be lowercase

          1 Warning

:warning:
Please provide a changelog summary in the Pull Request description @ohayon

  Generated by :no_entry_sign: Danger

:shipit: x2!

good catch!!!!!!!  :shipit: x3

👎  @ohayon
Deployed internally and it's leaking sw_vers everywhere 💥
Just running fastlane shows sw_vers info...
Captured Output
Command Used: fastlane
Output/Log

[13:08:52]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
ProductName:	Mac OS X
ProductVersion:	10.13
BuildVersion:	17A405
[13:08:54]: Welcome to fastlane! Here's what your app is setup to do:
+--------+-----------------+------------------------------+
|                 Available lanes to run                  |
+--------+-----------------+------------------------------+
| Number | Lane Name       | Description                  |
+--------+-----------------+------------------------------+
| 1      | devices         |                              |
| 0      | cancel          | No selection, exit fastlane! |
+--------+-----------------+------------------------------+
[13:08:54]: Which number would you like run?
0

[!] Run `fastlane` the next time you need to build, test or release your app 🚀

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13

Ruby
2.4.2

Bundler?
false

Git
git version 2.14.2

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.13 (17A405)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.4.2/lib

OpenSSL Version
OpenSSL 1.0.2l  25 May 2017

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-9.app/Contents/Developer/

Xcode Version
9.0

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
snip
fastlane gems

Gem
Version
Update-Status

fastlane
2.62.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.5.2

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.3.0

terminal-table
1.8.0

plist
3.3.0

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

excon
0.59.0

faraday
0.13.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

mini_magick
4.5.1

multi_json
1.12.2

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.1

bundler
1.14.6

faraday_middleware
0.12.2

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.1

addressable
2.5.2

mime-types-data
3.2016.0521

mime-types
3.1

httpclient
2.8.3

google-api-client
0.13.6

json
2.1.0

io-console
0.4.6

openssl
2.0.5

generated on: 2017-10-18

@ohayon it's the system('sw_vers') that is leaking

Fixed in #10630


Add image-references file

Added image-references file to support bundle creation.
Signed-off-by: Don Penney<EMAIL_ADDRESS>

/lgtm

/unhold

/ok-to-test

/test e2e-aws

/cherry-pick main

/cherry-pick release-4.11


Required minimal EmbeddedStatus for v1 PipelineRun

This issue tracks down the requirement of a similar validation function for the minimal Embedded Status for PipelineRun. Thanks to the discussion with @abayer and @lbernick , a warning should be emitted to users if they are creating a v1 PipelineRun while the feature flag is not set to "minimal".
However, right now in pipeline we don't have a great way of returning a warning to the user. Ideally we would want the webhook to accept the pipelinerun, but return a warning via its rest api.
Originally posted by and thanks to @lbernick in https://github.com/tektoncd/pipeline/pull/5219#discussion_r932170481

So this wouldn't really be warning on a deprecated field, exactly - the Status.TaskRuns and Status.Runs fields are created/populated by the reconciler, not the CRD author. What could make sense would be checking if embedded-status isn't minimal during v1 PipelineRun creation and warning there...or maybe appending something to the PipelineRun.Status's Condition.Message saying "yeah, we don't support that?" in addition to whatever's already going there.
Actually, maybe the right answer is for v1 PipelineRun reconciliation to treat embedded-status being set to full as if it were set to both instead - populating both the deprecated Status.TaskRuns/Status.Runs and the new Status.ChildReferences.

/remove-lifecycle stale
I think we still need to discuss / handle this.

I think this issue is handled by #5813 so I'm going to close, feel free to reopen if needed


optimize Throwable#getCause once more

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?
fixes #5119
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #5208 (c20cda7) into develop (1bad3b8) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

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

@@              Coverage Diff              @@
##             develop    #5208      +/-   ##
=============================================
- Coverage      48.49%   48.44%   -0.05%
  Complexity      4137     4137
=============================================
  Files            743      743
  Lines          26517    26519       +2
  Branches        3294     3294
=============================================
- Hits           12859    12848      -11
- Misses         12262    12272      +10
- Partials        1396     1399       +3

Impacted Files
Coverage Δ

...in/java/io/seata/server/transaction/at/ATCore.java
41.17% <0.00%> (-1.25%)
:arrow_down:

...ing/annotation/GlobalTransactionalInterceptor.java
33.33% <0.00%> (-0.19%)
:arrow_down:

...n/src/main/java/io/seata/common/util/IdWorker.java
77.08% <0.00%> (-6.25%)
:arrow_down:

...rage/redis/store/RedisTransactionStoreManager.java
72.06% <0.00%> (-2.09%)
:arrow_down:

...erver/storage/file/session/FileSessionManager.java
47.77% <0.00%> (-0.64%)
:arrow_down:

...er/src/main/java/io/seata/server/ServerRunner.java
50.00% <0.00%> (ø)

...torage/file/store/FileTransactionStoreManager.java
56.27% <0.00%> (ø)

...o/seata/server/coordinator/DefaultCoordinator.java
44.67% <0.00%> (+0.40%)
:arrow_up:


IndexError: too many indices for array

Traceback (most recent call last):
File "trainval_net.py", line 305, in
data = next(data_iter)
File "/data/zww/anaconda3/envs/zwwpac/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 568, in next
return self._process_next_batch(batch)
File "/data/zww/anaconda3/envs/zwwpac/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 608, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
IndexError: Traceback (most recent call last):
File "/data/zww/anaconda3/envs/zwwpac/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 99, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/data/zww/anaconda3/envs/zwwpac/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 99, in
samples = collate_fn([dataset[i] for i in batch_indices])
File "/data/zww/test/One-Shot-Object-Detection-master/lib/roi_data_layer/roibatchLoader.py", line 106, in getitem
catgory = blobs['gt_boxes'][:,-1]
IndexError: too many indices for array

I have miss the same problem ,how can you solve that?

I have met the same problem, have you solved it?


CV Backend to return no batch

Codecov Report

Merging #35 (a778ab2) into main (741718a) will decrease coverage by 0.48%.
The diff coverage is 81.81%.

@@             Coverage Diff             @@
##              main      #35      +/-   ##
===========================================
- Coverage   100.00%   99.51%   -0.49%
===========================================
  Files           36       36
  Lines          826      833       +7
===========================================
+ Hits           826      829       +3
- Misses           0        4       +4

Impacted Files
Coverage Δ

zetta_utils/io/indexes/volumetric.py
100.00% <ø> (ø)

zetta_utils/tensor/ops.py
97.22% <50.00%> (-2.78%)
:arrow_down:

zetta_utils/__init__.py
100.00% <100.00%> (ø)

zetta_utils/io/backends/cv.py
100.00% <100.00%> (ø)

zetta_utils/training/datasets/layer_dataset.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Local database not persisted

I am using the go-orbit-db implementation to persist data outside the browser. When I put and get in the same instance it does work. If I end the session and open a new one the data is not there.
What am I missing?

This is the js implementation, if you issue is with the go implementation please open the issue there.

Thanks, I am moving it there.


[fontconfig:x86-windows] build failure on Windows 7

Host Environment

OS: [Windows 10, Windows7]
Compiler: VS2017

To Reproduce
Steps to reproduce the behavior:
`./vcpkg install fontconfig
Failure logs
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:106 (message):
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_make.cmake:527 (vcpkg_execute_required_process)
ports/fontconfig/portfile.cmake:19 (vcpkg_configure_make)
scripts/ports.cmake:136 (include)
Additional context

Confirmed:
autoreconf: Entering directory `.'
autoreconf: running: autopoint --force
/usr/bin/autopoint: line 487: tar: command not found
autopoint: *** infrastructure files for version 0.19.8 not found; this is autopoint from GNU gettext-tools <IP_ADDRESS>
autopoint: *** Stop.
autoreconf: autopoint failed with exit status: 1

@smalltree Are you using Windows 7 too?

@smalltree Are you using Windows 7 too?

yes，OsgEarth recommend to use vcpkg，but in practice it's not easy to use.

This seems to be the same as #15508 (which I've also confirmed), albeit for x64 instead of x86.
In contrast to @smalltree I actually find vcpkg much easier than trying to compile GTK components on Windows manually. It's worked well for me in the past so I'm surprised to find it's broken currently (after more than a year since I last used it).


User missing deposit on profile - user is in the editor role, Mike says plugin pulling from "creators"

I've got a user who is looking for this deposit on his profile https://works.hcommons.org/records/gm8ty-j6234 profile https://hcommons.org/members/ccooijmans/ but he's listed as an editor not an author, he's an editor. Is editor in the creators list or contributors? Ideally it should show up.

Editors are in the "creators" list and he's listed in "creators" for that record. The record shows up in an api search for metadata.creators.person_or_org.name:"Cooijmans, Christian". So I think everything is working fine on the Works end.
You can see the record show up in an api request to https://works.hcommons.org/api/records?q=metadata.creators.person_or_org.name%3A"Cooijmans%2C Christian"&l=list&p=1&s=10&sort=bestmatch

I think there must be something happening on the WP end if it's not being displayed on his profile

@mikethicke can you take a look at this/

After talking with Mike, we realized that the user's hc id isn't present in the creator information for that record. I need to investigate why it didn't get added during the serialization/migration. Should be a relatively easy fix, but I should also run through the other migrated records for the same issue.

Turns out the issue is that the user uploaded this work and didn't include their KC username. (It's autopopulated if they use "add self"). So the solution is for them to go in and add it on their creator item on the upload/edit form. Under identifiers they add a new identifier of the type "KC id".


fix(console): fix ENS tests not working with embark side by side

I'd like @emizzle to confirm I didn't do something wrong, but long story short, when the console is a client in terms of IPC, it didn't do the EmbarkJS connectConsole so ENS tests were bound to fail.
I think we could actually remove the isEmbarkConsole condition altogether for the register, but maybe it slows things down a bit or we make it so that we eval only through the console? Because there's a weird gap between runCode and console, but they still need one another

@emizzle Changed according to your suggestion.
I also fixed the console and the logger in this commit https://github.com/embark-framework/embark/pull/1364/commits/68ea85f9bb3183ffb733f847afd9fb60f61cf36c

Good catch on the circular error. I forgot about that. It's an easy fix, we already have a function fix those. Gonna change it.

@emizzle Fixed by using node's util.inspect. It is most likely what REPL itself uses.

Found a few errors while testing:

The downside of not letting REPL handle the object display is we lose some color formatting. For example, before when typing web3, I had a nice colored display of the web3 object. Now it is just one color, due to using the logger. But not a deal breaker I guess. This is the same for displaying arrays, etc.
Errors are not shown, ie typing web.eth doesn't show anything.
Typing swarm in the cockpit, shows a 500 error (underlying error displayed in the console is TypeError: Cannot read property 'green' of undefined), then displays the correct message: Swarm is disabled or not configured. Please see https://embark.status.im/docs/storage_configuration.html for more information.. However, typing swarm in to the console shows nothing. This is probably related to errors not showing (the point above).
In the console, typing await EmbarkJS.Names.isAvailable() shows undefined as the result, but if I debug this, true is being returned from the VM.

@emizzle you will find here https://github.com/embark-framework/embark/pull/1364/commits/101bc43d466e4d742bb1902a9986c5af2094b770 that I reverted the changes to the repl, so the console is back to the old behaviour
What I did keep is that commands put in the cockpit are still outputted in Embark

Thanks @jrainville, it's much better now :)
There is still one error that seems like it could be related to the changes:
Typing swarm in the cockpit, shows a 500 error (underlying error displayed in the console is TypeError: Cannot read property 'green' of undefined), then continues on to display the correct message: Swarm is disabled or not configured. Please see https://embark.status.im/docs/storage_configuration.html for more information..
Full stack shown in the console:
TypeError: Cannot read property 'green' of undefined
    at _logFunction.args.map.arg (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/core/logger.js:22:77)
    at Array.map (<anonymous>)
    at Logger.map [as logFunction] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/core/logger.js:20:33)
    at Logger.info (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/core/logger.js:125:23)
    at info (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/console/index.ts:107:23)
    at Console.cb (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/swarm/index.js:36:11)
    at Console.call [as executeCmd] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/console/index.ts:174:33)
    at executeCmd (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/console/index.ts:100:12)
    at cb (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/api/server.ts:133:7)
    at EventEmitter.cb (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/authenticator/index.js:123:32)
    at EventEmitter.call (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/core/events.js:75:8)
    at EventEmitter.emit (events.js:182:13)
    at EventEmitter.emit (domain.js:442:20)
    at EventEmitter.emit [as request] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/core/events.js:69:15)
    at Server.request [as applyHTTPFunction] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/src/lib/modules/api/server.ts:129:24)
    at Layer.handle [as handle_request] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/layer.js:95:5)
    at /Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/emizzle/Code/__Github/embk-fw/embark/packages/embark/node_modules/express/lib/router/index.js:275:10)

@emizzle Thanks again for all your tests.
I fixed the undefined error.
I also tested with objects again in the cockpit, and since we limited html injections in the cockpit, printing objects from the console to the cockpit didn't work (it was showing html entities), so I reverted that too.


Can't build on ESP8266

The README contains performance measurements for the ESP8266 and also states how to build MicroPython with this module for the ESP8266. However, I can't get the current version of MicroPython to include this module when building.
I'm using the "recommended" way to build for ESP8266, which is using docker:
~/Downloads/micropython/ports/esp8266
> docker run --rm -v $HOME:$HOME -u (id -u) -w $PWD larsks/esp-open-sdk make USER_C_MODULES=../../../st7789_mpy/st7789/micropython.cmake all

This builds fine but produces exactly the same image as without the USER_C_MODULES argument. When flashing the produced image, import st7789 does not work.
When looking over the Makefile in micropython/ports/esp8266, I noticed that neither USER_C_MODULES nor cmake is referenced at all. I also couldn't find anything else on how to include external modules in an ESP8266 build.
Am I missing something here?

Unfortunately, I don't have an opportunity to run the build and fix it.
You can try this fork https://github.com/russhughes/st7789_mpy maybe it would work in your case.

After some help from the guys over on the Micropython repo I figured out that the problem was on my end.  The build instructions in the readme work (minus the new recommended docker-based build). Sorry for the inconvenience.
See: https://github.com/micropython/micropython/issues/8655


fix(app-team-landing): migrate resize to function and add remove event listener

https://openforge.teamwork.com/#/tasks/17521988
Migrated all the resize functionality to a function that is called by the window.addEventListener resize. Then created a window.removeEventListener for the resize to prevent this from being called or used outside of this page, or any data carrying over.

QA Passes

QA Passes


Client Bugfix

Description :: Update

Fixes an issue where the client connection was being closed after every stream but not restarted. This fix makes it so the client is closed only at the end of a full tap sync.
Changes the way the driver path is discovered. The old way used relative pathing to locate the driver jar file. Since this tap is designed with Meltano in mind, this update gets the absolute path of the jar file within the tap.
Increases the query limit for streams.
Comments out the xc_attainment_measure and xc_attainment_measure_criteria streams/tests due to the query not functioning the same as the rest of the streams.

Type of Update

[ ] New Feature
[x] Bug Fix
[x] Refactor
[ ] Testing
[ ] Dependency
[ ] Documentation
[ ] Breaking Change

Dependencies

[ ] Packages Added
[ ] Packages Updated
[ ] Packages Removed
[x] No Changes

Everything looks good to me!


Crash on replace_with

The following crashes:
Where current_data == {}
jsonpath_lib::replace_with(current_data, "$a", &mut |_v| {
})?;

It seems like the issue is here: https://github.com/freestrings/jsonpath/blob/5b878d7ba7e17284f8af43fb6d38f1b63a6ca470/src/select/mod.rs#L1061
In case tokens.len() is 0 then it crashes.... cause last_index is usize


Fix GrouperPropertyConfigurer and its unit test

Ticket Link
https://uhawaii.atlassian.net/browse/GROUPINGS-1678
List of squashed commits
Test Checklist

[x] Exhibits Clear Code Structure:
[x] Project Unit Tests Passed:
[x] Project Jasmine Tests Passed:
[x] Executes Expected Functionality:
[x] Tested For Incorrect/Unexpected Inputs:

Figured it out.  Wrong project.  This is an API PR.


[manila-csi-plugin] add OWNERS file

Commit 313fc67b856b8e21bebe1b4a45a55ca25070207e intended to set
up an OWNERS file for the manila-csi driver, but it was set up
under the old non-csi pkg/share/manila path and was lost when
that legacy path was dropped with 1.18.
Set up the OWNERS file in the right path with appropriate current
membership.

What this PR does / why we need it:
Adds an OWNERS file to delegate responsibility for the manila csi plugin.
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/verify-owners

@lingxiankong @ramineni PTAL

/assign raminieni
/assign lingxiankong

/assign ramineni

/lgtm

PR 1110 has now merged.
/test cloud-provider-openstack-acceptance-test-csi-manila

/test all

/lgtm

/approve


navigation bar not responding

**navigation bar **
whenever i click on explore or setting the purple color is stuck on home button only

remove the defalut from home and set position to relative

Thank you for taking the time to report this issue. I'm happy to inform you that I have investigated the problem and fixed it by removing the default from the home button and setting the position to relative. I used the active URL path request to make sure that the correct button is highlighted when clicked. Thank you again for your help in identifying this issue!
https://github.com/Ajinkgupta/DjangXel/commit/2286a163b91c88d18dc59fc5e6355f1ba65e442a

fixed issue


Lambda Collector Configuration

Page seems to be missing table of ARNs referred

Agreed, both the lambda collector config doc as well as the lambda auto-instrumentation doc tell the user to copy the ARN of the desired lambda layer, but the ARNs are not actually provided anywhere.
As far as I can tell this means that, as of now, since it's missing such key information, this documentation is basically unusable.

@svrnm Confirmed, closing issue.


United Airlines (Old Livery) B787-9 (Livery Request)

Thx for @BoeingBus747 for the united airlines tail, I managed to finish this livery. Once he has the texts in the Scoot livery, I'll make one for that. Btw can you also add the liveries in: https://github.com/kolos26/GEOFS-LiverySelector/issues/136

You're welcome

Is this good enough? It's quite unusual to have the text like that

 Is this good enough? It's quite unusual to have the text like that

Yeahh I think that's good, but the only thing I need is the detailed version of the image and the "scoot" text from the tail. No need for the yellow things, I can do it myself.

I had it but I removed the tail one but I removed it, why didn't you say so, well got to find it again...

btw I also need the tail logo of Avainca so that I can do the N797AV livery

and a Egypt Air logo both in the tail and the fesulage

OMG, I'll just do those liveries myself then

OMG, I'll just do those liveries myself then

ok


[Feature]KubeVela HA Enhancement (VelaHA)

Is your feature request related to a problem? Please describe.
KubeVela can be deployed in a single control cluster.
The KubeVela control cluster has a single point of risk.
When disaster occurs, business continuity cannot be guaranteed.
In the production environment of the financial industry, KubeVela needs to have higher availability requirements.
Describe the solution you'd like
Consider three enhancements to achieve this goal:

Cluster Meta backup & recovery,
Master redundancy,
Failover support

Solution: VelaHA

Cluster Meta backup & recovery:
#5483
Master redundancy and Leader selection:
#5481
Failover support & disaster recovery:
#5482

Additional context
Feel free to discuss below.

@wonderflow @Somefive @fourierr

velaha is vela addon that can be enabled by user.
two steps:

install velaha addon
vela cli> vela ha enable or vela cli>vela ha disable

The vela cluster meta backup&restore is first step.

implement velero as KubeVela addon to install velero in kubevela cluster.
implement cli> vela ha enable to enable cluster meta backup with config scheduled(cron).
implement cli> vela ha restore to restore cluster meta.

The issue can let gsoc mentee understand

how to customize kubevela addon
how to implement vela cli

divide the feature into 3 parts for sprint

Hi, I'm attracted to this issue and would like to contribute to it under GSoC in the future. Regarding to the 3-part breakdown, does this mean the GSoC program will only focus on part 1 instead, with part 2 and part 3 as complementary?

Hi! This HA-feature is amazing. I hope to participate in this project and contribute to community!
I know the distributed deployment and use of hadoop/hdfs/hadoop bigtable/hadoop mapreduce, have an understanding of CAP/BASE/raft. And I also did a demo about backup(compression, encryption) function on nfs-server using websocket when I was a senior student.
It's amazing for me to have a chance to join this VelaHA discussion!


Remove remainder of controller HTTP surface

This (dead) code can now be removed since only /healthz HTTP handler
is supported.
Also cleaning up propagation of port number from command line options.
There is no need to store the port number on the server instance.

LGTM
eventually I do think we'll need to pass in a struct to provide other options (like the interface to listen on), but for now port is ok.

LGTM. Didn't notice that these were missed in #84

LGTM, merging.


There is no copyright associated with this project

Nice work, but until there is a copyright, the project is toxic - its entirely up to you, but it would be super if you could add one - thx

added MIT license in https://github.com/munkyboy/docker-redsocks/commit/8eaa39d9c56868a53ac5726ed5e7d6593e83cd7d

Thanks - a huge help to my team.


Updated to 2.0.9

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


nf-core-ize notes

Mainly on the containers:

Conda declarations are great, we can build singulrity/docker images with wave for that or use the mulled containers.
Drop souporcell or add it to bioconda(shouldn't be too bad), containers will get built automagically

Hey @Emiller88 ! It's great to see you here. I kinda remember how things work :)
Souporcell is a major tool that we cannot drop. I am not sure how easy it is going to be to add souporcell to bioconda. I fear it might be challenging.
Would you be up for attempting to add it? If not @wxicu might be able to have a stab at it.


Revert "Exclude arm64 from supported iOS simulator architectures"

Reverts flutter/flutter#73458
This change leaked into the watch target?
2021-01-07T14:01:30.728056: stdout:     note: Using new build systemnote: Planning buildnote: Constructing build descriptionwarning: The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 6.1, but the range of supported deployment target versions is 2.0 to 6.0.99. (in target 'watch' from project 'Runner')warning: The watchOS Simulator deployment target 'WATCHOS_DEPLOYMENT_TARGET' is set to 6.1, but the range of supported deployment target versions is 2.0 to 6.0.99. (in target 'watch Extension' from project 'Runner')warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'device_info' from project 'Pods')warning: There are no architectures to compile for because all architectures in VALID_ARCHS (x86_64) are also in EXCLUDED_ARCHS (x86_64, i386). (in target 'device_info' from project 'Pods')warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'Runner' from project 'Runner')warning: There are no architectures to compile for because all architectures in VALID_ARCHS (i386, x86_64) are also in EXCLUDED_ARCHS (x86_64, i386). (in target 'Runner' from project 'Runner')warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'Pods-Runner' from project 'Pods')warning: There are no architectures to compile for because all architectures in VALID_ARCHS (i386, x86_64) are also in EXCLUDED_ARCHS (x86_64, i386). (in target 'Pods-Runner' from project 'Pods')warning: Mapping architecture arm64 to x86_64. Ensure that this target's Architectures and Valid Architectures build settings are configured correctly for the iOS Simulator platform. (in target 'Flutter' from project 'Pods')
stdout:

Merging to green the tree.

Merging to green the tree.


In-game video preview on gamelist

Hi!
Is it possible to make something to see a in-game video on gamelist?!

Not yet, but I have done some work on adding video support through the FFmpeg library in the video branch. There's a new <video> component that lets you place videos, but right now there's no looping at the end of videos and there's no support for loading videos by metadata yet on the detailed game list.

Cool!
I don't know if it's more easy but Gif support can help too!
On Mon, Apr 6, 2015 at 10:19 PM, Aloshi<EMAIL_ADDRESS>wrote:

Not yet, but I have done some work on adding video support through the
FFmpeg library in the video branch
https://github.com/Aloshi/EmulationStation/tree/video. There's a new
 component that lets you place videos, but right now there's no
looping at the end of videos and there's no support for loading videos by
metadata yet on the detailed game list.
—
Reply to this email directly or view it on GitHub
https://github.com/Aloshi/EmulationStation/issues/436#issuecomment-90304169
.

@mgoulartBR Seeing as .GIFs can be a lot smaller in size, I'd think they'd take up a lot less space (which would be useful for people with huge collections of games) and require less CPU to run (which could benefit Pi users). Seeing as @Aloshi has already started a video branch, I'm not suggesting he abandons it, after all the hard work he puts in to it, but your suggestion of using .GIFs is a great fallback idea!

To show a real preview would it be possible, as an alternative to a video, to launch the real game and load a previously created save state to get into the game (or title screen) and skip the intro ? I know performance would be very bad on big games, but for older systems it may be fast enough, what do you think ? Creating a save state is very easy and does not take much space on the filesystem.

The issue there Derek is it's more than video, that would effectively been opening a render window inside ES and executing the game and then the save state, which would mean the emulator would have to accept loading a save state via command line.  Also, when the game doesn't have a save state you'd still be sat watching splash screens.
Video thumbnails is a fantastic idea.  I already tried slipping an animated GIF in but it doesn't support them.  Worth a try though!
Having the whole background play a video clip of the game, but darkened so it didn't take too much attention from the foreground elements, would also look really smooth.
Distribution would also be a nightmare, ideally some people would need to band together to collect/create clips for an entire romset and then create a torrent.


Added mapping for PowerA Core Plus controller on Linux

I had two controllers that had this GUID, which were not in the DB, so I added the mapping.

Thank you !


[Op] Implement TensorPackTransH2DOp to improve SmartStage Performance

on GPU.

This commit implements TensorPackTransH2DOp which can merge and transmit tensors located on the CPU to the GPU to improve transmission efficiency.

This commit modifies the behavior of stage_subgraph_on_cpu optimization, placing the Stage and Unstage nodes on the GPU.

This commit contains a pass that automatically adds TensorPackTransOp before the Stage node, which is disabled by default.

Performance Result:

Model
base line (steps/sec)
after optimize (steps/sec)
Improvement (steps/sec)

dbmtl
47.26426
48.77022
1.50596

dcn
29.65154
33.816
4.16446

dcnv2
20.79466
22.40772
1.61306

deepfm
19.94762
21.40698
1.45936

din
32.85986
34.96146
2.1016

dlrm
40.02112
42.45896
2.43784

dssm
43.18712
46.5219
3.33478

esmm
46.79446
50.63016
3.8357

mmoe
55.60278
56.63794
1.03516

simple_multitask
58.50012
61.69042
3.1903

wdl
36.87816
39.26686
2.3887


adding realistic pyomo models in nevergrad

Several interesting Pyomo models that we might want to integrate in Nevergrad:
PowNet-Cambodia – implementation of PowNet for Cambodian power system with data for 2016
PowNet-Laos – implementation of PowNet for Laotian power system with data for 2016
PowNet-Thailand – implementation of PowNet for Thai power system with data for 2016
Network flow optimization of California's water supply system: https://github.com/ucd-cws/calvin

All of them open source on internet.
thx @pacowong  for the discussion :-)


Mitigation for "Missing from the token response"

Can this workaround section be expanded please? This appears to be my exact issue but I don't understand how to rectify it.

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

ID: 9d9d3e88-6f7d-904b-3e9d-fbe7c26ea649
Version Independent ID: 5d93c939-37c6-8cff-6002-0c569998c6d8
Content: Azure AD B2C (MSAL.NET) - Microsoft identity platform
Content Source: articles/active-directory/develop/msal-net-aad-b2c-considerations.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: jeferrie

@RhomGit
Thanks for your feedback! We will investigate and update as appropriate.

Hi @RhomGit, it seems that the link currently specified in the Mitigation for "Missing from the token response" section is out of date:

The article that it should point to is Tutorial: Create user flows in Azure Active Directory B2C, where step 8 in the Create a sign-up and sign-in user flow section says:

For User attributes and claims, choose the claims and attributes that you want to collect and send from the user during sign-up. For example, select Show more, and then choose attributes and claims for Country/Region, Display Name, and Postal Code. Click OK.

Please review that document and let us know if that helps. I'll update this article with the new link, as well.
Cc: @jmprieur @jennyf19

Hi @RhomGit, an update to this article has been merged and should be live sometime after 0300 Pacific time.

Hi, great to hear that this has been fixed, it was a touch confusing. That being said I had got this far myself. I already have Display Name checked and returning, what I was hoping to resolve is this:

This is when calling:
var accounts = await pca.GetAccountsAsync();
var firstAccount = accounts.FirstOrDefault();
authResult = await pca.AcquireTokenInteractive(AuthB2C.scopes)
.WithUseEmbeddedWebView(true)
.WithAccount(firstAccount)
.WithParentActivityOrWindow(parentActivity)
.WithPrompt(Prompt.SelectAccount)
.ExecuteAsync();
on a device that hasn't run the app in a while. I presume the token is expired and the webview is trying to repopulate the window with the previous account name (which would be great).

@RhomGit so this is coming from MSAL and the cache. B2C does not return a preferred_username, so we have no value to display there for B2C. And the webview is outside of the control of MSAL, it's presented by AAD B2C.
The way around this is to not send the account w/the request, as that's prepopulating the user name that you don't want, because that's the replacement username MSAL is using.
But, you can send in .WithLoginHint() and pass in any value that you parsed from the id_token (this only works if there is a token in the cache).
Your code above would be:
string email;
authResult = await pca.AcquireTokenInteractive(AuthB2C.scopes)
.WithUseEmbeddedWebView(true)
.WithLoginHint(email)
.WithParentActivityOrWindow(parentActivity)
.ExecuteAsync();

I got the email value when i parsed the id_token from the initial sign-in, and how it displays in the box, as you can see above.
Does that unblock you?
I'm not sure if LoginHint will work with non-AAD B2C accounts (ex. facebook, google), but if you are using system browser, it works really nice with the other IdPs as the user will sign in automatically if they have already signed in on their browser.
Hope this helps.

Thanks @jennyf19 that explained it perfectly.
I have done as you suggested and it worked, exactly what I was hoping for!

This was very painful. I'm using Azure AD B2C with a local account and I was also getting the "missing from the token response" -- and I had the "Display Name" as a claim. It would be helpful to change the documentation to use the solution you have provided here. I'm thankful to have found it.

@lorne-olo Thanks for the feedback and apologies for the difficulties in finding the solution. It is not very well documented. will work on getting this fixed. thanks

From @lorne-olo

Now, is there any way to put the email--or any other claim--into the cache being used by MSAL?

Yes, this is the bit that is not covered I believe - would be great if the IAccount that goes into the token cache could be extended to include other claims.
My (not pretty) workaround down @mmacy 's recommendation: context is B2C in a WPF application using an MsalAuthHelper and TokenCacheHelper. After sign in, I silently pull another token, simply to get those other attributes (like the user name or the email).
//using System.IdentityModel.Tokens.Jwt;
var handler = new JwtSecurityTokenHandler();
var tokenContent = (JwtSecurityToken)handler.ReadToken(await GetTokenAsync());
var email = tokenContent.Claims.FirstOrDefault(x => x.Type == "emails")?.Value;
var name = tokenContent.Claims.FirstOrDefault(x => x.Type == "name")?.Value;


'purd' tag can be added for enhancement

Hi, there's an issue I've encoutered when syncing the songs downloaded to my phone, where the album release time aren't displayed in the Music app. By checking tags using Mp3tag, I found that by adding a tag called iTunesPurchaseDate to each song, which uses the Greenwich Mean Time, the release date can be displayed properly. Here's the code I've added into gamdl.py.
Add to import:
import time

Add to tags in get_tags_song:
'purd': [(time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(time.time())))],

Also, if there's a need to get a higher-resolution cover art, simply change the line of covr in tags into
'covr': [MP4Cover(requests.get(artwork_url.replace('600x600bb.jpg', '3000x3000bb.jpg')).content, MP4Cover.FORMAT_JPEG)],

Pulled from the video tags part and altered the original resolution to fit.
btw, I just found that line 246 & 250 of tag playlistName seems to be repetitive.
Happy New Year! x

That's a good idea, but the time format you put in is wrong, it must be in ISO 8601 to follow the iTunes conventions. Also the artwork must stay in 600x600 to follow iTunes conventions.

The time format for release date follows ISO 8601, but the purchase date doesn't though. I've used the files I've purchased before to check and this is actually the right format. Already downloaded a few songs to examine.
You can check the screenshot down below from a song purchased in iTunes, in normal GMT format.


Incorporate file length estimation from endaq.ide

The current idelib contains a file start/end time estimation function, importer.estimateLength(), but it had a number of problems (inaccuracy being only one). A better estimator was written for another project; it should be incorporated.
See also issue #62, which also involves incorporating improved functionality from that project.

Addressed in PR #68


Navigating bash to specific or current dir at start

Hi,
is there some way to start bash in specific or current dir?
From shortcut LNK I found that I can start bash at home dir via:
bash ~
but when I type another directory like:
bash /mnt/c
it gives me /mnt/c: /mnt/c: is a directory and it won't start.
In the end what I would like to do is start bash with any path (unix or Windows) like:
bash /mnt/c/Users and it would start at dir /mnt/c/Users
bash C:\Users and it would start at dir /mnt/c/Users
I am asking because I start vscode and cmder in current dir from Total Commander like:
code . or cmder .
and I would like to also start bash like that:
bash . on current dir.
Thanks

By default bash.exe with no arguments  will start in your windows current working directory.  Is this what you're talking about?
Microsoft Windows [Version 10.0.14366]
(c) 2016 Microsoft Corporation. All rights reserved.

 Yes, that is exactly what I ment.

No problem at all :)
Going to go ahead and close this issue out if you don't mind.


recursive_ostruct_class option

Hi. In my project I subclassed RecursiveOpenStruct and added some checks to my custom initializer, e.g.:
raise "no :id" unless self.id
The error was thrown even when I provided a hash with an id:
Subclass.new({id: 1, deep: { a: 15, b: 20 }})
Problem was: my custom initializer was called recursively (for every nested level). I think that's a problem others might stumble upon, too. The behavior I expected was that my custom initializer is being called only once and nested levels are not being created recursively with Subclass.new, but with RecursiveOpenStruct.new. So I added an option that provides exactly that.
Default behavior not changed (you have to opt-in for RecursiveOpenStruct.new on nested levels).
Test case added.
Description added.
Anything missing?

I would recommend using the delegate pattern for your use-case rather than trying to subclass RecursiveOpenStruct and add yet another optional feature to RecursiveOpenStruct (the existing optional features create all sorts of problems). This would give you the behavior you are expecting and more control over custom behavior, although it isn't exactly analogous to building the feature into ROS itself:
require 'recursive-open-struct'
require 'delegate'

class SomeClass < DelegateClass(RecursiveOpenStruct)
  attr_accessor :ros

  def initialize(h)
    @ros = RecursiveOpenStruct.new(h)
    super(@ros)
  end
end

c = MyClass.new({a: 'a', b: { b: 'b', c: 'c'}})
# => #<RecursiveOpenStruct a="a", b={:b=>"b", :c=>"c"}>
# Actually a MyClass, but it is delegating #inspect to the ROS instance:
c.class
# => MyClass

# Existing getters and setters when the ROS is passed to super behave as expected:
c.a
# => "a"
c.a = 'b'
# => "b"
c.a
# => "b"
c.b.b = 'd'
# => "d"
c.b.b
# => "d"

# The one gotcha is that setters that do not exist on the delegate ROS object don't work on SomeClass:
c.foo = 'c'
# => NoMethodError: undefined method `foo=' for #<RecursiveOpenStruct a="b", b={:b=>"b", :c=>"c"}>
#    from .../lib/ruby/2.3.0/delegate.rb:87:in `method_missing'

# But you can set a new value on the ROS directly, and then it will show up on the MyClass instance:

c.ros.foo = 'asdf'
c.foo
# => "asdf"

 I suspect the delegate implementation is asking the ROS object whether it has a method (the exception is raised from delegate.rb's implementation of method_missing), rather than trying to blindly call the method. This would be straightforward to implement by overriding method_missing.

Closing b/c there hasn't been any discussion or activity on this PR in a year. I am reluctant to add another optional feature to ROS that seems to me like there are better patterns for implementing the desired behavior.


Designer Portal Issues: Unable to add http trigger to Standard SKU Logic App

Describe the Bug with repro steps
I am unable to add a new http trigger to my Standard SKU Logic App. The portal is loading really long and then not returning anything when searching for http triggers or any other In-App triggers:

No In-App triggers are shown at all:

What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes and the old designer seems to be having the same issue:

Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response

In the TSG there are instructions on collecting console logs and HAR traces. Can you get those and send them to me at<EMAIL_ADDRESS>https://aka.ms/lauxtsg

Moving this over to the backend repo, it looks liek the operationsGroup call is returning a 400 error for you and it's one we need to display this page. It doesn't appear to be a UI issue since it's only happening to you and is also happening on the designer that hasn't been updated in over a year with no problems.


set-strictmode -version $psversiontable.PSVersion.Major ?

PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 6.3.9600
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

steps to reproduce:
PS C:\> Set-StrictMode -Version 1
PS C:\> Set-StrictMode -Version 2
PS C:\> Set-StrictMode -Version 3
PS C:\> Set-StrictMode -Version 4
PS C:\> Set-StrictMode -Version 5
PS C:\> Set-StrictMode -Version 6
PS C:\> Set-StrictMode -Version 7

# but
PS C:\> Set-StrictMode -Version 8
Set-StrictMode: Cannot validate argument on parameter 'Version'. The "8.0" argument does not conta
in a valid PowerShell version. Supply a valid version number and then try the command again.

why the version to set-strictmode is the same tthe version of powershell ? and what the difference between the versions ? it's not documented...for example: what restriction for version 7

why Downvote ?
if set-strictmode -version 7  is the same as version 3 why increment the number of version to 7 ?

I think it's the same as PowerShell version to allow one to reference the latest coding guides that were available with a specific version of powershell, basically the same as with "-Requires", but for coding guides.
This however does not reflect the current state of how it is implemented as I had to learn after updating from Version 7 to 7.1 as it doesn't recognize 7.0 as valid anymore... (See #9206 for details about that)

Still exists in latest version of powershell.
PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.9
PSEdition                      Core
GitCommitId                    7.3.9
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

PS C:\> Set-StrictMode -Version 7.3
PS C:\> Set-StrictMode -Version 7.1
Set-StrictMode: Cannot validate argument on parameter 'Version'. The "7.1" argument does not contain a valid PowerShell version. Supply a valid version number and then try the command again.
PS C:\> Set-StrictMode -Version 7.2
Set-StrictMode: Cannot validate argument on parameter 'Version'. The "7.2" argument does not contain a valid PowerShell version. Supply a valid version number and then try the command again.
PS C:\> Set-StrictMode -Version 7.3
PS C:\>
PS C:\> Set-StrictMode -Version 7
Set-StrictMode: Cannot validate argument on parameter 'Version'. The "7.0" argument does not contain a valid PowerShell version. Supply a valid version number and then try the command again.
PS C:\> Set-StrictMode -Version 7.0
Set-StrictMode: Cannot validate argument on parameter 'Version'. The "7.0" argument does not contain a valid PowerShell version. Supply a valid version number and then try the command again.
PS C:\>


Add Swift 4 support

Codecov Report

Merging #102 into master will decrease coverage by 0.5%.
The diff coverage is 32.5%.

@@            Coverage Diff             @@
##           master     #102      +/-   ##
==========================================
- Coverage   85.73%   85.22%   -0.51%
==========================================
  Files          43       43
  Lines        3546     3580      +34
==========================================
+ Hits         3040     3051      +11
- Misses        506      529      +23

Flag
Coverage Δ

#SwiftKuery
85.22% <32.5%> (-0.51%)
:arrow_down:

Impacted Files
Coverage Δ

Sources/SwiftKuery/Utils.swift
49.01% <32.5%> (-8.34%)
: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 edd76ce...2e15c85. Read the comment docs.

IBM-Swift/Kitura#1121


[DNM: ASTScope lookup] Fix backwards PatternBindingEntry::getSourceRange

PatternBindingEntry::getSourceRange uses the end of the initializer for the end of the range. But, if the initializer is a property wrapper, the initializer comes before the start of the PatternBindingEntry. Prevent the  computation from using such an initializer.
At present, this change isn't quite ready for prime time because uses a check that bypasses the SourceManager::isBeforeInBuffer abstraction, since I don't see how to get the SourceManager into play where it is needed.
In addition to a fix being needed for ASTScope lookup, this fix will be needed to address part of rdar://53637494

@swift-ci please smoke test os x platform

@slavapestov @DougGregor Here is some functionality that would be very useful for ASTScope lookup. Without it, I'll have to intercept calls to getSourceRange to correct the result for PattternEntrys. The issue is that the fix here bypasses isBeforeInBuffer because the SourceManager seems to be unavailable. Can you suggest some sort of fix? Thanks

Would it be better if property wrappers synthesized the pattern to have the correct source location?

@slavapestov @DougGregor I think I found a way to do this that works without violating encapsulation. It uses the presence of the equals sign to detect a "following" initializer instead of a property wrapper one.

@swift-ci please smoke test

Don't review yet--needs more thought. Tx.


Fix intermittent crash on Electron 18+

This was not fun to track down. Probably ~3 weeks of work?
This PR bumps nan to a custom version hosted on the axosoft org(could be moved to nodegit if necessary) and bumps the internal field count on object templates to account for the updates made to nan.
more details on what is happening and why, here:
https://github.com/Axosoft/nan/pull/1
and here:
https://github.com/electron/electron/blob/693cf0ebdebb272494610a5ed2e9c405e825813e/patches/node/be_compatible_with_cppgc.patch

CI failures appear to be caused by an npm bug so ill publish the axosoft nan package and put it in this PR.


admin role missing can_welcome permissions

Leading to this:
2016-06-06 17:20:14,062:WARNING:flask_appbuilder.security.decorators:Access is Denied for: can_welcome on: Caravel

If you can give me any hint i can do the patch.

Mmmmh, I thought it would add all perms to the Admin role upon restart of the app. Can you try caravel init?

No errors, and i see log message of added permission:
2016-06-09 11:03:49,178:INFO:flask_appbuilder.security.sqla.manager:Added Permission can welcome on Caravel to role Alpha

Anyway since it's just a warning let's close this.


Stoch RSI results are wrong

Is there a way to set the 4 parameters we set in Tradingview ? K, D, RSI length, Stochastic length ?
To be sure to have the accurate results ?
Thanks a lot

No,.. there is no way.. for StochRSI you only can adjust the RSI length.
:|

I've set it to get the 3 results ... stoch K and D
All are wrong results.... when I check on Tradingview.
I see you are using STOCHRSI... why ? Since results are not accurate ?

Read the FAQ -> https://github.com/CryptoSignal/Crypto-Signal
Btw, I don't use it and I don't know how accurate it is, but when I have a little time I will review what you say.

@bluetyphoon77
I tested StochRSI and it is working as expected. I'm using this config to get Buy signals for 4h candles. Repeat, it is working.
  stoch_rsi:
    - enabled: true
      alert_enabled: true
      alert_frequency: once
      signal:
        - stoch_rsi
      hot: 20
      cold: 80
      candle_period: 4h
      period_count: 14
      hot_label: 'Possible Uptrend is coming'
      cold_label: 'Possible Downtred is coming'
      indicator_label: '#StochRSI'
      mute_cold: true

I don't know why you say it gives wrong results.
:/

Because when I use it on a daily in my case, I get wrong values.
When I check on Tradingview and compare, it is totally different. I would not bother here before testing first.
So what do you mean by "it is working" ? To grab data ? yes I get data. But NOT accurate at all.
How do you know your results are accurate ? what is your way to verify ?

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Sunday, December 6, 2020 1:50 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
@bluetyphoon77https://github.com/bluetyphoon77
I tested StochRSI and it is working as expected. I'm using this config to get Buy signals for 4h candles. Repeat, it is working.
stoch_rsi:
- enabled: true
alert_enabled: true
alert_frequency: once
signal:
- stoch_rsi
hot: 20
cold: 80
candle_period: 4h
period_count: 14
hot_label: 'Possible Uptrend is coming'
cold_label: 'Possible Downtred is coming'
indicator_label: '#StochRSI'
mute_cold: true
I don't know why you say it gives wrong results.
:/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-739442482, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYA57KUTC6A7H6EG3ITSTLPMZANCNFSM4UJHWYNQ.

And where did you set stoch/length/k/d settings ?

From: Yvan Rkm<EMAIL_ADDRESS>Sent: Sunday, December 6, 2020 1:56 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
Because when I use it on a daily in my case, I get wrong values.
When I check on Tradingview and compare, it is totally different. I would not bother here before testing first.
So what do you mean by "it is working" ? To grab data ? yes I get data. But NOT accurate at all.
How do you know your results are accurate ? what is your way to verify ?

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Sunday, December 6, 2020 1:50 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
@bluetyphoon77https://github.com/bluetyphoon77
I tested StochRSI and it is working as expected. I'm using this config to get Buy signals for 4h candles. Repeat, it is working.
stoch_rsi:
- enabled: true
alert_enabled: true
alert_frequency: once
signal:
- stoch_rsi
hot: 20
cold: 80
candle_period: 4h
period_count: 14
hot_label: 'Possible Uptrend is coming'
cold_label: 'Possible Downtred is coming'
indicator_label: '#StochRSI'
mute_cold: true
I don't know why you say it gives wrong results.
:/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-739442482, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYA57KUTC6A7H6EG3ITSTLPMZANCNFSM4UJHWYNQ.

  stoch_rsi:
    - enabled: true
      alert_enabled: true
      alert_frequency: once
      signal:
        - stoch_rsi
      hot: 20
      cold: 80
      candle_period: 1d
      period_count: 14
      hot_label: '--Possible Uptrend is coming'
      cold_label: '--Possible Downtred is coming'
      indicator_label: 'StochRSI 1D'
      mute_cold: true

Running this config with 1d candles I get buy signals for XLM/USDT , ZEC/USDT, LINK/USDT and many more (right now).
Works -> I receive this signals in my Telegram channel.
Verify -> I check Stoch RSI chart indicator in Binance(TradingView) and it is correct, I see buy signals.
The only value that you can configure here is period_count: 14 . In fact it is the standard value for RSI & StochRSI.

BTW, Binance/TradingView doesnt plot original STOCH_RSI line, just smoothK and smoothD.
The code in this program doesnt use config values for K and D because it works with original stoch_rsi not with smoothed K, D values.
period_count = 14  =>  rsi_length = 14 , stoch_rsi_length = 14

Thanks for your answer eduardo.
I've RE-tested with some other pairs a few minutes ago
This is what I get when I use the code you sent me NOW on the 6/12/2020, at 14:23 UTC+1 (PAris time)
Beginning analysis of LINK/USDT
LINK/USDT:
indicators:     stoch_rsi #0: 6.19683765
HBAR/USDT:
indicators:     stoch_rsi #0: 41.81868073
DGB/BTC:
indicators:     stoch_rsi #0: 19.01127194
VIA/BTC:
indicators:     stoch_rsi #0: 49.36108561
POWR/BTC:
indicators:     stoch_rsi #0: 34.24612329
When I check on binance or tradingview at the same moment I have
(for a stochrsi of k=3, d=4, length 14, stoch 14)
LINK: 7.22 for K/16.92 for D
HBAR: 31.31/58.82
DGB: 2.72/27.01
VIA: 36.94/52.39
POWR: 17.86/49.47
SO, you can see, totally wrong values !
Maybe you should test with these ones and send me your results.

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Sunday, December 6, 2020 2:11 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
stoch_rsi:
- enabled: true
alert_enabled: true
alert_frequency: once
signal:
- stoch_rsi
hot: 20
cold: 80
candle_period: 1d
period_count: 14
hot_label: '--Possible Uptrend is coming'
cold_label: '--Possible Downtred is coming'
indicator_label: 'StochRSI 1D'
mute_cold: true
Running this config with 1d candles I get buy signals for XLM/USDT , ZEC/USDT, LINK/USDT and many more (right now).
Works -> I receive this signals in my Telegram channel.
Verify -> I check Stoch RSI chart indicator in Binance(TradingView) and it is correct, I see buy signals.
The only value that you can configure here is period_count: 14 . In fact it is the standard value for RSI & StochRSI.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-739444084, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYFHGUOENDOQIF36XPDSTLR65ANCNFSM4UJHWYNQ.

I think I finally understood your point,..
Change the "signal" value in your config file, set:
  stoch_rsi:
    - enabled: true
      alert_enabled: true
      alert_frequency: once
      signal:
        - slow_k
        - slow_d
      hot: 20
      cold: 80
......

The output you will see is for K/D respectively.

Hi Eduardo, no it is not about this.
AS a showed you CLEARLY with RESULTS in my answer, NONE of the 3 values we get with this script is accurate !
So, I've seen people found ways to succeed with other libraries just for STOCHRSI,....
It's weird that a simple indicator is not working on this CRYPTO SIGNAL BOT
:(

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Monday, December 7, 2020 7:28 PM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
I think I finally understood your point,..
Change the "signal" value in your config file, set:
stoch_rsi:
- enabled: true
alert_enabled: true
alert_frequency: once
signal:
- slow_k
- slow_d
hot: 20
cold: 80
......
The output you will see is for K/D respectively.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-740129846, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYAKFKO2NYWQJ26O2MLSTUUFRANCNFSM4UJHWYNQ.

Did you see this comment?
Could be the solution:
https://github.com/mrjbq7/ta-lib/commit/3f872e3ff53a2ef0fa85c9ed8da66515001b2eed#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

thanks yes indeed, we were investigating and got this solution ;)
It is a little hack but it is supposed to work
Thanks a lot anyway ;)

I forgot to ask, this is an interesting hack, but if we are not a programmer and just using the script, how can we set this in the config ? thanks

@bluetyphoon77 I rewrote a good part of the code for this indicator, now should be given better results. The latest code is on develop branch.

@bluetyphoon77 I rewrote a good part of the code for this indicator, now should be given better results. The latest code is on develop branch.

Great Eduardo !!
I'll test it soon
Cheeers

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Sunday, January 24, 2021 2:47 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
@bluetyphoon77https://github.com/bluetyphoon77 I rewrote a good part of the code for this indicator, now should be given better results. The latest code is on develop branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-766280767, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYFHF6AK2WIZWOBX5RTS3OC3NANCNFSM4UJHWYNQ.

Great Eduardo !!
I'll test it soon
Cheeers

From: Eduardo Zarate<EMAIL_ADDRESS>Sent: Sunday, January 24, 2021 2:47 AM
To: CryptoSignal/Crypto-Signal<EMAIL_ADDRESS>Cc: bluetyphoon77<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [CryptoSignal/Crypto-Signal] Stoch RSI results are wrong (#409)
@bluetyphoon77https://github.com/bluetyphoon77 I rewrote a good part of the code for this indicator, now should be given better results. The latest code is on develop branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/CryptoSignal/Crypto-Signal/issues/409#issuecomment-766280767, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJEEGYFHF6AK2WIZWOBX5RTS3OC3NANCNFSM4UJHWYNQ.


Should result.css return a SlowBuffer?

I've noticed that in some cases, result.css is a SlowBuffer instead of a plain string. Is this expected behavior? I can't find anything in the docs about it.
I'm able to reproduce this in the following script:
var sass = require("node-sass");

var options = {
  data: ".test { version: version(); }",
  functions: {
    "version()": function(done) {
      done(sass.types.String('"' + "1.0.1" + '"'));
    }
  }
}
sass.render(options, function(err, result) {
  console.log(result.css);
});

It's a simple matter of calling result.css.toString(), but it just wasn't something I knew I needed to do.

In the docs we have: https://github.com/sass/node-sass/#result-object
The behavior was changed after this discussion: https://github.com/sass/node-sass/issues/711.

:+1: Thanks


CORE Spec - Org Management Component - Identity Management

Purpose:
Describes process requirements for Identity Management.
Brainstorm
Need to address below list of processes:
RequestIdentity - #22 - Should
CreateIdentity - Must
RegisterIdentity  - Must
GetRegisteredIdentity  - Must
Prerequisites and requirements
RequestUpdateIdentity  - Must
UpdateIdentity  - Must
RevokeIdentity  - Must
RequestIdentityPresentation  - Must
RecoverIdentity - Should

I am starting some brainstorming and collecting some thoughts here

Requirements from: https://github.com/ethereum-oasis/baseline-roadmap/issues/174

#
Component
Requirement Category
Requirement Type
Requirement

2
Identity
NFR
Operator MAY employ a centralized solution for baseline identities/accounts/workgroups

3
Org Management
Authentication & Authorization
NFR
Operator MUST synchronize workgroup entities and their accounts to the Baseline Global Phone book

4
Org Management
Authentication & Authorization
NFR
Operator MUST synchronize workgroup entities and their accounts to the Baseline Global Phone book

5
Org Management
Authentication & Authorization
NFR
Operator MAY add additional operator specific metadata to synchronized Baseline Global Phone book records

6
Org Management
Authentication & Authorization
NFR
Operator MUST NOT have the ability to change, update or delete Baseline global phonebook records


[nixos] systemd[1]: Failed to load default target: No such file or directory

Complete newbie to nix and NixOS, so I'm not sure if this is the correct place to ask for newbie help? If not, close this and point me to the correct place.
So I attempted a new (first time) NixOS install, and upon choosing the default NixOS option under grub, I get the following screen when NixOS tries to boot: http://i.imgur.com/PYj0fIRh.jpg (sorry for the bad quality)
Searching for this issue doesn't help much, so not sure how to continue/debug? The live image I used for the installation was nixos-minimal-16.03pre70421.e57024f-x86_64-linux.iso.

I was being dumb. I forgot I still had the remains of a previous GNU/Linux distribution installation on the partition I was installing NixOS on. I presume this error was because of a conflict between these two installations because I just reformatted the partition to clean it out, and did a re-install of NixOS and now it does work and boot as expected. Sorry for the noise. :\

Small question: NixOS boots into what looks like slim automatically, and saying "root" with an empty password here does not seem to let me login. (NixOS never asked me to set a password for the root user as it says it would at step 11 here: https://nixos.org/nixos/manual/). Also, in my /etc/nixos/configuration.nix, I set a user "u", but didn't do passwd with it yet to set a password for the user, so I assume the default would be an empty password? Asking because putting "u" for the username, and an empty password for it does not work either. So how do I set the passwords, or otherwise login somehow, if anyone knows?


Entity Metadata Not Found

This error happens when I initialize a new SeedingSource instance like the below (I followed the doc):
export default new SeedingSource({
	dataSource: {
		...(DatabaseConfig as DataSourceOptions),
		database: DatabaseConfig.database as never,
		entities: [__dirname + '/../../resources/**/*.entity{.ts,.js}'],
		synchronize: false, // MUST BE FALSE
	},
	seeders: [
		CreateBase,
		CreateGlassesBill,
		CreatePatient,
		CreateUser,
		CreateProduct,
	],
})

DatabaseConfig has everything to construct a DataSource
entities: It's the path leading to the entities folder. I checked it many many times to make sure it was correct.
But whenever I try to run the seeds, this error appears: No metadata for "" was found. This discussion is not about I asking for a solution, because I found one as I described below. It's simply a note for someone who has the same problem as me.
My solution
So I dug into the code of this project and also compared what TypeORM is actually doing, I figured out that entityMetadata wasn't set during the construction of the DataSource. You have to call dataSource.initialize() in order for that to happen.
So I edited the resolve-data-source.js like below:
import { DataSource, DataSourceOptions } from 'typeorm'

export const resolveDataSource = async (dataSource: DataSource | DataSourceOptions): DataSource => {
  // create new instance if necessary
  const dataSourceToReturn = dataSource instanceof DataSource ? dataSource : new DataSource(dataSource)

  // Entity Metadatas won't be resolved if we don't call dataSource.initialize()
  // Thus causing error "No metadata for '' not found"
  await dataSourceToReturn.initialize()

  // return the data source
  return dataSourceToReturn
}

After this change, the error disappeared. My entities loaded correctly. However, a couple of things need to be changed.
Since resolveDataSource now returns a Promise, hence the dataSource instance you get from SeedingSource getter is also a Promise. So if seeder class want to access dataSource instance, I did the following:
export default class CreateBase extends Seeder {
	public async run(): Promise<void> {
		const dataSource = await this.seedingSource.dataSource

		...
	}
}

And changed the function save of factory class in factory.js inside the typeorm-seeding folder to:
async save(entities, saveOptions) {
        const dataSource = await this.seedingSource.dataSource;
        // has been initialized yet?
        if (!dataSource.isInitialized) {
            // no, initialize it
            await dataSource.initialize();
        }
        return dataSource.createEntityManager().save(entities, saveOptions);
    }

Now everything works!
Footnote
I don't know if this thing is related to this topic, but anyway, I set synchronize: false, // MUST BE FALSE because if it is set to true, TypeORM will do crazy things without you even asking for it. In my case, it was trying to drop indexes of my tables when I didn't ask it to do.

I use TypeORM v0.3.12

@bquangDinh you mentioned a change you made to the Factory.save() method, but the source already contains this initialization... here is a link to the code on main.
https://github.com/conceptadev/typeorm-seeding/blob/main/src/factory.ts#L119
Can you confirm the version of this project you are on?

Yes I have that in my version. The thing is, with the code is arranged your way, that means TypeORM will be first initialized when you call saving (I tried to see if TypeORM is initialize somewhere else but couldn't find it so I assume this is the only one you call initialize) In my case, it isn't right. Since my seeds need to query something in the database before calling save. That's why I got the error. My quick solution in the moment is calling initialize on every seeds to make sure TypeORM is good to go. But it's kinda annoying tho since I have to do it on every seeds.

Yes I have that in my version. The thing is, with the code is arranged your way, that means TypeORM will be first initialized when you call saving (I tried to see if TypeORM is initialize somewhere else but couldn't find it so I assume this is the only one you call initialize) In my case, it isn't right. Since my seeds need to query something in the database before calling save. That's why I got the error. My quick solution in the moment is calling initialize on every seeds to make sure TypeORM is good to go. But it's kinda annoying tho since I have to do it on every seeds.

I found the issue, but no solution yet. It only happens when you provide a path for an entity. If you import the entity class and put it directly on the entities array, it works fine.
I thought providing a string path was deprecated on 0.3.X... but maybe I was mistaken, or they added it back since 0.3.0.
I will continue testing here, and try to release a fix soon.

Well, I tried to put entities file also, but it didn't work, the error was still there. That's why I had to go through the code to see if TypeORM actually doing anything at all in constructor. It turned out TypeORM doesn't build entity metadata in the constructor, all it does is create some variables and that's it.
This is the code I found in Datasource.js from my TypeORM:
    constructor(options) {
        this["@instanceof"] = Symbol.for("DataSource");
        /**
         * Migration instances that are registered for this connection.
         */
        this.migrations = [];
        /**
         * Entity subscriber instances that are registered for this connection.
         */
        this.subscribers = [];
        /**
         * All entity metadatas that are registered for this connection.
         */
        this.entityMetadatas = [];
        this.name = options.name || "default";
        this.options = options;
        this.logger = new LoggerFactory_1.LoggerFactory().create(this.options.logger, this.options.logging);
        this.driver = new DriverFactory_1.DriverFactory().create(this);
        this.manager = this.createEntityManager();
        this.namingStrategy =
            options.namingStrategy || new DefaultNamingStrategy_1.DefaultNamingStrategy();
        this.metadataTableName = options.metadataTableName || "typeorm_metadata";
        this.queryResultCache = options.cache
            ? new QueryResultCacheFactory_1.QueryResultCacheFactory(this).create()
            : undefined;
        this.relationLoader = new RelationLoader_1.RelationLoader(this);
        this.relationIdLoader = new RelationIdLoader_1.RelationIdLoader(this);
        this.isInitialized = false;
    }

As you can see, it barely does anything with entityMetadatas  array.
And it only does so in initialize()
    /**
     * Performs connection to the database.
     * This method should be called once on application bootstrap.
     * This method not necessarily creates database connection (depend on database type),
     * but it also can setup a connection pool with database to use.
     */
    async initialize() {
        if (this.isInitialized)
            throw new error_1.CannotConnectAlreadyConnectedError(this.name);
        // connect to the database via its driver
        await this.driver.connect()
        // connect to the cache-specific database if cache is enabled
        if (this.queryResultCache)
            await this.queryResultCache.connect();
        // set connected status for the current connection
        ObjectUtils_1.ObjectUtils.assign(this, { isInitialized: true });
        try {
            // ----> this line: build all metadatas registered in the current connection
            await this.buildMetadatas();
            await this.driver.afterConnect();
            // if option is set - drop schema once connection is done
            if (this.options.dropSchema)
                await this.dropDatabase();
            // if option is set - automatically synchronize a schema
            if (this.options.migrationsRun)
                await this.runMigrations({
                    transaction: this.options.migrationsTransactionMode,
                });
            // if option is set - automatically synchronize a schema
            if (this.options.synchronize)
                await this.synchronize();
        }
        catch (error) {
            // if for some reason build metadata fail (for example validation error during entity metadata check)
            // connection needs to be closed
            await this.destroy();
            throw error;
        }
        return this;
    }

But I'll close the issue anyway since I've fixed it

Can you post a short example of how you are making queries before save? After digging into the code, I see how there are cases where if you don't initialize the DataSource manually before passing to the SeedingSource options there will be no initialization done.
I am just curious about your pattern so I can make sure I cover these scenarios. Are you making queries inside the Factory classes, or inside the Seeder classes, or both?

I make queries inside the Seeder classes. This is one example of how I seed the Products table. Since each product needs an authorizer, and I want it to be randomly selected. So I have to perform a query to the database to get user ids before saving products into database
export default class CreateProduct extends Seeder {
	public async run(): Promise<void> {
		// make sure it's initialized
		const dataSource = this.seedingSource.dataSource

		if (!dataSource.isInitialized) {
			await this.seedingSource.dataSource.initialize()
		}

		const products = await this.factory(ProductFactory).makeMany(100)

		const repo = dataSource.getRepository(Product)

		const authorizerIds: { id: string }[] = await dataSource
			.getRepository(User)
			.createQueryBuilder('user')
			.select('id')
			.getRawMany()

		if (authorizerIds.length === 0) {
			console.warn('No user found in database. Need seed!')
			return
		}

		for (const product of products) {
			const existingProduct = await repo.findOne({
				where: {
					productCode: product.productCode,
				},
			})

			if (existingProduct) {
				product.quantity += existingProduct.quantity
				product.id = existingProduct.id
			} else {
				product.authorizerId = sample(authorizerIds).id
			}

			await dataSource.getRepository(Product).save(product)
		}
	}
}

@bquangDinh Please take a look at this PR and let me know if you think it will solve your issue. I also added some helpers for getting repositories inside seeder and factory classes.
https://github.com/conceptadev/typeorm-seeding/pull/6
Since this issue is closed, you can make comments on the PR itself 👍🏻


[Android][iOS][CheckBox] CheckBox shows a pressed state on first nav

Current behavior

Expected behavior
When user first navigates to CheckBox sample, a pressed state or ripple effect should not be displayed
How to reproduce it (as minimally and precisely as possible)

Launch app
Select CheckBox from burger menu
Notice the pressed state / ripple effect

Environment

Nuget Package:
Package Version(s):
Affected platform(s):

[x] iOS
[x] Android
[ ] WebAssembly
[ ] UWP

Anything else we need to know?

Issue also happens with RadioButton

Fix verified. Unable to reproduce issue


Selected Offset

How to bind the selected offset to MVVM property, or better bind the selected bytes itself.

Were looking for the same feature. I guess it's not really MVVM friendly implemented or better said: There's no non-user controlled selection method, sadly.


Codeblock formatting inside the environments is NOT supported.

This is a minor problem. We are not directly concerned about it. I am simply reporting it in case it may help other people...
In the example file here :
https://github.com/Wandmalfarbe/pandoc-latex-template/blame/master/examples/boxes-with-pandoc-latex-environment-and-awesomebox/document.md
The line 114 says

Markdown formatting inside the environments is supported.

This is partially true because the codeblock are breaking the latex output
$ pandoc document.md --listings --filter pandoc-latex-environment --from markdown --template=eisvogel -o document.pdf
Error producing PDF.
! Paragraph ended before \lst@next was complete.
<to be read again>
                   \par
l.537 \end{importantblock}

If I remove the backticks (line 119 and 123), the pdf is compiled with no issue.
Thanks for this great template !

It seems that tables are also not supported

That's interesting because I compile this file regularly with no issues. The generated example PDF looks fine https://github.com/Wandmalfarbe/pandoc-latex-template/blob/master/examples/boxes-with-pandoc-latex-environment-and-awesomebox/document.pdf. Maybe it depends on your TeX distribution and installed packages?


no citation option on chat texts

I haven't seen the citation option on the chats and/or other sections of MS Teams app
is that normal?
skype has it // is a quite common action in most apps, and it is quite useful also

Hi @wumpalumpa! This issues section is for this sample app only.
For Teams feature requests, please go to User Voice. There's already a few requests for this, and I recommend that you add your vote to an existing suggestion, perhaps this one: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/40226587-quote-a-message-and-reply-option


Implement asSeenFrom, and resolve member types according to their prefix.

Well, this is what I have so far. Opening a draft PR for reference, and if @bishabosha wants to take over from here in the coming weeks. One existing test is still failing. Something to do with the initialization of declaredType for a ClassSymbol of an inner class. It's unclear why it would even want to see the declaredType, but that's what it is.

I believe I have addressed all your comments so far.


Added readiness probe to vpn-seed-server deployment.

The readiness probe checks with netcat that the two server ports are open.
As a side effect the open vpn server port was extracted into a constant.
How to categorize this PR?

/area networking
/kind enhancement
What this PR does / why we need it:
Adds readiness probes to the containers of the vpn-seed-server deployment.
Which issue(s) this PR fixes:
Fixes #4303
Special notes for your reviewer:
Release note:

/invite @DockToFuture

@ScheererJ any chance to address Vladimir's comments? This way we had a good chance to include this change in the next Gardener release.

It is nice to have readiness probes. Do you think the same probes can be re-used for liveness check?

@vpnachev Good point. I added liveness checks as well reusing the same logic from the readiness probes.

@ScheererJ any chance to address Vladimir's comments? This way we had a good chance to include this change in the next Gardener release.

@timuthy Sorry for the delay. I hope now everything is as it should be.


No textbox to input response

I think a textbox should be showing here, unless I am doing this wrong.

@AshRing this extension has some issues when there is not enough width in devtools, maybe try detaching devtools to separate window and make it full screen


Update Kestrel

Fix for CVE-2023-38180

/azp run net - mgmt - ci

/azp run net - containerregistry - ci

I'm running net - mgmt - ci on a previously working and compliant service (containerregistry - mgmt) to make sure this didn't regress anything, and will merge then.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=3020943&view=results passed.


What is mshell installed on a remote?

What is mshell installed on any remote? I could not find any information about it in any documentation. If you just install something on a remote without even asking, it would be at least nice to know what it is and why it is required. Thank you.

mshell is the same as waveshell. It is a local agent that manages the pty sessions, etc. on your remote machine. This communicates with the main Wave app over SSH. It does not open any additional ports or send us any telemetry.
We understand the concern about installing things on remote computers unprompted. We are planning to document this agent more in and we are going to add an informational prompt in the "New Connection" pane that will require approval before we install it.

Thank you for the explanation.

I've added a FAQ entry to address this question.  https://docs.waveterm.dev/reference/faq#what-is-mshell-waveshell-why-does-it-need-to-be-installed-on-machines-i-connect-to


feat(chunking): add overlap on chunk-splits

There are two distinct overlap operations with completely different implementations. This is "intra-chunk" overlap, applying overlap to chunks resulting from text-splitting an oversized element.
So if an oversized element had text "abcd efgh ijkl mnop qrst" and was split at 15 chars with overlap of 5, it would produce "abcd efgh ijkl" and "ijkl mnop qrst". Any inter-chunk overlap from the prior chunk and applied at the beginning of the string (before "abcd") is handled in a separate operation in the next PR.

Is the final goal of a series of refactoring PRs to implement the "intra-chunking" overlap?
This PR seems to introduce a new concept of "intra-chunking" overlap so, it would probably be good to describe this "intra-chunking" overlap in the CHANGELOG file at this stage.

Yeah, I thought about that, but my thinking is that none of this is exposed yet (no way to engage these features from the unstructured API) so I thought it would be best to put the CHANGELOG updates in the later PR where these features are added to the API, "wired up" so to speak.
Otherwise someone reading the CHANGELOG might go looking for something they're not going to be able to find.
There's one more PR after this one to add the inter-chunk overlap capability, and then the next one (the last one) will actually add the chunk_by_character() strategy and add the overlap parameters to the decorator, the strategies, and probably in the documentation somewhere. I was thinking to put the feature additions on the CHANGELOG for that PR since that's when they'll be "published".

Thanks @christinestraub! :)

Otherwise someone reading the CHANGELOG might go looking for something they're not going to be able to find.

I think the CHANGELOG should reflect the state of the actual library. Historically, new functionality appears in the CHANGELOG always necessarily show up first as plain-old-partition parameters.
I do think it makes sense to have an additional CHANGELOG item later when unstructured-ingest supports, and at that point the API should too.

@cragwolfe This intra-chunk overlap behavior does not appear as partition parameters yet. The only way to trigger the behavior is by constructing a (lib internal-use only) ChunkingOptions instance with overlap > 0. That (new-ish) object is not an interface object, it's only used (outside of tests) by chunking-strategy code, chunk_by_title() so far.
Before the user can specify overlap, we have to:

Add it as a partition kwarg, in the documentation at least.
Add capture and use of that kwarg to the @apply_chunking_strategy decorator.
Add it as an explicit kwarg to chunk_by_title() and the new chunking strategy being added.

My plan was to postpone those bits until after the next PR which adds the second half of overlap and "wire-up" the new overlap args and announce the behavior together.
I'm happy to "pre-announce" it in CHANGELOG if that's how we do it, just let me know. I just figured we were focusing CHANGELOG on changes visible to the end-user rather than when we "laid the foundation" for those features, so to speak.

Ok, in the interest of time I've added a CHANGELOG entry that describes the new behavior but notes that it is not yet available from the interface.


Travis integration is added

Api Level 22 emulator is used. Marshmallow emulators have too small timeout. More info here
Build tools are updated to 1.5.0. It is because tests are more stable in 1.5.0. Not 100% necessary. I can revert it if requested.

@keyboardsurfer if you can enable android-topeka under https://travis-ci.org/googlesamples
I can trigger the build by amending and force pushing the commit here.

Thanks for this addition.
Since Topeka supports API levels down to 14, having multiple emulators down the API level lane would be great.

Thanks for share. My alternative explained here. Works for all the APIs but requires new test rules.
You can use
travis_wait to avoid the 10 minutes timeout (20 minutes by default or you can add a custom value)
and
cat ${TRAVIS_BUILD_DIR}/*/build/outputs/androidTest-results/connected/* for better output.

Hi @ardock I actually saw your work while I am working on this. I spent all my day yesterday and tests were flaky. Most of them are because of the issue described here
I avoided 10 minute timeout by adding -i at the end of the gradle build command. It shows additional information and it shows successful and failed tests. Since it outputs tests results for every test, Travis never timeouts.

I spent too much time on it. I was almost given up but I put 10 seconds sleep after emulator bootup and it seems that it is working good. I will squash my commits into 1 once the builds are successful.

typeText on Api 21 seems not working.

Finally its green! :green_heart:

It would be best to get integration on 14 as well as 21 and 23 in order to actually cover the low and high API levels as well.

It is impossible to test on 23 on Travis. Many people tried and reverted back.
21 should be ok but I couldn't get reliable results.
14 is one of the bests in emulator. I think it is because Android was lighter those days. The problem with <17 is that I cannot disable animations through command line. Which makes tests fail immediately because the project has protection about it.

We definitely would have to test against API level 22, since there are some vector graphics that are in drawable-v22.
Also disabling animations and transitions is essential in order to get reliable test results.

This code uses reflection to disable animations programatically: https://gist.github.com/xrigau/11284124
It is based on a code piece that is released by espresso team a while ago.
I spend too much time to make it work on Travis. I also tried it on GDG Android app: https://github.com/gdg-x/frisbee
Google Cloud Test Lab is btw promising. Building on Travis and uploading to CTL is also an option.

@keyboardsurfer Rules based on your current animationAwareTestRule and Espresso reflection:
disable and restore animations scales for any API explained here
api 15 to 19 https://travis-ci.org/ardock/android-topeka/builds/92165265
api 22 https://travis-ci.org/ardock/android-topeka/jobs/94146736#L1514

API level 22 and API level 23 are affected by the same bug, a hardcoded timeout, but you can use adb to avoid it and install directly https://github.com/ardock/android-topeka/commit/ab1ba23f93bde2825936c712a54332777349c3d5

Thanks to both of you for your time and expertise on this matter.
But since we're currently unable to have integration tests running on important API levels with this addition I don't see the benefit of merging this contribution.

Since this project is on of the best googlesamples in terms of tests, I really wanted to have them running on CI. But it is not reliable with arm emulators.
Thank you for your time. Cheers :smile:

Thank you for taking a deep look into this and working hard on a solution.
Once the situation changes we might be able to get this up and running on a public CI.

The change is coming.
Thanks to both of you for your time (and JD), the status of the issue is FutureRelease 2.0.0-beta3.
Please, give it another try when fixed, thank you.

Eventhough the problem with API 22-23 emulators are fixed, other problems with Travis are still there.


drone.yml parsing fails when starting by ---

I am running v1.0.0 and I noticed that when my drone.yml file starts with a --- before my first pipeline definition, the parsing fails. I tried the CLI linter but it doesn't return any error.
for example a file starting by
kind: pipeline
name: unit
steps:
  - name: unit

Will work but this will not:
---
kind: pipeline
name: unit
steps:
  - name: unit

Than I'm pretty sure you are doing something other wrong. Even the .drone.yml of Drone itself is using --- because this is the only way to define multiple pipelines: https://github.com/drone/drone/blob/master/.drone.yml#L1

Hi @tboerger,
That's odd, by just adding it before my first pipeline, my jobs fail with the error yaml: missing kind attribute

So I just checked and the actual version of the image we use is 1.2.3  not 1.0.0. Sorry

Please provide a full example that fails for you, best would be to reproduce that on cloud.drone.io.

@tboerger  I did some more testing and I think I found the issue.
We are running a python shop and the in the file license, was included, at the top:
# -*- coding: utf-8 -*-

this in combination with --- before the first pipeline generates an exception. If either the comment in the license or the --- is missing the document is parsed correctly

if you are adding it above the --- it is treated as a separate yml document, than the error is totally fine because it doesn't provide a kind: pipeline. Just don't add that before the yaml document separator.

According to the yaml spec https://yaml.org/spec/1.2/spec.html#id2760395 it seems like only comments before the first --- should not be counted as a document

According to the yaml spec https://yaml.org/spec/1.2/spec.html#id2760395 it seems like only comments before the first --- should not be counted as a document

Feel free to report an issue to the yaml parsing library, or provide a pull request to implement this part of the spec :)