Reducer playground

Creates a playground based on reducer!

https://deploy-preview-225--squiggle-documentation.netlify.app/docs/Playground
It works! But doesn't support anything xD

But doesn't support anything xD
What do you mean here? It supports a lot of stuff for me (though definitely not everything). Not sure if you were being literal or not.

Look at that! Log works now!

I get this error a lot when I play with this.
For example, if I enter a single character, like, "l"

This is fixed in the newest deployment

Sorry for the particularly large diffs, I'm piggybacking running prettier over everything in this PR

https://deploy-preview-225--squiggle-components.netlify.app/


Refactor/bsp interface

Hi @corneliusclaussen
thanks for sharing this pull request. Could you please elaborate the motivation of this pull request? Is it to move as much as possible IEC 61851 specific stuff out of the BSP?

This is a refactoring that was planned for quite some time. As it breaks the BSP interfaces in an incompatible way, all BSP drivers will need to be changed. It should be relatively easy though.
Main motivations:

board_support_AC was used for DC as well for a while now but some things were missing for proper DC support. Also naming was wrong

To synchronize with the charging state machine in evsemanager abstract events were used (such as CarPluggedIn). This proved to be complex to use as the hardware typically knows states ABCDEF and the translation was non-trivial. To simplify BSP development, remove complexity from BSP drivers and avoid code duplication this code was moved into EvseManager. We decided to still use those abstract events internally in EvseManager as they hide some nasty details of IEC61851-1 (such as simplified charging mode). Now the BSP needs to report only the states ABCDEF. Most BSP drivers now only contain protocol translation code to the MCU and no logic anymore.

Factor out AC RCD. The RCD was in the board_support_AC interface before, in order to make the design a little cleaner it was moved to a separate interface (just like the IMD for DC charging)

In addition a lot of small improvements were made.
As this breaks code for many users we will also announce this on the mailing list as well as in todays community dev meeting

Another note: EvseManager itself will need internal refactoring as well at some point as it got quite complex, but for now this is more about improving the interfaces to the outside so that we hopefully do not need to break BSP compatibility soon again.

Please especially review the following:
interfaces/evse_board_support.yaml
types/board_support_common.yaml
types/evse_board_support.yaml

I will need to do another review round, but at least I can confirm that the SIL is working now, also in multiple subsequent charging sessions.

Hi,
on our website there is a detailed list (chapter 3.3.4 ff) of all error codes from our old charging stack. If i ignore all persistence related errors there are still some errors which are not available (e.g. lock capacitor not charged) above.
How should we handle these? Add them on demand later?

About the BspEvent error codes: I'm trying to collect all useful error codes in this enum at the moment. I'll have a look at your list as well and will include them, I think it is a good moment as we are breaking things anyway right now. Of course also more can be added later on.
Before this PR gets undrafted, we want to also port it over to the new error handling framework, see PR #284. So the error list collected in the BspEvent enum is just a temporary list to collect all error codes that we want to be able to report.

I looked through the ChargeControl C documentation and added the lock motor failure details. I renamed them a bit to align better with the wording used in MREC codes. The other error codes such as RCD and powermeter do not belong to this interface, they should go into the ac_rcd and powermeter interfaces. Those will become reportable errors as well soon with the new error handling framework.

@corneliusclaussen I have a question regarding the detection of an EV. It's possible to implement this via different approaches (only CP, only PP, mixed CP/PP).
Is it up to the implementor of the board support package to decide if an EV is connected or is there some kind of EVerest policy how to detected this?

@corneliusclaussen: Would it be an option for you to cut the plug lock stuff out into a dedicated interface? This would make the bsp interface even more generic and minimalistic. BSPs with plug lock capabilities could easily implement both interfaces in a single module (e.g. Yeti if I'm right) and boards with no hardware support at all could easily just skip it. On platform like our Tarragon, we have for example two hardware plug lock interfaces. Our plan would be to create a module which cares about a single one, but customers could use another module instance for the second plug lock (e.g. for locking a fixed cable while a socket is in use...).

@corneliusclaussen: Would it be an option for you to cut the plug lock stuff out into a dedicated interface? This would make the bsp interface even more generic and minimalistic. BSPs with plug lock capabilities could easily implement both interfaces in a single module (e.g. Yeti if I'm right) and boards with no hardware support at all could easily just skip it. On platform like our Tarragon, we have for example two hardware plug lock interfaces. Our plan would be to create a module which cares about a single one, but customers could use another module instance for the second plug lock (e.g. for locking a fixed cable while a socket is in use...).

In this case EvseManager would need to decide when to lock/unlock. In all HW that we have here this is actually done by an MCU (which ensures proper unlocking in case of Linux fails etc). It could be done though as the MCU can still do it on its own and not use the evsemanager supplied information. I factored out the RCD for the same reason of . I can make a draft, but probably after charin testival

@corneliusclaussen: Would it be an option for you to cut the plug lock stuff out into a dedicated interface? This would make the bsp interface even more generic and minimalistic. BSPs with plug lock capabilities could easily implement both interfaces in a single module (e.g. Yeti if I'm right) and boards with no hardware support at all could easily just skip it. On platform like our Tarragon, we have for example two hardware plug lock interfaces. Our plan would be to create a module which cares about a single one, but customers could use another module instance for the second plug lock (e.g. for locking a fixed cable while a socket is in use...).

@mhei : Another though on this: If we refactor out all motor lock things into a separate interface, would it make sense to also move all PP related things to this motor lock interface? If there is a socket it also requires a lock and only with a socket PP is useful?
If there is a fixed attached cable you don't need motor lock but you also don't need PP. What do you think?

I agree that this is usually related, but as I mentioned, I'd like to (re-)use the lock motor interface for other purposes as well. Having then a stray PP interface in this interface would make things more complex on this side.

Agreed. Then we leave PP in the bsp interface and create a new one with just the lock/unlock commands and error reports for the lock

I pushed a draft for the interfaces/connector_lock.yaml, pls have a look. It is not used that, I'll implement in evsemanager once the interface is agreed

@corneliusclaussen : motor lock interface LGTM

Hello together,
we have found one possible bug plus one SIGABRT fault while testing the new interface and EvseManager module on our hardware.
The scenario:
The EV is plugged in, the EV is authorized and 26.76% duty cycle is signaled.
The EV starts charging (CP state C) and pauses charging (CP state B) after a few seconds.
When the EV tries to charge again, 100% is signaled for a short time, which is unexpected because the vehicle is already authorized. Furthermore, charging is unexpectedly interrupted with the log message:

[WARN] connector_1:Evs std::queuemodule::CPEvent module::IECStateMachine::state_machine() :: Timeout of 6 seconds reached, EV did not go back to state B after PWM was switched off. Power off under load.

If now the vehicle goes back from CP state B to A (EV unplugged), then EVerest terminates with an exit code 134 "Abnormal Termination (SIGABRT)".
The following log message can be seen:
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.375578 [INFO] cb_tarragon_dri  :: CP state change from B to A
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.445374 [INFO] cb_tarragon_dri  :: handle_pwm_off: Setting new duty cycle of 100.00%
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.630798 [INFO] cb_tarragon_dri  :: handle_allow_power_on: {
Oct 27 06:01:05 tarragon manager[13634]:     "allow_power_on": false,
Oct 27 06:01:05 tarragon manager[13634]:     "reason": "PowerOff"
Oct 27 06:01:05 tarragon manager[13634]: }
Oct 27 06:01:05 tarragon manager[13635]: terminate called after throwing an instance of 'std::future_error'
Oct 27 06:01:05 tarragon manager[13635]:   what():  std::future_error: Promise already satisfied
Oct 27 06:01:06 tarragon manager[13606]: 2023-10-27 06:01:06.157019 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Module connector_1 (pid: 13635) exited with status: 134. Terminating all modules.

Hello together,
we have found one possible bug plus one SIGABRT fault while testing the new interface and EvseManager module on our hardware.
The scenario:
The EV is plugged in, the EV is authorized and 26.76% duty cycle is signaled.
The EV starts charging (CP state C) and pauses charging (CP state B) after a few seconds.
When the EV tries to charge again, 100% is signaled for a short time, which is unexpected because the vehicle is already authorized. Furthermore, charging is unexpectedly interrupted with the log message:

[WARN] connector_1:Evs std::queuemodule::CPEvent module::IECStateMachine::state_machine() :: Timeout of 6 seconds reached, EV did not go back to state B after PWM was switched off. Power off under load.

If now the vehicle goes back from CP state B to A (EV unplugged), then EVerest terminates with an exit code 134 "Abnormal Termination (SIGABRT)".
The following log message can be seen:
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.375578 [INFO] cb_tarragon_dri  :: CP state change from B to A
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.445374 [INFO] cb_tarragon_dri  :: handle_pwm_off: Setting new duty cycle of 100.00%
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.630798 [INFO] cb_tarragon_dri  :: handle_allow_power_on: {
Oct 27 06:01:05 tarragon manager[13634]:     "allow_power_on": false,
Oct 27 06:01:05 tarragon manager[13634]:     "reason": "PowerOff"
Oct 27 06:01:05 tarragon manager[13634]: }
Oct 27 06:01:05 tarragon manager[13635]: terminate called after throwing an instance of 'std::future_error'
Oct 27 06:01:05 tarragon manager[13635]:   what():  std::future_error: Promise already satisfied
Oct 27 06:01:06 tarragon manager[13606]: 2023-10-27 06:01:06.157019 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Module connector_1 (pid: 13635) exited with status: 134. Terminating all modules.

Hi, thanks for the report. I will try to reproduce on our hardware early next week as well. On the promise satisfied crash: can you check the got revision of everest-framework? There was a quite recent commit that fixes one promise handling bug that showed up in another scenario. The short 100÷ in between looks more like a bug in the state machine that should be easy to find. If you still see the crash at the latest main of everest-framework it would be really helpful to do a gdb backtrace (run everest without the driver module (-s)) and then start the driver in gdb in a separate terminal)

Hello together,
we have found one possible bug plus one SIGABRT fault while testing the new interface and EvseManager module on our hardware.
The scenario:
The EV is plugged in, the EV is authorized and 26.76% duty cycle is signaled.
The EV starts charging (CP state C) and pauses charging (CP state B) after a few seconds.
When the EV tries to charge again, 100% is signaled for a short time, which is unexpected because the vehicle is already authorized. Furthermore, charging is unexpectedly interrupted with the log message:

[WARN] connector_1:Evs std::queuemodule::CPEvent module::IECStateMachine::state_machine() :: Timeout of 6 seconds reached, EV did not go back to state B after PWM was switched off. Power off under load.

If now the vehicle goes back from CP state B to A (EV unplugged), then EVerest terminates with an exit code 134 "Abnormal Termination (SIGABRT)".
The following log message can be seen:
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.375578 [INFO] cb_tarragon_dri  :: CP state change from B to A
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.445374 [INFO] cb_tarragon_dri  :: handle_pwm_off: Setting new duty cycle of 100.00%
Oct 27 06:01:05 tarragon manager[13634]: 2023-10-27 06:01:05.630798 [INFO] cb_tarragon_dri  :: handle_allow_power_on: {
Oct 27 06:01:05 tarragon manager[13634]:     "allow_power_on": false,
Oct 27 06:01:05 tarragon manager[13634]:     "reason": "PowerOff"
Oct 27 06:01:05 tarragon manager[13634]: }
Oct 27 06:01:05 tarragon manager[13635]: terminate called after throwing an instance of 'std::future_error'
Oct 27 06:01:05 tarragon manager[13635]:   what():  std::future_error: Promise already satisfied
Oct 27 06:01:06 tarragon manager[13606]: 2023-10-27 06:01:06.157019 [CRIT] manager         int boot(const boost::program_options::variables_map&) :: Module connector_1 (pid: 13635) exited with status: 134. Terminating all modules.

Hi, thanks for the report. I will try to reproduce on our hardware early next week as well. On the promise satisfied crash: can you check the git revision of everest-framework? There was a quite recent commit that fixes one promise handling bug that showed up in another scenario. The short 100÷ in between looks more like a bug in the state machine that should be easy to find. If you still see the crash at the latest main of everest-framework it would be really helpful to do a gdb backtrace (run everest without the driver module (-s)) and then start the driver in gdb in a separate terminal)
EVerest/everest-framework@e784a3c

Currently we are using "7fcf0ac1e2d5362b25e967d48e163f0fbb4382b9" (0.7.0) of everest-framework. We can repeat the test as soon as we have updated our build.

Hello together,
We at chargebyte would like to give you a brief update on the current draft of the BSP interface. We have tested the new interface for CP/PP and contactor handling with our hardware platform for the AC path. Everything seems to work as expected with the EvseManager. Some comments are still open from the code review, but once these are answered we see no problems to create a pull request from it.
Also the reported bug with resuming of the charging session by the EV (CP B -> C -> B -> C transition) works now after we updated everest framework.
We know that it will probably take a lot of effort on your side to prepare everything that it can be merged into erverest-core, but we are looking forward to working with the new interface soon :-).
Are there already plans when the new interface will be available?
Thank you and best regards

