Crash in BindingViewPagerAdapter

I'm finally getting around to upgrading to beta-3 in order to replace my own work-around for setting LifecycleOwner with yours.  I am getting a crash however in a Fragment that contains a ViewPager with a View that in turn has a RecyclerView.  I am using binding-collection-adapter for both the ViewPager as well as the RecyclerView.   The crash is occurring in BindingViewPagerAdapter.instantiateItem(...) when binding.setLifecycleOwner(...) is called.  I think the problem is that this is called before the onBindBinding(...) is called.  In my own implementation I am calling binding.setLifecycleOwner(...) inside the onBindBinding(...) method itself after executing binding.executePendingBindings().  I have found that the order of executePendingBindings() and setLifecyclerOwner(...) calls is important when dealing with nested data-bound views such as these.  For now I am reverting back to a previous version.  I will follow up on this issue with a Pull Request.

Uploaded a version with a fix, can you try it out when you have a chance?
repositories {
  maven { url "https://dl.bintray.com/evant/maven" }
}
dependencies {
  compile 'me.tatarka.bindingcollectionadapter2:bindingcollectionadapter:3.0.0-beta4'
}

branch is: https://github.com/evant/binding-collection-adapter/tree/lifecycle-fix

Unfortunately my project hasn't been upgraded to androidx yet.  Getting to that next month.   Can you upload the same for the backport?

I have the same issue, and am using the back-port.

@evant it fixes the issue for me. I had the same problem with beta3 though a slightly different case. The root cause was that executePendingBindings was called before the actual binding variable was set.
When will it be merged to the main branch & released?
thanks!

3.0.0 has been released which includes this fix.

@evant Actually the issue is not fixed for my in 3.0.0. It was fixed in commit be54e475e4 though.
I think the issue with the current implementation is line 135 in:
https://github.com/evant/binding-collection-adapter/blob/1657869aae3ef48b5164f3aca4109cb2e6b8069b/bindingcollectionadapter/src/main/java/me/tatarka/bindingcollectionadapter2/BindingViewPagerAdapter.java:
binding.setLifecycleOwner(lifecycleOwner);
adding the lifecycle owner listener causes executePendingBindings to be "prematurely" called causing the crash.

