text:
I cannot initiate a scroll from a clickable view inside SmoothAppBarLayout

I understand this was already reported as issue #54. I'm creating a new issue as that one was closed.
I need to have a clickable ImageView inside a CollapsingToolbarLayout inside the SmoothAppBarLayout.
And as long as the ImageView has a ClickListener the scrolling doesn't work starting the scroll on that view.
It's critical in my case as the ImageView is as big as the entire CollapsingToolbarLayout and contains the first item image and you can tap on it to transition to the all-images dedicated screen.
I reproduced this by adding a clickable view inside the CollapsingToolbarLayout of your samples project screens GsdScrollExitUntilCollapsedActivity and SmoothScrollExitUntilCollapsedActivity to confirm the problem is in SmoothAppBarLayout. This is not a from-scratch implenentation; I'm coming from a:
RelativeLayout
    CoordinatorLayout
        AppBarLayout
            CollapsingToolbarLayout
            RelativeLayout
                ImageView (clickable)
                ~other stuff floating around
            Toolbar
        NestedScrollView
            LinearLayout
                ~item details

I took a look and compared the onTouch events of the clickable view on each of those examples while starting a scroll and noticed that in the GsdScrollExitUntilCollapsedActivity case it receives the ACTION_DOWN... then a few ACTION_MOVE... then an ACTION_CANCEL... and then the further ACTION_MOVE events start to get detected on the parent views.
In the SmoothScrollExitUntilCollapsedActivity case the ACTION_CANCEL is never received by the clickable view and the ACTION_MOVE events never get received by it's parents.
On the other issue both you and the reporting guy mentioned something about "dispatching the touch events on my own" but I need a bit more help about how to do that.... should I be detecting the ACTION_MOVE onTouch events (I already have this) and dispatching them (using the dispatchTouchEvent function ?) but... to who ? to the CoordinatorLayout ?

Let me try it again. What SmoothAppBar version are you using?

Hi @pablo-oses
Can you change the order in your layout, then see how it works?
RelativeLayout
    CoordinatorLayout
        NestedScrollView
            LinearLayout
                ~item details
        AppBarLayout
            CollapsingToolbarLayout
            RelativeLayout
                ImageView (clickable)
                ~other stuff floating around
            Toolbar

In my app I'm using 23.1.0 for both the appcompat and smooth-app-bar-layout
The layout structure that I mentioned was before implementing SmoothAppBarLayout.
In the current one I have NestedScrollView first (with a top padding) and SmoothAppBarLayout later.
Instead of trying to fix this in my app with all it's complexities I'm trying to confirm that a possible fix is doable in the samples app as an in-vitro experiment.
I'm using the master branch as of last week (the last thing mentioned in the CHANGES.MD is "Version 23.2.1.1 - March 29th 2016"

In the sample GsdScrollExitUntilCollapsedActivity the clickable view inside CollapsingToolbarLayout inside AppBarLayout receives the onTouch(ACTION_CANCEL) event after a few onTouch(ACTION_MOVE) events. And in the sample SmoothScrollExitUntilCollapsedActivity it doesn't.
So to try to understand why it's not working I started to research exactly how is it working fine on the GsdScrollExitUntilCollapsedActivity case.
So I started to read about the Android's touch system event propagation and understood that such event (the ACTION_CANCEL) is received because some parent view answered true to a ViewGroup.onInterceptTouchEvent event. So I started to sniff the onInterceptTouchEvent activity of each of the parent views and noticed that CoordinatorLayout is the one detecting a true against ViewGroup.onInterceptTouchEvent and stops sending the ACTION_MOVE events to the clickable view and starts to process them on his own.
The one telling CoordinatorLayout that true is the AppBarLayout.Behavior.
The detection logic is in it's base class HeaderBehavior and is clear in the case of ACTION_MOVE if it detects yDiff > mTouchSlop
And when I analysed all that same logic again for the SmoothScrollExitUntilCollapsedActivity case I noticed that I'm in SmoothAppBarLayout.Behaviour which also extends the same HeaderBehavior so the detection logic should work in the same way but when action == ACTION_MOVE it fails to work because mActivePointerId is -1 (which should have been set in the ACTION_DOWN event.
When the HeaderBehavior of SmoothAppBarLayout received the ACTION_DOWN event it didn't saved the mActivePointerId because canDragView(child) is false (a function that in the case of AppBarLayout.Behavior answers true)
And the reason for that difference is that SmoothAppBarLayout.Behavior extends BaseBehavior before extending AppBarLayout.Behavior and in BaseBehavior's init function it set's a DragCallback that always return false.
I commented out that part and noticed that the ACTION_MOVE events are now properly transferred from the clickable view to the CoordinatorLayout as the case in which it works. But now while I initiate a scroll from SmoothAppBarLayout the other members of the CoordinatorLayout (in your sample a RecyclerView) doesn't scroll :(
Do you have any idea to have a clickable view inside SmoothAppBarLayout ?

Hi @pablo-oses
What AppCompat version are you using? The latest version of SmoothAppBarLayout is 23.3.0. Please check if it works for you.
Cheers,
Henry

I upgraded to 23.4.0 on the sample/build.gradle file and it's still not scrolling from a clickable view inside the SmoothAppBarLayout.   (the touch events never get intercepted and captured by it's parent views)

Just want to let you know that I am looking into this issue. It's a common problem with custom view, ViewGroup and View... Somehow, original AppBarLayout works. Investigating...

Thanks !... I hope all the debugging findings that I wrote helps.
Let me know if you can't reproduce in the samples app anything that I described or if I can help trying out possible ideas

I am just back from I/O and will ping you when I have some updates. Thanks for your attention.

I still haven't had perfect solution for this issue yet. This is tricky issue. I need to spend more time look into event dispatcher things...

Same issue here. I Have a button inside my CollapsingToolbarLayout but scrolling is disabled.

I am facing a similar issue too. I have a ViewPager inside the SmoothCollapsingToolbarLayout and ViewPager items are clickable.

I also encountered the same problem

I am also facing this issue, tested with latest lib
With android AppBarLayout they have fixed this issue
Does this issue has something to do with onTouchListener of clickable view

Right, because of the approach of SmoothAppBarLayout, I still can't figure out the way to make touch and scroll work at the same time. :(

I am still new to Application development  so i dont know the right approch , but is is possible to detect touch event inside SmoothAppBarLayout or any parent view  and check for action type
and separate down action from move action
if it is move then initiate SmoothAppBarLayout scroll event , else do nothing
https://developer.android.com/training/gestures/detector.html
http://stackoverflow.com/questions/14776271/android-ontouch-motionevent-action-move-is-not-recognized
please let me know is this possibly right approach or not

I also encountered the same problem for:
SmoothAppBarLayout---->CollapsingToolbarLayout----->ViewPager.

Thanks @nikhilreprime for your suggestion. It can be a right approach but it's still not an easy fix.
Thanks @anilbisht for reporting this issue too. I will try my best to support scrolling on clickable elements.

@henrytao-me Hey buddy, Any update on this ? I am also facing the same issue. Please help me out.

@henrytao-me Hey buddy, Any update on this ? I am also facing the same issue. Please help me out too ,thank you!.

@henrytao-me I found a workaround for the issue, which is nowhere near optimum, but for my requirements it works fine.
First one would need to return false for all dispatchTouchEvents in SmoothAppBarLayout, so the behaviour can take over the touches.
@CoordinatorLayout.DefaultBehavior(SmoothAppBarLayout.Behavior.class)
public class SmoothAppBarLayout extends AppBarLayout {
  // ...
  @Override
  public boolean dispatchTouchEvent(MotionEvent ev) {
    super.dispatchTouchEvent(ev);
    return false;
  }
// ...
}

Secondly, we will need to pass down the touch events, so all clicklisteners in the header etc. will receive their events, which unfortunately requires to override CoordinatorLayout
public class SmoothCoordinatorLayout extends CoordinatorLayout {
  private SmoothAppBarLayout vAppBarLayout;
 // ...

  @Override
  public boolean dispatchTouchEvent(MotionEvent ev) {
    boolean handled = super.dispatchTouchEvent(ev);
    if (handled && vAppBarLayout != null) {
      vAppBarLayout.dispatchTouchEvent(ev);
    }
    return handled;
  }

  @Override
  public void onLayoutChild(View child, int layoutDirection) {
    super.onLayoutChild(child, layoutDirection);
    if (child instanceof SmoothAppBarLayout) {
      vAppBarLayout = (SmoothAppBarLayout) child;
    }
  }
  // ...
}

This is far from optimum, but in my case it works fine.

@florianPOLARSTEPS that part didn't improved anything in my code. In fact, it has even disabled my touch events

Thanks for sharing. I will look into it shortly

@henrytao-me Due to the nature of the workaround ( basically duplicating touch events ) there are a few side effects. It can happen that 2 touches at the same time are registered.
I am still also looking for a proper solution, but I am still trying to wrap my head around the whole touch event propagation system in a coordinator layout.

@henrytao-me I found another possible workaround which is a bit nicer since it does not require a custom CoordinatorLayout and will work for clicks in the header only.
@CoordinatorLayout.DefaultBehavior(SmoothAppBarLayout.Behavior.class)
public class SmoothAppBarLayout extends AppBarLayout {

  private static final int CUSTOM_EDGE_FLAG = 2023477;

 // ...

@Override
  public boolean dispatchTouchEvent(MotionEvent ev) {

    // We need to check wether we have arrived from our own triggered motion dispatch,
    // There are no really appropriate fields on MotionEvents to store custom data, so we abuse edgeflags
    if (ev.getEdgeFlags() == CUSTOM_EDGE_FLAG) {
      return false;
    }

    boolean dispatched = super.dispatchTouchEvent(ev);
    if (dispatched && ev.getAction() == MotionEvent.ACTION_MOVE) {
      // After we know some view in our hierarchy would want to receive the move touch event, we don't want it to have though,
      // we create a new motion event which will cancel our current motion event stream and will be disregarded by appbarlayout,
      // so CoordinatorLayout.Behaviour can receive the new motion event stream
      MotionEvent motionEvent = MotionEvent.obtain(ev);
      motionEvent.offsetLocation(getLeft(), getTop());
      motionEvent.setAction(MotionEvent.ACTION_DOWN);
      motionEvent.setEdgeFlags(CUSTOM_EDGE_FLAG);

      // getParent() cannot return null, since well - who would have called this method
      ((ViewGroup) getParent()).dispatchTouchEvent(motionEvent);
      return false;
    }
    return dispatched;
  }
  // ...
}

Hi @florianPOLARSTEPS, it really works. Awesome. Let's me add that to next release and mark you as contribution. Thanks a lot.