One additional note to the CP B -> C -> B -> C transition scenario. There is still 100% duty cycle for a short time after the second switch from B to C. I think this not expected.

Will look into the comments. Apart from that I would like to move all error logic over to the new error handling in framework. After that I will undraft the PR

All comments should be addressed now. It was tested both in SIL as well as on real hardware.


Not able to resolve cross stack services by .

Rancher Version: Build from master
Docker Version:1.10.2
OS: Ubuntu 14.04 hosts
Steps to Reproduce:
Create a service in Default stack.
Create service "test1" in stack "hello".
Not able to resolve cross stack services by test1.hello , but I am able to resolve using by hello.test1.rancher.internal

@sangeethah I can't reproduce it....on the setup that you've given, the issue is no longer reproducible either. If you happen to see it again, could you pass an environment to me and @vincent99 for debugging?

Closing this issue for now. If I am able to reproduce this issue again will open a new issue.


Enable installing specific packages

It should be possible to install specific packages and not the whole platform. Especially since your platform is importing tons of items which may not be necessary, e.g. nx if migrations are not needed.

Hi @Tallyb
The idea of ngxtension is to be a single-stop-shop, which you can install, and use whatever you need, but only the things you use will end up in the bundle.
We probably will drop some of the code for migrations because most of them are already supported inside angular itself.
Also, everything we expose, can be easily copied inside your project, without having to install the whole lib.
cc @nartc

I understand your approach. However, as nx is one of your migrations dependencies, it can easily incur package discrepancies. How about separating the runtime and build time/migrations packages?


Epic: Active cooperation flow

Epic to collect user stories for active Student-Tutor cooperation and related activities like sharing study materials, leaving notes, feedback, finishing active cooperation.
Activity diagram that represents  high-level vision of the active cooperation flow:
https://drive.google.com/file/d/1jTFioeO4EAHXmQugatYNqVsgLkR0r0I1/view?usp=sharing
User stories list:
Status:
B - in progress, back
BD - done, back
F - in progress, front
FD - done, front
T - in progress, testing
Done - US is done
TBD - as the idea for the future but isn't high priority now; needs more discussion before user story creation
1. Feature: Cooperation Overview

№
User story
Link
Status
MVP

1
Student views cooperation details
#1261

2
Tutor views cooperation details
#1262

3
Student views Tutor's info
#1300

4
Tutor views Student's info
#1299

5

#

6

#

7
Tutor changes cooperation settings
#
TBD

2. Feature: Activities Management

№
User story
Link
Status
MVP

1
Tutor adds course into activities (no previously added activities)
#1275
Ready for review with QA

2
Tutor adds new module into activities (no previously added activities)
#1408

3
Tutor publishes all added activities instantly
#1276
Ready for review with QA

4
Tutor publishes activity starting from particular date
#1277
Ready for review with QA

5
Tutor publishes activity manually
#1278
Ready for review with QA

6
Tutor deletes activity
#1284

7
Tutor edits activity
#1285

8
Tutor reorders activities
#1286

9

#

10
Search courses while adding  to the cooperation
#
TBD

11
Sort courses while adding to the cooperation
#
TBD

3. Feature: Work with Activities

№
User story
Link
Status
MVP

1
Student views available study materials
#1263

2
Student views scheduled activities
#1265

3
Student views completed activities
#1273

4
Student works with activity
#1265

5

#

6
Progress bar
#
TBD

7
Search activities
#
TBD

4. Feature: Notes

№
User story
Link
Status
MVP

1
Student leaves public notes
#1267

2
Student leaves personal notes
#1266

3
Tutor leaves personal notes
#1280

4
Tutor leaves public notes
#1281

5

#

6
Pinned Notes
#
TBD

7
Notes with attachments
#
TBD

5. Feature: Cooperation completion

№
User story
Link
Status
MVP

1
Tutor initiates end of cooperation
#1279

2
Student confirms end of cooperation
#1268

3
Student leaves feedback for tutor
#1270

4
Students accesses study materials after cooperation has finished
#1269

5
Tutor leaves feedback for student
#1282

6

#

7

#

6. Feature: Notifications

№
User story
Link
Status
MVP

1
Student receives notification about new notes
#1272

2
Student receives notification about new activities
#1271

3
Tutor receives notification about new notes
#1283

4

#

5

#

6

#

7
Notification about deadlines
#
TBD

Notes meeting with PO from 15.11.23 :**

We will allow possibility to add more than 1 course into the cooperation. Modules from the new course will be added below the existing modules. If there are 2 courses, the title will be displayed from the 1st course.
Banner will be default for all cooperations (green gradient). Also the team plans to remove feature of  custom banner uploading.
It will be possible to delete resources in modules, the whole module and all activities in the cooperation.
Student will see all published resources but closed and open from will be  displayed as disabled.
Failed saving during editing - we will not implement scenario for such a case (at least for now).
Progress bar - nice to have feature, but we will postpone it for now. Since it requires tracking of items completed by Student and time allocated by Tutor for each activity.

Notes meeting with PO from 01.12.23:

We will keep only cooperation title, no courses titles are needed in activities space.
Category/subject/level should not be changed in the cooperation when adding/editing new modules/courses.


Custom Router Implementation

Description
Add custom router implementation. This mostly follows the RFC outlined here: https://github.com/Shopify/hydrogen/discussions/569
There are mainly 3 areas modified:

New <Route> component
Changes (breaking) to <Router>
Additive (non-breaking) changes to <FileRoutes>
New useParams() hook that can be used in both server and client components

See a more detailed explanation in the changset
Additional context
Try adding <Route> in various ways. Note, you lazily define a <Route>, as seen in the playground e2e tests. A limitation here is that you cannot render the fallback <Route path="*" page={<NotFound />} /> directly inside App.server.jsx, because hydrogen hasn't had time to lazily fetch all potential routes. You can only render  after all asynchronous routes have been fetched, and nothing matches.

Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[ ] Update docs in this repository according to your change
[x] Run yarn changeset add if this PR cause a version bump based on Keep a Changelog and adheres to Semantic Versioning

