Webchat keyboard focus not moving focus to new message on submission

Hi,
I've been asked to see if there a way for force the keyboard focus to move from an adaptive card action when pressed.
The idea being that the keyboard focus could then move to the new reply from the bot as a result or pressing the adaptive card action button.
Please let me know if there are any overrides that may help with this.
Kind regards

@LawrenceHarvey123 - Can you provide some additional details:

Which version of Web Chat are you using (4.15.x or something else)?
Which flavor of Web Chat are you using (WebChat.renderWebChat() or ReactDOM.render())?
To clarify, when a user clicks a button and the transcript window advances as new messages are processed you are wanting the focus to shift back to the send box, correct?
Are you able to share your code (minus any secrets / keys)?

In the meantime, I will research this and let you know what I find.

Hi @stevkan,
Please see below for the answers. It's also interesting to note that the behaviour also exists for PVA preview when using a "basic card". Essentially when clicking action buttons on cards from earlier in a conversation the incoming bot response to the button scrolls the user to see it. The keyboard focus is still locked on clicking the button. The user has to manually exit the card and scroll to see the response a second time. The ideal would be that the keyboard focus goes to the latest response or at least goes to the message box I guess.
- Which version of Web Chat are you using (4.15.x or something else)?
4.15.7
- Which flavor of Web Chat are you using (WebChat.renderWebChat() or ReactDOM.render())?
WebChat.renderWebChat()
- To clarify, when a user clicks a button and the transcript window advances as new messages are processed you are wanting the focus to shift back to the send box, correct?
Either the send box or ideally the latest response from the bot.
- Are you able to share your code (minus any secrets / keys)?
Not sure I can share the code I'm afraid. But as I said this is even the case for a basic PVA preview bot embed.
Using keyboard controls click an action button and notice how the keyboard focus is locked to the button pressed rather than moving to the response or message box in reaction.