@evant  I think you need to switch the order of binding.setLifeycleOwner(...) and binding.executePendingBindings().  This is counter-intuitive, but in my testing, this seems to be the correct order of operations.
In fact, I am currently using version 2.3.0-beta1 and I have extended your adapters with my own custom version.   In those I am doing the following:
    override fun onBindBinding(binding: ViewDataBinding, variableId: Int, layoutRes: Int,
                               position: Int, item: T) {
        super.onBindBinding(binding, variableId, layoutRes, position, item) // calls binding.executePendingBindings()
...
        if (lifecycleOwner != null) {
            binding.setLifecycleOwner(lifecycleOwner)
        }
    }```

These adapters are working without error.

@evant Any update on this one?

FYI - Google has now provided public a public getter for LifecycleOwner on ViewDataBinding so I don't think you need to use reflection any more.

I've also found a problem with how you are attempting to set the lifecycleOwner in BindingRecyclerViewAdapter.  Specifically, you are attempting to do it in the method onAttachedToRecyclerView.  I have found that this is too early in the databinding lifecycle, and that the lifecycleOwner of the RecyclerView's ViewDataBinding may be null here because it has not yet been set.   Instead I recommend trying to set it at the start of onBindBinding.
Below is a copy of my extended version of your BindingRecyclerViewAdapter and it is working perfectly.  (Note that I am still using version 2.3.0-beta1 of your library.)
open class LifecycleAwareBindingRecyclerViewAdapter<T> : BindingRecyclerViewAdapter<T>() {

    private var recyclerView: RecyclerView? = null
    private var lifecycleOwnerRef: WeakReference<LifecycleOwner>? = null

    /**
     * Sets the LifecycleOwner so that it can be set on item bindings.  Calling this method should
     * be unnecessary since the LifecycleOwner will be set automatically as long as the View
     * containing the RecyclerView uses databinding and has its LifecycleOwner set.
     */
    fun setLifecycleOwner(lifecycleOwner: LifecycleOwner?) {
        if (lifecycleOwner != null) lifecycleOwnerRef = WeakReference(lifecycleOwner)
    }

    override fun onBindBinding(binding: ViewDataBinding, variableId: Int, layoutRes: Int,
                               position: Int, item: T) {
        trySetLifecycleOwner()
        super.onBindBinding(binding, variableId, layoutRes, position, item)
        var lifecycleOwner: LifecycleOwner? = lifecycleOwnerRef?.get()
        if (lifecycleOwner == null && binding.root.context is LifecycleOwner) {
            lifecycleOwner = binding.root.context as LifecycleOwner
        }
        if (lifecycleOwner != null) {
            binding.lifecycleOwner = lifecycleOwner
        }
    }

    override fun onAttachedToRecyclerView(recyclerView: RecyclerView) {
        super.onAttachedToRecyclerView(recyclerView)
        this.recyclerView = recyclerView
    }

    override fun onDetachedFromRecyclerView(recyclerView: RecyclerView) {
        super.onDetachedFromRecyclerView(recyclerView)
        this.recyclerView = null
    }

    private fun trySetLifecycleOwner() {
        if (lifecycleOwnerRef?.get() == null) {
            val view = recyclerView ?: return
            val binding: ViewDataBinding = DataBindingUtil.findBinding(view) ?: return
            val bindingLifecycleOwner = binding.lifecycleOwner ?: return
            lifecycleOwnerRef = WeakReference(bindingLifecycleOwner)
        }
    }
}

@wongcain thanks for the input. Feel free to submit a pr with those changes, otherwise I'll try to make them when I get a chance.

@wongcain how do you use your LifecycleAwareBindingRecyclerViewAdapter? Where could I replace it with default BindingRecyclerViewAdapter?

Create an instance of the adapter in your Activity or Fragment and set it as a variable in your data-bound layout.  Then just bind it to the RecyclerView like this:
            <android.support.v7.widget.RecyclerView
                android:layout_width="match_parent"
                android:layout_height="wrap_content"
<EMAIL_ADDRESS><EMAIL_ADDRESS>                app:layoutManager="@{LayoutManagers.linear()}"
                **app:adapter="@{adapter}"**/>

@evant I've finally got my project updated to AndroidX and have just issued a pull request to fix these crashes: https://github.com/evant/binding-collection-adapter/pull/160
Please review and let me know when you will be able to include these changes into a new release.
Thank you!

Looks good! Will work on getting a release out in the coming week or so.

Awesome.  Thanks for the quick response!

Released as version 3.1.0

🎉


Create round-trip tests

Words can be converted from and into bytes/u16, messages can be converted from and into byte arrays. We should have tests that convert bytes into messages/words and then back into bytes.

Resolved by #53


📝[DOCS] adding Stargazers and Forkers section to readme.md

We need to add Stargazers and Forkers section to readme.md
adding Stargazers and Forkers section to readme.md
Suggested Change
we can add Stargazers and Forkers section to readme.md
Stargazers
Use Case:

Bookmarking Projects
Discovering Popularity

Benefits:

Visibility
Feedback Indicator
Community Engagement

Forkers
Use Case:

Creating Personal Copies
Contributing Back

Benefits:

Encouraging Innovation
Easy Collaboration
Building Ownership

ADD LABELS HACKTOBERFEST AND GSSOC EXT 24 AND LEVEL 2 OR LEVEL 3
ASSIGN ME THE WORK
THANK YOU @notsoocool  !

@amiya-cyber its only displaying black window, kindly fix it and raise a new PR, there i will assign you label if it works


Rat in a maze

I think rat in a maze would be a better algorithm for this repo with backtracking, and i would love to make it for hacktoberfest
thanks

@mendoza I would like to work on this assign me this issue. Please tell the programming language.

please assign  this issue to me in c++


Scrollbar not visible on Android

Hello,
I'm having some trouble to show the scrollbar in Android devices, it's working in all the others platforms (iOS and Windows)
To be more precise, the scroll is available. I can go down and up but I cannot see the scrollbar and only on an android device. I tried on a 4.4.4 and a 6.0.1 OS version.
I made an example : http://codepen.io/rberthome/pen/mEyMov
This will work on your desktop browser and even in your smartphone through your browser.
To reproduce the issue you have to put the code in a ionic project. Follow these steps :

Create a blank project => ionic start NoScrollBarAndroid blank
Add android platform => ionic platform add android
Replace the body of your index.html file with the codeopen one
Add the controller from the codeopen project to the app.js
Copy the content of the CSS part to the style.css
just run the application on your android (phone or simulator) => ionic run android

Do you have any workaround to correct this ?
Thanks.

I opened a topic in the forum : https://forum.ionicframework.com/t/scrollbar-not-visible-on-android/53616
Does anyone have a workaround or a solution ?

Hello as it looks like this issue was solved in the forums i will be closing this issue for now. Thanks for using Ionic!


[WIP] Fix dictionary encoding test bug

Coverage remained the same at 68.038% when pulling 61a0259c71f36a441269edbc75ab4f3cd5592c97 on liujiajun:master into 52f7248256b892750c695b2bf1b1f89547badbcf on apache:master.


fix data discovery issue in rake tasks (public schema is not accessed)

I am exploring a hotfix here: https://github.com/restarone/violet_rails/pull/686/files#diff-bff8182f3a99c39531f1db7b69790c3b38596cb871726bd02088776c73c289be

Can you provide some more context? What's the expected behavior? Also, you mentioned a hotfix. Did it work?


Feature request: Include AI instruction in 'data used to generate this message' dialog

You recently enhanced OpenCharacters so that AI instructions (given using the /ai command) are saved in the conversation history.
Now that that's done, it would be nice if the AI instruction was included in the 'Here's some data that the character used to generate this message:' dialog that appears when you click on the brain icon next to an AI response.
Thanks again for the extremely useful project!

Thanks! Just added this


Content refactoring 2

Fixes https://github.com/adr/adr.github.io/issues/57

The link "http://www.iso-architecture.org/42010/templates/ " worked yesterday, but not today. I leave it in. Maybe, in a follow-up we need to hadnle.


ReadReport loosing data

It seems like ReadReport is loosing data when a lot of data is sent to the Host in a short amount of time.  In my case about 60KB to 100KB is being sent at full speed on a USB 2.0 port in high speed mode.  This is likely because the buffer is too small and the ReadReport function takes too long.  I see there is a HidFastReadDevice with a faster read function, but no way to create an instance of the class.  There is also nothing exposed in the OpenDevice function to allow overriding the default buffer size to fit the application.
What is the best fix for this?  Do I need to download the source code and change it myself?

The latest code on the master branch includes the HidFastReadEnumerator class that will instantiateHidFastReadDevice objects.

I ending up adding the below code to the HidDevices.cs file to get around the issue.  It turned out the buffer was too small and this code allows me to change the buffer to a more reasonable number for my application.
       public int InputBuffer         {             get             {                 int i = 0;                 NativeMethods.HidD_GetNumInputBuffers(Handle, ref i);                 return i;             }             set             {                 if (value > 31)                 {                     NativeMethods.HidD_SetNumInputBuffers(Handle, value);                 }                 else                 {                     throw new ArgumentOutOfRangeException(string.Concat(value, " is too low of a value."));                 }             }         }

The purpose of the "Fast" subclass was to avoid checking "IsConnected" every time a packet comes in. The check is fairly slow (I can't remember why, I haven't touched this in years). I would say try it without the IsConnected check.
Also, why are you turning MonitorDeviceEvents on and off?

Thank you for the fast answer.
I have tried this without checking IsConnected and looks like receiving works better though my GUI is stalling when HID device connected. I guess i should find a way to run all HID stuff in other thread to fix it.
I thought DeviceEvents are different for instances of HidDevice and HidFastReadDevice (and HidDevice is passed to the event as argument) so i decided to monitor plugging/unplugging through hidDevice (HidDevice instance) while reading/writing is managed through fastDevice (HidFastReadDevice instance). It seem not working quite good but i want to reach proper report receiving first


Weird Error and I don't know how to describe it

Love the tool. Weird error this morning while running it.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x7c6bfc]
goroutine 758 [running]:
main.scanLog({0x944710, 0xc53ce0}, {0xc0000ac1a0, 0x1c}, 0xd952e6c0e0891067?, 0xe1acea4db374cd93?)
/root/go/pkg/mod/github.com/g0ldencybersec/gungnir@v1.0.2/gungnir/main.go:233 +0x8dc
created by main.main in goroutine 1
/root/go/pkg/mod/github.com/g0ldencybersec/gungnir@v1.0.2/gungnir/main.go:277 +0x1d0

Fixed with updated version


Add synthesis guard to generated VHDL simulation packages

In case user accidentally loads it into their synthesis project.

Tested in Vivado 2023.1 and this is not actually needed. Having a package file enabled that has lots on unmet dependencies and un-synthesizable code does not affect the build.


could cpu machines train the models?

which kind of model do you need to support cpu training,  self-supervised training should use gpu cause it is too slow to use gpu.  classification finetuning and detection finetuning using cpu may be possible

I see, self-supervised training with MAE.. (:


Trigger inlineAction with CTRL+Enter

Related Issue
Fixes #4575
Description
This ensures that the keyboard shortcut of Ctrl+Enter works when an inlineAction is assigned to a Text.Input.
How Verified
Verified manually in adaptivecards-designer-app
Microsoft Reviewers: Open in CodeFlow

/azp run


Add set_font() to porting-guide.md

I was just updating some of my very old code and noticed set_font() had been forgotten.

Thank you!


How to run this on Mac without CUDA?

Heyhey,
I have a question about how to run inference on Mac without CUDA:

The install instructions say this is compatible with Linux or macOS with Python ≥ 3.6
There's a github issue that says inference can be run without a GPU: https://github.com/facebookresearch/Mask2Former/issues/169

Whenever I try to run a trained model, I get an error that MSDeformAttn is not defined because that's a class that has to be compiled with CUDA libs.
Am I missing something? Is there some way to run this on Mac without CUDA or is CUDA strictly required?
Cheers,
Flo

I got same error here:
ModuleNotFoundError: No module named 'MultiScaleDeformableAttention'

During handling of the above exception, another exception occurred:
...
ModuleNotFoundError:

Please compile MultiScaleDeformableAttention CUDA op with the following commands:
	`cd mask2former/modeling/pixel_decoder/ops`
	`sh make.sh`

Hello,
I am also facing the same issue. Any solutions for this?

Are there any solutions now? I also get stuck here... ):

metoo! macOS user need help...

Tere's how I made it work on my laptop (AMD linux, no GPU).
The repo already provides the CUDA function MSDeformAttnFunction for non CUDA/just pytorch via ms_deform_attn_core_pytorch but it's most likely disabled so it doesn't hinder performance.
Simply disable the cuda checks and it works:
In mask2former/modeling/pixel_decoder/ops/modules/ms_deform_attn.py:
try:
    from ..functions import MSDeformAttnFunction
except ModuleNotFoundError:
    pass

and
mask2former/modeling/pixel_decoder/ops/functions/ms_deform_attn_func.py:
try:
    import MultiScaleDeformableAttention as MSDA
except ModuleNotFoundError as e:
    pass

and use
cfg.MODEL.DEVICE = "cpu"
predictor = DefaultPredictor(cfg)


[Bug]: Python sdk harness failed: TypeError: can only concatenate str (not "NoneType") to str

What happened?
I'm trying to send custom metrics to datadog using a DoFn but the python sdk test harness is failing with an error that I don't know how to interpret:
 Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker_main.py", line 181, in main
    sdk_harness.run()
  File "/usr/local/lib/python3.9/site-packages/apache_beam/runners/worker/sdk_worker.py", line 256, in run
    getattr(self, SdkHarness.REQUEST_METHOD_PREFIX + request_type)(
TypeError: can only concatenate str (not "NoneType") to str

I'm running the streaming pipeline as a flex template in gcp dataflow, using the python requests module for POST calls

apache-beam[gcp]==2.49.0
gcr.io/dataflow-templates-base/python310-template-launcher-base

Issue Priority
Priority: 3 (minor)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

When I comment out the windowinto line the error goes away but the pipeline still doesn't function as expected -- which might be an issue with my custom DoFn
    with beam.Pipeline(options=options) as pipeline:
        messages = (
            pipeline
            | f"Read from input topic {subscription_id}" >>
            beam.io.ReadFromPubSub(subscription=subscription_id,
                                   with_attributes=False)
            | f"Deserialize Avro {subscription_id}" >> beam.ParDo(
                ConfluentAvroReader(schema_registry_conf)).with_outputs(
                    "record", "error"))

        records = messages["record"]
        errors = messages["error"]

        (records
         | 'Aggregate msgs in fixed window' >> beam.WindowInto(beam.window.FixedWindows(15))
         | 'Send hardcoded value to datadog' >> beam.ParDo(SendToDatadog())
         | 'Print results' >> beam.Map(print)
        )

The error happens in the SDK internals and is rather strange. It sounds as though a runner sends a malformed request to the SDK. I would suggest you try again and if the issue still persist provide a minimal pipeline that reproduces it, that we could try out, or work with Dataflow customer support.

Hi, any news about the repro? Thanks!

Thanks for the followup! I ended up going a different route, by removing the datadog module from the pipeline and setting up a separate container to relay messages from pubsub to datadog. It feels like beam/dataflow is structured around data transformation -- trying to coerce it to do external API calls seems like a dumb idea in hindsight (especially on an unpeered-vpc)


feat: power modifier

Issue #, if available:
Description of changes:
Add support for raising gates to powers
Testing done:
Unit testing
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Also worth implementing __pow__ for Gate and Instruction

Agreed for instruction. Gate doesn't actually have a power attribute, only in the to_openqasm method and Instruction subroutine method


add leading path of subversion-migration

This should fix the broken css on the training-kit for https://training.github.com/kit/downloads/subversion-migration.html
cc @jordanmccullough

:sparkles: :+1: :sparkles:


Dont send emails to example email addresses

Codecov Report

Merging #109 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
+ Coverage   92.47%   92.49%   +0.02%
==========================================
  Files          11       11
  Lines        1461     1465       +4
  Branches      153      154       +1
==========================================
+ Hits         1351     1355       +4
  Misses         78       78
  Partials       32       32

Impacted Files
Coverage Δ

morpheus/app/worker.py
93.37% <100%> (+0.07%)
:arrow_up:

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 955f653...eacc0e0. Read the comment docs.


add some logic for known properties

makes #1649 go brrr. i haven't updated the examples yet but would something like this be ok?
- **Breaking** Known physical device properties (VkPhysicalDeviceProperties, VkPhysicalDeviceLimits, VkPhysicalDeviceSparseProperties) are now no longer `Option<T>`.
  - These properties are available with every `vkGetPhysicalDeviceProperties2` call
- Add some `Default` instances to make the auto trait happy

While it's funny, unfortunately GitHub doesn't understand "makes #1649 go brrr" to link the two issues. :D

any ideas for improving the macro would be greatly appreciated. i had to parse it as tt because literal would not work and had to duplicate some code in the macros but as long as it works i guess.

The autogen module is essentially already a macro, it generates code. So what you could do is eliminate the properties! macro entirely, and generate the final code entirely in autogen. That gives you much more freedom, because you are generating code with full Rust instead of the macro language.

@incertia Thank you for your work! This improvement looks good to me in general. Please fix the issue with indentation I mentioned above, and if possible maybe get rid of macro use(however, I can proceed with merging anyway, the improvement is useful!)

done

The autogen module is essentially already a macro, it generates code. So what you could do is eliminate the properties! macro entirely, and generate the final code entirely in autogen. That gives you much more freedom, because you are generating code with full Rust instead of the macro language.

I think this should be addressed in a separate PR. It would be quite a large change but if you think we can do it here I can look into making the changes as well.

It's fine. If you want to go ahead and do it, you can, but it's no problem if you leave this PR as it is. I or someone else can do the conversion some other time.

Probably good to merge then. I'll look into emitting the correct code within autogen sometime this week I hope.

@incertia Pull Request merged. Thanks again! I have a number of pending PRs to review, so the review process is taking time, but I hope to clean up the rest soon too.


feat: Implemented dynamic AI selection display in tab

Description of changes
display currently ai on tab
Issue number:
16

Can I get some screenshots of the change? Would also prefer you using qt designer/creator over directly adding the widget in the main code. Let me know through teams if you want a tutorial or need help setting up.


Multiple Report objects can refer to / update the same Layout, causing error/race/unpredictable updates

Describe the bug
If multiple AL Report objects specify the same RDLCLayout (and presumably WordLayout, although I didn't test that myself), it seems to be a coin-flip whether

we get an error that the RDL file is already 'opened by another application' (presumably another instance of the compiler)
the build succeeds, but who knows which one of them actually 'wins' and has its updates applied when the dust settles!

This is obviously wrong; such a condition of a layout specified in more than one object should be an error.
To Reproduce
Make 2 reports, give them the same Layout but different columns or other properties that would manifest in the layout, and then try building a bunch of times. You should see that sometimes one of the AL reports 'wins' and sometimes the other, and/or sometimes we get a build error because 2 compiler instances were trying to update the same layout.
Expected behavior
This should be a compiler error because it makes no sense to have 2 AL Reports in the same project that will try to update the same layout. Erroring if the developer accidentally let 2 objects target the same layout will avoid unwanted changes from old AL objects breaking production RDL layouts, and avoid developers becoming confused about why that's happening and having to manually search for duplicated layout filenames in AL files.
5. Versions:

AL Language: 6.1.352568

This is a bug, we should have a deterministic behavior for this. We should either block the use of the layout by two or more reports or create a copy for each object.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 24.0.15279.0 and VS Code Extension Version 13.0.924484.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 24.0.15812.0 and VS Code Extension Version 13.0.934715.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


Add documentation for ns-popover-angular-event

This is currently an undocumented option.

@ilyagelman
Thanks for reporting this :) Would you be kind enough to submit a pull request for that?


support reverse proxy to a unix socket

For debugging docker things I use the following method in 3 shells right now:
socat tcp-listen:3000,bind=<IP_ADDRESS>,reuseaddr,fork UNIX-CONNECT:/var/run/docker.sock

mitmproxy -R http://localhost:3000 -p 3001

export DOCKER_HOST=<IP_ADDRESS>:3001
docker service ps 53pr4a3e2zkj

It would be really cool if mitm proxy supported acting as a reverse proxy to a unix socket. That would remove the need for the socat. I imagine it working like this:
mitmproxy -R unix:///var/run/docker.sock -p 3001

Thanks for the suggestion. What would we need to do to support this? :)

Is opening the socket like this enough?
url = 'unix:///var/run/docker.sock'
if url.startswith('unix://'):
    s = socket.socket(socket.AF_UNIX)
    s.connect(path)
    # use socket as usual: s.send(...)

Yeah, it should be pretty simple IMO

The relevant bits are here.
We'd be happy to accept a well-written PR for this, but we're focusing on other things currently. I'm closing this for now - if it turns out there's significant interest from others, we're happy to reconsider that decision.

I'm in search of a reverse proxy capable of sending http requests to a Unix socket and am considering taking this bit of work on.
@mhils It looks like the code has changed substantially since 2017 and that the method and file referenced in the comment above no longer exists. Do you have any updated pointers that may help me to implement this feature today?

We now use asyncio, the relevant bits are around here: https://github.com/mitmproxy/mitmproxy/blob/a51dc10d8b97d46c77d11a4bbb4d0c393b2c8a39/mitmproxy/proxy/server.py#L153

Did anything ever come of this? The issue was closed but I don't see relevant code?


Current stable version of Firefox Android is 82, but caniuse.com says 79 is the latest stable version.

Actually, caniuse.com says that the latest stable version of Firefox for Android is 79. Example, https://caniuse.com/flexbox is that 79 is the latest version.
But Mozilla has already released 82 last month.  Why?

Firefox for Android for a long time was stuck on an older version so hadn't been keeping much of an eye on it. Fixed now, thanks!


Incorrect image versions in the manifest files

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When I accessed occm manifest file with the tag v1.25.3, openstack-cloud-controller-manager image version was only at v1.25.0.
What you expected to happen:
I wanted to use a fix introduced in the v1.25.2 so I downloaded the manifest file with tag v1.25.3 and I expected image version to be also v1.25.3.
How to reproduce it:
Download the manifest and check the image tag.
Anything else we need to know?:
It seems like all binaries are affected and also multiple tags, e.g. see cinder-csi-plugin manifest v1.22.2.
Environment:

openstack-cloud-controller-manager(or other related binary) version: v1.25.3
OpenStack version:
Others:

um.. looks like v1.25.x all not set the tag correctly
v1.24 did so like this, so after
https://github.com/kubernetes/cloud-provider-openstack/pull/2102
we should do another release and tag correctly
/assign
# grep v1.24 * -r
barbican-kms/pod.yaml:      image: docker.io/k8scloudprovider/barbican-kms-plugin:v1.24.2

please check the latest versions is this solved?

@chess-knight please check whether it's ok for you now per @zetaab
there is a new release recently and should updated the tag

Thank you for the releases. There are correct tags for the v1.24.6, v1.25.4 and v1.26.1. For our needs, it seems sufficient for now.
But I have a question. Do you support also older versions or do you maintain only the most recent three minor releases?

Do you support also older versions or do you maintain only the most recent three minor releases?

hard for us to maintain so many older version.. so usually we backport up to N-3 older version
this is a convention and I think we documented somewhere

hard for us to maintain so many older version.. so usually we backport up to N-3 older version this is a convention and I think we documented somewhere

Ok, I understand. Thank you again!

per above discussion


New Version Bug: no tab title for rooms

Describe the bug
The tab title is the URL, instead if the room name. I am using the latest Chrome on Windows 10.

As a sidenote, another bug I encountered was the language menu not working properly (clicking does nothing)

Currently we're waiting on @benawad to make a REST endpoint to get the room info.

#1778

Implemented by #1778


make check failing on NixOS

The tests start failing on 0.15.0, 0.14.3 builds fine.
fwup 0.15.0: tests/test-suite.log
=======================================
   fwup 0.15.0: tests/test-suite.log
=======================================

# TOTAL: 125
# PASS:  56
# SKIP:  0
# XFAIL: 0
# FAIL:  69
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: 001_simple_fw
===================

  0%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-001_simple_fw.test'
FAIL 001_simple_fw.test (exit status: 1)

FAIL: 002_resource_subdir
=========================

  0%
 33%
 66%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-002_resource_subdir.test'
FAIL 002_resource_subdir.test (exit status: 1)

FAIL: 003_write_offset
======================

  0%
 43%
 87%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-003_write_offset.test'
FAIL 003_write_offset.test (exit status: 1)

FAIL: 004_env_vars
==================

  0%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-004_env_vars.test'
FAIL 004_env_vars.test (exit status: 1)

FAIL: 005_define
================

  0%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-005_define.test'
FAIL 005_define.test (exit status: 1)

FAIL: 007_mbr
=============

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-007_mbr.test'
FAIL 007_mbr.test (exit status: 1)

FAIL: 008_partial_mbr
=====================

  0%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-008_partial_mbr.test'
FAIL 008_partial_mbr.test (exit status: 1)

FAIL: 010_fat_mkfs
==================

  0%
 50%
 99%
100%
Elapsed time: 0.002s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-010_fat_mkfs.test'
FAIL 010_fat_mkfs.test (exit status: 1)

FAIL: 011_fat_setlabel
======================

  0%
 33%
 66%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-011_fat_setlabel.test'
FAIL 011_fat_setlabel.test (exit status: 1)

FAIL: 012_fat_write
===================

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-012_fat_write.test'
FAIL 012_fat_write.test (exit status: 1)

FAIL: 013_fat_mv
================

  0%
 99%
100%
Elapsed time: 0.003s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-013_fat_mv.test'
FAIL 013_fat_mv.test (exit status: 1)

FAIL: 014_fat_cp
================

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-014_fat_cp.test'
FAIL 014_fat_cp.test (exit status: 1)

FAIL: 017_fat_rm
================

  0%
 99%
100%
Elapsed time: 0.002s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-017_fat_rm.test'
FAIL 017_fat_rm.test (exit status: 1)

FAIL: 018_numeric_progress
==========================

verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-018_numeric_progress.test'
FAIL 018_numeric_progress.test (exit status: 1)

FAIL: 019_quiet_progress
========================

verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-019_quiet_progress.test'
FAIL 019_quiet_progress.test (exit status: 1)

FAIL: 022_signed_fw
===================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.15.0.drv-0/source/tests
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-022_signed_fw.test'
FAIL 022_signed_fw.test (exit status: 1)

FAIL: 026_sign_again
====================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.15.0.drv-0/source/tests
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-026_sign_again.test'
FAIL 026_sign_again.test (exit status: 1)

FAIL: 027_fat_timestamp
=======================

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-027_fat_timestamp.test/fwup.img.1'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-027_fat_timestamp.test'
FAIL 027_fat_timestamp.test (exit status: 1)

FAIL: 028_osip
==============

  0%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-028_osip.test'
FAIL 028_osip.test (exit status: 1)

FAIL: 029_5G_offset
===================

Sparse files supported

  0%
 43%
 87%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-029_5G_offset.test'
FAIL 029_5G_offset.test (exit status: 1)

FAIL: 030_2T_offset
===================

Sparse files supported

  0%
 43%
 87%
 99%
100%
Elapsed time: 0.003s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-030_2T_offset.test'
FAIL 030_2T_offset.test (exit status: 1)

FAIL: 031_fat_mkfs_5G
=====================

Sparse files supported

  0%
 50%
 99%
100%
Elapsed time: 0.106s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-031_fat_mkfs_5G.test'
FAIL 031_fat_mkfs_5G.test (exit status: 1)

FAIL: 032_fat_2T_offset
=======================

Sparse files supported

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-032_fat_2T_offset.test'
FAIL 032_fat_2T_offset.test (exit status: 1)

FAIL: 035_streaming
===================

  0%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-035_streaming.test'
FAIL 035_streaming.test (exit status: 1)

FAIL: 036_streaming_signed_fw
=============================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.15.0.drv-0/source/tests
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-036_streaming_signed_fw.test'
FAIL 036_streaming_signed_fw.test (exit status: 1)

FAIL: 038_write_15M
===================

  0%
  1%
  2%
  3%
  4%
  5%
  6%
  7%
  8%
  9%
 10%
 11%
 12%
 13%
 14%
 15%
 16%
 17%
 18%
 19%
 20%
 21%
 22%
 23%
 24%
 25%
 26%
 27%
 28%
 29%
 30%
 31%
 32%
 33%
 34%
 35%
 36%
 37%
 38%
 39%
 40%
 41%
 42%
 43%
 44%
 45%
 46%
 47%
 48%
 49%
 50%
 51%
 52%
 53%
 54%
 55%
 56%
 57%
 58%
 59%
 60%
 61%
 62%
 63%
 64%
 65%
 66%
 67%
 68%
 69%
 70%
 71%
 72%
 73%
 74%
 75%
 76%
 77%
 78%
 79%
 80%
 81%
 82%
 83%
 84%
 85%
 86%
 87%
 88%
 89%
 90%
 91%
 92%
 93%
 94%
 95%
 96%
 97%
 98%
 99%
100%
Elapsed time: 0.058s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-038_write_15M.test'
FAIL 038_write_15M.test (exit status: 1)

FAIL: 039_upgrade
=================

  0%
  1%
 42%
 85%
 99%
100%
Elapsed time: 0.004s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-039_upgrade.test'
FAIL 039_upgrade.test (exit status: 1)

FAIL: 042_fat_am335x
====================

  0%
 50%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-042_fat_am335x.test'
FAIL 042_fat_am335x.test (exit status: 1)

FAIL: 043_fat_touch
===================

  0%
 33%
 66%
 99%
100%
Elapsed time: 0.001s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-043_fat_touch.test'
FAIL 043_fat_touch.test (exit status: 1)

FAIL: 044_require_file_exist
============================

  0%
 25%
 50%
 75%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-044_require_file_exist.test'
FAIL 044_require_file_exist.test (exit status: 1)

FAIL: 045_legacy_require_partition1
===================================

  0%
  1%
 42%
 85%
 99%
100%
Elapsed time: 0.002s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-045_legacy_require_partition1.test'
FAIL 045_legacy_require_partition1.test (exit status: 1)

FAIL: 047_unknown_apply_succeeds
================================

/tmp/nix-build-fwup-0.15.0.drv-0/source/tests

  0%
100%verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-047_unknown_apply_succeeds.test'
FAIL 047_unknown_apply_succeeds.test (exit status: 1)

FAIL: 052_file_concatenation
============================

  0%
 42%
 85%
 99%
100%
Elapsed time: 0.000s
verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-052_file_concatenation.test'
FAIL 052_file_concatenation.test (exit status: 1)

FAIL: 053_framed_progress
=========================

verify-syscalls: open was never called on 'fwup.img'

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.15.0.drv-0/source/tests/work-053_framed_progress.test'
FAIL 053_framed_progress.test (exit status: 1)

FAIL: 060_framed_streaming
==========================

With the current version, even more tests fail:
fwup 0.18.0: tests/test-suite.log
=======================================
   fwup 0.18.0: tests/test-suite.log
=======================================

# TOTAL: 141
# PASS:  60
# SKIP:  0
# XFAIL: 0
# FAIL:  81
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: 001_simple_fw
===================

|                                    | 0%
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-001_simple_fw.test'
FAIL 001_simple_fw.test (exit status: 1)

FAIL: 002_resource_subdir
=========================

|                                    | 0%
|===========                         | 33% (1.02 / 3.07) KB
|=======================             | 66% (2.05 / 3.07) KB
|=================================== | 99% (3.07 / 3.07) KB
|====================================| 100% (3.07 / 3.07) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-002_resource_subdir.test'
FAIL 002_resource_subdir.test (exit status: 1)

FAIL: 003_write_offset
======================

|                                    | 0%
|===============                     | 43% (65.17 / 150.00) KB
|===============================     | 87% (130.68 / 150.00) KB
|=================================== | 99% (150.00 / 150.00) KB
|====================================| 100% (150.00 / 150.00) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-003_write_offset.test'
FAIL 003_write_offset.test (exit status: 1)

FAIL: 004_env_vars
==================

|                                    | 0%
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-004_env_vars.test'
FAIL 004_env_vars.test (exit status: 1)

FAIL: 005_define
================

|                                    | 0%
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-005_define.test'
FAIL 005_define.test (exit status: 1)

FAIL: 007_mbr
=============

|                                    | 0%
|=================================== | 99% (512.00 / 512.00) bytes
|====================================| 100% (512.00 / 512.00) bytes
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-007_mbr.test'
FAIL 007_mbr.test (exit status: 1)

FAIL: 008_partial_mbr
=====================

|                                    | 0%
|=================================== | 99% (512.00 / 512.00) bytes
|====================================| 100% (512.00 / 512.00) bytes
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-008_partial_mbr.test'
FAIL 008_partial_mbr.test (exit status: 1)

FAIL: 010_fat_mkfs
==================

|                                    | 0%
|==================                  | 50% (0.51 / 1.02) KB
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-010_fat_mkfs.test'
FAIL 010_fat_mkfs.test (exit status: 1)

FAIL: 011_fat_setlabel
======================

|                                    | 0%
|===========                         | 33% (0.51 / 1.54) KB
|=======================             | 66% (1.02 / 1.54) KB
|=================================== | 99% (1.54 / 1.54) KB
|====================================| 100% (1.54 / 1.54) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-011_fat_setlabel.test'
FAIL 011_fat_setlabel.test (exit status: 1)

FAIL: 012_fat_write
===================

|                                    | 0%
|=========                           | 25% (0.51 / 2.05) KB
|==================                  | 50% (1.02 / 2.05) KB
|=================================== | 99% (2.05 / 2.05) KB
|====================================| 100% (2.05 / 2.05) KB
Success!
Elapsed time: 0.002s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-012_fat_write.test'
FAIL 012_fat_write.test (exit status: 1)

FAIL: 013_fat_mv
================

|                                    | 0%
|=======                             | 20% (0.51 / 2.56) KB
|==============                      | 40% (1.02 / 2.56) KB
|============================        | 80% (2.05 / 2.56) KB
|=================================== | 99% (2.56 / 2.56) KB
|====================================| 100% (2.56 / 2.56) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-013_fat_mv.test'
FAIL 013_fat_mv.test (exit status: 1)

FAIL: 014_fat_cp
================

|                                    | 0%
|===                                 | 9% (0.51 / 5.63) KB
|======                              | 18% (1.02 / 5.63) KB
|============                        | 36% (2.05 / 5.63) KB
|================                    | 45% (2.56 / 5.63) KB
|===================                 | 54% (3.07 / 5.63) KB
|======================              | 63% (3.58 / 5.63) KB
|=========================           | 72% (4.10 / 5.63) KB
|=============================       | 81% (4.61 / 5.63) KB
|================================    | 90% (5.12 / 5.63) KB
|=================================== | 99% (5.63 / 5.63) KB
|====================================| 100% (5.63 / 5.63) KB
Success!
Elapsed time: 0.005s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-014_fat_cp.test'
FAIL 014_fat_cp.test (exit status: 1)

FAIL: 017_fat_rm
================

|                                    | 0%
|==                                  | 8% (0.51 / 6.14) KB
|=====                               | 16% (1.02 / 6.14) KB
|===========                         | 33% (2.05 / 6.14) KB
|==============                      | 41% (2.56 / 6.14) KB
|==================                  | 50% (3.07 / 6.14) KB
|====================                | 58% (3.58 / 6.14) KB
|=======================             | 66% (4.10 / 6.14) KB
|===========================         | 75% (4.61 / 6.14) KB
|=============================       | 83% (5.12 / 6.14) KB
|================================    | 91% (5.63 / 6.14) KB
|=================================== | 99% (6.14 / 6.14) KB
|====================================| 100% (6.14 / 6.14) KB
Success!
Elapsed time: 0.002s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-017_fat_rm.test'
FAIL 017_fat_rm.test (exit status: 1)

FAIL: 018_numeric_progress
==========================

-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-018_numeric_progress.test'
FAIL 018_numeric_progress.test (exit status: 1)

FAIL: 019_quiet_progress
========================

-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-019_quiet_progress.test'
FAIL 019_quiet_progress.test (exit status: 1)

FAIL: 022_signed_fw
===================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.18.0.drv-0/source/tests
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-022_signed_fw.test'
FAIL 022_signed_fw.test (exit status: 1)

FAIL: 026_sign_again
====================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.18.0.drv-0/source/tests
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-026_sign_again.test'
FAIL 026_sign_again.test (exit status: 1)

FAIL: 027_fat_timestamp
=======================

|                                    | 0%
|=========                           | 25% (0.51 / 2.05) KB
|==================                  | 50% (1.02 / 2.05) KB
|=================================== | 99% (2.05 / 2.05) KB
|====================================| 100% (2.05 / 2.05) KB
Success!
Elapsed time: 0.002s
-- verify-syscalls report --
open() was never called on '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-027_fat_timestamp.test/fwup.img.1'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-027_fat_timestamp.test'
FAIL 027_fat_timestamp.test (exit status: 1)

FAIL: 028_osip
==============

|                                    | 0%
|=================================== | 99% (512.00 / 512.00) bytes
|====================================| 100% (512.00 / 512.00) bytes
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-028_osip.test'
FAIL 028_osip.test (exit status: 1)

FAIL: 029_5G_offset
===================

Sparse files supported

|                                    | 0%
|===============                     | 43% (65.16 / 150.00) KB
|===============================     | 87% (130.68 / 150.00) KB
|=================================== | 99% (150.00 / 150.00) KB
|====================================| 100% (150.00 / 150.00) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-029_5G_offset.test'
FAIL 029_5G_offset.test (exit status: 1)

FAIL: 030_2T_offset
===================

Sparse files supported

|                                    | 0%
|===============                     | 43% (65.16 / 150.00) KB
|===============================     | 87% (130.68 / 150.00) KB
|=================================== | 99% (150.00 / 150.00) KB
|====================================| 100% (150.00 / 150.00) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-030_2T_offset.test'
FAIL 030_2T_offset.test (exit status: 1)

FAIL: 031_fat_mkfs_5G
=====================

Sparse files supported

|                                    | 0%
|==================                  | 50% (0.51 / 1.02) KB
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.097s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-031_fat_mkfs_5G.test'
FAIL 031_fat_mkfs_5G.test (exit status: 1)

FAIL: 032_fat_2T_offset
=======================

Sparse files supported

|                                    | 0%
|=====                               | 16% (0.51 / 3.07) KB
|===========                         | 33% (1.02 / 3.07) KB
|=======================             | 66% (2.05 / 3.07) KB
|=============================       | 83% (2.56 / 3.07) KB
|=================================== | 99% (3.07 / 3.07) KB
|====================================| 100% (3.07 / 3.07) KB
Success!
Elapsed time: 0.002s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-032_fat_2T_offset.test'
FAIL 032_fat_2T_offset.test (exit status: 1)

FAIL: 035_streaming
===================

|                                    | 0%
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-035_streaming.test'
FAIL 035_streaming.test (exit status: 1)

FAIL: 036_streaming_signed_fw
=============================

Firmware signing keys created and saved to fwup-key.pub and fwup-key.priv

Distribute fwup-key.pub with your system so that firmware updates can be
authenticated. Keep fwup-key.priv in a safe location.
/tmp/nix-build-fwup-0.18.0.drv-0/source/tests
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-036_streaming_signed_fw.test'
FAIL 036_streaming_signed_fw.test (exit status: 1)

FAIL: 038_write_15M
===================

|                                    | 0%
|                                    | 1% (0.20 / 15.00) MB
|                                    | 2% (0.33 / 15.00) MB
|=                                   | 3% (0.46 / 15.00) MB
|=                                   | 4% (0.65 / 15.00) MB
|=                                   | 5% (0.79 / 15.00) MB
|==                                  | 6% (0.92 / 15.00) MB
|==                                  | 7% (1.11 / 15.00) MB
|==                                  | 8% (1.24 / 15.00) MB
|===                                 | 9% (1.38 / 15.00) MB
|===                                 | 10% (1.51 / 15.00) MB
|===                                 | 11% (1.70 / 15.00) MB
|====                                | 12% (1.83 / 15.00) MB
|====                                | 13% (1.97 / 15.00) MB
|=====                               | 14% (2.16 / 15.00) MB
|=====                               | 15% (2.29 / 15.00) MB
|=====                               | 16% (2.42 / 15.00) MB
|======                              | 17% (2.55 / 15.00) MB
|======                              | 18% (2.75 / 15.00) MB
|======                              | 19% (2.88 / 15.00) MB
|=======                             | 20% (3.01 / 15.00) MB
|=======                             | 21% (3.21 / 15.00) MB
|=======                             | 22% (3.34 / 15.00) MB
|========                            | 23% (3.47 / 15.00) MB
|========                            | 24% (3.60 / 15.00) MB
|=========                           | 25% (3.80 / 15.00) MB
|=========                           | 26% (3.93 / 15.00) MB
|=========                           | 27% (4.06 / 15.00) MB
|==========                          | 28% (4.26 / 15.00) MB
|==========                          | 29% (4.39 / 15.00) MB
|==========                          | 30% (4.52 / 15.00) MB
|===========                         | 31% (4.65 / 15.00) MB
|===========                         | 32% (4.85 / 15.00) MB
|===========                         | 33% (4.98 / 15.00) MB
|============                        | 34% (5.11 / 15.00) MB
|============                        | 35% (5.31 / 15.00) MB
|============                        | 36% (5.44 / 15.00) MB
|=============                       | 37% (5.57 / 15.00) MB
|=============                       | 38% (5.77 / 15.00) MB
|==============                      | 39% (5.90 / 15.00) MB
|==============                      | 40% (6.03 / 15.00) MB
|==============                      | 41% (6.16 / 15.00) MB
|===============                     | 42% (6.35 / 15.00) MB
|===============                     | 43% (6.49 / 15.00) MB
|===============                     | 44% (6.62 / 15.00) MB
|================                    | 45% (6.81 / 15.00) MB
|================                    | 46% (6.94 / 15.00) MB
|================                    | 47% (7.08 / 15.00) MB
|=================                   | 48% (7.21 / 15.00) MB
|=================                   | 49% (7.40 / 15.00) MB
|==================                  | 50% (7.53 / 15.00) MB
|==================                  | 51% (7.67 / 15.00) MB
|==================                  | 52% (7.86 / 15.00) MB
|===================                 | 53% (7.99 / 15.00) MB
|===================                 | 54% (8.12 / 15.00) MB
|===================                 | 55% (8.25 / 15.00) MB
|====================                | 56% (8.45 / 15.00) MB
|====================                | 57% (8.58 / 15.00) MB
|====================                | 58% (8.71 / 15.00) MB
|=====================               | 59% (8.91 / 15.00) MB
|=====================               | 60% (9.04 / 15.00) MB
|=====================               | 61% (9.17 / 15.00) MB
|======================              | 62% (9.30 / 15.00) MB
|======================              | 63% (9.50 / 15.00) MB
|=======================             | 64% (9.63 / 15.00) MB
|=======================             | 65% (9.76 / 15.00) MB
|=======================             | 66% (9.96 / 15.00) MB
|========================            | 67% (10.09 / 15.00) MB
|========================            | 68% (10.22 / 15.00) MB
|========================            | 69% (10.35 / 15.00) MB
|=========================           | 70% (10.55 / 15.00) MB
|=========================           | 71% (10.68 / 15.00) MB
|=========================           | 72% (10.81 / 15.00) MB
|==========================          | 73% (11.01 / 15.00) MB
|==========================          | 74% (11.14 / 15.00) MB
|===========================         | 75% (11.27 / 15.00) MB
|===========================         | 76% (11.46 / 15.00) MB
|===========================         | 77% (11.60 / 15.00) MB
|============================        | 78% (11.73 / 15.00) MB
|============================        | 79% (11.86 / 15.00) MB
|============================        | 80% (12.05 / 15.00) MB
|=============================       | 81% (12.19 / 15.00) MB
|=============================       | 82% (12.32 / 15.00) MB
|=============================       | 83% (12.51 / 15.00) MB
|==============================      | 84% (12.64 / 15.00) MB
|==============================      | 85% (12.78 / 15.00) MB
|==============================      | 86% (12.91 / 15.00) MB
|===============================     | 87% (13.10 / 15.00) MB
|===============================     | 88% (13.23 / 15.00) MB
|================================    | 89% (13.36 / 15.00) MB
|================================    | 90% (13.56 / 15.00) MB
|================================    | 91% (13.69 / 15.00) MB
|=================================   | 92% (13.82 / 15.00) MB
|=================================   | 93% (13.95 / 15.00) MB
|=================================   | 94% (14.15 / 15.00) MB
|==================================  | 95% (14.28 / 15.00) MB
|==================================  | 96% (14.41 / 15.00) MB
|==================================  | 97% (14.61 / 15.00) MB
|=================================== | 98% (14.74 / 15.00) MB
|=================================== | 99% (14.87 / 15.00) MB
|====================================| 100% (15.00 / 15.00) MB
Success!
Elapsed time: 0.060s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-038_write_15M.test'
FAIL 038_write_15M.test (exit status: 1)

FAIL: 039_upgrade
=================

|                                    | 0%
|                                    | 1% (1.54 / 152.56) KB
|===============                     | 42% (65.25 / 152.56) KB
|==============================      | 85% (130.77 / 152.56) KB
|=================================== | 99% (152.56 / 152.56) KB
|====================================| 100% (152.56 / 152.56) KB
Success!
Elapsed time: 0.003s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-039_upgrade.test'
FAIL 039_upgrade.test (exit status: 1)

FAIL: 042_fat_am335x
====================

|                                    | 0%
|==================                  | 50% (0.51 / 1.02) KB
|=================================== | 99% (1.02 / 1.02) KB
|====================================| 100% (1.02 / 1.02) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-042_fat_am335x.test'
FAIL 042_fat_am335x.test (exit status: 1)

FAIL: 043_fat_touch
===================

|                                    | 0%
|===========                         | 33% (0.51 / 1.54) KB
|=======================             | 66% (1.02 / 1.54) KB
|=================================== | 99% (1.54 / 1.54) KB
|====================================| 100% (1.54 / 1.54) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-043_fat_touch.test'
FAIL 043_fat_touch.test (exit status: 1)

FAIL: 044_require_file_exist
============================

|                                    | 0%
|=========                           | 25% (0.51 / 2.05) KB
|==================                  | 50% (1.02 / 2.05) KB
|===========================         | 75% (1.54 / 2.05) KB
|=================================== | 99% (2.05 / 2.05) KB
|====================================| 100% (2.05 / 2.05) KB
Success!
Elapsed time: 0.000s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-044_require_file_exist.test'
FAIL 044_require_file_exist.test (exit status: 1)

FAIL: 045_legacy_require_partition1
===================================

|                                    | 0%
|                                    | 1% (1.54 / 152.56) KB
|===============                     | 42% (65.26 / 152.56) KB
|==============================      | 85% (130.78 / 152.56) KB
|=================================== | 99% (152.56 / 152.56) KB
|====================================| 100% (152.56 / 152.56) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-045_legacy_require_partition1.test'
FAIL 045_legacy_require_partition1.test (exit status: 1)

FAIL: 047_unknown_apply_succeeds
================================

/tmp/nix-build-fwup-0.18.0.drv-0/source/tests

|                                    | 0%
|====================================| 100%
Success!
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-047_unknown_apply_succeeds.test'
FAIL 047_unknown_apply_succeeds.test (exit status: 1)

FAIL: 052_file_concatenation
============================

|                                    | 0%
|===============                     | 42% (65.18 / 152.05) KB
|==============================      | 85% (130.70 / 152.05) KB
|=================================== | 99% (152.05 / 152.05) KB
|====================================| 100% (152.05 / 152.05) KB
Success!
Elapsed time: 0.001s
-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-052_file_concatenation.test'
FAIL 052_file_concatenation.test (exit status: 1)

FAIL: 053_framed_progress
=========================

-- verify-syscalls report --
open() was never called on 'fwup.img'!
----------------------------

Test failed!

Leaving test work files in '/tmp/nix-build-fwup-0.18.0.drv-0/source/tests/work-053_framed_progress.test'
FAIL 053_framed_progress.test (exit status: 1)

FAIL: 060_framed_streaming
==========================

Thanks for letting me know about this. That really looks like an issue with the test suite rather than fwup itself. Between the versions that you referenced, I added code to validate syscalls since there are non-obvious constraints with buffer alignment, sizes and offsets on some platforms. That code is failing, but it's failing since the syscalls aren't being captured. I doubt that anything here is a problem for NixOS, but something could be hiding.
I'm not a NixOS user so I tried pulling down the NixOS appliance and installing everything needed to build fwup (like gcc, autoconf, automake, libconfuse, libarchive, etc.). I'm stuck at what looks like a noob issue, but my searches are failing me. gcc fails to build anything with error trying to exec 'as': execp: No such file or directory. I didn't see a build-essential package for NixOS. Any ideas how I may reproduce and debug?

@fhunleth Thank you for your effort! You can run nix-shell '<nixpkgs>' -A fwup to enter the build environment with all the dependencies for fwup.

I just ran the following in a fwup source directory:
nix-shell '<nixpkgs>' -A fwup
./autogen.sh
./configure
make
make check

All tests passed for me.
I'm running NixOS 17.09.2249.6b8833df272 (x86_64-linux) in VirtualBox. Are you running something different?

Sorry about that, NixOS 17.09 contains the old version of fwup. Could you run nix-channel --add https://nixos.org/channels/nixpkgs-unstable and nix-channel --update before entering the shell.

I checked out fwup v0.18.0 from Github to ~/fwup and built it there. I ran the commands that you wrote and re-entered the shell. Should I be compiling from a different directory?

My bad, that should be fine. Then it looks like a problem with environment. Could you try using nix-shell '<nixpkgs>' -A fwup --pure to sandbox the shell?

Ok, --pure is really cool.
I ran make distclean first to start a fresh build and then repeated what I did above. I have the same result. I.e. everything works.

Sorry, we have not checked if the tests of the newer fwup fail in NixOS 17.09, only in the NixOS master (aka unstable). One of the differences is the upgrade to Glibc 2.26.

Could you unpack https://github.com/NixOS/nixpkgs/archive/master.tar.gz somewhere and run nix-shell path/to/master -A fwup --pure? This should reproduce test failure.

Downloaded and unpacked and I'm finally getting the failures! Investigating...

Fixed! The difference was indeed related to glibc 2.26. The implementation of open() was changed to call the openat syscall. I didn't handle the openat syscall in the syscall validator, so it was throwing an error. It's handled now. Thanks for reporting this. I'll make a patch release shortly.

Thank you for the fix (and for introducing me to the open_by_handle_at syscall)!

Thanks @jtojnar and @orivej again for reporting the issue and helping me reproduce it. The 0.18.1 release is now available with the fix.


Internal error occurred when deploying a model to a Power BI Premium Enabled Workspace with -R -M flags (deploy roles and role members)

Describe the bug
I am deploying a tabular model to a Power BI Workspace, the tabular model contains roles and the roles contain role members.
I deploy the model directly from Tabular Editor using the 'Deploy' option in the menu, Model -> Deploy (F6).
When I deploy the model for the first time and check deploy: 'Roles' and 'Role Members' I get a popup with the error:
Deployment failed! An internal error occurred.
When I uncheck deploy 'Role Members' I am able to deploy the model, when I deploy the model once more and check: deploy 'Role members' the deployment succeeds.
To Reproduce
Steps to reproduce the behavior:

Start tabular editor and develop a simple model
Create a role and assign a role member from the Azure AD
Deploy the tabular model to a Power BI XMLA Endpoint (Power BI Premium Workspace)
Check deploy roles and role members when deploying

Expected behavior
The deployment should succeed in one go when deploy roles and role members are checked
Observed behavior
A popup window appears with the error: An internal error occurred.
Application specifics

Tabular Editor 2.20.0
Semantic Engine used: Power BI Premium
Model Compatibility Level: 1601

Could you try to generate a TMSL script (last page of the Deployment Wizard), and then run the script through SSMS? That should give you some more information about the error, which may be useful.

Thanks for the reply, when I first tried to connect to the XMLA endpoint via SSMS to run the TSML script I received an error. To solve that I installed SSMS 19.2 and then I ran the TSML script and it completed successfully. Then I thought, maybe Tabular Editor uses some shared components which are shipped by SSMS as well which could causing this issue. So I started a fresh deployment from the Tabular Editor UI and now the error doesn't occur anymore. Could this be the clarification?


feat: update the spaces in the form editor

@solittlework  can you update the css margin to use var(--goa-space-m) for the 1rem before you merge

@solittlework can you update the css margin to use var(--goa-space-m) design tokens for the 1rem before you merge

Hi @thdlam  thank you for your review. I updated the code based on your suggestion.


Overview UI components

Description
Created NavBar and ActionButton overview components to be extended as needed later. See commit for more info.
Type of change

[x] New feature (non-breaking change which adds functionality)

Change Status

[x] Complete, tested, ready to review and merge

How Has This Been Tested?

[x] Local Dev Server

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] There are no merge conflicts

Regarding the organisms:
I figured rather than have all of our components cluttering up one folder we could use the atomic design breakdown to classify our components.
Atoms - custom built components that handle a specific bit of data. For the most part this is taken care of by semantic but we may need to build some ourselves.
Molecules - groups or atoms built together to serve a single purpose (e.g. a search bar comprised of a search field and a search button.)
Organisms - groups of molecules grouped to serve a set of featured (e.g. the aforementioned searchbar grouped with an autocompletion dropdown that queries for potential answers as you type)
Then there's templates and pages. Right now the views is our pages but if we decide to do any templating we can always change it.
Does that make sense? Its up for grabs, I was just trying to follow some kind of organizational format.

And yes to the protected routes

Also feel free to hit me up on slack with any and all questions regarding semantic. Glad to help best i can.


Allow dall-e-3 model for image generation

Open AI have just updated their API and now allows dall-e-3 image generation. https://platform.openai.com/docs/guides/images?context=node
On this change, the request has been updated to also pass model.
Usage:
chatgpt -m dall-e-3 --size 1024x1024 "image: <image description>"

While this is not implemented here, you may wnat to try my chatgpt.sh shell script which supports dall-e-3 model for image generations by defaults.


Improve jaeger ui path replacement to make itore robust

Altough this solutionn  still feels hacky
Usign a regexp instead of a simple string replacement make the solution a little bit more robust. This make it works even if spaces are injected on the middle of the tags
Eg.
<base href="%s/" data-inject-target="BASE_URL"/>
<base href="%s/" data-inject-target="BASE_URL" />
<   base href="%s/"           data-inject-target="BASE_URL"/>

I had to recreate the PR, not sure why was not updated with my latest changes.

https://github.com/observatorium/api/pull/549


Tibia 11 Health List Display Issue

Anyone else having a problem with the Health list not showing?

yes same problem here used to work but now it just wont

Same :(

Any solution for this?

@Mytherin

still not working

And it probably won't be fixed, as far as we know tibialyzer will stop working after battleye


Add extracting(Function extractor) to Object assertions

Summary
When using Object assertion extracting(Function... extractors) with one extractor, we get a List of one element corresponding to the extracted value when users expect the extracted value directly.
https://stackoverflow.com/questions/50461109/assertj-retrieving-first-items-from-extracting-list-returns-list-instead

Fixed in de6e751563640c7d157018cf6c4c79573cb7b830


feat(BottomSheet): add default collapsed sheet height for android

Related to https://github.com/nativescript-community/ui-material-components/issues/306

@vallemar so the iOS counterpart is not working? Event with the setPee... method? Could you stil add the code to that PR so that i can look at it ?

@farfromrefug I have added the code for ios, but it does nothing :(

@vallemar i released it for iOS/Android ! thanks for your PR


How to programatically generate Markdown

I have a method that generates a markdown table. I tried:
import io.github.spencerpark.ijava.runtime.Display;

Display.display(cosineSimilarities, "text/markdown");

but that results in:
| King | Queen | Man | Woman | King - Man + Woman | |---|---|---|---|---|---| | King | 0.99999994 | 0.48587015 | 0.59400713 | 0.36629754 | 0.6379426 | | Queen | 0.48587015 | 1.0000001 | 0.3360686 | 0.28942698 | 0.36757925 | | Man | 0.59400713 | 0.3360686 | 1.0000001 | 0.6100262 | 0.14799908 | | Woman | 0.36629754 | 0.28942698 | 0.6100262 | 0.9999997 | 0.6598337 | | King - Man + Woman | 0.6379426 | 0.36757925 | 0.14799908 | 0.6598337 | 1.0000002 |

Thanks

Nevermind, my markdown generating library was spewing garbage! It works just fine.


Client Resource Access Action Does not throw an error when Two arguments are given Instead of one

Description:
Client Resource Access Action Does not throw an error when Two arguments are given Instead of one
Steps to reproduce:
public function main() {
    var successClient = client object {
        resource function get path/[int a]/foo(string name) returns int {
            return 1;
        }
    };
    result = successClient->/path/[1]/foo("x", "y");
}

Suggested Labels (optional):
Bug

Fixed with  #36959


#23 - phrase_suggest candidate generator types

Can you please test the refactor-suggesters branch. It comes with candidate generators. Furthermore, it brings all suggesters to ES 1.4 level.

aha! didn't see.
what the status of the refactor-suggesters branch? need some help?

No. The refactor-suggesters branch is just so big that I need someone to test it with real code. And you asked for it, so... ;-)
Notice that the branch breaks the API (e.g. property Smoothing of type interface{} has changed to SmoothingModel with SmoothingModel (an interface). I'm pretty confident that nobody is using that yet, but you never know.
However, breaking the API is really necessary if you want to keep up with Elasticsearch on the server-side. There's probably nothing I can do besides trying to keep things simple and obvious for the users of Elastic.
So. Can you test that branch with your code and see if it works okay? Then I'll probably merge with master.

I checked Phrase and Terms suggestors, our code base working well.
Completition suggestor - checking other guy - in progress.
Context suggestor - we don't use it...

Closed by this merge.


Bump Kubernetes dependencies to v0.17.0

What this PR does / why we need it:
Bumps our k8s.io/* dependencies to v1.17, and uses the new v0.17.0 semver tags to do so! :tada:
This is now possible as https://github.com/kubernetes/publishing-bot/pull/210 has merged. A big thanks to @nikhita for putting that patch together, and to all others involved for reporting issues, reviewing code and generally providing ideas on how to better handle this! 🙌
Release note:
Bump `k8s.io/*` dependencies to Kubernetes 1.17.0

/assign @JoshVanL

/retest

/retest

/retest


Update README.md

I added hl=en so that the example works in web browsers with other languages

@gaugebot recheck the pull request.

Thanks for the PR !


fixFix substr utf8 error when pos is larger than str size

Proposed changes
Issue Number: close #xxx

https://github.com/apache/doris/pull/29799#issuecomment-2247334457
When the str parameter of substr is a utf8 character, the correct result should return empty when pos > size of str, but this case is not handled.

run buildall

run buildall


Android - Composer - Area below composer flickers when collapsing composer that has long paragraph

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/31298
Action Performed:

Launch New Expensify app
Go to any chat
Paste the following paragraph into the composer:
Ever since Google took away free unlimited storage on Google Photos, I knew I’d have to figure out a way to keep my ever-growing photo library slim and lean. Google’s existing tools are a passable point to get started, but they lack important context. That’s why I’m very excited to get my hands on Google Photos’ new photo stacks, which are supposed to group similar photos taken at roughly the same time in a stack much like Top Shot does. While this is primarily intended to make it easier to scroll through your library, it will also make it much easier to pick a single great shot and discard the rest.Ever since Google took away free unlimited storage on Google Photos, I knew I’d have to figure out a way to keep my ever-growing photo library slim and lean. Google’s existing tools are a passable point to get started, but they lack important context. That’s why I’m very excited to get my hands on Google Photos’ new photo stacks, which are supposed to group similar photos taken at roughly the same time in a stack much like Top Shot does. While this is primarily intended to make it easier to scroll through your library, it will also make it much easier to pick a single great shot and discard the rest
Expand the composer
Collapse the composer

Expected Result:
There will be no flickering issue when collapsing the composer
Actual Result:
The area below the composer flickers when it is collapsing
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/006a1387-feb6-4261-bef4-1a0624b35a8e
View all open jobs on GitHub

No one assigned here?
🎀 👀 🎀 to get engineer to handle this

Happy to take this as C+

Okay sure, assigning @situchan

@greg-schroeder are you able to see if you can reproduce and if so get this out as Help Wanted? Let me know if you need anything from me.

Actually I don't think this necessarily fits into any of our current waves, so I'm going to close this.


Update cats-effect, cats-effect-testkit to 3.4.7

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-testkit

from 3.4.1 to 3.4.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #38.


Ionic and Electron

Hello World
So guys long story short : I have 0% Knowledge about building "PWA" Using Electron.
Any one of you fellow can help your friend out?

I can only recommend the Slack channels for these topics. The issues here are for posting issues ;-)


Refactor var description

This is my second refactoring pull request. First was #1302
My aim is to replace dictionaries with classes for easier feature developing.

new dataclasses for series description and series description hashable
add property for common propertyes from dict
support old dict like syntax in those classes
remove describe_counts and describe_generic (logic moved to classes VarDescription)

missing spark refactoring (tbd)

Hi @vorel99 ,
we don't use the refactor. Please ensure that you use "feat" instead.
In what concerns the proposed changes we will be analyzing and validating wether they fit the roadmap for the package.


Fix obstacle avoidance bug

There is a bug with obstacle avoidance, sometimes when you meet an obstacle you can't move at all when it should allow the user to be able to move to avoid the obstacle.  The car might stop even when obstacles are far away from it and wont turn towards any direction with the only solution to the problem being to reset the position of the car and start again.

[x] The car no longer stopes moving away from an obstacle when the sensors detect one.
[x] The bug fix does not make the cars obstacle avoidance less trustable.
[x] The solution has been tested on both the app and SMCE alone to make sure that no problems may occur from the apps perspective.

The bug has now been fixed thanks to the latest changes to the Arduino sketch. The issue can now be closed.


Queue API

I added the Queue API to this.

gofmt plz

.gitignore added in this PR is not mine. Remove it please.

HI Yosida, I have removed it from the pull-request-branch. If I understand this system correctly that should have removed it from the pull request. Sorry about that. Please verify.

I confirmed that .gitignore is removed.  Thanks.
I'll merge this Pull Request when below conditions described in my
before comments are met:

format source code using gofmt
remove api/json suffix from URL in (*Jenkins).GetQueue()
do git rebase to meld your changes in one commit

I'm sorry about my many demands to you.
--
Name: Kohei Yoshida
Mail<EMAIL_ADDRESS>Site:   http://yosida95.com/

I believe the URL suffix is required. Please see new pull request.


gazctl apply: interpret revision -1 as "don't care"

As an operator, I want manage my JournalSpecs / ShardSpecs in version control as the source of truth. I should have a means to tell gazctl apply it should apply my specs regardless of the current state of specifications in Etcd.
However this should be explicit. We'll use a YAML revision: -1 to convey that I know there may be non-zero revisions of these specs, and I don't care. revision: -1 may be specified either at a directory or journal literal in JournalSpec YAML, and the common map or a shard literal in ShardSpec YAML.
Update documentation examples to discuss this usage.
Bonus: Also discuss how to use the delete: true field in YAMLs to effect deletion, which is not covered by docs today.

Implemented by @adayNU


chore(main): release 0.6.2

:robot: I have created a release beep boop
0.6.2 (2024-07-10)
Bug Fixes

deps: update rust crate clap to v4.5.8 (cb8c6bc)
deps: update rust crate clap to v4.5.9 (d653d15)
deps: update rust crate rust-embed to v8.5.0 (586410e)
deps: update rust crate serde to v1.0.204 (188085d)
deps: update rust crate serde_json to v1.0.119 (3c0bc55)
deps: update rust crate serde_json to v1.0.120 (ce029a9)
deps: update rust crate service_conventions to 0.0.17 (4a1e476)
deps: update rust crate tonic to 0.12.0 (1534886)
deps: update rust crate uuid to v1.10.0 (d98714f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philipcristiano/w2z/releases/tag/v0.6.2 :sunflower:


+[1-8] should select tabs [1-8]

Hotkeys for selecting the first 8 tabs. Should not be considered without tests.

Fixed in f839ecb225b5b4bd5d37f35d8a1c9fc39437f74f and 7d6517e2863018f26a526c46c9122b7a9282c5d4


Added Product Type for WatchKit2AppContainer (i.e Independent Watch Apps)

Resolves https://github.com/tuist/xcodeproj/issues/438
Short description 📝

The resolves the missing product type for the new Independent Watch App containers.

Solution 📦

I added the PBXProductType enum case of com.apple.product-type.application.watchapp2-container. These act similar to how the iOS app acts except without being an iOS app.

Implementation 👩💻👨💻

[ ] Added the Enum Case under PBXProductType
[ ] Added the file extension for the Product Type

@leogdion would you mind updating the CHANGELOG?

@pepibumur Done


Twilio Error - 12100

Describe the bug
I've received several twilio errors since updating to 2.2.0. one 8 days ago, 2 19 hours ago.
they all say the same thing...
12100 - Document parse failure
What version are you running
yap 2.2.0
To Reproduce
I'm not the one making the error. I think it's when someone calls in.
Expected behavior
I expect it to do what it's supposed to do.  reply with meetings, or call a helpline or read the jft (when calling)
Error - 12100.docx
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I think I will remove 2.2.0 and go back to the previous version and see if that stops the twilio errors. i'm afraid some folks are using yap and not getting any results.  and i don't want that to happen since we just got approval the first of august to switch to yap for our helpline.

I will do that this weekend. I thought the errors were gone after going back to the previous version but just got another error email.
I’ll let you know how it goes.
Lucy
Lucy Owens
Communication Administrator
Grace-St. Luke's Episcopal Church
1720 Peabody Avenue
Memphis, Tennessee 38104
Direct<PHONE_NUMBER>
www.gracestlukes.org
facebook.com/gracestlukes
twitter.com/gracestlukes
instagram.com/gracestlukes
On Sep 13, 2018, at 9:23 PM, Danny Gershman<EMAIL_ADDRESS>wrote:
install yap 2.2.1 to receive this fix.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


'https://localhost:3000/microsoft') from origin 'https://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Access to XMLHttpRequest at 'https://login.microsoftonline.com/common/oauth2/authorize?redirect_uri=https%3A%2F%2Flocalhost%3A3000%2Fauth%2Fopenid%2Freturn&response_type=code id_token&response_mode=form_post&client_id=qweqweqwe-qwe-qweoqw0e1-a2bb1e8d786b&state=dasdasd762375434nadm-ZtdoQJTQ1K_PiPSmy_state&nonce=adad27389213123123213&resource=https%3A%2F%2Fgraph.windows.net&scope=openid&x-client-SKU=passport-azure-ad&x-client-Ver=4.0.0' (redirected from 'https://localhost:3000/microsoft') from origin 'https://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I'm using frontend(angularjs) for calling this API https://localhost:3000/microsoft, in the backend im redirecting (/login), etc  after some times I'm getting above error please help me on this

Closing this as we are archiving this repo. Please refer to https://github.com/Azure-Samples/ms-identity-node instead


2.2: FriendlyParamsTranslator Fix

Fixed can't use -z with test name starting with 'exclude' problem as reported here: https://github.com/scalatest/scalatest/issues/547

No applicable anymore, there's another PR to remove FriendlyParamsTranslator from 3.0.x instead:
https://github.com/scalatest/scalatest/pull/693


KML: make sure that portal items of type KML and item type "file" can be extracted and published

In order for this to work, I had to modify the URL_BASED_ITEM_TYPES and FILE_BASED_ITEM_TYPES lists in the portalpy__init__py file. I removed KML from the URL list, and added it to the FILE list.

The slight problem with that solution is that you can add KML urls to the Portal.

@conklinbd Correct. The functions to publishing items will need to be modified to add additional logic for this unique case where the item type is a member of two different categories (URL and FILE). Searching our production portal for type:KML I only find items of in the category FILE. So for now I was going to commit this change for UC until I have more time to look into the logic to handle both cases.

@conklinbd If your okay with my change I will make a pull request to get the change into master.

@elinz that seems fine.

There is an item type called 'KML Collection' that was not documented in the portal sharing api. I added this type to the FILE_BASED_ITEM_TYPES list.


spark33: Add version 3.3.4

This PR adds the Spark 3.3.x series which is the most recent version available in Cloudera.
If this is desired, it would be easy to add other Spark versions as well.

[X] I have read the Contributing Guide.

/verify

/verify

@niheaven good catch, that makes the version determination easier 😃


[EAGLE-868] Refactor metric chart render process to improve user experience

show "data loading icon" for each chart one by one
load metric data query for each chart
reader metric data into metric chart when response returned and remove "data loading icon" one by one

https://issues.apache.org/jira/browse/EAGLE-868

I will modify some typo in commit message,so I close the pr.


we need README.md & CONTRIBUTING.md

we need README.md
reference:https://github.com/brittanyrw/emojiscreen/blob/master/README.md
and for CONTRIBUTING.md
reference : https://github.com/alfg/opendrinks/blob/master/CONTRIBUTING.md
comment to this issue if you want take this PR

Can I take README.md?

Can I take README.md?

sure go ahead

I take CONTRIBUTING.md

I take CONTRIBUTING.md

sure

don't forget to mention this badge @pr0ph0z

noted

thanks @pr0ph0z @YogaSakti


docs: fix typos

Checklist

[x] commit message follows commit guidelines

Description of change
Fixed some typos in the documentation.

Thanks！


Rebase with upstream: go modules updates

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Release note:
none

/cc @Karthik-K-N

/retest


Added more url types

Added code for much more flexibility with the tests as discussed in https://github.com/muhajirframe/is-internal-link/issues/3

Perfect

Great. Please lease let me know when you publish the new version in npm and I'll install it :)


⚠ Bofrost.es has degraded performance

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

HTTP code: 200
Response time: 1422 ms

Resolved: Bofrost.es performance has improved in 99c06af after 13 minutes.


Support for private endpoints on subnets with service endpoints enabled

This documents has note "Private endpoint(s) are not permitted in conjunction with service endpoints in the same subnet!"
Whereas as per https://azure.microsoft.com/en-us/updates/azure-private-link-is-now-available-in-all-regions/
Support for private endpoints on subnets with service endpoints has been enabled. Please update this page with latest information.

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

ID: d16533ae-5e19-5769-4c29-581152f8c30c
Version Independent ID: 3f1b2b47-0bfe-b65c-ad0a-cca3586f7ba7
Content: Quickstart - Manage Private Endpoints in Azure
Content Source: articles/private-link/create-private-endpoint-portal.md
Service: private-link
GitHub Login: @malopMSFT
Microsoft Alias: allensu

@sumitjoshi , Thanks for raising the issue. We will investigate and update you.

@sumitjoshi , Appreciate your patience. We have edited the document accordingly. It will take sometime for the changes to get reflected over the document.


Perf stats - precompiled rules

Read this in the docs "because for YARA it is faster to load compiled rules than compiling the same rules over and over again" Wondering if you have any pointer/stats to compare scanning using with our without compiled rules ? Thank in advance!

I don't stats. However, the difference in performance won't be noticeable if you are compiling only a few rules. In that case compiling the rules from the ground-up will be very fast. But when you have tens of thousands of rules the compilation phase starts taking a few seconds, while loading compiled rules from a file is a lot faster.