I was a bit confused about the fact that we render one router in App.server.jsx and another one in entry-client.tsx. I understand the latter is just a client provider. The question is, could that be wrapped in a client component and rendered by Router.server instead? Any cons to that?

Good feedback. I changed the name of the file to be BrowserRouter.client.jsx and moved it to be rendered inside Router.server.jsx instead of entry-client. Part of the reason it wasn't there in the first place was that it can't run in SSR, it expects a window/document global. I updated the component to just if (isServer()) return children. The thing is, it needs to be a client component, otherwise it doesn't get properly executed in time if a shared component.

Should we add types to request.ctx.router in ServerComponentRequest? Or perhaps it's just simpler with any like now, as you prefer.

Added types.

Could we use the catch-all route (<Route path="*" />) to implement a proxy to Shopify online store? It can fallback to <NotFound /> I guess.

100% this would be a great use case! In that scenario I think it would be the responsibility of the shopify online store to render a not found page.

@blittle Here's my commit on the Shopify.dev side, in case it's easier to copy this over to the routes.md file: https://github.com/Shopify/shopify-dev/pull/17397/commits/636344df2e6ee3883d7a0d16f3af264549b3e735

@blittle I found a few other instances of params where we'll probably need to update the code:

Example code in https://github.com/Shopify/hydrogen/blob/v1.x-2022-07/packages/hydrogen/src/components/Seo/README.md
Example code in https://github.com/Shopify/hydrogen/blob/v1.x-2022-07/packages/hydrogen/src/components/Seo/examples/seo.example.tsx
Example code in https://github.com/Shopify/hydrogen/blob/v1.x-2022-07/packages/hydrogen/src/framework/docs/routes.md#example

Here's the commit on the Shopify.dev side, for reference: Shopify/shopify-dev@913fe01

The new useParams() hook doesn't mean all of the other params need to change. Params are still passed as a prop to the root server component.

Thanks, @blittle!

The new useParams() hook doesn't mean all of the other params need to change. Params are still passed as a prop to the root server component.

Ah! Good to know, I'll revert https://github.com/Shopify/shopify-dev/commit/913fe0194773b4dad666e05b25a7f076961185fc then, since those changes aren't applicable.

that file looks old. It is still referencing /pages instead of /routes. Also other example code is out-dated.

Which file were you looking at? I didn't see any references to /pages, but I might have missed something!


https://projects.spring.io/spring-shell/ The '@ShellMethod' miss the open parenthesis

Maybe we can change it to
@ShellMethod(value = "Translate text from one language to another.")

Could you create an issue or a PR on the spring-shell repository? This content is actually managed here: https://github.com/spring-projects/spring-shell/tree/gh-pages

Could you create an issue or a PR on the spring-shell repository? This content is actually managed here: https://github.com/spring-projects/spring-shell/tree/gh-pages

Ok, I'll create a PR for them 👍


stops playing after some songs

I run latest version od raspbian:
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
.....
● raspotify.service - Raspotify
Loaded: loaded (/lib/systemd/system/raspotify.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-01-09 16:42:43 CET; 20min ago
Process: 1740 ExecStartPre=/bin/mkdir -m 0755 -p /var/cache/raspotify (code=exited, status=0/SUCCESS)
Process: 1741 ExecStartPre=/bin/chown raspotify:raspotify /var/cache/raspotify (code=exited, status=0/SUCCESS)
Main PID: 1742 (librespot)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/raspotify.service
└─1742 /usr/bin/librespot -u<EMAIL_ADDRESS>-p xxxxxxx --device hw:1,0 --name raspotify (raspberrypi) --device-type speaker --backend alsa --bitrate 160 -c /var/cache/raspotify --enable-volume-normalisation --volume-ctrl linear --initial-volume 100
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z ERROR librespot_core::session] Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z WARN  librespot] Spirc shut down unexpectedly
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z WARN  librespot_audio::fetch] Error from channel for data receiver for range 5503572 (+21076).
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z WARN  librespot_audio::fetch] Error from channel for data receiver for range 5487188 (+16384).
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z WARN  librespot_audio::fetch] Error from channel for data receiver for range 5409364 (+32768).
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z WARN  librespot_audio::fetch] Error from channel for data receiver for range 5442132 (+45056).
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z INFO  librespot_core::session] Connecting to AP "gew1-accesspoint-b-f6mh.ap.spotify.com:4070"
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z INFO  librespot_core::session] Authenticated as "wdklotz" !
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z INFO  librespot_playback::audio_backend::alsa] Using alsa sink
Jan 09 17:03:00 raspberrypi librespot[1742]: [2021-01-09T16:03:00Z INFO  librespot_core::session] Country: "FR"
### What causes this connection reset? How can it be corrected?

I have found the following:
This happens to me when the track to be played does not have a Title show up in the queue.
It clears the entire Play Queue.
It only happens when playing on Raspotify.
Log messages captured as follows:
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z INFO  librespot_playback::player] Loading <> with Spotify URI spotify:track:0nbDRhm5RCixXYioMBt0sx
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z WARN  librespot_playback::player] spotify:track:0nbDRhm5RCixXYioMBt0sx is not available
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z WARN  librespot_connect::spirc] The player has stopped unexpectedly.

I have found the following:
This happens to me when the track to be played does not have a Title show up in the queue.
It clears the entire Play Queue.
It only happens when playing on Raspotify.
Log messages captured as follows:
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z INFO  librespot_playback::player] Loading <> with Spotify URI spotify:track:0nbDRhm5RCixXYioMBt0sx
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z WARN  librespot_playback::player] spotify:track:0nbDRhm5RCixXYioMBt0sx is not available
Jan 25 09:36:15 raspberrypi librespot[16994]: [2021-01-25T16:36:15Z WARN  librespot_connect::spirc] The player has stopped unexpectedly.

It's a network issue.


Cortex M4 SMP mode support

Is this request related to a particular hardware platform, SoC, board? Please describe.
Some SoCs, such as TI AM572x, has Dual-Cortex M4 (IPUx blocks on diagram).
Describe why you are asking for this support?
TI supports Cortex M4 SMP mode with their TI-RTOS, but it is not pre-certified.
Additional context
TI AM572x block diagram:

Hi @AJIOB - we do not yet have Cortex-M SMP. Is there a reason you need SMP on Cortex-M cores?

Hello @goldscott. As I know, that is a single possibility to use both Cortex M4 for every IPU block.


fix stack overflow issue with recursive schema

Currently, if you add a self-referencing type to multiple APIs, a
StackOverflowError will occur. This change fixes that by not attempting
to add a type to an API that's already added.

Codecov Report

Merging #66 into master will decrease coverage by -0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #66      +/-   ##
============================================
- Coverage     79.68%   79.63%   -0.05%
+ Complexity     1622     1620       -2
============================================
  Files           154      154
  Lines          5438     5440       +2
  Branches        700      700
============================================
- Hits           4333     4332       -1
- Misses          832      833       +1
- Partials        273      275       +2

Impacted Files
Coverage Δ
Complexity Δ

.../api/server/spi/config/model/SchemaRepository.java
91.83% <100%> (-2.96%)
26 <3> (-2)

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 0cd4fe7...47e7fbf. Read the comment docs.


[WIP] ESLint: no-restricted-syntax

SUMMARY
Enable no-restricted-syntax rule
TEST PLAN
Run npm run lint and verify there are no new linter errors
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

@kgabryje is this ready to merge or is it still WIP?

@nytai It's still WIP

@nytai It's ready now, I added some more changes. There are more changes required for no-restricted-syntax rule, but I will push them in separate PR to keep this one small

Codecov Report

Merging #10889 into master will decrease coverage by 4.39%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10889      +/-   ##
==========================================
- Coverage   65.84%   61.45%   -4.40%
==========================================
  Files         815      382     -433
  Lines       38335    24130   -14205
  Branches     3601        0    -3601
==========================================
- Hits        25243    14828   -10415
+ Misses      12990     9302    -3688
+ Partials      102        0     -102

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
61.45% <ø> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/db_engine_specs/presto.py
81.61% <0.00%> (-0.68%)
:arrow_down:

superset-frontend/src/SqlLab/utils/sqlKeywords.ts

...dashboard/components/ColorSchemeControlWrapper.jsx

...erset-frontend/src/profile/components/Security.tsx

...t-frontend/src/explore/reducers/getInitialState.js

...rc/explore/components/controls/TextAreaControl.jsx

...src/dashboard/components/HeaderActionsDropdown.jsx

superset-frontend/src/explore/AdhocFilter.js

...rontend/src/messageToasts/enhancers/withToasts.tsx

...frontend/src/dashboard/util/newEntitiesFromDrop.js

... and 415 more

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 5623cd6...d25662b. Read the comment docs.

Sorry I noticed that the "Prefer Typescript" hook was not able to detect new jsx files so was trying to work on a fix. Rebased the branch and pushed by accident. But the rebase shouldn't contain any new code.


message bucket: collect messages and send in a single prompt

The POST /chat/{chat_id} receives one message at a time, when it receives it, it processes it in the llm and returns a message to you, example:

QA 1: hello how are you?
QA 2: I need help, can you help me, please?
QA 3: how do I perform operation XYZ on the web page?

This flow of conversation is common in a chat environment (e.g. WhatsApp), where the user breaks the line. What the user would like to receive is only the answer to QA 3, the other messages are introductory ("presentation").
As implemented today, we answer one message at a time:

Reply from QA1: Hi, how can I help?
Reply from QA2: It would be a pleasure to help you, how can I help you?
Reply from QA3: You should access, ... the answer to the question

the answer that matters is QA3, QA1 and QA2 are "duplicated"

solution
Parameter in the endpoint (POST, create message) called message bucket, which activates intelligence to collect messages in the backend and make a single call to the LLM sending the collection of messages.
I can think of a solution to collect requests and if no message is received at X after the last message received, call the LLM aggregating all the messages not sent.

it's not the best solution, but it's the solution that comes to mind at first - this issue is to discuss the best solution, probably the proposed solution is not the best

@avelino I'm thinking that we will need a message buffer that stores the messages for a certain period before sending them to the server. Would we need a Redis or Memcached server or would you implement this by hand?

Would we need a Redis or Memcached server or would you implement this by hand?

I don't want to define technology (database) but rather discuss architecture, so we deal with "storage" as a storage resource (redis, memcached or other) and not a solution to the problem.

bucket endpoint:

temporary solution for storing messages
control is on the client side and calls the created bucket and sends all bucket messages to the LLM

I don't like this solution, I believe that we wouldn't have "intelligence" on the server side, but on the client side.

"Intelligence" based on the delay time for receiving messages:

provisional solution for storing messages, activated by a "parameter" of the endpoint
if it doesn't receive messages for X amount of time, it collects all the messages not sent to the LLM and sends them all at once (to the prompt)

version "2" is the way I'd like to see it working, but one doesn't prevent the other

We can achieve this by checking how langchain implemented the approach on batch/streaming endpoints on langserve.


Fix various audio bugs

Fixes #81 by making the Audio, AudioSink (and other AudioXYZ) classes have a virtual destructor.  Because of this most wonderful of implicit C++isms, the SdlAudioSink destructor wasn't being called, causing it to leak its ownership of the audio device!
Fixes #82 by not reading from the ringbuffer if there is nothing in it.
Removes a spurious SDL_Quit from the destructor, which would have ruined everything had the destructor been called.
Pauses playback on the device during the destructor, thus making it actually stop instantaneously rather than about a second afterwards.
Completely destructs one Audio before loading another.  This currently means there's a large amount of delay between audio stopping on a Load and the Load succeeding, so this may need reverting or tweaking later.  A problem is that currently this is needed to prevent two SdlAudioSinks from opening the same device.  It'd be nice if we waited until the file loads before killing the device, so maybe the device should be acquired as soon as the first Play occurs, there should be a separate ArmDevice (or equivalent) method, the Load could take ownership of the original Audio and kill it when necessary, or Audio could be responsible for Loading.

Coverage increased (+0.09%) to 22.58% when pulling 8f7f3666591d0eac5007a13b5220511af2ff11c4 on mw-no-device-contention into 92163ab5a522b2fc986bdc5c6a8e2cc17d978c90 on master.


Add contributing guide

Please add contributing guide so that new users can contribute.

@priyankarpal Would you want to work on it?

@priyankarpal Would you want to work on it?

Yes, I want to work on this issue. Please assign me.

Created a PR. Hope it will merge soon


GnomAD variants within class configuration

Along the same lines as #233, refactor of variant annotation to move configuration that it's datasource-specific to the class itself.
It also includes the chain file within the project, so there is one less external dependency

Codecov Report

Merging #234 (a22b537) into main (219e2c8) will increase coverage by 0.00%.
The diff coverage is 80.00%.

@@           Coverage Diff           @@
##             main     #234   +/-   ##
=======================================
  Coverage   85.72%   85.72%
=======================================
  Files          82       82
  Lines        1856     1857    +1
=======================================
+ Hits         1591     1592    +1
  Misses        265      265

Files
Coverage Δ

src/otg/datasource/gnomad/variants.py
63.63% <87.50%> (+10.69%)
:arrow_up:

src/otg/variant_annotation.py
80.00% <50.00%> (-4.22%)
:arrow_down:


build: Automate manylinux wheels build

Codecov Report

Merging #6 (e57498e) into master (982c021) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           18        18
=========================================
  Hits            18        18

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 982c021...e57498e. Read the comment docs.

Codecov Report

Merging #6 (e57498e) into master (982c021) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #6   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           18        18
=========================================
  Hits            18        18

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 982c021...e57498e. Read the comment docs.


Unclebay contribute

You made the PR correctly, however the PR was made to the wrong project.
You made a PR to DavidMatthewFraser/first-contributions
But You want https://github.com/firstcontributions/first-contributions


preResolveTypes doesn't respect naming convention/prefix config options

Describe the bug

Let's say you have your config set to convert type names to pascalCase and prefix types with I. You also have a type in your GraphQL schema named My_Type_Yo.
When preResolveTypes is false and this type is part of a Pick, this will output something like
...
Pick < IMyTypeYo, 'id' >
...

However, when preResolveTypes is true, formatting related config is ignored:
...
        id: My_Type_Yo,
...

Expected behavior

I would expect the config relating to conversions (pascal case, prefixing, etc.) to be respected so that the output uses types that exist within the codegen, not the non-converted type names straight from my schema.
Additional context