@florianPOLARSTEPS  thanks for providing this workaround
@henrytao-me when are you planning to deploy next release

The work around works fine in case of non scrolling elements in header
In my case horizontal scroll view is present in header view
So i added few extra line , please check if they are OK
Thank you
private float downXValue,downYValue;

@Override
public boolean dispatchTouchEvent(MotionEvent ev) {

    if (ev.getEdgeFlags() == CUSTOM_EDGE_FLAG) {
        return false;
    }

    boolean dispatched = super.dispatchTouchEvent(ev);
    if(ev.getAction() == MotionEvent.ACTION_DOWN) {
        downXValue = ev.getX();
        downYValue = ev.getY();
    }else{
        float currentX = ev.getX();
        float currentY = ev.getY();
        if (dispatched && ev.getAction() == MotionEvent.ACTION_MOVE) {
            if (Math.abs(downXValue - currentX) > Math.abs(downYValue - currentY)) {
                Log.d("Motion Type :","Horizantal");
            }else{
                Log.d("Motion Type :","Vertical");

                MotionEvent motionEvent = MotionEvent.obtain(ev);
                motionEvent.offsetLocation(getLeft(), getTop());
                motionEvent.setAction(MotionEvent.ACTION_DOWN);
                motionEvent.setEdgeFlags(CUSTOM_EDGE_FLAG);

                // getParent() cannot return null, since well - who would have called this method
                ((ViewGroup) getParent()).dispatchTouchEvent(motionEvent);
                return false;
            }
        }
    }
    return dispatched;
}

Thanks @nikhilreprime for the workaround. I think I will include it to next release by early next month when I have more spare time and add you guys to contributors list.

I heard that the fix for AppBarLayout issue is done. It will be included in 26.0.0. Stay tuned.

@florianPOLARSTEPS tried your fix, works great, but another issue arises because of this. The view on which touch has initiated, remains on a clicked state, until the AppbarLayout is touched again.

authors: MMCBen Pachouri-Sikandar anilbisht florianPOLARSTEPS gitanshu henrytao-me hrsalehi jimitpatel nikhilreprime pablo-oses prat-z yushilong

repo: henrytao-me/smooth-app-bar-layout


text:
🛑 hentaiOS Mail is down