@LawrenceHarvey123 - The simplest solution would be to set the focus on the send box after every message activity from the bot. Obviously, I can't say for certain that this won't interfere with other activities that might come thru since I am not familiar with the conversational flow of your bot. But, as it's based off of conditions, the most basic being if ( activity.from.role === 'bot' )..., you can adjust those to meet your needs.
const store = window.WebChat.createStore( {}, ( { dispatch } ) => next => action => {
  if ( action.type === 'DIRECT_LINE/INCOMING_ACTIVITY' ) {
    const activity = action.payload?.activity;
      if ( activity.from.role === 'bot') {
        document.querySelector( 'input.webchat__send-box-text-box__input' ).focus();
      }
  }
  next( action );
};

[ ... ]

window.WebChat.renderWebChat(
  {
    directLine: directLine,
    store: store
  },
  document.getElementById( 'webchat' )
);

This should suit your needs, but test this out and let me know.

Hi @stevkan ,
Thank you for this. Seems to be working for us.
Out of interest is there a way to shift the focus into the most recently received item or is it message box only you think?
Really helping us move forward, thanks again.

@LawrenceHarvey123 - Thank you for your patience. You should be able to focus on any element that is rendered. To do this you will need to consider the following:

Since there may be multiple cards already displayed that have the same element type or class, you will need to capture the last one to have rendered and act on that one.
There is a very slight delay between Web Chat receiving an activity and Web Chat rendering the associated HTML. It may be necessary to wrap a small time out (~50-300 ms) around the focus call in order to ensure the element exists on the page. In past tests, going much beyond 300 ms can result in any UI updates becoming noticeable. You will want to experiment with this, however, if even necessary.


update readme now that backend is registered

#3 is incredible! Thanks @rwegener2 and @jpswinski. Since you've got h5coro properly registered as a backend, xarray picks it up automatically and the user doesn't need to do anything special besides specify engine="h5coro"! I verified it's found locally with xr.backends.list_engines():

Do we want to add a link to h5coro docs for more info? I can add that here if so.

Thanks for these updates @JessicaS11!
I would say yes to adding a link to the h5coro docs, but unfortunately, we don't really have any documentation yet (other than the readme).


Wacky graph drawing problem

Clone this repo:
https://github.com/twodee/madeup.git
Scroll the graph down to commit d4bb5... which occurs on Jul 9 2015. The graph drawing is wrong; it looks like the commit loops around to point to itself. git lol shows otherwise. Fix it.

Might be the same or related problem: commit 09a2c07a should have just one parent (ec682f0), but it's confusing and it appears that Elegit shows multiple parents.
Adding print statements on commit helper objects at the end or RepoHelper.wrapRawCommits is consistent with what result should be (confirmed with git lol), so it appears that the problem is in our graph drawing.

Holy moly. Been digging. Turns out that the graph we draw is in fact "correct." The reason it looks wrong is because we've got multiple edges going in the same direction overlapping each other, which mucks up the picture. We need to make sure no two edges appear on top of each other.

At the command line, git log --graph by default does not show commits (necessarily) in date order, which we do. Instead, it shows them in topological order by default. (Every child appears above its parent.) That said, you can display by date order with git log --graph, and it still doesn't overlap; it uses a much more complex diagram. Easiest fix for now is certainly to go with topographical ordering. It should overcome all of these problems, though makes it harder to find a particular commit.

The place to update is TreeLayout.sortListOfCells. Create an alternative sorting method that does a topological sort instead.


Fix leaking issue when add lifecycle observer

Since the context is using ActivityLifeCycle. So trying to add lifeCycleObserver without remove when the view is being detached will causing leak memory issue.
The lifeCycleObserver is already remove itself once the lifeCycle is reached onDestroyed. But with activity, it will be never called until the activity is going on destroyed.

Since the context is using ActivityLifeCycle. So trying to add lifeCycleObserver without remove when the view is being detached will causing leak memory issue.
The lifeCycleObserver is already remove itself once the lifeCycle is reached onDestroyed. But with activity, it will be never called until the activity is going on destroyed.

The behavior for this flow has now been revised and adjusted by re-evaluating the LifecycleOwner on attach. Do you still the leak on the latest version?

Since the context is using ActivityLifeCycle. So trying to add lifeCycleObserver without remove when the view is being detached will causing leak memory issue.
The lifeCycleObserver is already remove itself once the lifeCycle is reached onDestroyed. But with activity, it will be never called until the activity is going on destroyed.

The behavior for this flow has now been revised and adjusted by re-evaluating the LifecycleOwner on attach. Do you still the leak on the latest version?

Is 5.1.5 the latest version ?

Since the context is using ActivityLifeCycle. So trying to add lifeCycleObserver without remove when the view is being detached will causing leak memory issue.
The lifeCycleObserver is already remove itself once the lifeCycle is reached onDestroyed. But with activity, it will be never called until the activity is going on destroyed.

The behavior for this flow has now been revised and adjusted by re-evaluating the LifecycleOwner on attach. Do you still the leak on the latest version?

The life-cycler you're using is activity lifecycle. The observer will be never removed in case activity not going on destroyed.
You should remove the observer while the RiveTextureView is going to detached.

Since the context is using ActivityLifeCycle. So trying to add lifeCycleObserver without remove when the view is being detached will causing leak memory issue.
The lifeCycleObserver is already remove itself once the lifeCycle is reached onDestroyed. But with activity, it will be never called until the activity is going on destroyed.

The behavior for this flow has now been revised and adjusted by re-evaluating the LifecycleOwner on attach. Do you still the leak on the latest version?

The life-cycler you're using is activity lifecycle. The observer will be never removed in case activity not going on destroyed. You should remove the observer while the RiveTextureView is going to detached.

The latest version is 6.0.0, is that what you're using?
Changes were introduced here but we're not referencing the Activity directly.


Trim down included js library

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Rustls feature

I am building a project that runs on Linux MUSL, so OpenSSL cannot be used. This crate would be an absolutely awesome alternative to the sqlx crate if it could use Rustls instead.

@recapitalverb the past few days, I implemented a cargo feature for rustls ... Though I don't have the time to test it, hence no PR.
If you need it urgently, feel free to have a look: https://github.com/super-horst/oxidizer

that's amazing @super-horst ! we really appreciate that. If u want u can open the pr and we can help test it and write some test cases for it

Seems like the RFC is merged! 🎉 Should this issue be closed then?

Yes! For now you need to use the main branch. We will issue a new release once all deps are ready to use tokio 0.3 :balloon:


Multi-process not supported

Chuck works perfect with single-process. But when coming to multi-process, it crashes.
The cause is ChuckContentProvider.TRANSACTION_URI. In another process, Conprovider.attachInfo(Context, ProviderInfo) seems to be not called, thus ChuckContentProvider.TRANSACTION_URI gets null. If we make a request in another process, NullPointerException occurs while saving data into database.

The same problem occurs to me, how you solve the multi-process?

@CKJOKER It seems that the author has no intent to support multi-process. I use chuck with source code instead of aar from maven, and I change some code. The value of ChuckContentProvider.TRANSACTION_URI is assigned with my package name when declared. So whether ContentProvider.attachInfo(Context, ProviderInfo) is called or not doesn't matter.


[software architecture question] point cloud on 3rd party app

Hello,
I would be interested in transmitting the full pointcloud (from all the sensors with the rotation/translation) to a 3rd party app, probably open frameworks, on another computer/ other OS.
Do you have any idea on where to get this full point cloud in the code or if not, where to get the pointclouds seperately?
Also, would you recommend a transmission protocol to get this done? PCL seems the best, but I'm just asking.
Great work on the gnocchi version!
Alex

Hi Alex
The registered point cloud can be accessed via ROS topics.
If you are just looking to display it, you can make use of Rviz  see here  but if you are looking to extract it, you have to write some code using a ROS library.
Please let us know if you have any other questions
Simeon


cpu_credits = "standard" results in "T2 Unlimited"

module "wat" {
  source  = "terraform-aws-modules/ec2-instance/aws"
  version = "1.11.0"

  instance_count = 1

  name                        = "wat"
  ami                         = "ami-01945499792201081"
  instance_type               = "t3.large"
  cpu_credits                 = "standard"
  subnet_id                   = "${element(module.vpc.public_subnets, 0)}"
  vpc_security_group_ids      = ["${module.security_group.this_security_group_id}"]
  associate_public_ip_address = true
}

results in:

Thanks for this bug report.
I have just released v1.12.0 where this has been fixed.


Update dataweave-formats.adoc, correct JSON skipNullOn section

The skipNullOn section for JSON had a description copied from the XML section. It has been updated to match runtime behaviour and now refers to arrays, objects instead of elements, attributes.
Included is one small examples.

I signed the contributor's agreement now :-)

example exists: https://docs.mulesoft.com/mule-runtime/4.3/dataweave-cookbook-set-reader-writer-props
closing due to age and lack of sig


Deadlock when using both read and write in the same handler

Having read an issue in axum-login I realized that it's really easy to get a deadlock with the current API of this crate. Since ReadableSession and WritableSession both using the same underlying resource behind an RwLock.
A simple axum handler to reproduce:
async fn deadlock(mut _write_session: WritableSession, _read_session: ReadableSession) {}

and this can be solved if you release the lock guard
async fn deadlock(mut _write_session: WritableSession, read_session: ReadableSession) {
    // do the read here..
    drop(read_session);
    // write operations get to run here..
}

This issue becomes especially awkward and more subtle when this becomes an implicit bound, just like here. AuthContext needs a write access, but also there's a session read in the same handler. The developer must be familiar with the implementation details of these structs to know to release the read guard.
I don't really know how to solve this with the current API, but I'm experimenting..

Why is Session behind a RWLock? Is the underlying implementation not thread-safe @maxcountryman?
Also from my quick glance at async_sessionit seems there's no division between a readable and writable version as implemented by this crate.
Maybe removing this division and the RWLock is a solution for this issue?

Why is Session behind a RWLock? Is the underlying implementation not thread-safe @maxcountryman?
Also from my quick glance at async_sessionit seems there's no division between a readable and writable version as implemented by this crate.
Maybe removing this division and the RWLock is a solution for this issue?

We've been iterating on this previously here. I personally avoid this issue by using a wrapper over async-session and this middleware, but we discussed this in #5 that this solution is kind of unfortunate and ugly. That being said, async-session's API is probably stable enough.

I'm certainly open to improving and changing this.
The reason we have to use interior mutability is because the underlying Session implementation has its own Clone semantics which unfortunately blow away the cookie value (this means we can't clone it directly if we want things like regenerate to work). And because we need Send and Sync to provide the extension, we're limited to a lock or similar if we use the current approach.

Seems like not Cloneing the cookie_value was intentional. I suggest to create a new RFC-like issue to plan a new breaking change to fix the problem mentioned here and chart a new roadmap for the interface of this crate. What do you think @maxcountryman, @Ptrskay3?
In reality a simpler change to just fix this problem would possibly be to use some kind of reentrant/recursive lock. There's no recursive Mutex  or RWLock implementation available ATM for async contexts and in reality needing a reentrant lock usually means there's some architectural problem in place (which there is, hence this task).

Yes, I knew that Clone on cookie_value was intentional. Because of we discussed this earlier and went down the interior mutability way I tried to present this as a non-API breaking thing, but it seems it might not be possible (or I don't know how to solve it yet).
I'm certainly not against a new API. A fairly simple solution is what I mentioned above (the wrapper over async_session). Did you have the chance to look at it?

@Ptrskay3 yes, seems reasonable in my opinion.

Another thing to point out here is that it's unclear how often users are going to run into this in practice. It's a bigger issue with axum-login because of the way that library implicitly leverages WritableSession. The reason I mention this is because there's also an opportunity to consider if that library would be a better place to address this. (Of course, other libraries that use axum-sessions in a similar manner would potentially run into the same issue, so that's worth pointing out.)
Additionally, it may be worth investigating with async-session: what would they intend library authors do in situations like this? While the semantics of Clone make sense for direct consumption (it's a nice way to enforce certain properties of the session lifetime through the type system) it's unclear to me if that holds for libraries that consume async-session. Were there some escape hatch for this behavior, then interior mutability wouldn't be needed at all.

@maxcountryman correct me if I'm wrong, but I think the WritableSession allows both for read and write operations? If yes then maybe just changing the name from WritableSession to ReadableWritableSession or RWSession (or just Session) and specifically either forbidding a situation when someone requests a ReadableSession and RWSession at the same time or clearly stating in the docs the "gotchas" in this case (the required drop) would solve this situation for now.
If there's some way to forbid this situation in the code - a compilation error or even a runtime panic in the worst case - this issue is solved without any major changes to the API. We'd just need to change the docs slightly.

I think it's a fairly common thing to both read from and write to the session in the same handler. A straight forward examples are OAuth or Two-factor authentication. In my opinion the root cause of this issue is in this repository, and this is were it should be addressed - that's why I opened the issue here.
RWSession seems to be a good idea, but I think it doesn't solve the issue with axum-login: the library's AuthContext extractor still holding onto the lock, and the users needs to be aware of that if they want to use either ReadableSession or WriteableSession.

I would propose replacing the ReadableSession and WritableSession extractors by just using the session handle.
The handle is added as Extension to the request anyway and can be extracted:
https://github.com/LeoniePhiline/axum-csrf-sync-pattern/blob/main/src/lib.rs#L151-L162
Guards should only be acquired as long as they are needed, and dropped afterwards.
Or did I miss anything in my CSRF synchronizer token middleware? The write guard is dropped before calling the inner service.
However, the middleware is of course awaiting many times between its start and its passing the request on to the inner service. Is there any chance this will cause a lock, e.g. in parallel requests using the same session? I would even think the session write lock should be held in that case, to avoid race conditions.

I would propose replacing the ReadableSession and WritableSession extractors by just using the session handle.

This is possible, but I'm not sure how obvious the API is. The tradeoff is the caller needs to directly manage the guard. This might be fine (it does make it explicit which seems to be part of the problem of abstraction here).
To your point, this is already possible with the current implementation: applications can choose to use the SessionHandle instead.


web login

Is it possible to web login on the existing network ?

Don't really understand what you are asking. The repeater itself has no web interface so far. Web traffic is forwarded without any problem. To access a server in the NATed subnet, you will need a port forward, e.g.:
portmap TCP 80 <IP_ADDRESS> 80

When i am connnected to a hotspot i am used to see a login page when i
first acces the internet.  This login is not shown when i range extend the
hotspot with your router although i can see the router is connected.
Verzonden met AquaMail voor Android
http://www.aqua-mail.com
Op 26 mei 2017 14:26:09 schreef martin-ger<EMAIL_ADDRESS>
Don't really understand what you are asking. The repeater itself has no web
interface so far. Web traffic is forwarded without any problem. To access a
server in the NATed subnet, you will need a port forward, e.g.:
portmap TCP 80 <IP_ADDRESS> 80
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/martin-ger/esp_wifi_repeater/issues/43#issuecomment-304270229

The login-page of an open hotspot is usually implemented by a captive portal, i.e. a DNS redirect. When the esp_wifi_repeater connects, it just does the WiFi-connection without any Web- or DNS-request. But when you now connect to the esp_wifi_repeater with a browser (smartphone or laptop), it will do an DNS-request and it will show up with the login page. You only have to login once, as this registers the MAC and the IP of the esp_wifi_repeater, which will be reused ba all other devices that connect through it later. Hope this explains...

I expected the mechanisme you discribe. When i open the browser it tries
google and should be redirected but in fact it stops and times out.  The
redirection should go to a network ip on port 8880 .
I will first try an an other hotspot to see if i can get a connection
Thanks so far
Verzonden met AquaMail voor Android
http://www.aqua-mail.com

The problem is partly solved.  Its probably caused by low wifi signal.
Closer to the wifi ap i could connect to the hotspot so we can close the
topic. What should the power value show in the show stats list.
Verzonden met AquaMail voor Android
http://www.aqua-mail.com


OAuth support for MFA

This will fix #2, and is built on top of #1.
~This is a breaking change in the API (replacing gettoken with get_info), so likely will require something like a new major version.~ It's now backward-compatible.
The token can be provided on init, e.g.,
>>> import auroraplus
>>> api = auroraplus.api({'access_token': 'xxx', 'token_type': 'bearer'})
>>> api.get_info()
>>> api.serviceAgreementID
'nnn'
>>> api.getday()
>>> api.day['SummaryTotals']
{'DollarValueUsage': {'Other': 0.0, 'Total': 0.0, 'T140': 0.0, 'T93OFFPEAK': 0.0}, 'KilowattHourUsage': {'Total': 0.0, 'T140': 0.0, 'T93OFFPEAK': 0.0}, 'DayContainsSubstitutedUsage': False, 'HasDailyBillSegments': False}

or fetched semi-interactively (wip).

I've re-added a layer of backward compat: if giving an empty username and just the access token string as the password (e.g., in HomeAssistant config), it may just work without code changes.
I also added and documented a methods to issue a new token. tl;dr:
>>> import auroraplus
>>> api = auroraplus.api()
>>> api.oauth_authorize()
'https://customers.auroraenergy.com.au/auroracustomers1p.onmicrosoft.com/b2c_1a_sign_in//oauth2/v2.0/authorize?response_type=code&client_id=2ff9da64-8629-4a92-a4b6-
850a3f02053d&redirect_uri=https%3A%2F%2Fmy.auroraenergy.com.au%2Flogin%2Fredirect&scope=openid+profile+offline_access&state=...&client_info=1'
Follow the URL above in a browser to authenticate with username+password and
MFA. This will redirect to an error page (Cradle Mountain). Copy the full URL,
of the error page and continue.
>>> api.oauth_redirect('https://my.auroraenergy.com.au/login/redirect?state=...')
{'id_token': 'ey...', 'access_token': 'ey...', 'token_type': 'bearer', ...}

The api object is now ready to use. The token returned in the last step can be saved for later use when re-initialising the api object without having to follow the OAuth flow to obtain a new authorisation.
@slothking87, wanna give this a go?

Yep - I'll give it a go later tonight

Hmmmm - Im probably missing a step here somewhere.  Visiting that link just gives me a "sorry, but we are having trouble signing you in" message.
On the plus side - the install of the new version seemed to work fine this time - it throws this error which is to be expected I guess
2023-11-24 19:30:20.040 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up auroraplus platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/auroraplus/sensor.py", line 98, in async_setup_platform
AuroraPlus = await hass.async_add_executor_job(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/auroraplus/sensor.py", line 96, in aurora_init
session.getmonth()
File "/usr/local/lib/python3.11/site-packages/auroraplus/init.py", line 89, in getmonth
self.month = self.request("month", index)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/auroraplus/init.py", line 63, in request
+ self.serviceAgreementID
^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'api' object has no attribute 'serviceAgreementID'

Ah, no, I meant try the lib itself. There still is some work needed to make the HA integration take it.
Olivier Mehani @.***>
Sent from my mobile, please excuse my brevity.

See if you can authenticate as per the readme.md, and get some data out in a Python console.
Olivier Mehani @.***>
Sent from my mobile, please excuse my brevity.

I just had a play with it and it's working for me. Thanks a lot for fixing!

Looks like there is a problem when upgrading HA to 2024.1.2 - I get an error that the minimum version is 2023.6.0
Rolling back now - but just flagging it as something that might need looking at

Did you get the full error message?
Olivier Mehani @.***>
Sent from my mobile, please excuse my brevity.

I did now - breaks with an upgrade, but fine after a downgrade
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 842, in get_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 859, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/auroraplus/sensor.py", line 39, in
from homeassistant_historical_sensor import (
File "/usr/local/lib/python3.11/site-packages/homeassistant_historical_sensor/init.py", line 39, in
raise SystemError(msg)
SystemError: Running HomeAssistant 2024.1.2, Minimum required version >=2023.6.0
and
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 842, in get_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 859, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/auroraplus/sensor.py", line 39, in
from homeassistant_historical_sensor import (
File "/usr/local/lib/python3.11/site-packages/homeassistant_historical_sensor/init.py", line 39, in
raise SystemError(msg)
SystemError: Running HomeAssistant 2024.1.2, Minimum required version >=2023.6.0
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config.py", line 1483, in async_process_component_config
platform = p_integration.get_platform(domain)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 851, in get_platform
raise ImportError(
ImportError: Exception importing custom_components.auroraplus.sensor
and a kind little note
STATE_CLASS_TOTAL was used from auroraplus, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL instead, please create a bug report at https://github.com/LeighCurran/AuroraPlusHA/issues

Hum, I think this error is better followed up on https://github.com/LeighCurran/AuroraPlusHA#9, as it's to do with the HA integration, not the underlying lib.


Apr eco kbs Round 1

Publishing this branch so maybe we can review the kb article on live site with partner later today.  Will create another branch for other docs we're publishing today.  Thank you!

Made the change that Nathan suggested, removed the ***** stuff.


Event height is incorrect for 15 minute slots

When the start and end times are 15 minutes apart, the height is rendered as if it's a 30 minute slot.

I think there's a min-height of 20px set on events (using css). You should be able to override this though.

The height of the 15-minute event is actually more than 20px. So, I know
the min-height isn't the problem. But it's good to keep in mind, in case I
make event cell smaller, thanks.
I see that calculation of the height is the same as 30-minute events.
The time range is from 8am - 5pm, total of 540 minutes. Thirty minutes give
5.55%, and that's exactly what I see for the 15-minute event. It should be
2.77%. There has to be something wrong with the event height calculations.
ᐧ
On Sun, Feb 18, 2018 at 7:41 AM, Tobias Andersen<EMAIL_ADDRESS>wrote:

I think there's a min-height of 20px set on events (using css). You
should be able to override this though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/intljusticemission/react-big-calendar/issues/731#issuecomment-366524780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFjTTyAcOaBs1BhTo6O7VNO8Z49z-nHks5tWESRgaJpZM4SJIBh
.

Can you please provide a repro using the code sandbox in the issue template thanks!

https://codesandbox.io/s/wjjq8k6ow
I created an event called "Event shorter than step" for 3/10/2015.
I think I know what the problem is. It seems the minimum height is based on the time-step. By default, the time-step is 30 minutes, so anything shorter will not have its actual height.
I bypassed this by setting the steps to 5 minutes and overriding the css to remove the step borders. That should cover most events, but not for events with time durations that are not a multiple of 5.

Any update on this?

I was also having issues when two 15 minute events where back-to-back. The style of the events would be like when events are at the same time.
<Calendar
    ...
    defaultView="week"
    views={['week']}
    step={15}
    timeslots={4}
/>

.rbc-event {
    //fix 15 minute events overlapping their timeslot
    min-height: 5px;
    //fix back-to-back 15minute event overlapping style
    width: 100% !important;
    left: 0% !important;
}


The log given by the failure.

Desired functionality.

Mention any other details that might be useful.

Hello guys,
I want to use postcss to with Angular CLI to make template RTL via rtlcss, I use this tutorial guides  but it not worked and this error appear in terminal.
PS E:\Work\ng2-admin\ng2-admin-rtl> ng serve

It seems like you're using a project generated using an old version of the Angular CLI.
The latest CLI now uses webpack and has a lot of improvements including a simpler
workflow, a faster build, and smaller bundles.

To get more info, including a step-by-step guide to upgrade the CLI, follow this link:
https://github.com/angular/angular-cli/wiki/Upgrading-from-Beta.10-to-Beta.14

any solutions?

@mmdsharifi Article uses an old version of CLI. Which is why you are getting the error. The current version of CLI uses postcss. If you want to customize it further you can use eject command to eject webpak config and make changes and run the project.

Closing as answered, thanks @sumitarora !


Adding 2 tools sites

Adding basic support for kittytools.herokuapp.com and
kittygenerations.herokuapp.com

I tested it and works ok but it gives some errors on the third party sites.

Can you let me know what those errors are? I didn't see any errors on the pages, but maybe I just didn't notice them.

Kitties with bun in oven or resting give a textContent undefined error

Ah, from the console. My apologizes, I was just looking at the page output to see whether it was able to show the data I was wanting, wasn't actually looking at what else happened behind the scenes. I'll investigate and see if I can exclude other mainsite features from the extra sites.

Good job


export in other formats

now the export option is png but exportation in other formats is easier to adapt it, especially since saving in not (yet) possible

In which other formats would you like to be able to save the diagram?


ERROR: pull access denied for shop-ca

dev@dev-VirtualBox:~/Downloads/build-blockchain-insurance-app$ docker-compose pull
Pulling shop-ca (shop-ca:latest)...
ERROR: pull access denied for shop-ca, repository does not exist or may require 'docker login'

Same issue, any workaround?

I did not try, but I suppose if you are using Windows OS you need to use other binaries for that. All existed now are for Mac OS.
it is necessary to run get-fabric-images.sh in the root of the repo.

I am running in on a linux VM, I dont see a file named get-fabric-images.sh in the repo. Let me know if I am missing anything.

I mean that it is necessary to this.
install the Hyperledger Fabric platform-specific binaries.
curl -sSL https://goo.gl/byy2Qj | bash -s 1.0.5

@rslu2000  still facing same error
Pulling insurance-ca (insurance-ca:)...
ERROR: pull access denied for insurance-ca, repository does not exist or may require 'docker login'

Hi All,
I have the same error in Ubuntu 16_04 on VirtualBox:
ERROR: pull access denied for shop-ca, repository does not exist or may require 'docker login'
Issue command docker login & can login successfully. But the same error still happens when I tried to run:
./build_ubuntu.sh
Any help?

ERROR: pull access denied for shop-ca, repository does not exist or may require 'docker login'
same error,any workaround?


Theme not appearing in search results on the site

Hello,
I can access my theme's intro page that jamstackthemes.dev renders through the URL :
https://jamstackthemes.dev/theme/gatsby-netlifycms-blog-web-app/
However, my theme doesn't appear in the search results, using filters like
SSG -> Gatsby,
CMS -> NetlifyCMS,
CMS -> Bulma,
ArcheType -> Blog
It's pretty much possible many other sites might also be having the same issue of NOT being iuncluded in the search results.

Just tested it and it is working


Commodity directive and format subdirective implementation

I'm submitting a ...
[ ] bug report
[ * ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

The commodity directive needs to be implemented as per the hledger documentation.
The format subdirective needs to be implemented alongside the commodity directive.
Subdirective comments are supported below the commodity directive in any order relative to the format subdirective (if present).
All other subdirectives are ignored and should not cause parsing errors.
We should examine other directives and how they handle subdirectives. Notably, the format subdirective should be ignored under all other directives and should not cause parsing errors.
Additionally, we should also implement the default commodity directive (or D directive) as it is functionally identical to a commodity directive without the format subdirective.

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

N/A

We should examine other directives and how they handle subdirectives. Notably, the format subdirective should be ignored under all other directives and should not cause parsing errors.

The format subdirective is invalid under the default commodity (D) directive. Subdirective comments are successfully parsed/ignored.

Work is ongoing in https://github.com/darylwright/hledger-parser/tree/feature/commodity_directive

Regarding the following points:

All other subdirectives are ignored and should not cause parsing errors.
We should examine other directives and how they handle subdirectives. Notably, the format subdirective should be ignored under all other directives and should not cause parsing errors.

This is something that concerns the behaviour of subdirectives in all top-level directives, and is therefore beyond the scope of this already large feature. It's debatable whether we should respect hledger behaviour here or not, especially given that it concerns subdirectives that are invalid anyway. This could also risk creating unnecessary clutter in the parsing diagrams, making them less readable. Disregarding the above two points for now.


Error Reporting for Batch mode

I am attempting to run PRIDICT in batch mode, and keep getting exceptions but I am not able to trace the error itself. I have attached my csv as an example... with this command
python pridict_pegRNA_design.py batch --input-fname design.csv --use_5folds --nicking --combine_results
design.csv
Calculating features took 19.3 seconds to run.
Deep model took 79.3 seconds to run.
-- Exception occured --
Length of values (2290) does not match length of index (459)
1it [00:28, 28.12s/it]
1it [00:07,  7.46s/it]
1it [00:28, 28.56s/it]

Calculating features took 18.8 seconds to run.
Deep model took 84.2 seconds to run.
-- Exception occured --
Length of values (2289) does not match length of index (459)
1it [00:02,  2.46s/it]

Calculating features took 18.9 seconds to run.
Deep model took 86.2 seconds to run.
-- Exception occured --
Length of values (2292) does not match length of index (459)
1it [00:02,  2.95s/it]
1it [00:01,  1.80s/it]

Calculating features took 29.7 seconds to run.
Deep model took 77.4 seconds to run.
-- Exception occured --
Length of values (3056) does not match length of index (612)
<<< joined row computation process
<<< joined row computation process
<<< joined row computation process
<<< joined row computation process
<<< joined row computation process
***
 Error :( Check your input format is compatible with PRIDICT! More information in input box on https://pridict.it/ ...
***

Hello!
Thanks for reaching out and using PRIDICT. I found that the error pops up only with --combine_results. Could you give it a go without this option? Meanwhile, I'm on the case to fix it! For now, sticking to individual files is a workaround (and combining them in separate scripts).
All the best,
Nicolas

Thanks! I can confirm it works perfect running without the combine script. Individual files isnt an issue at all!
P.S. Big fan of your tool. so far, our experiments show high correlation with your scores that are produced. Thanks for putting this together!


Need to handle new 'PAYMENT_FINALIZED' order state.

Need to handle the new 'PAYMENT_FINALIZED ' order state which occurs after an escrow payment has been released due to timeout.

[ ] there is a server issue for the vendor to get a socket. That way the vendor's order modal can refresh if they happen to be looking at the order.
[ ] ensure the 'PAYMENT_FINALIZED' state is properly represented in the status bar. It could probably just be represented as the 'FULFILLED' state since that is the only state we're currently allowing the timeout release to occur.
[ ] ensure the the vendor's order has the transaction with the released funds.
[ ] ensure that during the 'PAYMENT_FINALIZED' state, the buyer can leave a review to complete the order.
[ ] ensure the 'PAYMENT_FINALIZED' state is translatable and it's properly represented in the Status column of the transactions table.

Closing this since we're opting for a very limited handling of this scenario and the requirements are TBD as far as the more robust handling.


"Immune Regulation" link does not work

Go to a gene page, say http://hipc-dashboard.org/#gene/h/stat1
Click on the "Immune Regulation" link (https://immuneregulation.mssm.edu/metadata-all.html?s=STAT1). It says:
Not Found

The requested URL was not found on this server.

The problem does not happen anymore.


feature/task1-adjust-contacts

Update Contact Info + App Icon
:recycle: Current situation & Problem

The application required an app icon update, accent color update to align with app icon color scheme, and contact information update for the project contacts.

:gear: Release Notes

No new features added, only visual changes. Contact view information for three main contacts changed to only allow for email contact and website viewing.

:books: Documentation

No need to update documentation, only smaller visual changes

:white_check_mark: Testing

Updated text within prior working version of app, visual changes

:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

@bryant-jimenez Please make the changes and then request a review again! :)


Error: The underlying connection was closed: An unexpected error occurred on a receive

Since about 3-4 days ago, any attempt to run Slimcat now yields this error:
Oops! Can't connect to F-List!
Error: The underlying connection was closed: An unexpected error occurred on a receive
The error appears on the logging screen, before selecting your character.
Updating .Net Framework or downloading a different slimCat version does not fix this.
UPDATE: Somehow, after attempting to connect multiple times, I managed to get into character select screen, and then log in. The issue still persists on subsequent attempts to run Slimcat.

You're not able to connect at all? What version of windows are you using? slimCat probably will not connect under XP.

I am using Windows 8.1. There were no such issues previously, they appeared last week for no apparent reason. Judging by this thread: https://www.f-list.net/thread.php?thread=78701 , it appears I am not the only one.
What may or may not be related to the issue is that I am currently in Russian Federation, and using the localized version of Windows 8, though, again, it used to work perfectly fine just a week ago.


Introduce Preferences to the Flavor API

What this PR does / why we need it:
This PR introduces Preferences to the Flavor API as set out by the design proposal under https://github.com/kubevirt/community/pull/165. This includes:

Introduce new VirtualMachinePreference and VirtualMachineClusterPreference CRDs to the Flavors API and VirtualMachinePreferenceSpec type to define guestOS related preferences such as preferred device buses and models.

Allow for CPU preferred topology policy to be defined within VirtualMachinePreferenceSpec through a PreferredTopology attribute.

Extend VirtualMachineSpec to allow an optional reference to VirtualMachinePreference or VirtualMachineClusterPreference.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
"TBD"

/cc @akrejcir

/retest

/retest

/retest

Since Lee is away, I have rebased this PR and fixed minor issues.

/retest

@davidvossel @iholder-redhat , can you take a look when you have some time?

/retest

/retest

/retest

FWIW I think preferredMachineType has valid future usecases if we ever go through another pc to q35 like migration or what to ever pin VMs to a given version of a machine type.

yes, but it's unclear if this tuning has a use case today and it's also uncertain if we'd solve the migration of machine types using this tuning in the future.
I don't care that much about this specific tuning, I just want to make sure we're targeting the right set of fields... So for example, what's our target here for what tunings we're including and why?
My suggestion would be to target creating a VMPreference feature set that covers all the options used in the ssp-operator's common templates. I'd suggest using that as our razor of what we include and what we don't need initially. In the end, i'd like the ability to express everything that's current encoded in the common templates using a single common template where the variables are just the flavor and the preference we want to match when stamping a new VM out of that template.

FWIW I think preferredMachineType has valid future usecases if we ever go through another pc to q35 like migration or what to ever pin VMs to a given version of a machine type.

yes, but it's unclear if this tuning has a use case today and it's also uncertain if we'd solve the migration of machine types using this tuning in the future.
I don't care that much about this specific tuning, I just want to make sure we're targeting the right set of fields... So for example, what's our target here for what tunings we're including and why?
My suggestion would be to target creating a VMPreference feature set that covers all the options used in the ssp-operator's common templates. I'd suggest using that as our razor of what we include and what we don't need initially. In the end, i'd like the ability to express everything that's current encoded in the common templates using a single common template where the variables are just the flavor and the preference we want to match when stamping a new VM out of that template.

How about a compromise, I've started running through this exercise using a local branch of common-templates to build up the required flavors and preferences to reduce our templates down to one per OS, taking a flavor and set of preferences as an input. Once that's complete I'll remove anything we haven't used from the flavors or preferences ahead of moving to beta.
In the meantime I really want to get this initial series landed so we can at least post follow ups introducing versioning, a validation subresource and finally moving application to the VMI mutating webhook. Doing all of the above in this PR with an ever increasing number of commits is just going to get messy IMHO.

https://github.com/kubevirt/common-templates/pull/448/commits is the WIP/DNM change exploring the use of flavors and preferences on common-templates. It has already highlighted a few issues that I'll seek to address shortly once this initial PR lands unblocking various other bits of work.

Excuse me，If anyone can tell me the difference between vmflavor and vmipreset？In my opinion, this two CRD have many similarities. If the community is plan to give up the vmipreset? if this is realy, can you tell me the roadmap?

A previous revision of the design document for flavors and preferences did reference why VirtualMachineInstancePreset wasn't suitable but I appear to have dropped it recently accidentally, I'll include it again in a respin. However in short:

VirtualMachineInstancePreset was derived from the PodPresets concept in core k8s, however this has been removed from k8s in 1.20
VirtualMachineInstancePreset is only Namespace scoped and thus there was no way of providing cluster wide resources
Non deterministic behaviour, a VirtualMachineInstance that results in merging multiple presets together can produce unexpected results
Undetectable merging conflicts if matching presets are altered
No validation during VirtualMachine creation, only applied when the VirtualMachineInstance is created
No way of expressing presets for devices (disks, network interfaces etc) without knowing their topology ahead of time within the VirtualMachine or VirtualMachineInstance
No clear separation between resource and other guest OS related presets

VirtualMachineInstancePreset hasn't been deprecated at this point but I did want to explore that once this initial series had landed.

@iholder-redhat would you mind hitting this one final time?

@iholder-redhat would you mind hitting this one final time?

/lgtm
Thanks a lot!

@iholder-redhat sorry had to resolve a silly merge conflict in the example VM definitions, should be good now.

/retest

@iholder-redhat sorry had to resolve a silly merge conflict in the example VM definitions, should be good now.

/lgtm
Thanks once again!


Suggesting new blog

Its been a while following his blog and I find it amazing. Maybe you can take a look as well when you have the chance :)

Haha, didn't see that coming. Please ignore my pathetic tries to squash the commits (they were already pushed ;( )


server.exe crashes on fresh install of 2.0.2

Hey man, got a new odd one for you. I downloaded your newest 2.0.2 today. To be safe, I totally uninstalled the previous version, and deleted any temp folders (.keras and .notion-py) to clean the slate. I installed 2.0.2 and launched server.exe. It asks me for the port, and then immediately crashes. I've uninstalled and reinstalled multiple times but receiving the same issue.
Here is the bit in the console right before it crashes:

Traceback (most recent call last):
File "server.py", line 181, in
File "NotionAI\NotionAI.py", line 24, in init
open_browser_at_start(port)
TypeError: open_browser_at_start() missing 1 required positional argument: 'port'
[32324] Failed to execute script server

What a fast response!
That is a strange issue , I have fixed this issue today. May you please try downloading the latest, latest installer?
Sorry for it, but I had modified the published installer some times today before the final release.

I just re-downloaded this version from 1 hour ago, same issue. Did you upload a newer version than this that I am not seeing?

So strange I did delete the release because I was to fast and hadn't fix a bug yet and release it again .

Give a sec I see what is happening

No worries, take your time

Ok I feel I know the issue. Did create the installer before the bugfix 🤦♂
I will update the installer now.
Sorry for it!

Please re-download the installer again and see if it is fixed.

Alright, that solved that problem! However it seems that I cannot test it out until the browser extension stores are updated. You said you submitted them, but Chrome says it hasn't been updated since Mar 3 and Firefox says it was updated 5 hours ago. I may have to wait longer for Chrome to approve your update.
I tried testing it with Firefox, but it seems that nothing happens. I uninstalled and reinstalled the Firefox addon from the addons page (says updated 5 hours ago). I configure it with the server IP:PORT (as I did with previous versions). However when I try to capture text or capture a whole page, But nothing happens.
I've verified that the extension is connected. If I go to the server IP:PORT in a new tab, the server.exe console log shows the GET successfully
[2021-03-08 13:34:11,283] <IP_ADDRESS>:55486 GET / 1.1 200 5974 8977
But when I try to capture text, the server.exe console log does not show any changes. And there is no error or popup in the webpage.
Maybe the Firefox extension is not up to date on the addons page?

Ok, Thanks for the feedback. As you said, the chrome extension takes longer to publish as google revises it in case it has any privacy or virus. In Firefox, the extension update is published in minutes.
I will try to reproduce your error.

Dumb question from my part.
Have you tried refreshing the collection? This needs to be done every time you add a collection. Before it was done when the website loaded, but it made many requests to the notion API, so it was not a very good idea.

Just tried that, and I get this error:

[2021-03-08 15:11:30,852] Running on http://<IP_ADDRESS>:6767 (CTRL + C to quit)
[2021-03-08 15:11:34,318] ERROR in app: Exception on request GET /get_mind_structure
Traceback (most recent call last):
File "quart\app.py", line 1862, in handle_request
File "quart\app.py", line 1887, in full_dispatch_request
File "quart\app.py", line 1104, in handle_user_exception
File "quart\app.py", line 1885, in full_dispatch_request
File "quart\app.py", line 1933, in dispatch_request
File "server.py", line 61, in get_mind_structure
AttributeError: 'NotionAI' object has no attribute 'mind_structure'
[2021-03-08 15:11:34,320] Error in ASGI Framework
Traceback (most recent call last):
File "hypercorn\asyncio\context.py", line 39, in _handle
File "hypercorn\utils.py", line 239, in invoke_asgi
File "quart\app.py", line 2117, in call
File "quart\app.py", line 2140, in asgi_app
File "quart\asgi.py", line 33, in call
File "quart\asgi.py", line 256, in _raise_exceptions
File "quart\asgi.py", line 72, in handle_request
File "quart\app.py", line 1866, in handle_request
File "quart\app.py", line 1118, in handle_exception
File "quart\app.py", line 1862, in handle_request
File "quart\app.py", line 1887, in full_dispatch_request
File "quart\app.py", line 1104, in handle_user_exception
File "quart\app.py", line 1885, in full_dispatch_request
File "quart\app.py", line 1933, in dispatch_request
File "server.py", line 61, in get_mind_structure
AttributeError: 'NotionAI' object has no attribute 'mind_structure'
[2021-03-08 15:11:34,322] <IP_ADDRESS>:60961 GET /get_mind_structure 1.1 500 - 6981

Please, could you try putting your credentials again and then refreshing again?

Yessir, same issue unfortunately. I even tried using my Token v2 instead of credentials. This is what I get when using token:

Login in with tokenV2
[2021-03-08 16:02:25,650] <IP_ADDRESS>:60425 POST /handle_data 1.1 200 3 4301447
[2021-03-08 16:02:29,985] ERROR in app: Exception on request GET /get_mind_structure
Traceback (most recent call last):
File "quart\app.py", line 1862, in handle_request
File "quart\app.py", line 1887, in full_dispatch_request
File "quart\app.py", line 1104, in handle_user_exception
File "quart\app.py", line 1885, in full_dispatch_request
File "quart\app.py", line 1933, in dispatch_request
File "server.py", line 61, in get_mind_structure
File "NotionAI\mind_structure.py", line 25, in get_mind_structure
structure = self.client.get_block(structure_url)
File "notion\client.py", line 169, in get_block
File "notion\client.py", line 162, in get_record_data
File "notion\store.py", line 184, in get
File "notion\store.py", line 286, in call_load_page_chunk
File "notion\client.py", line 260, in post
requests.exceptions.HTTPError: Invalid input.
[2021-03-08 16:02:29,987] Error in ASGI Framework
Traceback (most recent call last):
File "hypercorn\asyncio\context.py", line 39, in _handle
File "hypercorn\utils.py", line 239, in invoke_asgi
File "quart\app.py", line 2117, in call
File "quart\app.py", line 2140, in asgi_app
File "quart\asgi.py", line 33, in call
File "quart\asgi.py", line 256, in _raise_exceptions
File "quart\asgi.py", line 72, in handle_request
File "quart\app.py", line 1866, in handle_request
File "quart\app.py", line 1118, in handle_exception
File "quart\app.py", line 1862, in handle_request
File "quart\app.py", line 1887, in full_dispatch_request
File "quart\app.py", line 1104, in handle_user_exception
File "quart\app.py", line 1885, in full_dispatch_request
File "quart\app.py", line 1933, in dispatch_request
File "server.py", line 61, in get_mind_structure
File "NotionAI\mind_structure.py", line 25, in get_mind_structure
structure = self.client.get_block(structure_url)
File "notion\client.py", line 169, in get_block
File "notion\client.py", line 162, in get_record_data
File "notion\store.py", line 184, in get
File "notion\store.py", line 286, in call_load_page_chunk
File "notion\client.py", line 260, in post
requests.exceptions.HTTPError: Invalid input.
[2021-03-08 16:02:29,990] <IP_ADDRESS>:60425 GET /get_mind_structure 1.1 500 - 124674

Ok I see what is happening
As I have said on the release text and changelog, notion API has changed and so it affects notion-py, which is the library I use to interact with notion.
The fix is in here https://github.com/jamalex/notion-py/issues/292 but you need to modify manually the library. In case of the windows installer, I haven't found a way yet to manually modify the library files.  Meanwhile, I am waiting for the library owner to update it.
I am sorry for it, but it is not  my fault, unfortunately,

ok may have find a temporal solution so you don't have to do anything. Wait a sec.

Ok, I am rebuilding the installer. I did made a fork and modified the library myself and packed it in on the project. Once the new installer is uploaded reinstall the server, put your credentials in, refresh the collections and you should be ready to enjoy!!

Whenever you want you can download the latest installer!
Hope it works this time.

Ok I will give it a try. I am still seeing the 2.0.2 release from earlier today https://github.com/elblogbruno/NotionAI-MyMind/tree/2.0.2
Do you want me to just download the server installer from within that release? Or did you create a separate release tag for the fix?

I did updated the installer on that release, so people don't get confused.
Obtener Outlook para Androidhttps://aka.ms/ghei36

From: profucius<EMAIL_ADDRESS>Sent: Monday, March 8, 2021 10:43:40 PM
To: elblogbruno/NotionAI-MyMind<EMAIL_ADDRESS>Cc: Bruno Moya<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [elblogbruno/NotionAI-MyMind] server.exe crashes on fresh install of 2.0.2 (#12)
Ok I will give it a try. I am still seeing the 2.0.2 release from earlier today https://github.com/elblogbruno/NotionAI-MyMind/tree/2.0.2
Do you want me to just download the server installer from within that release? Or did you create a separate release tag for the fix?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/elblogbruno/NotionAI-MyMind/issues/12#issuecomment-793101488, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACP63IWHWIS6WRWWPF2UGPLTCVAIZANCNFSM4YZZHREQ.

Hi,
Good Morning
How did it go?


Dashboard executable does not render if working directory isn't set the executable folder

We should make it resilient to where it runs from, either by embedding the static content or maybe looking next to the executable (setting the file provider explicitly). See https://github.com/dotnet/aspire/issues/1556#issuecomment-1916202657 for more details.

Moving to the backlog.

I’d like to work on this issue.


nixos/postfix: systemd sandbox

Motivation for this change
Add systemd service sandbox features.
Things done

[x] tested on a mailserver based on simple-nixos-mailserver

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

cc: postfix maintainers @rickynils @globin

It's probably a good idea to also discuss this with the people from simple-nixos-mailserver @r-raymond
Same for your opendkim PR #93314, rspamd PR #93293, and redis PR #93277

@hmenke thanks for the heads up, I'll ping the current maintainers.

Thanks for the heads up, and thanks for these patches! I really like this idea;)
Did you run the nixos-mailserver tests with your patches? I will do it this WE.

Did you run the nixos-mailserver tests with your patches?

I have not yet run any of the official tests. Just tested my usecase for now.

This should definitely be opt-in.

I will try to do something like services.nginx.enableSandbox.

I will try to do something like services.nginx.enableSandbox.

@Mic92 given enableSandbox was meant as a temporary measure and enough time has passed with no negative reports can we please remove it now?
@tnias I'm not in favor of module randomly adding enableSandbox with no consistency at all. Please see my thoughts on the matter here. I think @flokli articulated the issue very well with this comment:

Sandboxing is not a boolean, but something very fuzzy.

The fixup changes loosen up rules to allow more general actions.
@peti:

mailing lists (mailman3) deliver mail by lmtp (tcp or unix socket). This should not be blocked by the current rules. Are other mailinglists using something not allowed yet?
are "reflector scripts" just forwarding mailservers? If yes, I don't see why this should not work.
"any other mail service that needs resources other than Postfix itself" can you provide examples? So that I can loosen up the ruleset accordingly

Rules systemd.tmpfiles can be taken from here - https://github.com/NixOS/nixpkgs/pull/76604
I running this variant on my server - it worked fine.

I used @Izorkin's tmpfiles patch and addded some (hopefully) reasonable sandboxing options.

There are some permission/ownership issues in the /var/lib/postfix directory.

@tnias nixos-mailserver tests passed with this patchset.

@nlewo I just cleared my /var/lib/postfix directory and now it works just fine. I probably messed up the permissions at some point. ¯_(ツ)_/¯

I ran into the fatal: open lock file pid/inet.submission: cannot open file: Permission denied issue again. This widens the sandbox, so it hopefully won't happen again.

@GrahamcOfBorg test rspamd

I would also say to have it tested in unstable for a bit longer and merge it after the branch-off. Postfix itself already does quite a bit of privilege separation so these sandboxes would not improve too much in terms of security.

Due to the use of ExecStartPre= (as a str) this breaks configs using it as a str, or using preStart=. The error is:
The option `systemd.services.postfix.serviceConfig.ExecStartPre' has conflicting definitions, in `/nix/store/pb48ks5whk0sk5nn5602m6xw307vjbaj-nixpkgs-patched/nixos/modules/system/boot/systemd.nix' and `/nix/store/pb48ks5whk0sk5nn5602m6xw307vjbaj-nixpkgs-patched/nixos/modules/services/mail/postfix.nix'.

Such option merging conflict happens regularly to me and others https://github.com/NixOS/nixpkgs/pull/97371
So this does not concern only this PR (though at least it may be more user friendly to set services.postfix's ExecStartPre= as a listOf str). One general solution could be to modify the merging of systemd unit options to merge str and listOf str into listOf str. Or at least also make preStart= generate an ExecStartPre= which is a listOf str.

Was this closed on purpose?

Was this closed on purpose?

@Mic92 There seemed to be little action around it and in the spirit of reducing the number of open PRs I closed it. We can also keep it open if you prefer.

@Mic92 There seemed to be little action around it and in the spirit of reducing the number of open PRs I closed it. We can also keep it open if you prefer.

@tnias I think it just take some time to make sure that postfix does not break.
/marvin opt-in
/status needs_reviewer

@tnias I think it just take some time to make sure that postfix does not break.
/marvin opt-in
/status needs_reviewer

/marvin opt-in
/status needs_reviewer

/marvin opt-in
/status needs_reviewer

We're roughly 4-5 months away from a new release. This change presents high enough risk that I would love to see it merged very soon.  4-5 months sounds like a long enough time to break and fix enough machines that we don't have to worry when this goes stable.
Just a thought...

We're roughly 4-5 months away from a new release. This change presents high enough risk that I would love to see it merged very soon.  4-5 months sounds like a long enough time to break and fix enough machines that we don't have to worry when this goes stable.
Just a thought...

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/hardening-systemd-services/17147/7


fixed chunk mutating orignal collection

~ fixed formating in test .js - as per eslint 2 space rule ~ eslint is being worked upon as per https://github.com/ecrmnn/collect.js/issues/19

It would be best to leave out the space formatting changes. Those can be fixed automatically with eslint, so no point including them in an unrelated PR.

Done,


Add Julius as release shepherd for v2.28

Signed-off-by: Julius Volz<EMAIL_ADDRESS>

Thanks! Can you add @brancz for 2.29?
And next releases: 2.30 (date: September 8) / 2.31 (date: October 20).

Added @brancz and entries for those releases as well.


[feature] --enable-config support custom config file

e.g.
--enable-config="~/fcying/clangd/clangd.yaml"

Sometimes will temporarily share an account for development, config file is different for everyone.

Dupe of #845


feat: add tests to WorkBench

Added a bunch of tests to WorkBench.
I'm not testing the Test methods because it will be removed at a later
date.
Also added a Reset() method to WorkBench so that I could do minimal
testing (see #140).
Closes #74.

Yeah, I was also considering whether they could be extension methods. In any case, I think we should consider just removing workbench.


Brian doyle/zora tutorial

What changed? Why?
Add tutorial using Zora's premint feature
Notes to reviewers
How has it been tested?

Review Error for oveddan @ 2024-06-24 15:03:08 UTC
User must have write permissions to review


Creating duplicate calendars

Not sure its a bug or expected behavior or something can be improved.
Describe the bug
So when we create a new calendar to add some event for first time, the calendar is successfully created. But when we add a second event to calendar, it creates another calendar with different id under the same name (see screenshot below). And when user deletes the event from the calendar app itself, it wont delete the calendar result which was created using createCalendar() making so too many redundant instances in the end never to be used again.
To Reproduce
Steps to reproduce the behavior:

Use the code provided or create a button that initiates a calendar and adds the event to calendar.
Run it more than 1 times
Open calendar app and you will see duplicate event names with different ids which cant be deleted by user.

Expected behavior
When calendar was created for the first as a local account, the plugin checks if the local account already exists. If it does, it checks if the event is already created. If it that exists, it uses its data to create events.
Actual behavior
No method of checking if the calendar event exists. Making the app create duplicate results with different id's each time.
Screenshots

Device(s) tested
This can be very important as not all device vendors do calendar in the same way.

Device: Xiaomi 11 Lite NE 5G
OS: Android 13
Plugin version: 4.3.1

Flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.5, on Microsoft Windows [Version 10.0.22621.1992], locale en-IN)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Android Studio (version 2022.2)
[✓] VS Code, 64-bit edition (version 1.80.1)
[✓] Connected device (1 available)
[✓] Network resources

• No issues found!

Additional context
Code used:
import 'package:device_calendar/device_calendar.dart';
import 'package:fluttertoast/fluttertoast.dart';
import 'package:timezone/timezone.dart' as tz;

class CalendarService {
  void addTaskToCalendar(
    String taskTitle,
    DateTime taskDate,
    bool allDay,
  ) async {
    final deviceCalendarPlugin = DeviceCalendarPlugin();

    final result = await deviceCalendarPlugin.createCalendar(
      "Tasks",
      localAccountName: "Todoify",
    );

    Event event = Event(
      result.data,
      title: taskTitle,
      allDay: allDay,
      start: tz.TZDateTime.from(
        taskDate,
        tz.local,
      ),
      end: tz.TZDateTime.from(
        taskDate,
        tz.local,
      ),
    );

    final createEvent = await deviceCalendarPlugin.createOrUpdateEvent(event);
    if (createEvent!.isSuccess) {
      Fluttertoast.showToast(msg: "Task successfully added");
    } else {
      print(createEvent.errors.first.errorCode);
      print(createEvent.errors.first.errorMessage);
    }
  }
}

Another thing, more like feature enhancement:
Possibility to add events using intent which opens the calendar app to add the event/task/anything.


Remove unbound PHP version constraint

Ref: https://getcomposer.org/doc/faqs/why-are-unbound-version-constraints-a-bad-idea.md

Can you use a single pipe as it is done in Symfony (for people using an old version of Composer).

Can you use a single pipe as it is done in Symfony

:-1: This is a very old and "should not be used" composer convention.

(for people using an old version of Composer).

You mean unstable then? Because this is OK since v1.0.0 stable. IMHO you should not take care of this. Old composer version should be simply upgraded to the last stable.
For a personal case, we use new constraint formats for all sonata project for a while and we didn't get any issue of people using a not compatible composer binary. :wink:

as it is done in Symfony

Maybe Symfony is lagging behind the best practice? Are you sure they do this on purpose ? Is it part of their standard ?

Is it part of their standard ?

I think it's more a historical issue than a standard.

My goal is to include this bundle in the Symfony SE. I would prefer keeping with SF conventions for now. If it really matter for you, please at least update all constraints in the composer file for consistency.

Or maybe open an issue in Symfony, to know why they do this?

If you want to include it in the Symfony SE, then you should not accept my PR, at least for now.
Symfony uses unbound PHP constraint ATM.

Or maybe open an issue / PR in Symfony, to know why they do this?

:+1:

This change has already been discussed on the SF repository and rejected: https://github.com/symfony/symfony/pull/18186

@dunglas but this was about replacing the OR operator, whereas @Soullivaneuh point was more focused on the unbound version of PHP.

No one would be using old Composer with a spanking new Symfony SE. That's a moot point.

Ok then go for the new notation. @Soullivaneuh can you standardize the composer.json file to use || everywhere?


Supporting Spring Boot 2.1.0

Closes #24
Signed-off-by: Ali Dehghani<EMAIL_ADDRESS>

Codecov Report

Merging #26 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master      #26      +/-   ##
============================================
+ Coverage     94.86%   94.91%   +0.05%
- Complexity      133      135       +2
============================================
  Files            13       14       +1
  Lines           292      295       +3
  Branches         32       32
============================================
+ Hits            277      280       +3
  Misses            7        7
  Partials          8        8

Impacted Files
Coverage Δ
Complexity Δ

.../me/alidg/errors/conf/ErrorsAutoConfiguration.java
88.88% <ø> (ø)
8 <0> (ø)
:arrow_down:

...dg/errors/conf/ErrorsEnvironmentPostProcessor.java
100% <100%> (ø)
2 <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 ff504e0...5fab4a6. Read the comment docs.


Releases need to be created for each new rsi editor version

Compiling it is cool but downloading it is even cooler

Just make a GitHub Action

EL STUPIDO

Done since https://github.com/space-wizards/RSIEdit/commit/b47b3baabf8b2780cd456335eebd340848b4ac77


[feature request] return span informantion on the fly

It is a common usage to report a syntax error or a semantic error at a specific span, it would be better if we can carry the span info at the AST node.

it would be better if we can carry the span info at the AST node.

This can be done by deriving Spanned trait for ASTs, like:
https://github.com/MaxXSoft/laps/blob/3c59c7acb3e9bbda7fcc9846dc672ff09d74727a/examples/clike/main.rs#L255-L260
And then you can get span of the entire AST and report errors about that:
https://github.com/MaxXSoft/laps/blob/3c59c7acb3e9bbda7fcc9846dc672ff09d74727a/examples/clike/main.rs#L635-L638

Thanks


Unspecified realString(y, 1, 0) function still present in annotations inside several libraries.

Reported by adrpo on 2 Nov 2010 17:32 UTC
Hi all,
We still have realString present in the MSL3.2 library, in the annotations:
textString=DynamicSelect(" ", realString(
                    y,
                    1,
                    0))),

In Modelica/package.mo is said that ticket:
http://trac.modelica.org/Modelica/ticket/211
fixed this issue, but is still not entirely fixed.
Affected models:
Modelica.Blocks.Interfaces.PartialIntegerSISO
Modelica.Blocks.Interfaces.PartialIntegerMISO
Modelica.Blocks.Math.MultiSwitch
Modelica.Blocks.MathInteger.MultiSwitch

Migrated-From: https://trac.modelica.org/Modelica/ticket/451

Comment by dietmarw on 1 Sep 2011 11:46 UTC
Adrian, next time simply reopen the original ticket and a comment to it.
Anyway, thanks for spotting this. It's now fixed in 929d8a76da64536f8fc9937d6a2af43166d2c895 (trunk) and 1e3c00b3b4ae1f6a4a15c0561bb4af9b9b899db8 (maint3.2)


ARTEMIS-277 IncompatibleVersionTest fails on slower machines

I modified the ClientStarter class so that it tries to connect to the server for 10 sec. If it does not succeed, it exits with non zero return code.

@dudaerich  I was already working on a change. Can you see if that's ok with you.. already merged on master

Yes, it is ok now, thank you @clebertsuconic


Twig Extension need find all fields

something like: {{ fieldAll('field-name') }}

You have cases that many fields has the same name?


⚠ Bofrost.es has degraded performance

In 7306555, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1401 ms

Resolved: Bofrost.es performance has improved in 5f81f52 after 8 minutes.


HMPPS Performance Hub test environment please

Environment details

1x WIndows Server / IIS / .NET (application server)
1x Windows Server / SQL Server (DB server)

Application Name
HMPPS Performance Hub
Github team slug
ministryofjustice/performance-hub-developers
Environments
Just "test" for now

[ ] Development
[x] Test
[ ] Preproduction
[ ] Production

Tags

tag
value

application
hmpps-performance-hub

business-unit
HMPPS

owner
Mark Roberts DASD

Networking options
Connectivity

Network connectivity between application and DB;
Developer access to SQL Server;
Probably developer access to application server;
HTTPS out needed for AWS / GOV.UK Notify API;
No special external connectivity to other networks / services

Additional features
Unsure at this stage - I think Bastion was mentioned in relation to SQL Server, but don't know enough to expand on that yet.

[ ] Bastion
[ ] Additional VPC Endpoints
[ ] Extended DNS Zones

Other information
This is a proof of concept at this stage.

This environment has been created as preproduction rather than test.


Docker tag ubi-jre not working

What are you trying to do?
docker pull adoptopenjdk/openjdk11:ubi-jre
Expected behaviour:
Image pulled from DockerHub
Observed behaviour:
ubi-jre: Pulling from adoptopenjdk/openjdk11
no matching manifest for linux/amd64 in the manifest list entries
Any other comments:
Seems to have been broken today 15th August 2022

(Bear in mind we do not offer much in the way of support for these images now, as we've moved only supporting a subset of the distributions in our official docker images for Temurin) although the automation is still in place to keep them updated.

The tag is now working. Closing


 And then reiterate until they are all gone.
This resolves #1926
Signed-off-by: baude<EMAIL_ADDRESS>

LGTM
/approve

/lgtm


Fix tests

Task/Issue URL: https://app.asana.com/0/488551667048375/1205608778367074/f
Description
Fix unit tests
Steps to test this PR
CI build is greed

Current dependencies on/for this PR:

develop

PR #3725   👈

This comment was auto-generated by Graphite.


Add 'pyrrolnitrin' to anti-infective list

For https://github.com/PHI-base/curation/issues/144
https://github.com/PHI-base/phipo/issues/398
https://github.com/PHI-base/phi-eco/issues/31

Done


Only using Reactstrap to replace Bootstrap 4's Jquery-based components

To make it easier (or at least more familiar) to style an app, I was thinking of only using Reactstrap for the parts of Bootstrap that require Jquery, and using regular Bootstrap markup for the rest of the app. For example,

      Navbar

        <NavDropdown isOpen={this.state.dropdownOpen} toggle={this.toggle}>
          <DropdownToggle nav caret>
            Dropdown
          </DropdownToggle>
          <DropdownMenu right>
            <DropdownItem header>Header</DropdownItem>
            <DropdownItem disabled>Action</DropdownItem>
            <DropdownItem>Another Action</DropdownItem>
            <DropdownItem divider/>
            <DropdownItem>Another Action</DropdownItem>
          </DropdownMenu>
        </NavDropdown>

Does it make sense to do so, or should I be using ReactStrap for everything?

To me it makes sense to use all of reactstrap for a few reasons.

No need to have className everywhere. This makes your jsx a little clearer and nicer to look at. You already have a mixture of class and className in the example you made.
Reactstrap abstracts underlying changes to bootstrap (as much as possible). When bootstrap changes, reactstrap will adapt but the way you use reactstrap will remain unchanged. Note this is less likely since bootstrap v4 is coming stable, but before when classNames for things like button outlines changed, users of reactstrap didn't have to update their jsx.
It's consistent and ensures the bootstrap classes and extra attributes are correct (much harder to typo, especially with typescript definitions)

There are some potential downside.

Your not using bootstrap directly so you might not learn/know the underlying classNames and such being used (mostly a problem for when you change to a project not using reactstrap)
If you do already know bootstrap (v4), you'll have to learn reactstrap. It's not hard, we try to make component names and props predictable.
You might have to take a given markup and convert it to reactstrap.

I'm closing this since the the issue is no longer active and it appear it was answered above. Please comment and it will be opened if you feel the issue has not been resolved / the question has not been answered


About appendix

Hi,
thanks for the interesting work.
Could you please share the appendix?

@hyBlue Hi, thanks for your interest. The appendix is at page 13 of https://arxiv.org/pdf/2110.15678.pdf


NIFI-8678 Forced Calcite Versions for Hive Bundle

Description of PR
NIFI-8678 Sets calcite-core to 1.27.0 and calcite-avatica to 1.6.0 in nifi-hive-bundle in order to remove dependencies 1.0.0-incubating and 1.2.0-incubating versions that require retrieval of transitive dependencies from third-party repositories.  Changes also include setting org.glassfish:javax.el to a version that avoids snapshot dependencies.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Why not latest version of Avatica 1.18.0 ?
Avatica 1.18.0 fix one serious bug in NIFI-7601.
I have also submitted a PR for upgrading calcite to 1.27.0
here https://github.com/apache/nifi/pull/5138

Why not latest version of Avatica 1.18.0 ?
Avatica 1.18.0 fix one serious bug in NIFI-7601.
I have also submitted a PR for upgrading calcite to 1.27.0
here #5138

Thanks for the feedback @kent-nguyen!  These are transitive dependencies in hive-hcatalog-streaming, and version 1.6.0 appears to be the latest version for the dependency coordinates of org.apache.calcite:calcite-avatica.  I see a more recent version of 1.18.0 as you noted, but the Maven coordinates are different.  Unfortunately these Hive components have a number of very old dependencies, which makes management difficult.  The goal of this current PR is to update transitive dependencies enough to avoid third-party repositories, but in the long run, removing these legacy Hive components is probably the best way to go.

+1 LGTM, thanks for the upgrade! Merging to main


BUG: Resource library card's don't fit

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
@Suchitra-Sahoo
check this out,

the card's image not fit properly
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

on my side it seems fine.


Create a release build for pushing artifacts

Summary
After our initial manual release of 1.0.0-beta artifacts, we need to create automated builds that will handle the release for us.
We won't be using the maven-release-plugin for this tool. @tklovett presented a pretty solid idea by just releasing with scm. These links are good references:

https://axelfontaine.com/blog/final-nail.html
https://axelfontaine.com/blog/dead-burried.html

For our CI tool, let's think about using gitlab. In this ticket, investigate the setup required for using it.
A/C

Investigate gitlab CI
Create a new build for maven releases

After some initial investigations, the scope of this ticket is going to change a bit.
Instead of using a private gitlab account, we're going to move forward with a public build on Travis CI. Follow the documentation as specced out here: https://docs.travis-ci.com/user/tutorial/


Made Item entities hurtable by fire or cacti

Resolves #571.

Closing due to the entity system rewrite


Laradock integration with VSCode Remote Development

This is just to keep track of what's needed to have laradock workspace container properly supported in Visual Studio Code Remote Development (Containers).
Current pending issues from VSCode side (please add more, if needed):

[Dev Container] allow passing another user to "docker-compose exec" command when connecting to a container - https://github.com/microsoft/vscode-remote-release/issues/538
Open folder in container starts all compose services - https://github.com/microsoft/vscode-remote-release/issues/211

Once theses issues are addressed, it would be interesting if laradock provides an example devcontainer.json configuration to make VSCode attach to laradock workspace container.

I have a working devcontainer.json.
// For format details, see https://aka.ms/vscode-remote/devcontainer.json or the definition README at
// https://github.com/microsoft/vscode-dev-containers/tree/master/containers/docker-existing-docker-compose
{
	// See https://aka.ms/vscode-remote/devcontainer.json for format details.
	"name": "Existing Docker Compose (Extend)",

	// Update the 'dockerComposeFile' list if you have more compose files or use different names.
	// The .devcontainer/docker-compose.yml file contains any overrides you need/want to make.
	"dockerComposeFile": [
		"../../laradock/docker-compose.yml"
	],

	// The 'service' property is the name of the service for the container that VS Code should
	// use. Update this value and .devcontainer/docker-compose.yml to the real service name.
	"service": "workspace",

	// The optional 'workspaceFolder' property is the path VS Code should open by default when
	// connected. This is typically a file mount in .devcontainer/docker-compose.yml
	"workspaceFolder": "/var/www/first-project",

	// Uncomment the next line if you want to keep your containers running after VS Code shuts down.
	// "shutdownAction": "none",

	// Uncomment the next line if you want to add in default container specific settings.json values
	// "settings":  { "workbench.colorTheme": "Quiet Light" },

	// Uncomment the next line to run commands after the container is created - for example installing git.
	// "postCreateCommand": "apt-get update && apt-get install -y git",

	// Add the IDs of any extensions you want installed in the array below.
	"extensions": [
		"onecentlin.laravel-blade",
		"felixfbecker.php-intellisense",
		"amiralizadeh9480.laravel-extra-intellisense",
		"fterrag.vscode-php-cs-fixer"
	]
}

Be sure to make the following path point to your Laradock docker-compose.yml.
"dockerComposeFile": [
		"../../laradock/docker-compose.yml"
	],

Also make sure that the following path is pointing to the folder of the project you want to work on this is the path inside the workspace container
"workspaceFolder": "/var/www/first-project",

You're also free to add and remove extensions from:
"extensions": [
		"onecentlin.laravel-blade",
		"felixfbecker.php-intellisense",
		"amiralizadeh9480.laravel-extra-intellisense",
		"fterrag.vscode-php-cs-fixer"
	]

note: This devcontainer.json is meant for remote development when Laradock is already up and running. I think there are multiple ways to approach this. This is the one that I've been using for the last couple of weeks.

Thanks @boumanb your snippet works like a charm. Cheers.

@boumanb Thank your very much. I have also been this configuration for a few weeks now and it really bring development to a new level!
One thing I would like to achieve to improve my workflow even more, would be to automatically start the dev containers, if they are not running already.
I tried to add the services to runServices, but it just fails. It seems its missing the env. file, so how can I provide it to the extension?

I think my configuration should actually work, but the problem is that the command you see in the picture fails. It fails, because somehow the env variables are not present when this command is run from a different location that the laradock directory itself. So how can I provide the .env file to the devcontainer?
I know this is probably not the best place to ask, because it is rather a configuration of the vscode remote containers extension, but maybe you know how to solve this issue.

@MannikJ , have you tried the sample configuration now shipped with laradock? https://github.com/laradock/laradock/blob/master/.devcontainer/devcontainer.example.json
Just go to folder laradock/.devcontainer, copy devcontainer.example.json as devcontainer.json, make your own adjustments, open laradock folder in VSCode (with Remote-Containers extension already installed), and click on the button Repoen in container.

Hey, as I tried to explain, I have a working configuration. At least when the containers are running before I connect via remote container extension.
But it is not able to spin of the containers itself, because the laradock .env file does not reside in the project directory. I guess it tries to run docker-compose with the laravel .env file, because that's what the command sees.
I use the multi project setup which can is also important to know.
{
  "name": "Laradock",
  "dockerComposeFile": "../docker-compose.yml",
  "remoteUser": "laradock",
  "runServices": [
    "nginx",
    "postgres",
    "pgadmin"
  ],
  "service": "workspace",
  "workspaceFolder": "/var/www",
  "shutdownAction": "stopCompose",
  "postCreateCommand": "uname -a"
}

From the default configuration it looks like the docker-composer file is located in the project directory (one level up from devcontainer.json) which I don't quite understand.

@MannikJ , the trick here, assuming you have a laradock folder in your project root (example: /home/me/my-project/laradock), is opnening /home/me/my-project/laradock subfolder directly on VSCode, rather than /home/me/my-project. Note that your devcontainer.json file should go to /home/me/my-project/laradock/.devcontainer folder.

Ok, I understand that. But the point is still my scenario is different. My laradock folder is not in the project directory but one level up like the laradock docs propose for a multi project setup.
But actually I feel this isn't the best setup anyway. As I am thinking about a way to provide the whole laradock environment for each project with its .env files etc. I had something like that a while ago, but it got very tedious because it wasn't done properly. But this is another very complicated topic. For now I just would like to have a way to tell the remote extension to use the environment file from another directory (the laradock directory that is located one level up from the project directory).

Hi @MannikJ,
No problem. I found your request interesting and played with it all day, never ran into this since my containers are always up. To my surprise, it's very confusing.
My setup (tried to replicate yours based on your comments, please say so if I'm wrong):

What I've found out:

"runArgs" is not available for Docker Compose according to VS Code documentation (it isn't listed underneath Docker Compose and/or General).
VS Code takes the .env file from the project / workspace root by default*. I even managed to get the whole thing working this way 😄 .
For as far as I could discover, it is not possible to override the path VS code takes the .env file from right now. Not by settings in VS Code and not by settings in the .devcontainer.json.

So besides from placing the Laradock .env file into our project root, it isn't possible to provide a different .env file location (at this moment). 4 possible ways around of which 2 are working and tested by me (number 2 and 3). They're ordered to my preferences:

I'm not aware of what OS you're using, but if you're on Linux, you may succeed by symlinking the .env file like so: For project A ln -s /home/user/development/laradock/.env /home/user/development/projecta/.env and for project B ln -s /home/user/development/laradock/.env /home/user/development/projectb/.env this way you have a central .env file that is identical for each and every project. If you would like to differ from it for whatever reason, just copy it instead of making a symlink. This solution is, in my eyes, the best.
Copy your .env file from laradock/.env to projecta/.env and open the projecta folder in VS Code.
Copy your .env file from laradock/.env to laradock/../. Create a .devcontainer folder in laradock/../ and create a devcontainer.json file identic identical to the one you're using right now but let the dockerComposeFile reference "../laradock/docker-compose.yml". Lastly, set workspaceFolder to /var/www. Now open laradock/../ in VS Code and reopen in container. Result should look like the following:

Leverage something like the initializeCommand inside of the devcontainer.json file to set all the variables in the environment (?) 🤷♂

*The default .env file is picked up from the root of the project, but you can use env_file in your Docker Compose file to specify an alternate location.
copied from: VS Code documentation underneath Docker Composer


Add Documentation about Components state

Hi , please add documentation about components state. For example TextField's hasValue and isClean state.

Components state should be considered internal. The only public API is supposed to be the propTypes. There is some rare exception like the focus() method.
I'm closing this issue as I don't think we should fix it.
@mehdijjz What's your use case for this?

@oliviertassinari Actually I wanted to have some flags on my TextFields like 'isDirty' , 'isTouched' or in this case 'isClean' and etc. And when I inspected the TextField's state I saw the isClean state available there. so I said why not, why not make this available to use or add these props to the TextField Component. I don't know if this is related to the purpose of Mui library but it certainly will be a good option.

I'm not sure to understand what you mean by flags.
But I see different ways to tackle it.

If the use case is common enough, we can expose some callback properties.
We could split the text field component into a statefull and a stateless one so users can rewrite the state management part for their use cases https://github.com/callemall/material-ui/issues/2784.


SetFromResponse doesn't seem useful with no access to response headers

Question
hi there - i'm confused about how to use SetFromResponse since you can't actually read the setcookie header value from a fetch request.
in my app i have performed a fetch request that responds with a setcookie header. this header should be saved for use in react-native-webview but it's not working (not on ios). so i'm here trying to manually set the cookie. however i have no access to it so i'm pretty confused as to how this is supposed to work.
the flow of using fetch and then loading the webview works perfectly fine on android - that is to say the cookie is set via fetch request and then is available when the webview reloads. i have also enabled the webview shared cookies setting.

Hey, we use axios in our app to do the backend request that returns the cookies. In axios, it's possible to read the set-cookies header. Maybe that helps :)

thanks - using an alternative to fetch seems to be the most reasonable solution.


Segmentation fault in WAV generation

Hi all,
I've set up and run my files and directories in Merlin, but upon the final step of WAV generation, I always receive the following error:
2017-06-02 10:43:42,417 INFO     wav_generation: creating waveform for 1096 of 1262: tr0394f_appwrd37
2017-06-02 10:43:43,192 CRITICAL     subprocess: exit status -11
2017-06-02 10:43:43,193 CRITICAL     subprocess:  for command: /homes/kl2792/merlin/tools/bin/WORLD/synth 1024 16000 tr0394f_appwrd37.f0 tr0394f_appwrd37.sp tr0394f_appwrd37.ap tr0394f_appwrd37.wav
2017-06-02 10:43:43,193 CRITICAL     subprocess:       stderr:
2017-06-02 10:43:43,193 CRITICAL     subprocess:       stdout:
2017-06-02 10:43:43,193 CRITICAL     subprocess: OSError for /homes/kl2792/merlin/tools/bin/WORLD/synth 1024 16000 tr0394f_appwrd37.f0 tr0394f_appwrd37.sp tr0394f_appwrd37.ap tr0394f_appwrd37.wav
Traceback (most recent call last):
  File "/homes/kl2792/merlin/src/run_merlin.py", line 1175, in <module>
    main_function(cfg)
  File "/homes/kl2792/merlin/src/run_merlin.py", line 961, in main_function
    generate_wav(gen_dir, gen_file_id_list, cfg)     # generated speech
  File "/homes/kl2792/merlin/src/utils/generate.py", line 281, in generate_wav
    .format(synworld=WORLD['SYNTHESIS'], fl=cfg.fl, sr=cfg.sr, f0=files['f0'], sp=files['sp'], ap=files['ap'], wav=files['wav']))
  File "/homes/kl2792/merlin/src/utils/generate.py", line 93, in run_process
    raise OSError
OSError

There appear to be instances of this error with other utterances as well, because when I remove the specified utterance, I receive the same error on others. When I run the command specified, ~/merlin/tools/bin/WORLD/synth 1024 16000 tr0394f_appwrd37.f0 tr0394f_appwrd37.sp tr0394f_appwrd37.ap tr0394f_appwrd37.wav, I receive a segmentation fault.
The label, utterance, and WAV files appear to be normal, but one thing that I've noticed is that I've only been receiving the error on single-word utterances ('not', 'position', etc.) with WAV file lengths of around 2-3 seconds.
Does anybody know of what might be causing this, or of ways to fix this problem?
Thanks!

Can you check the f0 file using sptk's x2x command. Perhaps there are no voiced frames since the utterance length is very small.

The error is caused by the WORLD vocoder, so it's not a merlin problem. It seems that WORLD handles an F0 value of 0.0 as silence, but small values different than that will cause a segfault. Merlin does some preprocessing during audio generation where it treats LF0 values of -1e10 as silence and converts them to a F0 value of 0.0. So manually correcting some LF0 values
lf0[lf0 <= math.log(20)] = -1e10
fixed it for me.

Thank you for pointing out. It's been fixed now in acoustic decomposition function.