Skimming through the preResolveTypes change (https://github.com/dotansimha/graphql-code-generator/pull/2107), it looks like the convert name function isn't being applied within the new {...}withoutPick methods.

Hi @joshlam
I'm not sure how to reproduce it. I tested it but the result it: id: string and not My_Type_Yo. Maybe I'm missing something, can you please provide a reproduction for this?

@dotansimha
Sorry, gave an incorrect example. The id will be coming from an enum.
Here is an example .graphql file:
type Information {
    entries: [Information_Entry!]!
}

enum Information_EntryType {
  NAME
  ADDRESS
  ...
}

type Information_Entry {
  id: Information_EntryType!
  value: string
}

Fragment:
fragment information on Information {
  entries {
    id
    value
  }
}

Generated types with  preResolveTypes false:
export type IInformationFragment = {
  entries: Array < ({
        __typename ? : 'Information_Entry'
    } & Pick < IInformationEntry, 'id' > &
    ...
)

Generated types with  preResolveTypes true:
export type IInformationFragment = {
    entries: Array < {
        __typename ? : 'Information_Entry',
        id: Information_EntryType,
        ...
    } >
};

Thanks, I'm taking a look :)

Fixed in: https://github.com/dotansimha/graphql-code-generator/pull/2284

@dotansimha Thanks for the fix! I'm running into an issue now though where types are no longer generated for some fragments, will investigate

@joshlam can you please share a reproduction?

@dotansimha
It looks like what's happening is that files that import other fragments aren't getting types generated.
Config:
overwrite: true
schema: path/to/schema
documents: src/**/*.gql
generates:
    codegen/graphql.d.ts:
        plugins:
            - 'typescript'
            - 'typescript-operations'
        config:
            namingConvention:
                enumValues: keep
                typeNames: change-case#pascalCase
            preResolveTypes: true
            typesPrefix: I
    codegen/graphql.schema.json:
        plugins:
            - 'fragment-matcher'

If I have two files
src/fragments/clickEventInfo.gql:
fragment clickEventInfo on ClickEvent {
  __typename
  .
  .
  .
}

and
src/fragments/blah.gql:
#import 'src/fragments/clickEventInfo.gql'

fragment blah on Blah {
  clickEvent {
    ...clickEventInfo
  }
}

A type will only be generated for the IClickEventInfoFragment.

Thanks @joshlam . I'm not sure it's related to those changes, maybe it's another change we did. Any chance you can open a new issue for that?

Yeah, it's a separate issue since encountering it with and without the preResolveTypes. Will open a new issue

I noticed when upgrading fro 1.4.0 to "<EMAIL_ADDRESS>. that I see diffs like this:

This is with preResolveTypes: true and enumAsTypes not set. Is this an intended diff? Just wanted to mentioned it before the next release 😄

@JKillian it's fine, because now enums are also resolved into a primitive value :)

Fixed in 1.5.0 🎉

@dotansimha I'm afraid there's still issues here I believe. For example, I have this fragment type:

this enum gets generated:

and this actual type gets generated:

Notice how CredentialDocument.status is the enum type DocumentStatus, but DocumentsTableFragment.statusis a string literal type. Unfortunately, this means thatDocumentsTableFragment.statusis not assignable toCredentialDocument.status` because of the way TypeScript handles string enums. This inconsistency in the generated types can lead to some tricky difficulties in user code.
Does this make sense? Let me know if you need more info or if I'm misunderstanding something!


Set upper bound for Python

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Closes https://github.com/coiled/coiled-runtime/issues/121
cc @ncclementi

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.

Thanks @jrbourbeau I'll merge this in!


feat: added delete methods for sample

closes #29

@jonstuebe Could you add an a delete button to the example app so it's possible to try it out as well?
I've made a some refactoring on the TypeScript side which improves typing and DX - sorry that it causes some conflicts. I hope it's not too much of a hassle 👍

Didn't mean to close this :( Can you re-open?

Got the example added!

Looks great - thanks @jonstuebe! Released in 5.1.0 🚀
One question is whether it's possible to catch delete errors when trying to delete external sources somehow? I've noticed I cannot delete samples coming from my Apple Watch for example - but it seems to just return success for this. I suppose it's the "typical Healthkit behaviour" of failing silently (as when fetching data the user has denied access to) - but maybe there is a way around it?

Looks great - thanks @jonstuebe! Released in 5.1.0 🚀
One question is whether it's possible to catch errors when trying to delete external sources somehow? I've noticed I cannot delete samples coming from my Apple Watch for example - but it seems to just return success for this. I suppose it's the "typical Healthkit behaviour" of failing silently (as when fetching data the user has denied access to) - but maybe there is a way around it?

Good question. I think you could possible check the metadata of the app and validate if it's the same as the sample that's coming back? 🤔


Fix indefinite duration on snackbar example and use proper root view for snackbar parent

Also:

Removed unused snackbar drawable files
Fixed “show long” snackbar text

the parmas parentView is getWindow().getDecorView() which is one kind of parentView.
Snackbar will walk up the view tree trying to find a suitable parent, which is defined as a {@link CoordinatorLayout} or the window decor's content view, whichever comes first.

On my test device (Nexus 6p), getWindow().getDecorView() causes the Snackbar to display over the system buttons. findViewById(android.R.id.content); results in the expected behavior (the Snackbar is displayed at the content view's bottom but above the software system buttons), at least on that device.


Recipe broken in Fabric 1.19 version

It looks like the tags being used in the default recipe do not exist, so you are able to craft luggage with an empty crafting table.

I confirmed this with a minimal modpack that included only REI, Luggage, and their respective required libraries.

Fixed in latest release


google-services.json file is missing

while running application on android studio it's showing warning like google-serives.json is missing.
could you please upload it once

Please create your own google-services.json file using your app package name & your personal Firebase account.
To download a google-service.json for an Android app:

Sign in to Firebase and open your project.
Click and select Project settings.
In the Your apps card, select the package name of the app you need a config file for from the list.
Click google-services.json.

After downloading file, paste the google-services.json file to your project’s app folder.
Thank you.

im asking about your project .json file
in firebase im not able to download that file

will you please mail it to<EMAIL_ADDRESS>


Adds an ELK Stack setup for Docker

Cool stuff! Is it possible to split each process to its own container? So a separate container for Elastic search, Logstash, Kibana (and maybe even nginx)?
Are the officials repos for Elasticsearch and Logstash re-usable at all?

@jamespamplin this should be as easy as possible to get running (and is at least initially intended only to be run in a dev environment) so i'm not sure adding the orchestration overhead is useful.

I am inclined to agree with @kenoir on this one. Because we don't yet use Docker widely, the target audience that I had in mind for this was people who aren't already using Docker and just want a quickstart way of getting Logging up and running. There will already probably be some overhead with running Docker and getting the options right when starting an instance of the container.
Having said that, it would certainly be a good idea to have a parallel Dockerfile that had more flexibility for people who had a better idea of how to use Docker effectively (not sure how to best apply DRY in Dockerfile-land though).


Implement Context-Based Mention Suggestions with "@"

Description
I would like to propose the implementation of a feature similar to ChatGPT, where typing the "@" character shows a list of suggestions or mentions. This would improve the user experience, allowing for easy mention of other users or commands.
Requested Features
When the user types "@", a context-based suggestion list should appear.
The list should include usernames, commands, or other relevant entities.
The suggestions should update in real-time as the user types.
Usage Examples
Typing "@" followed by the first few letters of a username should show a list of matching users.
It could also be used to suggest specific system commands, improving navigation and accessibility of available functions.
Benefits
Makes the use of commands and additional functionalities more intuitive.
Screenshot / Mockup

Hi @marcoserafini2.
As cool as this sounds there are currently have a lot of planned features with a higher priority and with the limited time that I recently have it will be difficult to implement it in the near future.
If you would like to have a go at implementing it yourself, you can fork/clone the project and follow the set up instructions which are very simple.
Apologies for not being able to commit to this feature, but we may consider adding it in the future.
Thankyou!


Reduce deepcopy for VarInfo

The current implementation of HMC/NUTS contains many calls to deepcopy for VarInfo. This substantially increases memory allocation and may deteriorate performance. Perhaps we can share the same VarInfo between leapfrog iterations that belong to a single HMC/NUTS proposal (or sample).

TODOs

[ ] Create separate builds for LDA and MoC, so that we can record performance changes for every commit.

What does "create separate builds" mean?

At the moment, we have benchmark.jl and runtests.jl on Travis. Perhaps we should separate lda.run.jl and moc.run.jl into separate builds so that we don't exceed the build time limits imposed by Travis.

I see!

Resolved in https://github.com/yebai/Turing.jl/pull/254


Minion (Specifically Skeletons) & Generocity Support

Are you planning to make Minion (specifically skeletons) and generocity support for auras any time soon (by that I mean the next 2-4 weeks). If you are not planning to do so, I would love to give it a try to make that functionality.
Also are you using Microsoft Visual Studio for this? There is a .sln file, however Im not sure how I am supposed to compile and debug the thing if I make changes. Is there a plugin or something for lua?
** Note that I am not good with lua, but could probably pick it up.

Minion support won't be coming any time soon, as there isn't really enough information available on how minion calculations work. I could conceivably add in health calculations (the program already does it for totems), but DPS calculations would be far more difficult, both due to the lack of information, and because there's no way to verify that the calculations are correct. You're welcome to try, though.
I do indeed use VS (with NPL_LuaLanguageService, although that's optional). Lua isn't compiled (well, not statically anyway); the source files are loaded and run directly. If you're looking to make changes, you have two options:

Edit the source files within your installation. If you used the installer (the .exe), you'll find them in "%ProgramData%\Path of Building". Once you make a change, you need to restart the program for it to take effect; after restarting it'll prompt to update, which will revert the changes, so ignore it.

Set up a development install. I haven't documented that process yet, but I recommend using this option for any serious development, so here's how:

Clone the repository somewhere; it's best to clone the dev branch, as that's where changes are committed first.
Extract runtime-win32-.zip into a different folder (outside the repository).
Create a shortcut to the "Path of Building.exe" in the runtime folder, and add an argument containing the path and filename of the "Launch.lua" in the repository.
You can now use that shortcut to launch the program. It will take a while to start up for the first time, as it needs to download the passive tree data, which isn't kept in the repository. Running from the repository will automatically enable developer mode, which has a few handy debugging features; most notably, you can now use F5 to restart the program in-place.

Are Minions going to be supported with the released spreadsheet which can be found here?

I still need to actually add support for minion calculations, which is hardly straightforward. It's likely to be a few weeks at least before I get anything working, maybe longer.

Added in 1.4.0.
Boy am I glad to finally close this one!


PS Integrated Console 'crashes' when trying to run any PS script

Opening any PS scrpt and running it, the PS Integrated Console crashes.
Problem signature:
Problem Event Name:	CLR20r3
Problem Signature 01:	powershell.exe
Problem Signature 02:	10.0.14409.1005
Problem Signature 03:	584a185c
Problem Signature 04:	System.Management.Automation
Problem Signature 05:	10.0.14409.1018
Problem Signature 06:	5bac3bc0
Problem Signature 07:	7aae
Problem Signature 08:	0
Problem Signature 09:	System.StackOverflowException
OS Version:	6.3.96<IP_ADDRESS>.272.7
Locale ID:	1033
Additional Information 1:	d34e
Additional Information 2:	d34e763b2334d493da43dffdedbbc013
Additional Information 3:	8a01
Additional Information 4:	8a014f3d872478b583b3a363b4438989

I wasn't able to repro this by creating a simple test script that echos a string and running in integrated terminal (as shown below).  Are there any additional repro steps that you could provide that would help diagnosis what's happening?
PS C:\Users\kburt\Desktop> .\test.ps1
test1

Closing as stale. Not enough info to investigate.

There’s been no communication asking for more info.
Regards,
Iain Barnetson
T:<PHONE_NUMBER>

From: Cheena Malhotra @.>
Sent: Tuesday, July 11, 2023 8:18:39 PM
To: microsoft/azuredatastudio @.>
Cc: Firmbyte @.>; Author @.>
Subject: Re: [microsoft/azuredatastudio] PS Integrated Console 'crashes' when trying to run any PS script (Issue #17839)
Closed #17839https://github.com/microsoft/azuredatastudio/issues/17839 as not planned.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azuredatastudio/issues/17839#event-9793522689, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACDVAP6UGC2KXO6Q6XEIDZ3XPX3O7ANCNFSM5JSABAJA.
You are receiving this because you authored the thread.Message ID: @.***>

Pasting as posted by @kburtram above:

I wasn't able to repro this by creating a simple test script that echos a string and running in integrated terminal (as shown below). Are there any additional repro steps that you could provide that would help diagnosis what's happening?
PS C:\Users\kburt\Desktop> .\test.ps1
test1


[Feature Request] Bigger server banner size

Describe the feature request
Get a bigger server banner image size for better quality.
Expected behavior
Getting a better quality image for a better life.
This probably needs a special function because from what I've seen here,
this plugin gets the image source from the element itself and the default banner size is 512.
It's not necessary feature but it would give a good experience.

yeah ik but when directly saving or viewing the image from discord itself.
as I said above "It's not necessary feature but it would give a good experience."

of course it's not hard to implement

of course it's not hard to implement
that would be a good addition to this beautiful plugin,
thx.


Failed to find NEWT Display Class <.windows.DisplayDriver>

Hi, need your help.I run your 'jogl-samples' project in eclipse, I select the helloTriangle.HelloTriangle.java to run, but error happened.

Hi lj52man,
jogl version?

Ps: be sure the native are located in the same directory.
https://jogamp.org/wiki/index.php/Setting_up_a_JogAmp_project_in_your_favorite_IDE
I created a lib called jogl, substitute the jar in that folder with those of your just-download (jogamp-all-platforms.7z)[http://jogamp.org/deployment/jogamp-current/archive/jogamp-all-platforms.7z]

Hey lj52man,
solved? :)

I am gonna close it, if you need help, just pop up  :wink:


No way to update a repo description

Repo descriptions are added with a pachctl flag (--description) at creation time, but that means there doesn't seem to be a way to update a repo description without deleting and recreating the whole repo

Fixed by #2218 (although it was kinda already fixed).


Model Checking Task Parallel Programs Using Gradual Permissions (N)

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7372041&punumber%3D7371449%26filter%3DAND(p_IS_Number%3A7371976)%26pageNumber%3D3

HJ-V and JPF-HJ:
http://jpf.byu.edu/jpf-hj/


Enrich tests configuration

A vsi's network interface with multiple security groups
src -> dst connection in which both sg and nacl effect is not trivial
nacl that imposes connection only on a subset of the ports

1: ...\vpc-network-config-analyzer\pkg\ibmvpc\examples\out\explain_out\VsiWithTwoSgs_all_vpcs_explain_detail.txt
2. E.g.: ...\vpc-network-config-analyzer\pkg\awsvpc\examples\out\explain_out\subnet_to_subnet_all_vpcs_explain_detail.txt
3. E.g.: ...\vpc-network-config-analyzer\pkg\ibmvpc\examples\out\explain_out\NACLQueryConnectionRules2_all_vpcs_explain_detail.txt


Display Leaflet map on home page

References User Story #16

[t:120]

Finally figuring out docker-compose, project is now building containers and I can see it running

[t:10]

Stubbing out code for leaflet data in react app


📖 Initial stab at documenting config options

Just based on reading the code and adding a bit of intuition

Superseded by #2 - I wanted to add more detailed docs and put it in a documentation site format that I can publish to GitHub pages. Thanks for taking a stab at writing an initial set of docs!


[Feat]: Show Active Page on Navbar

What feature?
We can add styling to show the active page. For example, if the user is on the about page, we can make the About link in navbar to have different styling that other links.
Add screenshots
Add screenshots
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Do you want to work on this @kailashchoudhary11 . Are you working under GSSOC23??

Hey @JasonDsouza212  yeah I would like to work on this. Also review #329  As well.

You can only be assigned to other issues only after you finish both of the assigned issues

You can only be assigned to other issues only after you finish both of the assigned issues

I've already made a PR for the other issue.


Allow overriding the ? query argument

Summary
Adds query_with_arg that allows using something other than ? for binding.
Just a simple workaround for #60 that I needed to get unblocked that I thought might be useful to others.
Checklist

[x] A human-readable description of the changes was provided so that we can include it in CHANGELOG later

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

So.. does https://github.com/ClickHouse/clickhouse-rs/pull/154 make sense once this one is merged?
If not, I'm sure we should think firstly about server parameters instead of extending API with the current syntax.


make all fails

If I just clone the git repo and run make all, I get the following error. I may be new at this, but this at the very least should point to some incompleteness in the Readme file which would have pointed me to the resource needed to fill my knowledge gaps.
Error applying plan:
1 error(s) occurred:

module.s3.aws_s3_bucket.pki: 1 error(s) occurred:

aws_s3_bucket.pki: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
status code: 409, request id: FCFE75F95FEFE173, host id: nvIosND/19mGDz/Dj9quII+0CfgbqXNgoIg1wsQ4y37EbyyN/TnfOREZQazNnmwGWhOvaBbBDDg=

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

It is the first time that you run make all? If not run make clean and make all or change the cluster name.

I tried make clean and make all and got the same error. Then I tried export CLUSTER_NAME=k8s and got this error:
Failed to parse input: unexpected end of JSON input

finish
'[' -z 6194 ']'
kill 6194
✗ create admin certificate - FAIL

make[2]: *** [create-admin-certificate] Error 1
make[1]: *** [post-terraform] Error 2
make: *** [all] Error 2
Maybe I should just ask this:
What is the bare minimum information I need to specify and change to get a sample working that I can start to tinker with?

On Aug 30, 2017, at 09:47, Yago Nobre<EMAIL_ADDRESS>wrote:
It is the first time that you run make all? If not run make clean and make all or change the cluster name.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kz8s/tack/issues/207#issuecomment-325995546, or mute the thread https://github.com/notifications/unsubscribe-auth/AEa73qyhYSwk7h9-2aLjNV4-AmVMd-W7ks5sdWgLgaJpZM4PHaMC.

You no need to edit anything, check in s3 if you have a bucket named ${AWS_ACCOUNT_ID}-${CLUSTER_NAME}-${AWS_REGION} and delete this

I deleted all buckets, but terraform had a lock on it. I tried make clean, and terraform destroy, then deleting the the tfstate file and again deleted s3 buckets. This time I get the following error:
003e"}
Failed to parse input: unexpected end of JSON input

finish
'[' -z 16794 ']'
kill 16794
✗ create admin certificate - FAIL

make[2]: *** [create-admin-certificate] Error 1
make[1]: *** [post-terraform] Error 2
make: *** [all] Error 2
I’m guessing if it couldn’t make an admin certificate, the user does not have proper permissions to do so.

On Aug 30, 2017, at 10:34, Yago Nobre<EMAIL_ADDRESS>wrote:
You no need to edit anything, check in s3 if you have a bucket named ${AWS_ACCOUNT_ID}-${CLUSTER_NAME}-${AWS_REGION} and delete this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/kz8s/tack/issues/207#issuecomment-326009939, or mute the thread https://github.com/notifications/unsubscribe-auth/AEa73oPqfeleI4u8aO7im2_FqMc4T7Wbks5sdXLogaJpZM4PHaMC.


Introduce automation test sending extrinsic to KAGOME

Automate the following scenario.
Environment: s1 (Kagome validator), s2-s4 (substrate validators)

Send transfer from Alice to Bob via s1
Make sure balances of Alice and Bob changed accordingly

Useful links:
https://kagome.readthedocs.io/en/latest/tutorials/first_kagome_chain.html
https://kagome.readthedocs.io/en/latest/tutorials/private_network.html

Part 1.
0. Build polkadot or use from docker. Info: https://github.com/paritytech/polkadot

Launch polkadot : ./target/releases/polkadot --dev
Go to https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F<IP_ADDRESS>%3A9944#/accounts and try to send transaction from Alice to Bob

Part 2.

Build KAGOME https://kagome.readthedocs.io/en/latest/overview/getting_started.html
Launch KAGOME ./build/node/kagome --dev
Go to https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F<IP_ADDRESS>%3A9944#/accounts and try to send transaction from Alice to Bob

Part 3.
Try to send extrinsic through Java substrate SDK
Part 4.

Bootstrap network of validators containing KAGOMe and Substrate
Send extrinsic to KAGOME, ensure it was finalized on Substrate


vendor-specific properties

@giraud, what's your opinion on vendor-specific prefixes?
I took a look at our codebase and I see many usages of -webkit-appearance and -webkit-overflow-scrolling. I know it's potentially a can of worms (if we add support for these properties, why not add it for everything). But maybe bs-css should cover some of the specialized props that do not have standard alternatives? For example, don't cover -webkit-flex/-ms-flex etc, but cover -webkit-overflow-scrolling? What do you think?

I prefer to not have any vendor prefix in the lib, there is always the possibility to create a function with unsafe in user app.


Add checking datasets before each tailored download

Also small refactor to make name of function more pythonic
Pull Request
Description
Checks each dataset when using the Data Tailor to see if its already been downloaded, before starting. This should hopefully reduce how long it takes to download the 15 minute data, and reduce duplication of work.
Fixes #189
How Has This Been Tested?
Unit tests

[ ] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

I've approved, the tests are failing but this is due to 5 min satellite down at the moment, i think

Should we do this at the start of getting the 5 mins data aswell? So if another Consumer starts running (dataset order is randomized) but then once we start putting the next image, we check if its downlaoded by the other consumer in the meantime?

Yeah, that's probably worth it
On Thu, Aug 17, 2023, 12:36 PM Peter Dudfield @.***>
wrote:

Should we do this at the start of getting the 5 mins data aswell? So if
another Consumer starts running (dataset order is randomized) but then once
we start putting the next image, we check if its downlaoded by the other
consumer in the meantime?
—
Reply to this email directly, view it on GitHub
https://github.com/openclimatefix/Satip/pull/190#issuecomment-1682131379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWWSN3EJLW6MQCOU6PJTO3XVX65FANCNFSM6AAAAAA3TUICYM
.
You are receiving this because you were assigned.Message ID:
@.***>

@peterdudfield tests now pass and it does it for both 5 minutely and 15 minutely data


Selecting BaseRating.GREAT progammatically makes the view only partially visible on the left

When i use smileRating.setSelectedSmile(BaseRating.GREAT); it makes the view invisible(only partially visible on the left) but the rest of the rating work okay during the initialization of the view .When you tap on any rating it reverts to the normal state.Cheers.

Can you attach the screenshot, So that I can clearly see the problem. Thank you :)

You can check out the first one(great) then the second (good) is okay :)

Really sorry for this, can you tell me the device model and if possible can you share the xml layout you created?

Here is the model and the xml file.Thanks :
Android build version: G900HXXS1CPJ9
Android release version: 6.0.1
Android SDK version: 23
Android build ID: MMB29K.G900HXXS1CPJ9
Device brand: samsung
Device manufacturer: samsung
Device name: k3g
fragment_about.txt

I have the same problem

Really sorry for the delay, came back after a long vacation. I couldn't find the problem. You are saying it is only happening on setting GREAT. Let's try one thing, try to set some size for the rating bar. Just set the width of the ratingbar. Height will be automatically taken care of. Let me know the output.

Yep, this help me to make it works correct. The problem appears when view width equals to display width. At first I just set width in layout file and this solve problem, so I tried to change width programmaticaly and when I set view width equals to display width it stop working again. For normal work, view width just should't equals to display width.
     Point size=new Point();         Display display=getWindowManager().getDefaultDisplay();         display.getSize(size);         mSmileRating.setLayoutParams(new LinearLayout.LayoutParams(size.x-1, ViewGroup.LayoutParams.WRAP_CONTENT));
Thanks a lot.


Beautysh does nothing

I installed beautysh as pip install beautysh, and then tried to run it but it did nothing.
~ ❱❱❱ python --version
Python 3.9.6
~ ❱❱❱ cat temp.sh
echo "meep"|grep "e";echo "no u"~ ❱❱❱
~ ❱❱❱ beautysh temp.sh
~ ❱❱❱ cat temp.sh
echo "meep"|grep "e";echo "no u"~ ❱❱❱

I tried this on some of my somewhat messy scripts and it did nothing apparently. I used the -b argument and it didn't even backup anything so I presume the program itself is broken somehow. Not well versed in python so I can't check it out.

Hi @starty-arty,

I installed beautysh as pip install beautysh, and then tried to run it but it did nothing.
echo "meep"|grep "e";echo "no u"

Actually there is nothing to beautify in your example. There is no best practice for using pipes and semicolons. So, beautysh does nothing.
But we agree that if statements should be formatted in a special way with indentation.
I recommend using beautysh on files containing lots of loops, if statements, etc.
If you try this example;
        if [[ $(id -u) != "0" ]]; then
echo "Error: You must be root to run this script."
else
echo "Installing ..."
        fi

will be changed to:
if [[ $(id -u) != "0" ]]; then
    echo "Error: You must be root to run this script."
else
    echo "Installing ..."
fi


Resource cleanup on Node.js process exit

A user came to the Node.js repo and raised an interesting and well thought out use case here that basically boils down to:
async function run() {
  let file;
  try {
    file = createFile();
    await doLongWork(file);
  } finally {
    await closeFile(file);
  }
}
run();

If the user interrupts the program with Control+C Node.js will exit the process and the file will leak and not be gracefully cleaned up which violates user expectations.
Some non-Node.js examples could be:

The user switching the tab to the background which causes JavaScript to stop running.
The user putting the computer to sleep when JavaScript is running in a tab.

Node.js could potentially reject the promise returned from closeFile but a rejection is not an error and users would no expect catch blocks to run. Ideally, Node.js would clean up "as if" the program exited "cleanly", this would be really easy in the old third-state proposal.
I am not sure if this is solveable in scope or a good idea to solve rather than address this in the docs but I consider this a possible footgun.

If the user exits the Node.js process, wouldn't the process automatically close all open file handles?
Also, suspending a program isn't the same as closing the program. If the program becomes suspended, what happens to a pending promise likely depends on what's being requested. Network file IO such as a fetch request will likely fail, while operations like setTimeout will "catch up" when the process/tab is resumed.  @@asyncDispose is handled just like finally, and would work just as the above code would work today. Other languages with similar features also have the same caveats due to a process exiting abnormally (i.e. crashing a process, loss of power, etc.), so solving that is out of scope for this feature.

I'm not sure if there's something actionable here. The using declaration semantics are built around try..catch..finally semantics. I could see how NodeJS might want to augment its own disposable objects to potentially dispose early and throw when a process exits, or provide an api to track user-defined disposables on process exit, but I wouldn't want to enforce this behavior globally.


”PlayReady Hardware DRM support“ does not work in the portable version

can fix it？

Sorry! I can't fix this on my end. Your graphics card or the card driver does not support this function. Because on my PC this is set to "true".

thank you ,
It should be my system problem, V79 can display true


TF 2.0 tf.image.non_max_suppression always output the length of max_output_size

tensorflow version: tensorflow-2.0.0-beta0
import tensorflow as tf

print(tf.__version__)

bbox = [[0,0,0,0],[0,0,0,0],[0.71619,0.3128575,0.7752377,0.37428612],[0.71619,0.3128575,0.7752377,0.37428612]]
scores = [2.4719129,1.701416,0.89775455,4.354542]

selected_index = tf.image.non_max_suppression(bbox,scores,3000,0.99)

print(selected_index)

and the output is
2.0.0-beta0
tf.Tensor([3 0 0 ... 0 0 0], shape=(3000,), dtype=int32)

I also tried tf.image.non_max_suppression_padded function with parameter pad_to_max_output_size=False and pad_to_max_output_size=True, the output shape is the same

I have tried on Colab with TF CPU version 2.0.0-beta and was able to reproduce the issue.

@JoelTsui
Can you please try with nightly version (!pip install tf-nightly) and let us know the whether the issue persists.I have tried and please find the gist here. Thanks!


To do list peer feedback

To-do list peer feedback
In this project, I:

Received feedback from my coding partner based on clean code best practices
Performed a simple code review for a coding partner

About the functionalities,  after removing a specific task from the list, when this same task is added again, it not automatically added back to the tasks lists. it only appears after multiple tries. Try checking this bug and fix it.
https://user-images.githubusercontent.com/119133987/229763354-d85424be-cc97-4831-a879-8fcaa25dadfa.mp4

Try implementing those changes and feel free to tag e if you need some enlightenment. ♻
Having done this, the project will improve 😄 💯 ✅


The PaymentIntent object

Hello,
I m trying to get into your Stripe project but have problems with some inconsistencies.
When creating a payment intent the method Stripe.createPaymentSheet expects three variables (paymentIntent, ephemeralKey, customer):
    const { paymentIntent, ephemeralKey, customer } = await this.http.post<{
    paymentIntent: string;
    ephemeralKey: string;
    customer: string;
  }>(environment.api + 'intent', {}).pipe(first()).toPromise(Promise);

Compared to the expected response found at https://stripe.com/docs/api/payment_intents/object I can not find all appropriate variables.
"id": "pi_1JKS5a2Tb35ankTn5AFisSig",
"object": "payment_intent",
"customer": null,
????
  <?php
[...]
\Stripe\Stripe::setApiKey('sk_test_...');
$intent = \Stripe\PaymentIntent::create([
'amount' => 1099,
'currency' => 'eur',
'payment_method_types' => ['card'],
]);
echo json_encode(array('client_secret' => $intent->client_secret));
?>
`
Which object variables do I have to put into the array for json_encode?

@Th-Barth  Hi, thanks for issue. Please check implements of server-demo:
https://github.com/capacitor-community/stripe/blob/master/demo/server/src/app.controller.ts
This is written in Node, but the essential process is the same.
Thanks.

Hi,
thanks for responding. Here is my current php test version now:
`
use Stripe\Stripe;
try {
\Stripe\Stripe::setApiKey('sk_test_51...');
$customer = \Stripe\Customer::create();
$ephemeralKey = \Stripe\EphemeralKey::create(
['customer' => $customer->id],
['stripe_version' => '2020-08-27']);
$intent = \Stripe\PaymentIntent::create([
'amount' => 100,
'currency' => 'eur',
'customer' => $customer->id,
'automatic_payment_methods' => ['enabled' => 'true']
]);
echo json_encode(['paymentIntent' => $intent->client_secret,
'ephemeralKey' => $ephemeralKey->secret,
'customer' => $customer->id]);
} catch (Error $e) {
http_response_code(500);
echo json_encode(['error' => $e->getMessage()]);
}
`
I got the final result "completed" after sending the card .
Today I had among other things a problem with the version transfer. I first always passed the version number of Stripe installed via composer on the server. But I had to pass the API version which is shown in the dashboard :-/ This caused an error in the server log:
PHP Fatal error: Uncaught (Status 400) Invalid Stripe API version: 2022-07-25\n thrown in /var/www/.../vendor/stripe/stripe-php/lib/Exception/ApiErrorException.php on line 38
What also surprised me is that try/catch could not catch this error.
And there is another error or app crash, when you press the close button of the card after presentation. Is this normal for this demo version?
I ve got another question. Why do I get in this demo just a very simple card formular? With the settings
'automatic_payment_methods' => ['enabled' => 'true']
I expected all payment methods for my region like listed on this page https://stripe.com/docs/payments/payment-element
Have I perhaps forgotten or misunderstood something?

@Th-Barth  This does not seem to be a question about this plugin. You should talk to the experts at stripe at https://github.com/stripe/stripe-php.
Best regards.

You re right, sorry. In the meantime I got some help from Stripe und I was able to implement stripe-elements into my project.

@Th-Barth  No worries. I'm glad you got it sorted out!
Did you use this plugin for production? If yes, please tell us what app. This help development this plugin.
👉 https://github.com/capacitor-community/stripe/issues/145
Thanks.


In-band data channel test failing

Describe the bug
The C# in-band data channel test is failing with what appear to be a race condition. Sometimes the opening side's channel stays in kConnecting state forever, making the test fail.
https://dev.azure.com/aipmr/MixedReality-WebRTC-CI/_build/results?buildId=11370&view=results
To Reproduce
Steps to reproduce the behavior:

See CI above; run the in-band C# test

Expected behavior
Test passes
Additional context
Not sure what's happening in details:

Initial investigation shows some likely race condition with the SCTP handshake, although it doesn't explain to me why that would have an impact on setting the kOpen state.
Data channel is functional for all intents and purposes, but its state is wrong.
Many users reported similar issues on many different implementations/platforms (Firefox, Chrome, etc.) and therefore there is a lot of noise when searching for info, with unrelated bugs leading to the same behavior.

@fibann you likely need to fix #348 first, and cherry-pick https://github.com/djee-ms/MixedReality-WebRTC/commit/6de8bb595aff176c11d1b0a71d277d6dd6cfd477, which was cherry-picked from somewhere but can't find where anymore. That branch also has some attempt to fix, but it didn't work.


Added support for cmake 3.17 to test/set_compiler_flag.cmake

With cmake 3.17-rc1 the compiler checks for MSVC fails. This is because the flag _flag_works is unset with unset(_flag_works CACHE) which is not sufficient. It must also be unset without the CACHE option.

I think at least some of the failling builds are unrelated, so I hope this change does not break anything.

For a reason I don't understand, conda now install openblas 0.3.6 by default instead of 0.3.7. I really don't have the time to investigate why, so I forced the version to 0.3.7 in #154. I think that rebasing your PR on master should ifx the issue.

I forced the version to 0.3.7 in #154. I think that rebasing your PR on master should ifx the issue.

Thanks! I'm testing this now as we speak...

Thanks!

Ok this looks indeed better... thanks @JohanMabille


New "insert text/bytes" brick

I would find it useful to have a step that adds additional text (or bytes) at the beginning or end of the input so far.  The use-case I'm trying to solve today is
Text (Base64 encoded string of salt) -> Base64 decode -> (New brick) Insert text at end (the password) -> Hash SHA1 -> Base64 encode -> Text output
If you provide some options, this could also be used to add padding.  Options would include

"add N times" (the default choice, add the exact text N times, default 1)
"add until length is a multiple of N" (If the input string is longer than needed, add only part of the string. If the input string is not long enough, add repeatedly until the length is reached.)
and if you really want to be fancy:
"add length of input value as" text or byte or word or dword or qword

Thank you for bringing up your use case. I definitely consider introducing a brick for appending content at the beginning or end of the payload. I'll get back to you when I start the implementation of it.


Alternate solution of Mediapipe.Net.Solutions

          Mediapipe.Net.Solutions no longer exists as of 0.9.1-mpu-0.9.1 as there are no proper maintainers for that API surface. Please consider using the raw MediaPipe API provided in the managed layer.

Originally posted by @sr229 in https://github.com/vignetteapp/MediaPipe.NET/issues/49#issuecomment-1447609928
Could you elaborate more on the solution suggested (using the raw MediaPipe API provided in the managed layer)?

See MediaPipeUnity on their examples. I'm working on porting those when I have the time.


Harmonize spacing

When reformatting in set language, have the ability to harmonize spacing around punctuation:
word ! Word? Word! Word ?
To
Word! Word? Word! Word?
Or
Word ! Word ? Word ! Word ?

Duplicate of #19.


Update and search operations fail when attributes contain dot

Hi @davidiamyou,
I noticed some issues using attributes that contain a dot in its own name (ie when I use the urn for extension attributes, using urn:ietf:params:scim:schemas:extension:enterprise:2.0:User like a complex attribute).
Mongodb does not allow the . within the attribute name, so:

Update fails if one of  the attribute of your resource contains a .
Search fails if you are searching for an attribute contains a .

I think a solution would be to set up a mapping between the attribute actual name and the key used within db (avoiding the usage of . in the db key string for mongodb, may be another db could have issue with other chars).
Could "assist" custom property suitable to support this mapping?

You are right, I haven't thought about that. And if mongo rejects dot within field names, it is certainly going to be a design flaw.
One way I can think of is to use a "dbName" assist field on the container of schema extension attributes. The implementation will be a bit different for v2, as I am separating out the definition of schema/schema extensions, resource type, and assist metadata into separate structures to allow cleaner definitions.
But thanks for bringing this up. I will make sure there's a test case for it in v2.


Cannot connect to Postgres database with space in name

My database is named "Foo Bar", but specifying this in the YAML as either name: Foo Bar or name: '"Foo Bar"' results in the following error.

In PdoAdapter.php line 83:
There was a problem connecting to the database: SQLSTATE[08006] [7] missing "=" after "Bar" in connection info string
In PdoAdapter.php line 80:
SQLSTATE[08006] [7] missing "=" after "Bar" in connection info string

Although it's not really intuitive, the correct way to specify this is: name: Foo\ Bar.


Error page not working

E.g. https://componette.org/webchemistry/invoice/

Fixed with https://github.com/contributte/componette-site/commit/2b4f153fb2350690be8f0f4e03acb77c98811685


tx_kernel::get_inputs MASM compilation test

This PR is stacked on the #198 and should be merged after it
This PR adds a MASM compilation test for tx_kernel::get_inputs call

@bitwalker After dealing with repeated tree detach (moved to the end of the treeify pass) I hit an issue where the loop header block (block2) was treeified for every predecessor except the entry block(block0) in #_ZN9wee_alloc15alloc_first_fit17h5cf1f963ec6ad59fE function because we're explicitly skipping treefication in our outer loop but the loop header block treefied later when It's reached through other predecessors. In the entry block, the original successor is referenced, which was detached during the treeification. This blows up in the inlining pass when the detached original loop header block (block2) is inlined into the entry block (block0).
To reproduce run cargo test get_inputs.

I cleaned this PR to contain only the tx_kernel::get_inputs compilation. It's ready for review and merge.

@greenhat You can remove the changes to the treeify pass here, and rebase on main, then we should be able to merge this.

@greenhat You can remove the changes to the treeify pass here, and rebase on main, then we should be able to merge this.

Done.


Statusbar icons for testnet added

...and the existing ones for main-net beautified for better readability.
Builds with Gitian and looks okay on Linux, Win and OSX.
Look:

Looks good for me :+1:


Move parse error output into the CST

Required to make the Language interface useful.

An initial cut of this doesn't need to insert nodes at the correct offset, just to get the API started,


not runable with Cocos 2.4.x

Hi @CocosTechLabs @barinbritva
Could you please help to check if we can have a version to run with 2.4.x editor pls?
I tried to merge but inside editor console it show some issue
Unexpected token (381:4) while parsing<EMAIL_ADDRESS>Error: Parsing file<EMAIL_ADDRESS>Unexpected token (391:4)
load script [@ton/cocos-sdk] failed : Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>Many thanks.

这个只支持 3.8.3以上的版本


Cannot debug Node.js applications in development environment

VSCode Version: Master Branch
OS Version: OS X Elcapitan 10.11.6 (15G31)

Steps to Reproduce:

Clone the master branch
Run ./scripts/npm.sh install
Open a folder with the javascript named test.js with a simple console.log statement
Try to debug using the node debugger
The following launch.json file gets created:

{
    "version": "0.2.0",
    "configurations": []
}

Updated launch.json as follows:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/test.js",
            "stopOnEntry": false,
            "args": [],
            "cwd": "${workspaceRoot}",
            "preLaunchTask": null,
            "runtimeExecutable": null,
            "runtimeArgs": [
                "--nolazy"
            ],
            "env": {
                "NODE_ENV": "development"
            },
            "externalConsole": false,
            "sourceMaps": false,
            "outDir": null
        },

Start debugging and then you get the following error:

No extension installed for 'node' debugging.

Is this the expected behaviour?
I was under the impression that built in extensions such as the node debugger would work out of the box.
Here's the output in the console window:
[56660:0721/120327:INFO:CONSOLE(222)] "%c[Extension Host] %cdebugger listening on port 5870", source: file:////<VscodePath>/out/vs/workbench/services/thread/electron-browser/threadService.js (222)
[56660:0721/120338:INFO:CONSOLE(80)] "No extension installed for 'node' debugging.: Error: No extension installed for 'node' debugging.
    at Object.create (file:////<VscodePath>/out/vs/base/common/errors.js:317:22)
    at file:////<VscodePath>/out/vs/workbench/parts/debug/electron-browser/debugService.js:557:67
    at ErrorPromise_then [as then] (file:////<VscodePath>/out/vs/base/common/winjs.base.raw.js:1436:50)
    at file:////<VscodePath>/out/vs/workbench/parts/debug/electron-browser/debugService.js:541:20
    at CompletePromise_ctor.CompletePromise_then [as then] (file:////<VscodePath>/out/vs/base/common/winjs.base.raw.js:1566:49)
    at DebugService.doCreateSession (file:////<VscodePath>/out/vs/workbench/parts/debug/electron-browser/debugService.js:480:16)
    at _this.runPreLaunchTask.then._this.messageService.show.message (file:////<VscodePath>/out/vs/workbench/parts/debug/electron-browser/debugService.js:450:38)
    at CompletePromise_ctor.CompletePromise_then [as then] (file:////<VscodePath>/out/vs/base/common/winjs.base.raw.js:1566:49)
    at file:////<VscodePath>/out/vs/workbench/parts/debug/electron-browser/debugService.js:445:76
    at CompletePromise_then [as then] (file:////<VscodePath>/out/vs/base/common/winjs.base.raw.js:1566:49)", source: file:////<VscodePath>/out/vs/workbench/services/message/browser/messageService.js (80)

@DonJayamanne yes, this is the expected behaviour. The node-debug extension lives in a different repository and is added to VS Code as part of the build process.
If you just clone the VS Code repo, node-debug is missing.
To fix this you can copy the node-debug extension folder from VS Code insider to ~/.vscode-oss-dev/extensions/

@weinand , thanks