In 32c4ecc, hentaiOS Mail (https://mail.hentaios.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hentaiOS Mail is back up in ea7cec3.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 hentaiOS Download Page is down

In 3ba4039, hentaiOS Download Page (https://downloads.hentaios.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: hentaiOS Download Page is back up in 31fd170.


text:
Extend the authenticator to enable reading data from the configmap

Currently the config is only loaded on startup, requiring the authenticator to be restarted each time there is a change to the config.  There is already an issue (#7 ) to reload the config when it changes.  Although this is an improvement, it still requires modifying the file on disk wherever the authenticator is running.
This proposal is to separate the server configuration from the mapping configurations, and to load the mapping configurations from a configmap.  This will enable a user to update the user/role mappings using kubectl without needing access to the config file where the authenticator is running.  The source of this data can be expanded in the future to allow for additional sources such as dynamodb or s3 which will make it easier for organizations with large user bases to build automated tooling for creating the mappings.  It's worth noting that the specific use case we are thinking of involves running the authenticator on the master outside of kubernetes, talking to the apiserver via localhost on the unsecured port.  This bypasses authentication and voids a circular dependency.  Using an x509 cert or another (non-bearer token) authentication mechanism would also work.
This proposed design would:

Extend the server config to include a loadMappingsFromConfigMap bool, an apiServerURL and kubeconfigPath
Extract the logic to convert an ARN to a username/groups
When looking for mappings check all configured sources (config file and configmap).
The configmap mapping source would read the configmap on startup and perform a  watch looking for changes and updating its mapping when necessary

Sounds good.  I have something in progress.  I'll send out a PR when it is ready for review.

@mattlandis @mattmoyer Sorry to say this after coming late to the party but - is this really what you would want?
A biggest concern (to me) of live-reloading in this way is that you can't easily roll-back your configuration, or stop roll in case of a configuration error.
I'd rather just use helm + configmap checksums + readiness probes to stop rolling on configuration error plus easy rollbacks.
So, I appreciate it if you could let me confirm your original intention.
I feel like doing it natively in authenticator is a kind of reinvention of wheels.
Was your intention to support some level of automation even without helm? In that case, your direction makes a lot sense to me.
But I couldn't figure it just by reading this thread. Thx!

My intention is to provide a mechanism for people an cluster administrator who does not have access to a managed cluster to be able to update the user and role mappings.
Since RBAC already happens through kuberenetes mechanisms it seems like a good place to put the user/group data instead of a external API that would then update the config file and restart the service.
We could also potentially look at a custom resource if people think that makes more sense but the configmap is what we have been exploring.

@mattlandis Thank you very much for the response!
Excuse me if I'm still missing your point - So, our intention here would be to:

Allow an operator with fairy restrictive RBAC permissions(w/ configmap update permission but w/o pod CRUD access) to update mappings
(In the future) Allow an operator with no K8S API access at all to update mappings

And the 2. above is especially relevant to your use-case:

authenticator on the master outside of kubernetes, talking to the apiserver via localhost on the unsecured port. This bypasses authentication and voids a circular dependency

because 2. allows authenticator outside of K8S(no serviceaccount, also no TLS key/cert for ClientAuth) to authenticate against apiserver with K8S user/group from IAM session/role, to read the configmap for mappings?

My intention is to be able to enable someone who has API access (either system:masters or something more restrictive to the configmap for aws auth) is able to update the configurations without having access to the instances running the API server or the authenticator itself.  It is for a manged kubernetes experience.  This is the primary use case we are focusing on right now.
The use case for non-k8s operators updating the mappings would be when we look at reading them from an external source (possibly s3 and/or dynamodb) which would allow for someone to build an API and tooling around updating them that would be easier to fit into existing IT infrastructure that doesn't currently talk k8s.

I am a little confused by this issue, but I'd like to summarize a conversation I had with @mattlandis -- I think the authenticator should use config in a file, like how it is implemented today, the only difference being it should reload the file from disk.  This supports the use case of running the authenticator in a pod and outside of kubernetes.  I think there should be one config file, and some parameters can be passed in on command line, which solves our use case.

And that means not having a client to watch a configmap, just looking for a local file and reloading it.

I think the CRD is a better solution.

authors: mattlandis mumoshu nckturner

repo: heptio/authenticator


text:
map.intersectMapObjects(e.pageX, e.pageY) notWork

Describe the bug
after adding litener for click to examle
map.addDataSource(featuresDataSource).then(() => {         map.canvas.addEventListener("click", (e: MouseEvent) => {             const intersectionResults = map.intersectMapObjects(e.pageX, e.pageY);             const usableResults = intersectionResults.filter(result => result.userData !== undefined);             console.log(intersectionResults, usableResults)         });     });
has error in console

thanks @BoryaMogila, I will have a fix soon. Good spotting.

authors: BoryaMogila nzjony


text:
Go application not detected according to README requirements

Hi!
In the readme, it states:

This buildpack will detect your repository as Go if it contains a .go file.

However, this is not true, as in detect it checks for Godeps or gb configurations. That means that if a simple repo with only main.go in it is tested, detect will fail. The repo must either have a Godeps folder and Godeps.json, or a src directory with a go file in it.
I am happy to make a PR, but please let me know which you would prefer:

Change README to reflect actual behavior
Add detect line to find go files in the root
Something else?

Thanks!
:heart: @ngauthier

It would have to be #1 or #3. It's very possible to get valid go repos that contain no .go files in the root of the repo. We also shouldn't blindly search for any .go files either and I've seen valid repos that are ruby apps that contain .go files. I am open to other suggestions or improvements though.

After digging more I realized your compile system depends on godeps or gb, so we'd have to write a new one for when those aren't present. I'll submit a pr to update the readme.

At the very least the Godeps.json file is required with some minimal info, see here: https://github.com/heroku/heroku-buildpack-go/issues/114#issuecomment-196542765

authors: freeformz ngauthier

repo: heroku/heroku-buildpack-go

license: mit

license_source: bigquery


text:
Add caching for .coursier directory

Fixes #114
Replaces #115

lgtm 👍

source: gharchive/pull-request

authors: hunterloftis jkutner

repo: heroku/heroku-buildpack-scala


text:
ENV NODE_ENGINE 0.10.38 <- How to I switch this to io.js latest?

Can't figure it out.  Help!

Hi @dstroot - the plugin currently only supports the node project; PRs for iojs support welcome!

https://github.com/heroku/heroku-docker/blob/master/platforms/node/Dockerfile.t#L13

(however, since they're merging, any such change will likely be short-lived)

Ok thanks. Glad they are merging back.  ;)

authors: dstroot hunterloftis

repo: heroku/heroku-docker

license: isc


text:
Re-organize error list in documentation

We mention that Rack::Timeout::RequestTimeoutException is the most important, so let's put it at the top.

If this is not a good enough change to be merged, feel free to close it! I just found it weird that the most important exception would be mentioned last.

repo: heroku/rack-timeout


text:
🛑 Software Center - Test 1 is down

In 4c139a1, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 21d16fe.

repo: herrphon/upptime


text:
🛑 Software Center - Test 1 is down

In 864a214, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in affe598.


text:
🛑 Auth-Bridge - Test 1 is down

In 4a2e1cf, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in abce671.


text:
🛑 Auth-Bridge - Test 1 is down

In 036a626, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 1bde24a.


text:
🛑 Auth-Bridge - Test 1 is down

In 3cb6e6d, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in cd11af2.


text:
🛑 Auth-Bridge - Test 1 is down

In 031f21a, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 06b640f after 46 minutes.


text:
🛑 Software Center - Test 1 is down

In 6296afa, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 1883db2 after 26 minutes.


text:
🛑 Software Center - Test 1 is down

In ebca4a6, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 6f73eb1 after 1 hour, 11 minutes.


text:
🛑 Software Center - Test 1 is down

In a509dda, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7d964f5.


text:
🛑 Software Center - Test 1 is down

In 2c05d2c, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 91d91fe.


text:
🛑 Auth-Bridge - Test 1 is down

In e373618, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 707f69b.


text:
cliobot.cache missing

it breaks at line 9 of cliobot/bots/init.py:

from cliobot.cache import InMemoryCache

Same here after editing this project a lot! to run in docker

repo: herval/cliobot


text:
support geo-interface

First of all, really great experience so far with vegafusion!
I tried the first example of this page https://altair-viz.github.io/user_guide/marks/geoshape.html using vegafusion, but I received an error. I can reproduce it with the following code snippet based on altair-tests available here: https://github.com/altair-viz/altair/blob/master/tests/vegalite/v5/tests/test_geo_interface.py
Given the following code snippet:
import altair as alt
import vegafusion

def geom_obj(geom):
    class Geom:
        pass

    geom_obj = Geom()
    setattr(geom_obj, "__geo_interface__", geom)
    return geom_obj

geom = {
    "coordinates": [[(0, 0), (0, 2), (2, 2), (2, 0), (0, 0)]],
    "type": "Polygon",
}
feat = geom_obj(geom)

chart = alt.Chart(feat).mark_geoshape()

with vegafusion.disable():
    with alt.data_transformers.enable(consolidate_datasets=False):
        chart_dict = chart.to_dict()
chart_dict

{'config': {'view': {'continuousWidth': 300, 'continuousHeight': 300}},
 'data': {'values': {'type': 'Feature',
   'geometry': {'coordinates': [[[0, 0], [0, 2], [2, 2], [2, 0], [0, 0]]],
    'type': 'Polygon'}}},
 'mark': {'type': 'geoshape'},
 '$schema': 'https://vega.github.io/schema/vega-lite/v5.6.1.json'}

But with vegafusion enabled it gives the following:
with vegafusion.enable():
    with alt.data_transformers.enable(consolidate_datasets=False):
        chart_data = vegafusion.transformed_data(chart)
chart_data

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[54], line 3
      1 with vegafusion.enable():
      2     with alt.data_transformers.enable(consolidate_datasets=False):
----> 3         chart_data = vegafusion.transformed_data(chart)
      4 chart_data

File [d:\Software\Miniconda3\envs\stable\lib\site-packages\vegafusion\evaluation.py:46](file:///D:/Software/Miniconda3/envs/stable/lib/site-packages/vegafusion/evaluation.py:46), in transformed_data(chart, row_limit)
     43 if dataset is None:
     44     raise ValueError("Failed to identify mark for Altair chart")
---> 46 (data,), warnings = runtime.pre_transform_datasets(
     47     vega_spec,
     48     [dataset],
     49     get_local_tz(),
     50     row_limit=row_limit,
     51     inline_datasets=inline_datasets
     52 )
     54 return data

File [d:\Software\Miniconda3\envs\stable\lib\site-packages\vegafusion\runtime.py:168](file:///D:/Software/Miniconda3/envs/stable/lib/site-packages/vegafusion/runtime.py:168), in VegaFusionRuntime.pre_transform_datasets(self, spec, datasets, local_tz, default_input_tz, row_limit, inline_datasets)
    165     raise ValueError("pre_transform_datasets not yet supported over gRPC")
    166 else:
    167     # Serialize inline datasets
--> 168     inline_dataset_bytes = self._serialize_inline_datasets(inline_datasets)
...
---> 31 if getattr(data.index, "name", None) is not None:
     32     data = data.reset_index()
     34 # Use pyarrow to infer schema from DataFrame

AttributeError: 'Geom' object has no attribute 'index'

I've implemented the support for the geo-interface in altair in here: https://github.com/altair-viz/altair/pull/1664, so I should probably be able to assist if you face issues or have questions regarding this geo-interface.

For reference, there is also https://github.com/geoarrow/geoarrow, which potentially would make geometry support easier using a solely arrow approach.

Thanks for raising this issue @mattijn, I wasn't familiar with Altair's support for __geo_interface__.
It shouldn't take a lot of effort to avoid this crash by skipping the extraction of geo datasets to the server (allowing Altair to convert them to JSON as it normally does).
Longer term, do you see a benefit in having VegaFusion process geo datasets directly? Are there Vega-Lite transforms that operate on geo datasets that would be good candidates for server-side acceleration?

Not crashing is fine for now. I did a talk on geo datasets with altair last week, the presentation is here: https://mattijn.github.io/talks/geopython2023.slides.html. I use geo datasets only for context and for selections, the aggregation accelerators happens on the other, compounded charts. This combination will be supported with the merge of #251?

This combination will be supported with the merge of https://github.com/hex-inc/vegafusion/pull/251?

Yes, it should be. I hope to get an RC out tomorrow. I'll ping you when that's available. Thanks for sharing your slides, it's really neat to see what you're doing with Altair!

@mattijn I just published 1.1.0rc1 to PyPI. If you have time, please give it a try and see if that address the issue for you. I'm tentatively planning to publish the final 1.1.0 early next week. Thanks!

Hi Jon, I did the following test, which did not yet succeed:
import altair as alt
import geopandas as gpd
import vegafusion as vf
vf.enable()

gdf = gpd.read_file(gpd.datasets.get_path("naturalearth_lowres")).query('iso_a3 == "LUX"')
c_enable = alt.Chart(gdf).mark_geoshape()
c_enable.to_dict()

{'config': {'view': {'continuousWidth': 300, 'continuousHeight': 300}},
 'data': {'url': 'vegafusion+dataset://table_cf9ac0d5_c800_4f66_b6fe_38202f75d920'},
 'mark': {'type': 'geoshape'},
 '$schema': 'https://vega.github.io/schema/vega-lite/v5.6.1.json'}

The data is still parsed as vegafusion dataset. Maybe because a geopandas dataframe is still of type pandas dataframe?
In Altair code base we therefor first check if it contains a __geo_interface__ attribute before doing checks on types
See e.g. here https://github.com/altair-viz/altair/blob/master/altair/utils/data.py#L197-L204:
if hasattr(data, "__geo_interface__"):
    if isinstance(data, pd.DataFrame):
        data = sanitize_dataframe(data)
    data = sanitize_geo_interface(data.__geo_interface__)
    return json.dumps(data)
elif isinstance(data, pd.DataFrame):
    data = sanitize_dataframe(data)
    return data.to_json(orient="records", double_precision=15)

Yeah, I think you're exactly right about the issue being that the geopandas dataframe is also a Pandas dataframe. Thanks!

That's what I do in PX as well. Are there non-GeoPandas implementations that use __geo_interface__?

Yes, see a non-complete list here https://github.com/mlaloux/Python-geo_interface-applications

Ok, should be fixed in 1.1.0rc2! Let me know if you see any other issues with GeoPandas. Thanks again for the feedback!

All fine now👍

authors: jonmmease mattijn nicolaskruchten

repo: hex-inc/vegafusion


text:
fix: Typos

Fix typos found by spell checkers.
OBS: my IDE also fixed some spaces, I can revert that if wanted
To run spell checkers
codespell (this is also used by Velero and we could add to the project CI)
Create a Dockerfile in the project root with the following content
FROM python:3.11.4-slim-bullseye

WORKDIR /oadp/

RUN pip install codespell[toml]>=2.2.5

CMD codespell \
    --check-filenames \
    --check-hidden \
    --skip .git,*.png,*.jpg \
    --ignore-words-list master \
    --count \
    --summary \
    --builtin "clear,rare,informal,usage,code,names"

and run
docker image build --tag codespell - < Dockerfile.codespell
docker container run --rm -it -v "./oadp/:/oadp" codespell

cspell
Create a Dockerfile in the project root with the following content
FROM node:16.16.0-alpine

WORKDIR /oadp/

RUN npm install -g cspell@latest

CMD cspell "**" \
    --gitignore \
    --dot \
    --show-suggestions

a cspell.yaml in the oadp/ folder with the following content
version": "0.2"
language: "en"
caseSensitive: true
words: [
  "OADP",
  "RHPDS",
  "Velero",
  "restic",
]
ignorePaths: [
  ".git",
  "*.png",
  "*.jpg",
]

and run
docker image build --tag cspell - < Dockerfile.cspell
docker container run --rm -it -v "./oadp/:/oadp" cspell

(this one gives a lot of false positives)

Thank you @mateusoliveira43. This is very helpful! We will merge this after LAB-day


text:
HH-196378 : Доработать логику генерации спецификации openapi

version changes : MINOR
compatible : true
description:

added support for default enum value of @FormParam per REST endpoint
added Jersey multipart types and annotations support
added support for ExceptionMapper hierarchies
added support for ExceptionMapper @Priority

HH-196378 : Added augmentation for @FormParam default values
HH-196378 : Add Priority for exception mappers and change the way we derive generic type exception
HH-196378 : Configure build process with respect to hh nexus repository
HH-196378 : Add jersey annotations and types support for generation
HH-196378 : Derive Exception type from Generics instead of a method signature
HH-196378 : Remove interfaces without implementors during scan process
HH-196378 : Workaround for a broken IDEA openapi plugin
HH-196378 : Integrate with hh-release

repo: hhru/smallrye-open-api


text:
Nuscenes detection errors on validation set

Hello! Thanks for the great work!
Could you please share what errors you get for Nuscenes detection on the validation set? By errors, I mean mATE, mASE, mAOE, mAVE, mAAE.
Thank you!

The result of our EA-LSS in val set:
mAP	mATE	mASE	mAOE	mAVE	mAAE	NDS
71.24	0.2709	0.251	0.285	0.2536	0.1899	73.12

Thank you very much for the details!


text:
layouts

How to fix layouts? They are not working at all
try to put some text, for example, DEFAULT LAYOUT into layouts/default.vue and you will see - nothing changed.

can you share a reproduction?

npx degit zynth17/vitailse my-vitailse-app
cd my-vitailse-app
pnpm i
pnpm run dev
try to add something into layouts/default.vue and check for changes in the browser. nothing.

also... your src/router.ts...
is useless.
no router passed into the app from here.
if you add
router.beforeEach((to, from) => {}
nothing will happen.
your router defined in vite.config in imports section.
btw... if you know how to properly configure router.beforeEach  ,, will be great.

woa thats so rude bro, you not even reading the docs of unplugin vue router. im closing this since you dont event know what youre talking about.

Just stumbled over this. So if anyone faces the same issue and still needs a fix:
Go in router.ts and swap
extendedRoutes = routes;
return setupLayouts(routes);

for
extendedRoutes = setupLayouts(routes);
return extendedRoutes;

Though @sil2 seems right about this router not being used, hence beforeEach doesn't work here. But the router setup generates the extendedRoutes, which is then imported in main.ts.
You can add beforeEach in main.ts in the setup of ViteSSG.
For example like this:
export const createApp = ViteSSG(
	App,
	{ routes: extendedRoutes, history: import.meta.env.SSR ? createMemoryHistory() : createWebHistory() },
	async ctx => {
        ctx.router.beforeEach((to, from, next) => {
            console.log("Before route:");
            console.log(to);
            next();
        });
		Object.values(
			import.meta.glob<{ install: ViteSetupModule }>('./modules/*.ts', {
				eager: true,
			})
		).map(i => i.install?.(ctx));
	},
	{}
);

repo: hi-reeve/vitailse


text:
HHH-15186 Dynamic update wrongly enabled

Issue: HHH-15186

Hi @BlackTazz89 ,
This issue seems being resolved in recent versions see https://github.com/hibernate/hibernate-orm/pull/9397.

Hi @BlackTazz89 ,
thanks for your PR, I'm going to close it since the issue seems resolved.

repo: hibernate/hibernate-orm


text:
blaa blaaa

just for testing

Can one of the admins add this person to the trusted builders? (reply with: "add to whitelist" or "ok to test")

authors: Hibernate-CI swethakrishna

repo: hibernate/hibernate-validator


text:
Question about _id inserting in Raw mode

Hi
When i insert document with my own _id field and value  _id = "ABCDED";
i am getting below error. please let me knonw how to pass
i want to insert my own mongodb _id field. please let me know how to do that.
Error: Argument passed in must be a single String of 12 bytes or a string of 24
hex characters
at new ObjectID (Path\node_modules
\robe\node_modules\monk\node_modules\mongoskin\node_modules\mongodb\node_modules
\bson\lib\bson\objectid.js:35:11)
at SkinClass.ObjectID [as id](pnode_modulesrobenode_modulesmonknode_modulesmongoskinnode_modulesmongod
bnode_modulesbsonlibbsonobjectid.js:26:42)
at Collection.id.Collection.oid (node_modules\robe\node_modules\monk\lib\collection.js:51:44)
at Collection.cast (Path\node_modu
les\robe\node_modules\monk\lib\collection.js:532:20)
at Collection.insert (Path\node_mo
dules\robe\node_modules\monk\lib\collection.js:316:15)
at Collection.insert (Path\node_mo
dules\robe\build\collection.js:162:41)
at GeneratorFunctionPrototype.next (native)
at onFulfilled (Path\node_modules
co\index.js:64:19)
at runMicrotasksCallback (node.js:337:7)
at process._tickCallback (node.js:355:11)

This seems to be a problem in Monk (see https://github.com/Automattic/monk/issues/1). It needs to be fixed there for it to work in Robe. In future I may remove Monk and directly call through to the native node.js layer but for now we're stuck with this issue until it gets fixed in Monk.

This is now fixed in monk

authors: hiddentao mathieudutour thiyaga123

repo: hiddentao/robe


text:
Draft: Allow to call showCallkitIncoming() from Objective C code

hi @hiennguyen92
I've added these few lines to allow the method showCallkitIncoming to be called from Objective C (https://github.com/hiennguyen92/flutter_callkit_incoming/issues/21)
Still a problem remains.
The initializer of Data takes a [String: Any?] as param, which cannot be represented in Objective-C.
Can you change it to something representable in Objective-C?
Thanks

Hi @hiennguyen92 , any update on this?
If you tell me how can I change [String: Any?] into something can be represented in Objective-C I can do the work and test all.

@marcoberetta96 sorry for late. I will update version using for Object-C soon.

@hiennguyen92 do you have any ETA time for this? Just to know :)

Hi @marcoberetta96
for Objective-C
#if __has_include(<flutter_callkit_incoming/flutter_callkit_incoming-Swift.h>)
  #import <flutter_callkit_incoming/flutter_callkit_incoming-Swift.h>
  #else
  #import "flutter_callkit_incoming-Swift.h"
  #endif

Data * data = [[Data alloc]initWithId:@"44d915e1-5ff4-4bed-bf13-c423048ec97a" nameCaller:@"Hien Nguyen" handle:@"0123456789" type:1];
[SwiftFlutterCallkitIncomingPlugin.sharedInstance showCallkitIncoming:data fromPushKit:YES];

closing since not needed anymore


text:
The argument methodNameStyle of service macro should default to "Unchanged"

By default, when the "muSrcGenIdiomaticEndpoints" setting is true, the generated service has "methodNameStyle = Capitalize", this is a surprise to most grpc developers.
In addition, if muSrcGenIdiomaticEndpoints = false, the generated service does not have namespace set. Thus, there is not option available that allows us to have namespace and unchanged method names.
When we use protobuf as a rpc protocol, we often use some protobuf tools as well, like grpcui, or BloomRPC to test grpc services. However, due to the fact that grpc services generated by mu-srcgen is not compatible to its proto file, those tools do not work anymore.
In conclusion, we expect the generated grpc service to be like the following, to comply with conventions of grpc ecosystem.
@service(Protobuf, Identity, namespace = Some("example.seed.protocol.proto"), methodNameStyle = Unchanged) trait PeopleService[F[_]]

Hi @lilac, thanks for filing this issue!  This is an interesting request, I was under the impression that idiomatic gRPC services being capitalized was the expected behavior for those services; in fact there was an issue filed about a year ago about this very topic, and based on that discussion the assumption was that capitalizing the method names was how we should go about generating them.
That said, after digging around on the internet about it seems like your request is perfectly reasonable; we shouldn't necessarily mandate that all idiomatic endpoints have capitalized method names, and I think providing the option to make them unchanged while still providing the namespace and all that good stuff is something that mu could reasonably support.  I don't know if I'd be comfortable changing the default behavior (since changing defaults is a recipe for breaking things), but I'm definitely open to the idea of allowing mu users to specify both idiomatic endpoints and unchanged method names.  Does that sound amenable to you?

@dmarticus Thanks for the reply. Having read through the issue you mentioned, I did not get a hint of why method names of an idiomatic endpoint should be capitalized. In addition, I think most grpc code generators and tools make the method names unchanged, just like you type in proto files. That's why I think it should be the default behavior of mu-srcgen. In addition, since this plugin has not reached v1.0, this surprising behavior should be rectified ASAP to avoid more technical debt.
However, if a break change is not expected at this stage, adding another option is acceptable to me.

@lilac My pleasure!  And yeah, I should've clarified that the discussion didn't explain why the previous development decided to capitalize it, just that they did.  I'm more than open to seeing if they'd be willing to change the default since we're not at v1.0.0, but either way I definitely agree that this option should exist.  I'll ask a few of the original engineers about this, too.
@pepegar @fedefernandez @cb372 what do you think about this proposed change?

I'm fine with that breaking change. We'd want to add the option to customize that option.

authors: dmarticus fedefernandez lilac

repo: higherkindness/sbt-mu-srcgen


text:
Javascript not always recognized

Example:
var f=45
new OptimizeCSSPlugin({
cssProcessorOptions: config.build.productionSourceMap
? { safe: true, map: { inline: false } }
: { safe: true }
})

Auto detection is best effort and not guaranteed. The problem is that it’s not a large enough sample to accurately determine the language.

Should your reaction be understood that you don't care about this feature anymore?

Not at all.  Read CHANGES.md.  We make improvements to auto-detect regularly.  It's a key differentiating feature, but it is not magic.  At best it's accurate 80-90% of the time when given a large enough snippets of text (and when the languages used for auto-detect are scoped narrowly).  Using only a few languages will have better results than using the default web build, but even that will have better results than just loading the whole library (and all languages) via Node, etc.
What you are seeing here (with this small JS snippet) is merely the limits of the existing auto-detect system - not a "bug" (ie there is nothing immediately to "fix"), which is what my original response tried to state clearly and directly.
If every issue like this was left open we'd just have a forum full of "hey auto-detect doesn't work on my small snippet".
Context:
https://github.com/highlightjs/highlight.js/issues/1213

For many use cases where it's hard or impossible to manually identify the code snippet auto-detect can be quite useful even when making a "best guess"... and sometimes that doesn't work well at all... that's par for the course.
If you have experience with such things and think you could help improve them, we're all ears, but it's a non-trivial problem.  Also auto-detect is not our -primary- use case - that is highlighting.

@allejo @egor-rogov It's also possible there is room for a docfix here, though this issue doesn't come up so commonly anymore.

I do have a warning in highlight.php about autodetection not being magic. I don't think there'd be any harm in making that clear in highlight.js

I'd be fine with some verbiage along those lines somewhere in the readme. :)  @step135 Would that have helped you though?  I always wonder about just adding things to the README how many people actually read it. :)

authors: allejo joshgoebel step135


text:
Fix: update selected status of current item when switching to select mode

Thank you for providing this tool, it's just what I needed :)
I've made a pull request with small suggestion for improvement.
I suppose it is generally expected that when entering select/deselect mode, the currently selected item will also be selected/deselected.

Sorry for the delay in replying.
Thank you, I had just recently used it and felt uncomfortable too!

authors: higumachan lusingander

repo: higumachan/cargo-cleaner


text:
🛑 KeeWeb is down

In 142d61f, KeeWeb (https://hinzwifi.xyz/passwords/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KeeWeb is back up in 25657ad after 16 minutes.

repo: hinzwifi/uptime-hinz


text:
🛑 μlogger is down

In 1824089, μlogger (https://gps.hinzwifi.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: μlogger is back up in 91ebc1d after 30 minutes.


text:
Solo5 doesn't build on MacOS

To install latest dev:
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index fc715aa..ebfecb1 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -41,7 +41,7 @@ set(OS_OBJECTS
   kernel/fiber.cpp kernel/tls.cpp
   kernel/profile.cpp
   kernel/timers.cpp kernel/rtc.cpp kernel/rng.cpp kernel/rdrand.cpp
-  kernel/solo5_manager.cpp
+  #kernel/solo5_manager.cpp
   util/memstream.c util/async.cpp util/statman.cpp util/logger.cpp util/sha1.cpp
   util/syslog_facility.cpp util/syslogd.cpp util/uri.cpp util/percent_encoding.cpp
   util/tar.cpp util/path_to_regex.cpp
@@ -76,7 +76,7 @@ add_dependencies(os PrecompiledLibraries botan)
 add_subdirectory(arch/${ARCH})
 add_subdirectory(platform/x86_pc)
 add_subdirectory(platform/x86_nano)
-add_subdirectory(platform/x86_solo5)
+#add_subdirectory(platform/x86_solo5)
 add_subdirectory(drivers)
 add_subdirectory(plugins)

diff --git a/src/drivers/CMakeLists.txt b/src/drivers/CMakeLists.txt
index 85f4417..604e07e 100644
--- a/src/drivers/CMakeLists.txt
+++ b/src/drivers/CMakeLists.txt
@@ -22,15 +22,15 @@ add_dependencies(silent_start PrecompiledLibraries)
 add_library(vga_output STATIC vgaout.cpp)
 add_dependencies(vga_output PrecompiledLibraries)

-add_library(solo5blk STATIC solo5blk.cpp)
-add_dependencies(solo5blk PrecompiledLibraries)
+#add_library(solo5blk STATIC solo5blk.cpp)
+#add_dependencies(solo5blk PrecompiledLibraries)

-add_library(solo5net STATIC solo5net.cpp)
-add_dependencies(solo5net PrecompiledLibraries)
+#add_library(solo5net STATIC solo5net.cpp)
+#add_dependencies(solo5net PrecompiledLibraries)

 install(TARGETS
     virtionet virtioblk
-    solo5net solo5blk
+    #solo5net solo5blk
     vmxnet3
     heap_debugging
     silent_start vga_output

diff --git a/cmake/cross_compiled_libraries.txt b/cmake/cross_compiled_libraries.txt
index bf124ec..6abd5e0 100644
--- a/cmake/cross_compiled_libraries.txt
+++ b/cmake/cross_compiled_libraries.txt
@@ -28,34 +28,34 @@ else(BUNDLE_LOC)

 endif (BUNDLE_LOC)

-ExternalProject_Add(solo5_repo
-   PREFIX precompiled
-   BUILD_IN_SOURCE 1
-   GIT_REPOSITORY https://github.com/ricarkol/solo5.git
-   GIT_TAG includeos64
-   CONFIGURE_COMMAND ./configure.sh
-   UPDATE_COMMAND ""
-   BUILD_COMMAND make build
-   INSTALL_COMMAND ""
-)
-
-set(SOLO5_REPO_DIR ${CMAKE_CURRENT_BINARY_DIR}/precompiled/src/solo5_repo)
-set(SOLO5_INCLUDE_DIR ${SOLO5_REPO_DIR}/build/include/)
-set(SOLO5_LIB_DIR ${SOLO5_REPO_DIR}/build/${ARCH})
+#ExternalProject_Add(solo5_repo
+#    PREFIX precompiled
+#    BUILD_IN_SOURCE 1
+#    GIT_REPOSITORY https://github.com/ricarkol/solo5.git
+#    GIT_TAG includeos64
+#    CONFIGURE_COMMAND ./configure.sh
+#    UPDATE_COMMAND ""
+#    BUILD_COMMAND make build
+#    INSTALL_COMMAND ""
+#)
+
+#set(SOLO5_REPO_DIR ${CMAKE_CURRENT_BINARY_DIR}/precompiled/src/solo5_repo)
+#set(SOLO5_INCLUDE_DIR ${SOLO5_REPO_DIR}/build/include/)
+#set(SOLO5_LIB_DIR ${SOLO5_REPO_DIR}/build/${ARCH})

 # solo5 in ukvm mode (let's call it "solo5")
-add_library(solo5 STATIC IMPORTED)
-set_target_properties(solo5 PROPERTIES IMPORTED_LOCATION ${SOLO5_LIB_DIR}/ukvm/solo5.o)
+#add_library(solo5 STATIC IMPORTED)
+#set_target_properties(solo5 PROPERTIES IMPORTED_LOCATION ${SOLO5_LIB_DIR}/ukvm/solo5.o)

 # ukvm-bin
-add_library(ukvm-bin STATIC IMPORTED)
-set_target_properties(solo5 PROPERTIES IMPORTED_LOCATION ${SOLO5_LIB_DIR}/ukvm/ukvm-bin)
+#add_library(ukvm-bin STATIC IMPORTED)
+#set_target_properties(solo5 PROPERTIES IMPORTED_LOCATION ${SOLO5_LIB_DIR}/ukvm/ukvm-bin)

-add_dependencies(solo5 solo5_repo)
-add_dependencies(ukvm-bin solo5_repo)
+#add_dependencies(solo5 solo5_repo)
+#add_dependencies(ukvm-bin solo5_repo)

 # Some OS components depend on solo5 (for solo5.h for example)
-add_dependencies(PrecompiledLibraries solo5)
+#add_dependencies(PrecompiledLibraries solo5)

 set(PRECOMPILED_DIR ${CMAKE_CURRENT_BINARY_DIR}/precompiled/src/PrecompiledLibraries/${ARCH})

@@ -91,13 +91,13 @@ install(DIRECTORY ${LIBCXX_INCLUDE_DIR} DESTINATION includeos/${ARCH}/include/li

 install(DIRECTORY ${NEWLIB_INCLUDE_DIR} DESTINATION includeos/${ARCH}/include/newlib)

-install(DIRECTORY ${SOLO5_INCLUDE_DIR} DESTINATION includeos/${ARCH}/include/solo5)
+#install(DIRECTORY ${SOLO5_INCLUDE_DIR} DESTINATION includeos/${ARCH}/include/solo5)

 install(FILES ${CRTEND} ${CRTBEGIN} DESTINATION includeos/${ARCH}/lib)

 # Only x86_64 supported at the moment
-if ("${ARCH}" STREQUAL "x86_64")
-  install(FILES ${SOLO5_LIB_DIR}/ukvm/solo5.o ${SOLO5_LIB_DIR}/ukvm/ukvm-bin DESTINATION includeos/${ARCH}/lib)
-endif()
+#if ("${ARCH}" STREQUAL "x86_64")
+#  install(FILES ${SOLO5_LIB_DIR}/ukvm/solo5.o ${SOLO5_LIB_DIR}/ukvm/ukvm-bin DESTINATION includeos/${ARCH}/lib)
+#endif()

 install(FILES ${NEWLIB_LIB_DIR}/libc.a ${NEWLIB_LIB_DIR}/libg.a ${NEWLIB_LIB_DIR}/libm.a ${LIBGCC_LIB_DIR}/libgcc.a ${LIBCXX_LIB_DIR}/libc++.a ${LIBCXX_LIB_DIR}/libc++abi.a DESTINATION includeos/${ARCH}/lib)

diff --git a/src/drivers/CMakeLists.txt b/src/drivers/CMakeLists.txt
index 85f4417..604e07e 100644
--- a/src/drivers/CMakeLists.txt
+++ b/src/drivers/CMakeLists.txt
@@ -22,15 +22,15 @@ add_dependencies(silent_start PrecompiledLibraries)
 add_library(vga_output STATIC vgaout.cpp)
 add_dependencies(vga_output PrecompiledLibraries)

-add_library(solo5blk STATIC solo5blk.cpp)
-add_dependencies(solo5blk PrecompiledLibraries)
+#add_library(solo5blk STATIC solo5blk.cpp)
+#add_dependencies(solo5blk PrecompiledLibraries)

-add_library(solo5net STATIC solo5net.cpp)
-add_dependencies(solo5net PrecompiledLibraries)
+#add_library(solo5net STATIC solo5net.cpp)
+#add_dependencies(solo5net PrecompiledLibraries)

 install(TARGETS
     virtionet virtioblk
-    solo5net solo5blk
+    #solo5net solo5blk
     vmxnet3
     heap_debugging
     silent_start vga_output

Solo5 in IncludeOS is now turned of on Mac. Do not really solves this issue, but it's due to the solo5 project not being buildable on Mac.

Yes, as Andreas says, solo5 doesn't support MacOS yet. There is a pending PR to do so, but it might take a while.

authors: AndreasAakesson AnnikaH ricarkol

repo: hioa-cs/IncludeOS


text:
UI guides PR feedback

ShouldDisplayGuides > shouldDisplayGuides in Redux, now the Settings modal works.

The placement issue was related to a ref being needed and a related issue on Chakra's end. Changes:

We are using the same Icon for all categories. This should be in its own component; I have created GuideIcon and given it the feature prop which it passes to GuidePopover.
The component wrapped with PopoverTrigger needs to use Chakra's forwardRef. This is added to GuideIcon.
What if we want to use some other custom component as the trigger? We will need to use forwardRef there as well, same as on GuideIcon.  Chakra's own components already have this.
Unfortunately - this is the related issue linked above - Chakra has a quirk where we cannot give the PopoverTrigger a functional component, so we need to wrap children in something else. Box is Chakra-speak for div, I've used that. This doesn't really affect anything; it is just unexpected.

Further feedback, which I have not implemented in this PR:

Javascript convention is to use ALL_CAPS_WITH_UNDERSCORES for "constants", like your object Guides. I suppose its keys should also would be all caps. It may even be a good idea to, instead of passing a string , pass the actual object.key So like:

const GUIDES = {
    SEED_AND_VARIATION: "Help text"
}

... feature={GUIDES.SEED_AND_VARIATION} ...

Then the GUIDES object and feature prop would need to be typed properly. This would cause the TS compilation to fail when an incorrect GUIDES is provided, making bugs with misspelling impossible.
I've made a substantial organizational change and you are not up to date with it. Sorry about that. If you accept and pull in my changes in this PR, you could then make a new branch from invoke-ai/InvokeAI development branch, and copy your work over. Hope that makes sense.

I was about to switch back to my dev branch but the got carried away slightly. My last note was about using object keys instead of strings to prevent typos, but I didn't think that through. Your editor still cannot catch an invalid feature name like that.
You need to use something like an enum that has objects for values. This isn't directly possible in TS but it's still simple to implement. I'll walk through my thought process.
Firstly, I changed the name of guides.tsx to features.ts (TSX is for typescript JSX files, TS is for plain typescript files). What we are describing in the file is help info for all features, so it made more sense to me to call it features.
First have a look at features.ts where we:

Make a type to define the shape of each feature's help info FeatureHelpInfo
Make an enum of valid feature names Feature.
Make an object FEATURES which has uses the enum for keys, and values are feature help info in the shape defined by the type FeatureHelpInfo. The shape of this object is described by the type Record<Feature, FeatureHelpInfo>
Syntax for the keys must to be in the format Feature.NAME with square brackets

Now, in GuideIcon and GuidePopover, we can use the enum Feature as the type for the feature prop.
Finally, to use it, in OptionsAccordion we use feature={Feature.NAME]. Your editor should complain if you use an invalid NAME, or don't use Feature.NAME. It is now basically impossible to use the GuideIcon or GuidePopover incorrectly, because anything you do wrong will cause your editor to complain and prevent the project from compiling.
Didn't mean to step on your shoes, just can't help but fiddle with things.

repo: hipsterusername/stable-diffusion


text:
Разработать новый дизайн страницы Личный кабинет

Разработать макет страницы с формой Личный кабинет в новом дизайне.
Адаптивная верстка - десктопные устройства (19201080, 1366768), планшет (1024768), мобильные телефоны (320568)
Страница с формой Личный кабинет содержит:

Текст “Личный кабинет”
Кнопку с текстом “Выйти”, при нажатии осуществляет переход на главную страницу неавторизованного пользователя. Кнопка “Логин” пользователя в хэдере меняется на “Войти”.

Согласована с РО, внесены необходимые правки по замечаниям. Передана в работу Фронту.

https://www.figma.com/file/SLsP9UQstJOh4NYNj6GMY5/НаймиНайми?type=design&node-id=719-3060&t=TGnWyECOt1tzKQAX-4

repo: hire-hire/hire-hire


text:
请问使用软件批量OCR时，无法将图片或者文件夹拖入候选框是什么原因呢？或者是否可以选择图片文件夹目录呢？

Issues

[X] I have browsed through the Issues. 我已浏览过Issues，确定没有重复提问。

Umi-OCR version 程序版本
2.1.4
Windows version 系统版本
win10
OCR plugins Used 使用的OCR插件
PaddleOCR
Reproduction steps 复现步骤
批量处理时无法拖入文件夹是什么原因呢？
Problem screenshots or related files (optional) 问题截图或相关文件（可选）

无法将图片或者文件夹拖入候选框是什么原因呢？

这应该是win10/win11祖传的bug，在网上搜索 win10 无法拖入 即可找到很多解答。
可参考：

https://www.bilibili.com/read/cv6924395/
https://zhuanlan.zhihu.com/p/508842446

是否可以选择图片文件夹目录呢？

标签页的左上角有个 打开图片 的按钮，你可以先打开目标文件夹，按 ctrl+A 选中全部文件，再点击打开。

谢谢作者的回复，很有帮助
yjg
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "hiroi-sora/Umi-OCR"                                                                                @.>;
发送时间: 2024年10月24日(星期四) 凌晨1:49
@.>;
@.>;"State @.>;
主题: Re: [hiroi-sora/Umi-OCR] 请问使用软件批量OCR时，无法将图片或者文件夹拖入候选框是什么原因呢？或者是否可以选择图片文件夹目录呢？ (Issue #698)
无法将图片或者文件夹拖入候选框是什么原因呢？
这应该是win10/win11祖传的bug，在网上搜索 win10 无法拖入 即可找到很多解答。
可参考：
https://www.bilibili.com/read/cv6924395/
https://zhuanlan.zhihu.com/p/508842446
是否可以选择图片文件夹目录呢？
标签页的左上角有个 打开图片 的按钮，你可以先打开目标文件夹，按 ctrl+A 选中全部文件，再点击打开。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

authors: JianguoYu hiroi-sora

repo: hiroi-sora/Umi-OCR


text:
Difference b/w KITTI and KITTI-with-improved-GT

Thank you for making your code public !
I saw the results in your paper in Table 1 and 2. What is the difference b/w "KITTI eigen benchmark" and "KITTI-with-improved-groundtruth" ?
What do you call these depths that are on the official KITTI website , and where can I find the other one?

You can run the export_gt_depth.py to get gt_depths of KITTI eigen benchmark and KITTI-with-improved-groundtruth.
python export_gt_depth.py --data_path kitti_data --split eigen
python export_gt_depth.py --data_path kitti_data --split eigen_benchmark

Depths on the official KITTI website is another test split, neither eigen nor eigen_benchmark, and the gt_depths are not publicly available.
See https://github.com/nianticlabs/monodepth2#-kitti-evaluation

Thank you @hisfog for clarification!!

authors: hisfog surajiitd

repo: hisfog/SfMNeXt-Impl


text:
NECO-113 renamed the library name.

Changes

Renamed the library name.

Tests
For the Source Code
Tested the sample project can run as Xcode workspace by select "RicohAPIMstorage.xcworkspace" file.

Run git clone --recursive https://github.com/hishida/media-storage-swift.git -b feature/NECO-113
Run open media-storage-swift/RicohAPIMstorage.xcworkspace
Choose MediaStorageSample scheme at the scheme menu of Xcode and run MediaStorageSample.

For the Test Code
Tested the empty test code can run as Xcode workspace.

Run git clone --recursive https://github.com/hishida/media-storage-swift.git -b feature/NECO-113
Run open media-storage-swift/RicohAPIMstorage.xcworkspace
Choose MediaStorage scheme at the scheme menu of Xcode.
Click MediaStorageTests.swift
Click the run button the left side of 9th line: class MediaStorageTests: XCTestCase {.

Now I'm reviewing...

I reviewed again and found no problems. I will merge this.

authors: hishida sohda

repo: hishida/media-storage-swift


text:
Building in 64bit OS

Hi,
i've been trying to get the headless compile running for the 64 bit Raspberry Pi OS, but I keep getting errors like so:
In file included from /usr/lib/llvm-10/lib/clang/10.0.0/include/xmmintrin.h:13:
/usr/lib/llvm-10/lib/clang/10.0.0/include/mmintrin.h:33:5: error: use of undeclared identifier '__builtin_ia32_emms'; did you mean '__builtin_isless'?
    __builtin_ia32_emms();
    ^

Is there a known way around this error?

same for Ubuntu 64Bit

What version is this? I've managed to build them all here's the wetransfer link. I've also uploaded them to google drive and i'll add the link here shortly https://wetransfer.com/downloads/732cf71758bb8792ea9660c759d3b7fa20210225110741/203cdc900b955314bc06de5ceb70068e20210225110933/d24e03

What version is this? I've managed to build them all here's the wetransfer link. I've also uploaded them to google drive and i'll add the link here shortly https://wetransfer.com/downloads/732cf71758bb8792ea9660c759d3b7fa20210225110741/203cdc900b955314bc06de5ceb70068e20210225110933/d24e03

Could you tell us how you did that?

I really don't know. I haven't tried to compile for the 64 bit Raspberry Pi OS. I'll upload the binaries that @irishgreencitrus compiled for us when I have the time :)

I just compiled them on Ubuntu 20.10 server.

Sorry, @irishgreencitrus , would you mind sharing the 64 bit binaries? The WeTransfer doesn't work and I can't find the link to the Google Drive.
Thank you! :D

@hiulit Sure! I'll compile all of them now.

@irishgreencitrus are you going to compile the latest 3.3.2? Was just release a couple weeks ago.

Thank you @irishgreencitrus ! :D
BTW, are you compiling on the Pi itself or are you cross-compiling? If it's the later, I'm interested to know what toolchain are you using, because the one I'm using only compiles for 32 bits https://github.com/hiulit/cross-compile-godot-raspberry-pi

Thank you @irishgreencitrus ! :D
BTW, are you compiling on the Pi itself or are you cross-compiling? If it's the later, I'm interested to know what toolchain are you using, because the one I'm using only compiles for 32 bits https://github.com/hiulit/cross-compile-godot-raspberry-pi

Compiling on 64bit Manjaro ARM minimal, on a Raspberry Pi 4 8GB

@hiulit I can only seem to compile server builds for 3.3-stable and upwards. Is there any changes to flags that you made after the update?

ah i found the logs.
                  ^
/usr/lib/clang/11.1.0/include/mmintrin.h:352:19: note: '__builtin_arm_addg' declared here
/usr/lib/clang/11.1.0/include/mmintrin.h:352:19: error: first argument of MTE builtin function must be a pointer ('__v8qi' (vector of 8 'char' values) invalid)
    return (__m64)__builtin_ia32_paddb((__v8qi)__m1, (__v8qi)__m2);
                  ^                    ~~~~~~~~~~~~
/usr/lib/clang/11.1.0/include/mmintrin.h:373:19: error: use of undeclared identifier '__builtin_ia32_paddw'; did you mean '__builtin_arm_addg'?
    return (__m64)__builtin_ia32_paddw((__v4hi)__m1, (__v4hi)__m2);
                  ^
/usr/lib/clang/11.1.0/include/mmintrin.h:352:19: note: '__builtin_arm_addg' declared here
    return (__m64)__builtin_ia32_paddb((__v8qi)__m1, (__v8qi)__m2);
                  ^
/usr/lib/clang/11.1.0/include/mmintrin.h:373:19: error: first argument of MTE builtin function must be a pointer ('__v4hi' (vector of 4 'short' values) invalid)
    return (__m64)__builtin_ia32_paddw((__v4hi)__m1, (__v4hi)__m2);
                  ^                    ~~~~~~~~~~~~
/usr/lib/clang/11.1.0/include/mmintrin.h:394:19: error: use of undeclared identifier '__builtin_ia32_paddd'; did you mean '__builtin_arm_addg'?
    return (__m64)__builtin_ia32_paddd((__v2si)__m1, (__v2si)__m2);
                  ^
/usr/lib/clang/11.1.0/include/mmintrin.h:352:19: note: '__builtin_arm_addg' declared here
    return (__m64)__builtin_ia32_paddb((__v8qi)__m1, (__v8qi)__m2);
                  ^
/usr/lib/clang/11.1.0/include/mmintrin.h:394:19: error: first argument of MTE builtin function must be a pointer ('__v2si' (vector of 2 'int' values) invalid)
    return (__m64)__builtin_ia32_paddd((__v2si)__m1, (__v2si)__m2);
                  ^                    ~~~~~~~~~~~~
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
scons: *** [thirdparty/oidn/core/device.x11.opt.tools.64.llvm.o] Error 1

hmm interesting I also get the same error as OP. I'll see if i can find a fix
In file included from thirdparty/oidn/core/api.cpp:48:
In file included from thirdparty/oidn/core/device.h:19:
In file included from thirdparty/oidn/core/common.h:19:                                                                             In file included from thirdparty/oidn/common/platform.h:27:                                                                         In file included from /usr/lib/clang/11.1.0/include/xmmintrin.h:13:                                                                 /usr/lib/clang/11.1.0/include/mmintrin.h:33:5: error: use of undeclared identifier '__builtin_ia32_emms'; did you mean '__builtin_isless'?                                                                                __builtin_ia32_emms();                                                                                ^                                                                                /usr/lib/clang/11.1.0/include/mmintrin.h:33:5: note: '__builtin_isless' declared here                                               /usr/lib/clang/11.1.0/include/mmintrin.h:33:25: error: too few arguments to function call, expected 2, have 0                           __builtin_ia32_emms();                                                                                ^

Thank you! I'll upload them right away!
BTW, I only upload the latest version of each minor release, in this case: 2.1.6, 3.1.2 and 3.3.2. So you can save some compilation hours next time ;)
P.S. Have you tried running the editor and export templates? Can you confirm that they work? Specially the editor, where there has been some improvements on the 3.3 version which makes it run very smooth, as oposed to the 3.2.1, which works but it's not very snappy.

@irishgreencitrus Oh, I didn't see all the issues you were having when compiling 3.3 builds. I didn't have any issues using this tool to cross-compile from Linux x86_64 https://github.com/hiulit/cross-compile-godot-raspberry-pi (but it only works for 32 bits)

Following up on this, did anyone ever get it to compile on 64bit Raspberry Pi OS?

I'm waiting for the Godot team to release a the cross-compilation tools with 64 bits support.
But as Raspbian has 64 bits "official" support, I'll try and compile it on the Pi itself when I have the time.

I've succesfully compiled Godot 3.4.2 on my Pi 4 with Raspberry Pi OS.
I'm using Clang, which is not the best option. I'll try again with GCC and LTO, but I haven't had any success with this option on the PI, only when using cross-compilation.

Hey! I've successfully compiled Godot 3.4.2 using GCC and LTO on my Raspberry Pi 4GB with a 64GB SD card and a 16GB swap using Raspberry Pi OS 64 bits. It takes a loooot of time :)

@hiulit Any chance I can get the binaries for 3.4.2 arm64? I dont have an sd card big enough to compile, nor am I very proficient.

@hiulit Im getting a '-bash: ./godot_3.4.2-stable_rpi4_server_lto.bin: No such file or directory' error when trying to run on ubuntu arm64 for rpi4
I did have it working on armhf. Am I doing something wrong or missing something?

@HansKillinger those binaries are compiled for 32 bits. I'll upload the 64 bits later. But they are built on the latest Raspbian OS 64 bits so they might now work on lower versions of the OS  or other OS. I'm waiting for the Godot team to release 64 bit toolchains to cross-compile

@hiulit Ok. So you have working 64 bit binaries but haven't uploaded to github? Or do we have to wait for the toolchain to be released before getting a 64 bit binary? Just wondering if I should downgrade my OS back to 32 bit.

Im not too savvy when it comes to compiling :(

@HansKillinger I have them compiled but they might not work for your OS because they are built on the latest Raspbian OS 64 bits. I'll upload them here so you can test them.
I'm waiting for the 64 bit toolchain, because:

It's waaay quicker to compile
The binaries work for all OS

@hiulit Thanks a million! I will test and reply back to you with results.

There you go! https://drive.google.com/drive/folders/1YdoYAyNhFHsIiPQS67ifgiMM5OpmCpqM?usp=sharing

Btw, this is what I used to compile:
scons platform=x11 target=release_debug tools=yes use_lto=yes CCFLAGS="-march=armv8-a+fp+simd" arch="arm64" -j4

This is for the editor.

@hiulit I can confirm server is working under Ubuntu 20.04 arm64 :)

@HansKillinger Nice! I'm glad it's working! :)

Hey, could you the new 3.4.3 binaries for the Pi 4 64 bits? https://drive.google.com/drive/folders/1E2IgjWmr-7DyKG3Gx8Rfu6hwg170ship?usp=sharing
Thanks!

Hey! I've "officially" released 64-bits binaries for the Pi 4 https://github.com/hiulit/Unofficial-Godot-Engine-Raspberry-Pi#343

I've also added instructions on how to compile on a Raspberry Pi 4 64 bits https://github.com/hiulit/Unofficial-Godot-Engine-Raspberry-Pi/blob/main/COMPILING.md#raspberry-pi-4

I'll close this issue for now. Feel free to open it again if needed.

authors: 0none HansKillinger daviel frankhale hiulit irishgreencitrus polyrain


text:
Lint Fixes

This PR resolves some linter issues. We are ignoring the code within contracts/revert since that's minified.

@Rishi556 this PR now has conflicts that need to be resolved.

repo: hive-engine/hivesmartcontracts


text:
RLHF的效果是否有提升

您好，请问您离线测试过RLHF的效果吗？我用我自己的数据集进行测试，感觉reward+RLHF效果跟直接finetune差的挺远的

RLHF 应当结合 SFT 使用，单独使用 RLHF 很难有效果提升。

RLHF 应当结合 SFT 使用，单独使用 RLHF 很难有效果提升。

您的意思是先使用SFT进行fine-tune，然后模型load finetune的结果再进行reward+RLHF吗

在 InstructGPT 原论文中，作者首先进行 SFT，然后在 SFT 模型的基础上进行 RLHF，我们在 Readme 和 examples 中给出了 PPO 训练的例子。

authors: hiyouga reborm

repo: hiyouga/ChatGLM-Efficient-Tuning


text:
galore SFT训练 每次新epoch，loss都会大幅下降

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
使用galore SFT训练 每次新epoch开始，loss都会大幅下降

Expected behavior
No response
System Info
No response
Others
No response

最终模型训练的其他指标，比如rouge和你目标数据集自己的metric上的结果呢，是否符合预期？
每个epoch后 loss 有较大变化，确实是有这种情况的。

全参训练时数据集较小出现这个很正常

authors: codemayq hiyouga xxll88

repo: hiyouga/LLaMA-Factory


text:
Refactor hyper-parameters of adapters and model loader

We deprecate the checkpoint_dir argument and use the adapter_model_or_path argument to load peft adapters and rename resume_lora_training to create_new_adapter with reversed values.
We create llmtuner.model.patches module to disentangle the patches from the model loader.

No reference in code for --adapter_model_or_path, so is --adapter_name_or_path.

We deprecate the checkpoint_dir argument and use the adapter_model_or_path argument to load peft adapters and rename resume_lora_training to create_new_adapter with reversed values.

@Katehuuh thanks for pointing it out

authors: Katehuuh hiyouga


text:
Fix linewrapping bug

Hi,
I think there is a small mistake where lineWidth is first calculated correctly but then gets immediately reset to 0. (Be sure to check the expanded diff)
Here is side-by-side comparison of the issue with the basic demo

Left is before the change and right is after
Notice e.g. that the word mots. is cut of on the left image whereas on the right it is wrapped correctly.
Edit: Upon further testing there seem to be some other edge cases with linewrapping, but this is a first step.

Thanks!

authors: hjanetzek schmittl

repo: hjanetzek/alfons


text:
🛑 Griffo is down

In bba740b, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 5a36325 after 16 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 Griffo is down

In e38932d, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 6a69bc9 after 38 minutes.


text:
🛑 LM Bogen WSV is down

In e6cacdf, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 4216a07 after 39 minutes.


text:
Update ModLinks.xml

Tried to add new mod, Stop Hitting Yourself. I believe everything should be okay, as I tried looking at other mods' xml manifests, but I had not done this before, so there could still be errors.

It seems that your repo doesn't contain the source code but just a build of the mod - typically people upload the source code in the repository and make a release which contains the dll (or, more often, a zip containing the dll and pdb, which means that bug reports are more helpful)

Source code added (i hope that's all of it).
Makes sense mods should be open source.
thanks for the help

authors: ChouchIsCool flibber-hk

repo: hk-modding/modlinks


text:
About 1000==1 GPU

Hello! First and foremost, I would like to express my sincere gratitude for your hard work on the Kubernetes Scheduler Simulator project. Your contribution is of immense value to the community.
During my reading of the documentation and usage, I came across a question regarding the GPU metrics. I noticed that 1000==1 GPU is used as an important criterion in certain configurations. I am curious about the meaning behind this metric and why such a division was chosen. I would greatly appreciate it if you could provide some background information or explanation on this matter.
Thank you once again for your contribution, and I look forward to your response.
Best regards!

Hi @hjiema ,
The idea of 1000 milliGPU =1 GPU is inspired by the Kubernetes CPU units (docs):

CPU units
The CPU resource is measured in CPU units. One CPU, in Kubernetes, is equivalent to:

1 AWS vCPU
1 GCP Core
1 Azure vCore
1 Hyperthread on a bare-metal Intel processor with Hyperthreading

Fractional values are allowed. A Container that requests 0.5 CPU is guaranteed half as much CPU as a Container that requests 1 CPU. You can use the suffix m to mean milli. For example 100m CPU, 100 milliCPU, and 0.1 CPU are all the same. Precision finer than 1m is not allowed.

Since the simulator is featured by the support of GPU sharing workloads, it allows GPU requirements with precision between 1 GPU and 1/1000 GPUs.

authors: hjiema qzweng


text:
Implement variance analysis

This will be important to simplify inferred types further.

We're trying to create a method here say getVariance in Typer.scala. This method will find the variance of an expression for all it's type parameters (inputs and outputs).
As discussed on discord the following class is a good way to encode variance information.
case class VarianceInfo(isCovariant: Bool, isContravariant: Bool), which would start as VarianceInfo(isCovariant = true, isContravariant = true) (i.e., bivariant)

Since variance will be used for further simplification this analysis should be done on the internal representation of types i.e. SimpleType and PolymorphicType.
So tenatively the method might have the following signature.
getVariance(ty: TypeScheme): List[BoundedVariable -> VarianceInfo]

It would make more sense to make it computeVariances(ctx: Ctx), because it will have to figure out the variance of all related classes (which may refer to each other recursively) in a type hierarchy at once, using a fixed point. The computeVariances method would leave those types that already have their variance info untouched, and would set the variance info for the others.

Ohk so tentatively computeVariances(ctx: Ctx, typeVariances: HashMap[BoundedVariable, VarianceInfo]): Unit takes the context and free type variables. Recursively keeps updating the variance info and stops when there is no further change. The hash map could be part of Ctx as well, if that's better design.
These are the rules I can think off to compute the variance -

(arg: a) -> b => a is contravariant, b is covariant
Box[T] => T is invariant
lower..upper => covariant on upper, contravariant on lower
contra & contra => co
contra & co => contra
co & co => co
invariant & {contra, co} => invariant
bivariant & {contra, co} => {contra, co}

(arg: a) -> b => a is contravariant, b is covariant
Box[T] => T is invariant
lower..upper => covariant on upper, contravariant on lower

This is only true in positive positions. Obviously they reverse in the opposite polarity.
The real difficulty here is what to do when you arrive at something like C[S, T, ...]. You can't recurse into analyzing S, T, ... without knowing the parameter variances of C. But to compute these parameter variances, you may need to look at other occurrences of C[S', T', ...] types.
So you probably need to keep these C[S, T, ...] traversals "on hold" while you accumulate the rest of the variance information. Then you revisit those that may have changed based on the new information you found. For example, if you saw A in positive position in class C[A, B, ...], you need to mark C's first param as not contravariant (so if its current state is bivariant, you change it to covariant; if it's contravariant, you change it to invariant), and this should then trigger you to revisit the C[S, T, ...] we had put on hold, meaning that you should analyze S at positive polarity since it's currently believed to be at most covariant (but possibly invariant).

What if we have a commutative and associatve operation to combine the variances. For e.g. this
contra x contra => co
contra x co => contra
co x co => co
invariant x {contra, co} => invariant
bivariant x {contra, co} => {contra, co}

Feels very much like integer multiplication, co => +, contra => -, inv => 0, bi => +1. Being commutative and associative the order does not matter, we could go down one C[S, T..] and apply whatever we learn. If we encounter another C[S', T'...] we again apply whatever we learn to existing variance of say S'. And we keep doing this till, just like you mentioned, we'll reached the fixed point when there'll be no more change. Wouldn't this remove the need to pause the traversals?
Now looking at the internal types to see which ones will contribute to variance. I can see is that any SimpleType with universally qualified type variables is a wrapped in a PolymorphicType. So we consider these SimpleTypes now among these (using Scala notation) -

TypeBounds[-lb, +ub]
NegType[t]
ComposedType[a, b]
FieldType[-lb, +ub]
TypeRef[T1, T2, ...]
FunctionType[-in, +out]
Without[T]

Example given in group meeting:
class D[X]
  method M1: C[X]
  method M2: ... X ...

class C[A]
  method M1: D[C[int]]
  method M2: ... A ...

[ ] TODO: Raise a warning when a type parameter is found to be bivariant – something like "type parameter T is irrelevant and could be removed".

authors: LPTK twitu

repo: hkust-taco/mlscript


text:
Tests that are incorrectly marked as Optional

The following tests are NOT Optional as they are mandatory search parameter combinations in AU Core. Please fix so not optional:

Observation search by patient + category + date e.g. 1.3.08, 1.4.08, 1.5.08, etc
1.19.05 Optional Server returns valid results for Procedure search by patient + date
1.15.09 Optional Server returns valid results for Encounter search by date + patient

To fix:
[ ] Observation search by patient + category + date e.g. 1.3.08, 1.4.08, 1.5.08, etc
[ ] 1.19.05 Optional Server returns valid results for Procedure search by patient + date
[ ] 1.15.09 Optional Server returns valid results for Encounter search by date + patient

Hello Steph @StephThaoOng
Looks like this issue can be closed.

authors: dt-r projkov


text:
dired says hit 'g' to refresh but that does something else

What did you expect to happen?
dired should refresh or it should give the correct key sequence to refresh
What actually happened?
it brought up the 'g' leader key menu
Additional details:

Include a link to your private config
I don't think this is necessary because I just installed and there's nothing remarkable in there.

Include screenshots/casts of your issue

also shouldn't be necessary because everyone with a somewhat generic install should have the same issue (and with my new minimal window manager I haven't figured out how to do this yet)

If you mention key sequences, include what commands they're bound to

inspecting keys does no good because the 'g' is a leader key and doesn't result in a complete key sequence

Include any warnings or errors logged to *Messages* (use M-x view-echo-area-messages to see it).

no warnings

If an error message is involved include a backtrace of it.
no error message
How to acquire a backtrace:
https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error

Steps to reproduce:
I had a bunch of PDF files left over from windows who's names were upper case but they had internal links to each other in lower case so they didn't work in Linux.   In order to try and get these running I marked them all then did a M-x dired-downcase command on them.   Some of the file names didn't get updated in the buffer (not sure how one could reproduce this as it was probably a glitch).  I tried to go into one of the still upper case ones to see what was going on and it told me the file was no longer there and I should hit 'g' to refresh it.   When I did it just gave me the 'g' leadin key menu.
System information:

emacs   version    26.2
        features   XPM JPEG TIFF GIF PNG RSVG SOUND GPM DBUS GLIB NOTIFY ACL GNUTLS LIBXML2 FREETYPE XFT ZLIB GTK3 X11 XDBE XIM THREADS LIBSYSTEMD LCMS2
        build      Jun 29, 2019
        buildopts  (--prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-silent-rules --docdir=/usr/share/doc/emacs-26.2 --htmldir=/usr/share/doc/emacs-26.2/html --libdir=/usr/lib64 --program-suffix=-emacs-26 --includedir=/usr/include/emacs-26 --infodir=/usr/share/info/emacs-26 --localstatedir=/var --enable-locallisppath=/etc/emacs:/usr/share/emacs/site-lisp --without-compress-install --without-hesiod --without-pop --with-file-notification=inotify --enable-acl --with-dbus --without-modules --without-gameuser --with-gpm --with-kerberos --with-kerberos5 --with-lcms2 --with-xml2 --without-mailutils --without-selinux --with-gnutls --with-libsystemd --with-threads --without-wide-int --with-zlib --with-sound=alsa --with-x --without-ns --without-gconf --without-gsettings --without-toolkit-scroll-bars --with-gif --with-jpeg --with-png --with-rsvg --with-tiff --with-xpm --without-imagemagick --with-xft --without-cairo --without-libotf --without-m17n-flt --with-x-toolkit=gtk3 --without-xwidgets 'CFLAGS=-O2 -march=x86-64 -pipe' CPPFLAGS= 'LDFLAGS=-Wl,-O1 -Wl,--as-needed')
        windowsys  x
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 4b20c7206 2020-03-13 17:34:44 -0400
        dir        ~/.doom.d/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /bin/bash
        uname      Linux 5.4.0-sabayon #1 SMP Tue Feb 25 22:46:38 UTC 2020 x86_64
        path       (~/bin ~/sbin ~/.npm-global/bin ~/.emacs.d/bin /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin /opt/bin /usr/lib/llvm/9/bin /usr/games/bin /usr/libexec/emacs/26.2/x86_64-pc-linux-gnu/)
config  envfile    envvar-file
        elc-files  0
        modules    (:completion company ivy :ui doom doom-dashboard doom-quit hl-todo modeline nav-flash ophints (popup +defaults) vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold snippets :emacs dired electric vc :checkers syntax spell :tools (eval +overlay) lookup magit :lang clojure csharp data emacs-lisp fsharp javascript latex factor markdown (org +dragndrop +present) racket scheme sh :config (default +bindings +smartparens))
        packages   (n/a)
        unpin      (n/a)
        elpa       (n/a)

FYI you can update dired with gr, when using evil.

it brought up the 'g' leader key menu

Not the leader key, but the g prefix in normal mode, which has a number of sub bindings.
In any case, we are using the evil-collection package, which provides "evilified" keybinds for a number of packages, including dired. It binds gr to revert-buffer here, which is what you want. You'll find other keybinds there too.
Hope that helps!

authors: hlissner vigilancetech-com yoavm448

repo: hlissner/doom-emacs


text:
rtags doesn't work with ivy unless it is reloaded

Observed behavior

When using the +lookup functions in c++-mode, which calls functions rtags-find-symbol-at-point and rtags-find-references-at-point, if there are multiple results, all you get is a message in the echo area saying RTags: Found n locations.
If you open up rtags.el and eval the buffer, then the expected behavior occurs afterwards.
Expected behavior
Ivy should open up with the list of locations.
System information

Click to expand

OS: gnu/linux (x86_64-pc-linux-gnu)
Emacs: 26.1 (Jul 05, 2018)
Doom: 2.0.9 (develop e865526c75c307b8a2cf48fcf7a018364b8660e7)
Graphic display: t (daemon: nil)
System features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 MODULES THREADS LIBSYSTEMD LCMS2
Details:elc count: 0
uname -a:  Linux thinkpad 4.17.8-1-zen #1 ZEN SMP PREEMPT Wed Jul 18 09:56:17 UTC 2018 x86_64 GNU/Linux
modules:   (:feature eval (evil +everywhere) file-templates (lookup +devdocs +docsets) snippets spellcheck (syntax-checker +childframe) workspaces :completion (ivy +fuzzy) :ui doom doom-dashboard doom-modeline doom-quit evil-goggles fci hl-todo nav-flash neotree (popup +all +defaults) vi-tilde-fringe window-select :editor :emacs dired ediff electric eshell imenu term :tools make (magit +hub) pdf tmux upload :lang (cc +irony +rtags) crystal clojure csharp data elixir elm emacs-lisp ess go (haskell +intero) hy (java +meghanada) javascript julia (latex +pdf-tools) ledger lua markdown nim nix ocaml (org +attach +babel +capture +export +present) perl php plantuml purescript python rest ruby rust scala sh swift web :collab impatient-mode :config)
packages:  n/a
exec-path: (/usr/local/bin /usr/local/sbin /usr/bin /opt/flutter/bin /usr/lib/jvm/default/bin /opt/openresty/bin /opt/openresty/nginx/sbin /usr/bin/site_perl /usr/bin/vendor_perl /usr/bin/core_perl /usr/lib/emacs/26.1/x86_64-pc-linux-gnu)

If you delete rtags.elc and restart Emacs, does this fix the problem?
(delete-file (locate-library "rtags.elc"))

That didn't help, but some change made in the last few days did. After a pull and make it works again

Very odd. I'll consider this resolved in the meantime. Feel free to reopen this if the issue resurfaces.


text:
modules/lang: Add GraphQL module

Based on e24b8cd1d1e4ceb7e4454a267985b639d5e7eb06, the only difference is support for .graphql extension.
Also, cleanup core/autoload/help.el, it was pointing for support for some files in data module that is not support since the commit above, and was making me confused about why GraphQL was not working.

Hi. Thanks for the PR, but I cannot accept it. The config for graphql is too small to warrant its own module. The updates to autoload/help.el is useful, however. I'll accept a PR for those separately.

authors: hlissner thiagokokada


text:
#173 QA fixes for company page

Fix https://github.com/hlxsites/merative/issues/173
Test URLs:

Before: https://main--merative2--hlxsites.hlx.page/company
After: https://issue-173-company-page--merative2--hlxsites.hlx.page/company

Description:

add promo section styles
remove hero auto blocking
fix teaser-list spacing
fix columns spacing

Changes to columns.css appears long since .columns was added to some class names which required moving the order around to satisfy linting rules.


text:
feat: Vertical tabs for https://github.com/hlxsites/mmm-af/issues/10

Partial Fix for #10
Test URLs:

https://issue-10--mmm-af--hlxsites.hlx.page/drafts/fragments/explore

cityName? 😉

Thanks. Copy-paste error :( . Fixed. BTW, I refactored the whole thing to make it render correctly on smaller screens.

repo: hlxsites/mmm-af


text:
KB Resources visible in Tagging

KB resources are showing in Tagging, they should remain hidden where the source is KB. For instance, if we take the example of the SpectraMax i3x product page
https://www.moleculardevices.com/products/microplate-readers/multi-mode-readers/spectramax-i3x-readers#resources
The user guide should not be displayed in the resources section and should be hidden.

@dev-rajneeshkumar @MeghnaTewari what is the rule here? Should all KB resources be hidden in the resource tab, every time?
We did not get that requirement, so far we filter only some of the resources by resource type.

Yes @mhaack  all KB resources should be hidden from tagging  however they will appear in resources hub/coveo search that's why source column is provided in the export. It might not be discussed directly but this is how it is on old site.

@dev-rajneeshkumar what about sitemap.xml should they also be filtered out there?

Well in old site @mhaack we didn't excluded from sitemap but still we need to confirm from client that if they want to exclude it now.

@MeghnaTewari please test again should be fixed. Overall this filtered out ~3.300 KB (tagged and untagged) entries which should not show up any more on the resource tabs.

authors: MeghnaTewari dev-rajneeshkumar mhaack

repo: hlxsites/moleculardevices


text:
[SKIP-PREVIEW] Update documentation

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

See https://github.com/hmcts/ccd-definition-store-api/pull/67

repo: hmcts/ccd-definition-store-api