Transitive public dependency of private gem not resolved

Package ecosystem

Bundler
Package manager version

2.2.9
Language version

Ruby 2.7.2
Manifest location and content prior to update

/project-name/Gemfile
dependabot.yml content

version: 2
registries:
  rubygems-server-our-private-server:
    type: rubygems-server
    url: https://our-private-server.example.com
    username: "${{secrets.RUBYGEMS_SERVER_USERNAME}}"
    password: "${{secrets.RUBYGEMS_SERVER_PASSWORD}}"
updates:
- package-ecosystem: bundler
  directory: "/project-name"
  schedule:
    interval: daily
  open-pull-requests-limit: 2
  registries:
  - rubygems-server-our-private-server

We are using GitHub-native Dependabot now, but our project is private so I can't link you to the actual dependabot.yml.
Updated dependency

We have a private gem hosted in the repository rubygems-server-our-private-server; let's call it private-gem.
private-gem has a dependency on locale ~> 2.1, which is publicly hosted on https://rubygems.org.
Our application's Gemfile has (relevant items only):
source 'https://our-private-server.example.com' do
  gem 'private-gem', '~> 0.1'
end

Our application's Gemfile.lock has (relevant items only):
GEM
  remote: https://rubygems.org/
  remote: https://our-private-server.example.com/
  specs:
    locale (2.1.3)
    private-gem (0.1.0)
      locale (~> 2.1)

DEPENDENCIES
  private-gem (~> 0.1)!

Neither of these gems have been updated, but they appear to be the trigger of the error described below.
Images of the diff or a link to the PR, issue or logs

The Insights > Dependency graph > Dependabot page is showing the following error:
Bundler::GemNotFound with message: Your bundle is locked to locale (2.1.3), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of locale (2.1.3) has removed it. You'll need to update your bundle to a version other than locale (2.1.3) that hasn't been removed in order to install.

Further, the Dependabot log shows:
  proxy | 2021/04/08 02:31:51 [066] GET https://our-private-server.example.com:443/quick/Marshal.4.8/private-gem-0.1.0.gemspec.rz
  proxy | 2021/04/08 02:31:51 [066] * authenticating rubygems server request (host: our-private-server.example.com)
⋮
  proxy | 2021/04/08 02:33:33 [180] GET https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.0.gemspec.rz
  proxy | 2021/04/08 02:33:33 [180] 200 https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.0.gemspec.rz
  proxy | 2021/04/08 02:33:33 [182] GET https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.1.gemspec.rz
  proxy | 2021/04/08 02:33:33 [182] 200 https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.1.gemspec.rz
  proxy | 2021/04/08 02:33:33 [184] GET https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.2.gemspec.rz
  proxy | 2021/04/08 02:33:33 [184] 200 https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.2.gemspec.rz
  proxy | 2021/04/08 02:33:33 [186] GET https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.3.gemspec.rz
  proxy | 2021/04/08 02:33:33 [186] 200 https://rubygems.org:443/quick/Marshal.4.8/locale-2.1.3.gemspec.rz
updater | INFO <job_108675550> Handled error whilst updating bundler: dependency_file_not_resolvable {:message=>"Bundler::GemNotFound with message: Your bundle is locked to locale (2.1.3), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of locale (2.1.3) has removed it. You'll need to update your bundle to a version other than locale (2.1.3) that hasn't been removed in order to install."}

Observations:

Dependabot is correctly resolving private-gem on our-private-server.example.com.
Dependabot is finding locale on rubygems.org (the GETs legitimately return 200 OK)
Despite this, it seems as though Dependabot is expecting to find locale on our-private-server.example.com? We definitely do not re-host public dependencies there.

Other thoughts

I don't understand the current support level for Bundler v2 in Dependabot given #1699. We have been using Dependabot Preview for many months with Bundler v2 without issue, but apparently it wasn't supported? Now we have moved to GitHub-native Dependabot and I think it worked for a bit but then started failing soon after.
In Bunder 2.2.10+ they have split the GEM sections by remote for security reasons; we have not yet updated to that format. How will that affect things? Is this issue happening because we haven't updated yet?

What you expected to see, versus what you actually saw

Before we moved to GitHub-native Dependabot, we had been running in this configuration for months with no issues.
I expect that Dependabot would be able to check our dependencies as we are hosting them without error.
Native package manager behavior

Running bundle locally succeeds as expected.
🕹 Bonus points: Smallest manifest that reproduces the issue

Unfortunately I can't easily provide a minimal repro because this involves private registries.

Thanks for reporting this @amake, that definitely seems weird

I don't understand the current support level for Bundler v2 in Dependabot given #1699. We have been using Dependabot Preview for many months with Bundler v2 without issue, but apparently it wasn't supported? Now we have moved to GitHub-native Dependabot and I think it worked for a bit but then started failing soon after.

Yeah good question, what we do for bundler is basically strip out the BUNDLED WITH line from the lockfile, run the update with the latest bundler version we have installed (now 2.1.15, but used to be 1.7.3 before v2 support), and put back the BUNDLED WITH line. That actually mostly worked fine, but it broke down if you depended on bundler in the Gemfile, and we were missing some fixes that bundler had introduced.

In Bunder 2.2.10+ they have split the GEM sections by remote for security reasons; we have not yet updated to that format. How will that affect things? Is this issue happening because we haven't updated yet?

Tbh I'm not entirely sure, we've not seen this before, but it does sound like it might! Are you able to give this a go? I believe bundle update --bundler will update the format.
If that doesn't work or isn't feasible I'll need to set up a repro, lmk. 🤞

We updated to Bundler 2.2.15 with the new Gemfile.lock format and now Dependabot is working again!

what we do for bundler is basically strip out the BUNDLED WITH line from the lockfile, run the update with the latest bundler version we have installed (now 2.1.15, but used to be 1.7.3 before v2 support), and put back the BUNDLED WITH line

:scream:

That is really really scary. 😱

What do you find scary about it?

It opens the possibility for all sorts of unpredictable problems, like this one for instance.

It opens the possibility for all sorts of unpredictable problems, like this one for instance.

It has its tradeoffs for sure, but it saves a bunch of complexity as well. This scenario would have happened either way I think.

@jurre I have very same issue here. I have a private gem which depends on some other "public" gems and Dependabot Native seems to find it on GitHub Packages rather than Rubygems.org... Therefore, I do not get any PRs from Dependabot native.
PLATFORMS
  ruby

RUBY VERSION
   ruby 3.0.1p64

BUNDLED WITH
   2.2.17

However, I am able to install all gems locally (bundle install) and in CI/CD side.
Dependabot shows this error for every gem it checks:
updater | INFO <job_135224420> Handled error whilst updating puma: dependency_file_not_resolvable {:message=>"Bundler::GemNotFound with message: Your bundle is locked to dkim (1.0.1), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of dkim (1.0.1) has removed it. You'll need to update your bundle to a version other than dkim (1.0.1) that hasn't been removed in order to install."}

Yes, dkim is a public gem and my private gem depends on it. And, These are the logs where dependabot checks dkim:
proxy | 2021/05/18 18:39:21 [206] 200 https://rubygems.pkg.github.com:443/my-org/api/v1/dependencies?gems=celluloid-gems%2Cchilkat%2Cfugit%2Crack%2Crest-client%2Csequel-bulk-audit%2Csequel-redis-cache
  proxy | 2021/05/18 18:39:21 [208] GET https://rubygems.pkg.github.com:443/my-org/api/v1/dependencies?gems=dkim%2Cmail%2Cpg%2Csequel
  proxy | 2021/05/18 18:39:21 [208] * authenticating rubygems server request (host: rubygems.pkg.github.com)
  proxy | 2021/05/18 18:39:21 [208] 200 https://rubygems.pkg.github.com:443/my-org/api/v1/dependencies?gems=dkim%2Cmail%2Cpg%2Csequel%2Cwork_queue
  proxy | 2021/05/18 18:39:21 [210] GET https://index.rubygems.org:443/versions
  proxy | 2021/05/18 18:39:21 [210] 304 https://index.rubygems.org:443/versions
  proxy | 2021/05/18 18:39:22 [214] GET https://index.rubygems.org:443/info/work_queue
  proxy | 2021/05/18 18:39:22 [214] 200 https://index.rubygems.org:443/info/work_queue
  proxy | 2021/05/18 18:39:22 [216] GET https://index.rubygems.org:443/info/dkim
  proxy | 2021/05/18 18:39:22 [216] 200 https://index.rubygems.org:443/info/dkim
  proxy | 2021/05/18 18:39:23 [218] GET


[libSyntax] Add support for parsing #sourceLocation directives

Add support for parsing #sourceLocation directives in libSyntax.

@swift-ci Please smoke test


IGNITE-18016: Get rid of schema mention in javadoc in IgniteTables.

looks like it was made by mistake


Updated projects

Added a few of the latest curated and playgrounds.

Added Wrapture with a maximum set at 50. If it opens to 666 (there can't be anything inbetween), we can update the max project size. Until we get the change allowing for random selection of partially minted projects, this is probably the most straight forward way to allow for random calls.


Memory cannot be recycled correctly when object is referenced circularly

my test code:
`class A:
def init(self,name,ref):
self.name = name
self.ref = ref
self.data = [0]*1000000
class B:
def set_ref(self,ref):
self.ref = ref
def test():
while True:
b = B()
a = A("name",b)
b.set_ref(a)
print("Hello, RustPython!")
test()`
the error message:
memory allocation of 16000000 bytes failed
error: process didn't exit successfully: target\release\rustpython.exe demo.py (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)
I want to know how we design the object model, because I found that it can clear some memory when I test. I'm also trying to write the JVM with rust, but I can't solve the problem of circular reference. I hope I can get inspiration from you

In python, gc resolve circular reference but we don't have one yet.

In CPython, gc resolve circular reference but we don't have one yet.

ok, but we need one, isn't it


Replace flatbuffers with json serialization library

https://github.com/nlohmann/json
Why?

Has easier serialization APIs for C++ STL storage
Can add custom types (C++ structs -> json)
Can output in human readable (json) and binary format (ubjson, cbor, messagepack etc)

Problems with Flatbuffers

Harder to create a C++ to FBS interface
For JSON like output need to use flexbuffers instead of flatbuffers (no array like root_type allowed)
Schema -> C++ conversion is harder, since there is no explicit support for hashmaps/hashtables/maps/tables.

#223 Initial JSON Serialization library + CustomGenerator addition

#225 JSON Serialization for Target

#226 Remove flatbuffer/flexbuffer usage and library from BuildCC


Use LocalPreferences.toml to use system level libEGL by default for linux systems

@VarLad came up with this option. Now we have to figure out how to ship this solution that works on all Linux-systems.

Preferences.jl looks interesting.

slack discussion is going on this approach.

WGPUCanvas.jl is registered with this fix https://github.com/JuliaRegistries/General/pull/95352

We can close this once anyone confirms that this is indeed fixed.

@arhik Apologies, I'm running into the same issue again (it crashes with GLFW loaded)
I believe that the examples need to be updated to use WGPUCanvas.jl instead of directly GLFW.jl?

I was able to get the cube example running (using the hack I wrote).
I'm guessing that the examples have to be updated to use WGPUCanvas.jl instead of GLFW.jl?
@arhik Correct me if I'm wrong of this

May be you are not placing LocalPreferences.toml file in global folder. I am placing it in the julia dev folder (like ~/.julia/dev). Yes. On linux I had to manually create LocalPreferences.toml file like you suggested and it works but I wish it can automated. I will have to dig into it. Anyways check know your configuration and let me know.

By the way all examples in the GUI must be flipped vertically if you are using the master branch; I made few changes while working on gaussian splatting code.

@arhik The LocalPreferences.jl file worked but I'm asking if instead of directly using GLFW.jl, does it make more sense to use WGPUCanvas instead?
Seems like its function is to reduce boilerplate of working with WGPU + GLFW :P

Yes totally. A little more abstraction with WGPUCanvas will help. If we don't have to use these in examples like these

using GLFW
using GLFW: WindowShouldClose, PollEvents, DestroyWindow

with abstracted functions defined in WGPUCanvas would be great.

I am not happy with too much clutter of duplicate includes too. I see your point.

@arhik Is there any examples of WGPUCanvas.jl in action?

All examples use WGPUCanvas.  WGPUgfx loads WGPUCanvas. And its WGPUCanvas's job to load appropriate surface based on platform.

If I misunderstood your question correct me please.

It doesn't look like it but in WGPUCanvas we provide getCanvas through WGPUCore definitions.
https://github.com/JuliaWGPU/WGPUgfx.jl/blob/f95dfd5114765abd251e2c452fbc49dffbf0c474/src/scene.jl#L22

Platform dependent canvas will be loaded here.
https://github.com/JuliaWGPU/WGPUCanvas.jl/blob/02d0b98a0cef3cefd755d9fa4a30bb3e258ee06b/src/WGPUCanvas.jl#L35

@arhik Ah, sorry, I thought WGPUCanvas acted as a replacement for directly using GLFW :sweat_smile:
Didn't see that it was imported and used by WGPUgfx
By the way, were you able to figure out why the libglvnd provided by BinaryBuilder gives issues here?

No. But its a prevalent Symbol collision issue.

@arhik I'm interested in helping to get the circle example working.
I guess I need to work on the circle primitive first. I believe that would be a good starting point for contribution as well.
Can you give me some directions towards this?

UI circle example should help. Divide circle into triangle primitive. Within triangle primitive, you only need two sides for as a template unit (i.e three vertices). You will have rotate these three vertices with 360/n degrees ( n - no of divisions). All these already part of ui/circle.jl.
https://github.com/JuliaWGPU/WGPUgfx.jl/blob/main/src/ui/circle.jl

Basically you should return a Circle object with indexData, vertexData, colorData and normalData (optional)

@arhik Is there any example that deals with 2D shapes?

plane.jl is simplest

@arhik Thanks, that was really helpful.
Do you have an example which shows working with mouse or keypresses?

splat.jl should be listening to both mouse events and keypresses. No visual aid for key pressess. That would interesting project.
For splat.jl to work you will have to download a file from here https://drive.google.com/drive/folders/1B8fBd3ivh1OuJBY_P28woJfmzvWc8WlO

@arhik I looked at the specific example (splat.jl) but I can't seem to find the specific lines that seem to be listening to keypresses or mouse movements.
Is there a way to print them to screen?

key - 'a' for attaching event system and 'd' for detaching event system. You should see mouse pointer output and key events in the terminal window.

Look into events.jl files in both WGPUCanvas and WGPUgfx. Basically WGPUCanvas provides hooks which WGPUgfx will hook into and overwrite event output. In detached mode you will all events printed out in terminal. WGPUgfx override events with no print statements.


Superset 3.0.0 generates invalid SQL for Dremio after releasing #23872

A clear and concise description of what the bug is.
How to reproduce the bug

Create a new chart that has the options of Series Limit. Eg. Time-Series Chart, Area Chart etc.
Set requried fields and Series Limit
Click Create Chart.
See error

Expected results
The chart is shown successfully on the right.
Actual results
Unexpected error returned. Superset generates invalid SQL for Dremio, which then throws an error. See screenshots
Screenshots

Comparison of SQL generated for Dremio for a Time series chart in 3.0.0 and 2.1.1, respectively:

Environment

superset version: 3.0.0

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
This pull request has introduced the regression: https://github.com/apache/superset/pull/23872
This is also apparent in the above screenshots. The invalid SQL is due to aliases missing.
How should we proceed from there? https://github.com/apache/superset/pull/23872 be reverted?

@betodealmeida Could you take a look?


Mongotest

I've incorporated a test database with mongodb which holds the recommended course sequences (ex: https://www.concordia.ca/encs/computer-science-software-engineering/students/course-sequences/co-op-soen-general.html).
The database is located at /opt/course-db and it contains a collection named courseSequences which holds all the data as BSON documents. One Document per sequence. As a reminder for what this sequence json data looks like, check out one of the files from the system that we currently have in place (plain text instead of db): http://<IP_ADDRESS>/courses/sequences/SOEN-General-Sept.json
Command used to start mongodb server on vm: sudo mongod --dbpath=/opt/course-db &.
Notable code changes:

The sequence scraper now writes the sequence json data to mongodb as well as in plain text. (See webscraping/node/main.js:129-143)
There is a new servlet in the Java backend which responds to POST requests at /mongosequences. It expects the POST body to contain the value: "sequenceID" and responds with the corresponding sequence based on the ID (see screenshot below for example). As usual, the logging done by this servlet will appear in /opt/tomcat/logs/courseplanner.log from my VM. (See src/main/java/SequenceProvider.java)
I've changed the index.html so the splash screen lets you select which default sequence to use. Select a new one, press continue, then press Reset Default. The website will make a request to the server based on which sequence you selected, and load the result into the page. Don't expect all the sequences to work perfectly yet.

Manual POST request to SequenceProvider servlet. The lower half is the response from the server:

what part of the deployment took longer than usual?

@Davidster not sure how to reply to ur comment more directly than tagging you, but both building the project and deploying. I get that my internet speed definitely slows down the deployment, so I assume that the building time is actually longer and that deployment may or may not be... which is why I didn't want to specify (so that you do check both)

it must be some intermittent issue with ur computer/internet, for me the deploy speed is the same as always

you actually don't need to click reset default if there is no saved sequence local storage variable present. The variable only gets created once you start dragging coureses around, and it gets removed each time you click reset default.
I agree that we should look into the UI looking all funky for certain default sequences. Not sure if this is due to the sequence JSON being bad or a bug in the UI code.


chore(readme): fix links in readme doc

I think we can redirect all the links to the vitejs.dev document site for better UX and navigation.

I think we can redirect all the links to the vitejs.dev document site for better UX and navigation.

Thanks for the PR - I updated them to point to the docs site instead.

Thanks for the PR - I updated them to point to the docs site instead.


Get Current Task

Server must provide a way for a player to get it's current assignment

already done


Job(with no triggers) not added to store after calling add_job() post scheduler.start()

Though a job that is created after scheduler.start() is scheduled, it is not added to the DjangoJobStore on the database.
Seeing this in case where the job has no triggers so it can be run on demand.

Occurs also when using DateTrigger.

After digging into the code base it seems that this is by design. Actually, the job is added and removed right away, cf.:

https://github.com/agronholm/apscheduler/blob/8a174843acb499d7f327cc49efa4e47bdddeb8da/apscheduler/schedulers/base.py#L991

As per the comments above, jobs will only be persisted to the job store if they have a next execution time.


SQL clause WITH is being added as a referenced object

Hi,
In my code I am writing a sql statement that has a WITH clause in it.  Source Orbit is picking this up as a object that is referenced.
exec sql declare c1 cursor for
        with temp as (
          select
           field1,
           field2
          from table1
        )
Select * from temp;

Source orbit is throwing an error saying it cannot find the TEMP object....well this doesn't really exist.
I think in these cases SO will have to figure out that temp is used in connection to the WITH clause and will need to only consider objects inside the WITH clause as valid objects referenced.  In my example above, SO should only find TABLE1.

Release 0.10.4 with the fix and also created an additional test case for it.


Update custom-aliases: usage methods, File formatting, and version numbers

What are you changing in this pull request and why?

Updated first version for Dispatch to 1.0. I'm using it in 1.4 so it had to be introduced before what was stated. The dispatch doc page says 1.0. I also updated the link to have the in-page reference it seemed to want. I re-titled the section header so it would stand out in the right navigation and be more descriptive.
I added the File macro around two files that were missing it.
I added an example of configuring an alias in YAML instead of Jinja.

Checklist

[x] Review the Content style guide and About versioning so my content adheres to these guidelines.
[x] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

remove version block since its available for all current (1.0 is deprecated)


Remove aquavanjaram942_20&80CU TT libs

If your commit involves changes to a YAML file, please take note.
Due to PR-1117 (https://github.com/ROCm/hipBLASLt/pull/1117) adding ActivationType: hipblaslt_all, all YAML files now need to include the ActivationType field (for hipblaslt logic YAML, use ActivationType: hipblaslt_all (not all); for tensile test YAML, you can use either all or hipblaslt_all).
Correspondingly, in the Logic YAML filename, the _A that originally represented ActivationType: all should also be changed to _HA. These changes have been implemented in PR-1117.

This PR is just removing some logic yaml. No further change needed related to 1117.


Game crash version 2.1

Game crashes every time with this version.
crash-2017-04-18_01.12.52-client.txt

I deleted the config file and the game started.


Request - Not a Issue : Can magpie be used for Keyword Extraction

It has been specified in intro section as
"""
has been developed at CERN to assign subject categories to High Energy Physics abstracts and extract keywords from them.
"""
How to extract keywords from a given abstract using Magpie.

You can treat each keyword as a label and then you can frame keyword extraction as a multilabel classification problem. You need to define the keyword vocabulary in advance though.

Not sure if this is helpful but I am guessing you can directly use word2vec model, which is generated from Gensim via Magpie (magpie.word2vec_model), to extract keywords from documents. One way of solving this problem is outline in this project, though I have no idea if this is the right or best way - https://github.com/bguvenc/keyword_extraction.

Thanks for suggestions


added the SlideForm-Login/SignUp

Fixes Issue🛠#855

Closes #855
Description👨💻

Added the navbar files to the components folder and updated the html file as well.
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[x] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[ ] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

https://github.com/Rakesh9100/Beautiify/assets/137754636/c1414ab7-3725-4c57-a146-d79a42a0f841

@Rakesh9100 please review this pr


New 7.1 "iterable" pseudo-type is not recognized

Don't know that I'd call this a bug, as it's a very new feature -- but at the least I'll mention it for your TODO list.
The new iterable pseudo-type in v7.1 is not recognized as a valid type. Instead, it is interpreted as a class in the current namespace. It should work like callable. For example, consider this code:
class Foo
{

    /**
     * Process a thing.
     *
     * @param callable $thing The thing to process.
     *
     * @return null
     */
    public function process(callable $thing)
    {
    }

}

This generates the following doc:

process(callable  $thing) : null

Changing the callable to iterable we get:

process(\iterable  $thing) : null

Hello @AlexHowansky,
Thanks for mentioning this to us. We, unfortunately, have a bit of a backlog with new features but I have added this to the backlog to fix. For the record, here is the PHP Documentation page referring to this new type: http://php.net/manual/en/language.types.iterable.php

Added a test to show this is resolved in v3.


i cant eat

i cant eat food bigger than me , please fix that.

yes you cant able to eat food when you are smaller than food lol!

lol, but i believe someone made a issue on this.....

 Do not make any more issues on the subject.


how to train my own data?

1.can this project train my own data?
2.if can,how to train?

Yes, of course. please follow dataset/convert_tfrecords.py to make your own *.tfrecords for your own dataset

I want to train my own data too, and I already make my own *.tfrecords. But when I run train_ssd.py ,I found that must provide the checkpoint_path,the path to a checkpoint from which to fine-tune,and put the pre-trained VGG-16 model in it. my question is pre-trained VGG-16 is not sutable for my dataset. How to solve it?

@HiKapok

@moonyoung430 set scafford  to None if you don't want use a pretained weights


Correct device name field to not show the email of the user, but to rather show device name

Here's an example of how it should be:

Seems to be an easy fix:
        return DeviceInfo(
            name=self._water_heater.name,
        )

The name prop of the DeviceInfo class should be populated.

Fixed with 1.0.0.


EPIC: Competitions & Teams

Core Feature

Tasks

[x] Define high level requirements
[x] Create basic mockups
[x] Update "API Requirements" in core spec
[x] Update "User-Interface Spec" in relevant front end repo
[x] Create detailed user stories using normal template

High Level Requirements
Basic Mockups
Link to API Requirements in Core spec
https://github.com/vegaprotocol/vega/issues/9981
https://github.com/vegaprotocol/vega/issues/9257
https://github.com/vegaprotocol/vega/issues/9980
https://github.com/vegaprotocol/vega/issues/9260
Link to User Interface Specs
Linked User Stories

#5485
#5486
#5196
#5487
#5194
#5488
#5195
#5557
#5558
#4715 (may not do)

I think we can safely close this as done at this point.
Minor improvements are continuing but can be treated as BAU at this point IMO.


Tisserand plots

📕 About Tisserand plots
Imagine you are observing asteroids which are orbiting near Jupiter. The big
planet might create perturbations among these small bodies orbits but you want
to make sure if an actual observed body was previously observed, althought their
COE parameters might be suffered some variations.
Previous question arised to Félix Tisserand, who was a French astronomer that in
the 19th century developed a method based on an invariant constant (which today
carries his name). You can understand the tisserand parameters as some way to
measure the "energy" of a body. In fact, its units are distance2 / time2 which
is also known as "characteristic energy".
Nowadays, Tisserand graphs can be plotted in many different ways:

Tisserand parameter VS apoapsis || eccentricity || inclination
Heliocentric periapsis VS Heliocentric apoapsis
Heliocentric orbital period VS Heliocentric apoapsis

The most common ones are the last two, though the first one might be plotted by
making use of a contourf plot as seen in this page:

All Tisserand Solutions by contourf plots

The most powerful feature this kind of plots show is related to mission design,
in particular to gravity assist maneuvers. They would lead to the solution to
the question: if I want to go from body A to body B, what would be the most
optimal set of flybys to achieve the trip?

💡 Feature request
The algorithm on how to obtain these kind of plots is very well explained in the
following document. Furthermore, it includes lots of solved cases which could be used as unit tests.
With the implementation of the function get_mean_elements() it is now possible
to obtain the necessary parameters for any desired body.
🎯 Goal
Although the working algorithm is pretty clear, the problem might arise on how
to implement this feature inside poliastro. I am thinking about the following
usage:
# File poliastro/plotting/tisserand.py

class Tisserand:
    """ Plots a Tisserand parameter contourf """

    def __init__(a_span, ecc_span, icc_span):
        ...

class FlybyPlotter():
    """ Plots Tisserand graphs for given bodies and V_inf span """

    def plot(body, Vinf_span, **kargs)

Previous code might lead to the following working flow:
from poliastro.plotting.tisserand import FlybyPlotter
from poliastro.bodies import Venus, Earth, Jupiter
import numpy as np

fp = FlybyPlotter()
fp.plot(Venus, np.linspace(0, 10, 11) * u.km / u.s)
fp.plot(Earth, np.linspace(0, 9, 10) * u.km / u.s)
fp.plot(Jupiter, np.linspace(0, 15, 16) * u.km / u.s)

I would like to read your opinions and suggestions on how to adapt the algorithm
to the actual API, not pretty happy with the previous "FlybyPlotter", migh lead
to confusion.
🔖 References and papers

Preliminary Trajectory Design of a Mission to Enceladus

Graphical method for Gravity-assist sequancing

Awesome @jorgepiloto, thanks for adding all the technical background :heart:
Perhaps we can do something like this?
from poliastro.plotting.tisserand import FlybyPlotter
from poliastro.bodies import Venus, Earth, Jupiter

fp = TisserandPlotter()  # defaults to 10 contours
fp.plot(Venus, (0, 10) * u.km / u.s, num_contours=11)
fp.plot(Earth, (0, 9) * u.km / u.s,  # no need to specify num_contours=10
fp.plot(Jupiter, (0, 15) * u.km / u.s, 16)

(I renamed the object to TisserandPlotter and removed the need to import np.linspace by giving a pair (start, end)).
Let's save the FlyByPlotter for #662 :smirk:

Closed in #927 :tada:


Add persistent synonyms with pdictng

A bot with a thesaurus!
We want to be able to easily define synonyms for the various commands within bots: "hi" for "hello", "picture" for "imagine", etc.
I pulled the relevant logic out of https://github.com/mobilecoinofficial/forest/pull/127 and put it into SynonymBot class, using the powerful aPersistDict for stateful storage of synonyms.
Devs can still add lists of synonyms to methods in development, but now admins and users can adjust the bot's vocabulary directly in Signal. The interface is roughly based on the syntax of ln in the command line, like so:
link hello wazzup
SynonymBot has commands for linking, unlinking, listing synonyms, and more. It also has dialogue branches for various error states.
Still wondering:
Design/abstraction

Should this be integrated lower, into core?
Or should it inherit from a higher level bot?

Features from QuestionBot might make error handling more natural

Technical hurdles

Mypy doesn't support adding attributes to functions. Currently just bypassing this with type: ignore but it seems to be an open issue in the community. Several hacky solutions are listed at https://github.com/python/mypy/issues/2087
Checks are failing due to unrelated files? (raised issue at https://github.com/mobilecoinofficial/forest/issues/133)
The backend for aPersistDict is kind of tricky and undocumented (notes at https://github.com/mobilecoinofficial/forest/issues/125#issuecomment-1047291669)

NLP questions

Some commands are restricted to admin, but currently link and unlink are available to users. This opens possibilities for abuse.

Should they also be admin-only?
Or have a restricted-words list, like berduck and bouncebot?

Unclear how synonyms will interact with fuzzy matching from string_dist
Currently devs can add the same synonym to two different commands. The first one alphabetically gets priority, i think. Users will be rebuffed from doing this though. (see sample dialogue below)

Happy to accept feedback on any of the above, or anything I missed.
Sample dialogue

maybe a decorator, like requires_admin / hide? at least fewer # type: hides
in the link it looks like a protocol might be the way to go, or a Command class that inherits from Callable but has more attributes....
mobfriend issue should be fixed, run pip install --upgrade prometheus_client prometheus_async locally; they added type hints in a new release

Okay @technillogue , I pulled your fix from main (thx!) and then updated to a decorator and protocol. This fixes most of the issues with mypy, except for adding synonyms to an inherited method, because the signatures no longer match. Don't know how common this use case is though? Definitely reduced the amount of #type: ignore although not total LOC

this is so exciting.

I'm going to add the pdictng_readme.md document requested by @technillogue in #112


Use cargo from devcontainer in comparison benchmarks

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.99%. Comparing base (7c196f0) to head (e6fc248).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #129      +/-   ##
==========================================
+ Coverage   96.66%   96.99%   +0.33%
==========================================
  Files           5        5
  Lines         510      433      -77
==========================================
- Hits          493      420      -73
+ Misses         17       13       -4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update versions.

Update tests to include 1.8 (and ideally master, too).
Update index page.
Update docs pages.

:+1:

@auvipy If you're feeling proactive then any pull requests for this would be most welcome! :smile:

for the pointed tasks I have to update the tox.ini? run the tests localy with django 1.8 and update the docs to 1.8 right?

The tox.ini and the .travis.yml

#47


⚠ Transitioning Support for Awesome Notifications to Discord ⚠

Important Announcement:
Hello Awesome Notifications Community!
After careful consideration and review of our current support system via GitHub issues, we have decided to make a significant change. Effective immediately, we will be transitioning all support for Awesome Notifications to our Discord community. The decision to move away from GitHub issues as a platform for support was not taken lightly. However, we've encountered several challenges that have led us to this decision:

Respect for Community Rules: Despite clear guidelines and repeated efforts to maintain a constructive and respectful environment, a considerable number of issues posted have unfortunately disregarded our community rules. This disregard not only undermines the spirit of collaboration but also impacts the efficiency and effectiveness of our support.

Efficiency and Effectiveness: In our attempts to enforce these guidelines by marking posts as "invalid" and requesting necessary information to understand the issues better, we found the process to be exceedingly time-consuming. The critical aspects and information omitted by the community guidelines are often essential for resolving problems, making the request and follow-up process through GitHub issues inefficient.

Focus on Quality Support: Our goal has always been to provide the best support possible to our users. After evaluating various platforms, we believe that our Discord community https://discord.awesome-notifications.carda.me/ offers a more dynamic, interactive, and efficient way to support you. Discord will allow us to engage with you in real-time, share resources more effectively, and foster a closer-knit community.

What This Means for You:

❌ GitHub Issues will be permanently closed for new support requests. We will, however, keep the existing issues accessible as an archive and a resource.
➡ Join us on Discord! We invite you to join our Discord community where we'll continue to offer support, updates, and engage with all of you. It's a space for you to ask questions, share feedback, and connect with fellow Awesome Notifications users and the development team.

We understand this is a significant change and appreciate your understanding and support as we make this transition. Our commitment to providing you with the best support has not changed, and we believe this new approach will allow us to serve you better.
Thank you for being a part of our journey. We look forward to seeing you on Discord and continuing to build an even more awesome community together.
Best regards,
Rafael Setragni,
Founder of Awesome Notifications

Also, to remember you guys. Because of the consuming time that issues on GitHub inevitable causes, I will had to ignore every post here on issues.

This makes all of the information and discussion inaccessible from web/google, I think this is really a bad idea and will deter people adopting the package

This is a bad decision for the package

Thank you for sharing your thoughts on the transition to Discord. I understand the concern about information and discussions on Discord not being indexed by Google, making it harder for users to find answers through a web search.
However, we’ve observed that those who actively participate in the Discord community tend to stay engaged, contributing to discussions, sharing insights, and helping one another. On GitHub, we noticed a different pattern—many users would only engage when they needed something, often disregarding community guidelines and disappearing after their issues were resolved.
To give you a clearer picture, I temporarily reactivated the GitHub Issues section as an experiment. Unfortunately, 100% of the new posts ignored the guidelines entirely, including the form we set up to gather essential information. This form is crucial for us to efficiently understand and address issues. Instead, people would erase the form, copy and paste their errors, and expect us to decipher the problem—often due to skipping the documentation and example pages we worked hard to create.
The reality is that many users were not respecting the time and effort we put into providing support. They would rather have us spend our time unraveling their issues than take a few minutes to fill out the form or read the provided resources.
Our decision to move to Discord is not just about efficiency but about fostering a more engaged and respectful community where support is a two-way street. We believe that this platform will allow us to offer better support while building a stronger, more collaborative environment.
We appreciate your understanding and hope you’ll join us on Discord, where we can continue to grow together.

@rafaelsetragni it's true that many people don't follow the issue template which is frustrating. A different solution than using Discord can be to use the Github Issue Forms instead with required and optional fields for creating a more disciplined issues structure.

@rafaelsetragni, I'd like to share an opinion here that challenges this decision and ultimately is questioning the maintenance status of the project.
Please, do not take it personnally.
The job of maintainer can be harsh because you mainly just receive negative feedbacks and it is really understandable that you may end up reading most tickets as disregarding your time and effort.
I do not know anything about your personal life. This is still a personal project and you are not accountable to us for your benevolant work.
But as you justly pointed, this is a two-way street, the users of this library are not accountable for being engaged in the maintenance of the library and it should be accepted that they disappear after their issue is resolved.
The mere reporting of (constructive) issue is already a valuable participation.
If I understood well that your main concern was that users tend to waste your time (which I do not oppose any argument, that's an understandable feeling) by avoiding to take on their time to just express their issues, then, if I consider your solution to go to Discord, I actually do not see any real benefit to this.
I checked the latest 15 threads (which is the same number of open issue on Gitlab at the time of writing this) and none of them structure the issue in an more accessible way than what is done on Gitlab Issue.
As of in Discord, the issues on Github still allow for comments and discussion. You are allowed to just say to the reporter that he must clarify his point before being able to continue, and ultimately close that ticket without being able to solve it.
After several months of using Discord, do you see real benefits of it instead than using Github Issues ?
And if so, does it compensate for the lack of accessibility of this platform for developers in comparison to github ?
My main concern for me is that we can see your move as disregarding the work and effort of some of your users as well.
Take the issue (sorry to take the issue that impacted me, but it's a relevant point I can make then) of release mode being too aggressive since a recent change in Android tools (#960 but already opened before the move to Discord in #909 and #814). Most of them didn't follow the issue template (or left the explanation text in most parts) but the same issue on Discord still kept silent from your part and was just responded with users that took time to find a workaround.
Actually, the guy who just posted in this thread just above mine, @OutdatedGuy took more time to investigate because these workaround are actually bad response as they are just asking to deactive optimisations made in release builds. He is not the only one who made that effort, since myself took some time to try to reproduce the bug in a clean project but without success :sweat_smile:
@OutdatedGuy succeeded in pinpointing the issue and opened a PR: https://github.com/rafaelsetragni/AndroidAwnCore/pull/2
But this is still kept unresponded. How can we, as the unengaged users, interpret this then ? :thinking:
Still, this is not a criticism about the time you take for this project. You are really allowed to have less motivation, take holidays, forget about this entirely, or anything that explains the lack of engagement in the project. But really, this is the same for anyone.
This is a criticism about how you let the users of this library report their issue with it and question about if there is a need to reorganise how this library is maintained to offer that possibility.
As we begin to depend on this library for our own projects and more importantly if this applies to projects we are accountable for to someone or a company, you cannot take this concern about maintenance badly, this is a logical concern.
For giving a positive feedback, take these issues as facts that instead than looking for another library, users want yours to be fixed. This is (for my case at least) because you currently have the best option for notifications in Flutter application. So kudos for that !
It'd be sad that the community needs to fork this in order to continue using it responsibly.
In conclusion, my point is that this is probably a human problem here and not a technical one. Maybe it is the opportunity to look to reorganise the team behind this project. To look for a human solution instead than looking for a technical one.
Kind regards


Update the home page

I would like to update the homepage and change the background of it. I would also like to change the colors of the text.

Hey ! I would like to improve UI of home page .please assign this task to me

Could you plz assign this task to me

I would like to work on this.Please assign this to me


The failure_callback was not called at the correct place

Coverage remained the same at 26.043% when pulling a3c8c260e7c103844abd69baf2fa2121f7ad443e on calixteman:fix_failure_cb into fbf6a4cb4b30afcc39d98c3be269bdf4fa1e9cc7 on mozilla:master.


Minimal File Issue

I caught this in my crash log...
Minecraft Version: 1.12.2
Minecraft Forge Version: <IP_ADDRESS>08
Advanced Rocketry Version: 1.5.0-126
LibVulpes Version: 0.4.0-49

[05:10:45] [main/WARN] [FML]: Found FMLCorePluginContainsFMLMod marker in [1.12.2] Advanced Rocketry by zmaster587 (1.5.0-126).jar. This is not recommended, @Mods should be in a separate jar from the coremod.
[05:10:45] [main/WARN] [FML]: The coremod AdvancedRocketryPlugin (zmaster587.advancedRocketry.asm.AdvancedRocketryPlugin) is not signed!

Note: This showed up in the crash log 3 times whilst I was debugging my modpack. It seems to be spammed for many mods, actually.

I just had no idea why this message has spammed the console for so many mods? I was curious, and thought to report it...

That's fair, I'm not familiar enough with forge to explain why they yell about it (not the mod dev, obviously). I just didn't want you thinking that warning lead to a crash, because then you'd be off on a wild goose chase trying to get things running again D:

that is fine. as long as its not crashing the game.


Images are saved in full size and without augmentations

Images are saved at full capture resolution. At higher (1080p+) resolutions, this can cause a sever bottleneck to file saving speed. record.py should be changed so that it resizes the image before saving. This will also reduce file sizes.
Augmentations occur in the prepare stage, so after the data is saved as .jpg or .png, and then they are saved as .npy arrays. This reduces the transparency of the image augmentations as it is impossible to tell what the augmented image looks like. The images should be augmented before they are saved.

https://github.com/mgagvani/Xbox-Game-AI/commit/5dab37ca03fd70b2c4669a4e59eb88b7ad2168ca fixes these issues. Closing this issue for now. I have noticed a performance degradation but that is less of a priority.


auto-clicking next in sarcApp.py + myomesin stain

Thank you for this wonderful tool. I work in heart disease research doing imaging analysis, so sarcApp is super interesting in being able to quantify the sarcomeres.
I have 2 questions:

sarcApp.py, runs 1 image at a time, and then prompts me to click next before proceeding to the next image. This is cumbersome if I have several hundred images I want to analyze. Is there a way to run all the images in the folder at once?

My data has the stains myomesin and dapi. If I specify myomesin and dapi channels and run, I get a correct-looking binary image, but then the output myomesin_cellResults0.csv almost completely empty/nan, and myomesinImage0.jpg is a blank white image. There is also no output in the dapi output folder. If I choose actinin and dapi however, but use my myomesin images for actinin, then it runs fine and outputs the expected results but it's the wrong stain. The actininImage0.jpg looks like this. Is this correct? I was expecting a binary image with the myofibrils annotated.

Is it possible to run with the myomesin and dapi stains only?

Hello! I'm glad you've been finding the tool useful and apologize for the issues, hopefully we can solve them asap.
For the first issue, you can run all of the images in the folder at once if you input data (csv files) instead of images, but I understand that you if you don't need to individually look at each of the images it will be cumbersome to have to click next every time. I will make a new version as a branch to this repository that does not show any images to click through and link it to you in a comment with the new version tomorrow.
For the next issue, let me ask a few questions first so I can best understand what is going wrong: are you inputting images alone and using the internal binarization method for both myomesin and dapi?  The actinin image looks incorrect and should show stripes at each Z-Line with colors denoting individual myofibrils. Let me look into why no results are saving from the DAPI images in the meantime!
Thank you for reaching out, and please continue to raise issues as you find them!

Thank you for the response! Once I can get the images to analyze correctly I will try inputting a csv so that all the images can run at once.
Yes, I am inputting the images alone. They are in the .tiff format but there is no additional metadata. I did not run the images through ImageJ or anything like that. My actual images are of the myomesin and DAPI stain, and there are 2 scenarios in which I'm running:

Specify myomesin and DAPI in sarcApp. There is no output for DAPI, and the myomesin_cellResult.csv output is mostly nan. The corresponding myomesinImage.jpg is a blank outline. There is also no myomesin_mfResults.csv output as no myofibrils are identified.

Set actinin in sarcApp while using my myomesin images. Now there is a result for DAPI and actinin, though as seen above, the results don't seem correct.

My images are 1080 by 1080 pixels at 40x/0.25 microns per pixel, and have around 100 cells present.


Fix cssparser read-write-read target to iterate correctly.

https://github.com/servo/rust-cssparser/issues/165#issuecomment-311017408

One of those cases where Option and Result as Iterator are surprising, right?
bors r+


game hangs when i try to eat food FIXED

soory for the inactivity on my side, the problem fixed in the new version. thank you for your efforts OreCruncher, keep up the good work !

Cool!  Thanks for letting me know.


CVSL-1710 add migration to set updated_by_id

This PR introduces the updated_by_id column which we need in order to show the full name of the person who last updated the licence on the CA screen. This includes the modelling of the column to set the updatedByFullName field correctly as well as a migration to populate the value where possible for existing data.

Two outstanding questions (which could be a subsequent PR):

Are we changing to using the staff member everywhere updatedByUsername is used (i.e should we be updating the updatedByUsername and setting updatedBy everywhere we currently have updatedByUsername - eg in submit, timeout, deactivate ... I think yes we should to ensure consistent data around who updated what
What about licence and audit events which use the username - should these be set using the staffMember?.username ?: SYSTEM_USER as well?


HDDS-4665. Fix when update quota the usedBytes and namespace will become to 0

What changes were proposed in this pull request?
When update quota the usedBytes and namespace will become to 0. This is a bug that needs to be fixed.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4665
How was this patch tested?
UT added

LGTM thanks!

LGTM thanks!

+1.
The failed UT is irrevelent.

+1.
The failed UT is irrevelent.


Missing email in RHP header and message when adding new contact

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/48968
PROPOSAL: https://github.com/Expensify/App/issues/48968#issuecomment-2345207080
Tests

Precondition:

Login as copilot
Go to Account settings.
Click on the account switcher.
Switch to another account.

Bug:

Click Contact method.
Click New contact method.
Enter a new contact method > Next.
Verify that: The RHP header will show the current contact method.

Do the same with features like Manage trips, Add delegate in Security page, Reveal details in Expensify Card page and verify that: we didn't miss the email.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Precondition:

Login as copilot
Go to Account settings.
Click on the account switcher.
Switch to another account.

Bug:

Click Contact method.
Click New contact method.
Enter a new contact method > Next.
Verify that: The RHP header will show the current contact method.

Do the same with features like Manage trips, Add delegate in Security page, Reveal details in Expensify Card page and verify that: we didn't miss the email.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/e21954f9-0611-4758-a774-af15983f2d6d

Android: mWeb Chrome

https://github.com/user-attachments/assets/8c709730-1847-4346-b21c-da55f52f5233

iOS: Native

https://github.com/user-attachments/assets/96e53e15-623f-4a8a-bef9-f8bf103dc9c5

iOS: mWeb Safari

https://github.com/user-attachments/assets/397a244a-6b62-48a2-8dec-ae6d85722a44

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/99e84bbe-8d3e-4672-8da3-f7e2a5578b5f

MacOS: Desktop

https://github.com/user-attachments/assets/37913be7-15e8-4604-9f75-d312d39088d4

@nkdengineer Thanks for the PR.
Let's add test steps for all the changes made in the PR. I believe we have make changes unrelated to New Contact Method as well.

@sobitneupane i updated, please check again

@nkdengineer Thanks for the update.
Can you please add the screen recordings for at least one platform for each case.

I'll update soon

@sobitneupane I noticed that in some places where we changed the code, that feature is not being used for Copilot. Should I revert those code changes? Because as of now, there doesn’t seem to be any issue.

@sobitneupane After I merged the main branch, there was an issue with using withOnyx. Should I fix it in this PR right away?

I noticed that in some places where we changed the code, that feature is not being used for Copilot. Should I revert those code changes? Because as of now, there doesn’t seem to be any issue.

Yup. Let's not make the change if it is not required.

After I merged the main branch, there was an issue with using withOnyx. Should I fix it in this PR right away?

Have we added any new usecase for withOnyx in this PR? If not, let's not deal it with in this PR.

@sobitneupane i updated, and added the screenshots to MacOS: Chrome / Safari

I'll update soon

Thanks. @sobitneupane please re-review after the updates

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


{Compute} Fix ValueError in vm commands

Description

This PR works as a part of fixing the none-actionable issues in #14986

It fixes the ValueErrors with patterns below in VM commands.

not enough values to unpack (expected 4, got 2)
too many values to unpack (expected 4)
...

It applies the AzCLIError in comand group
It inroduces the new AzCLIErrorType: UsageError, ResourceNotFound

Testing Guide

Case1: Run az vm image show --urn a:b:c
before
UnexpectedError: The command failed with an unexpected error. Here is the traceback:
not enough values to unpack (expected 4, got 3)
Traceback (most recent call last):
  File "C:\Users\houk\Desktop\msws\env_new\lib\site-packages\knack\cli.py", line 215, in invoke
    cmd_result = self.invocation.execute(args)
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\__init__.py", line 654, in execute
    raise ex
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\__init__.py", line 718, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\__init__.py", line 711, in _run_job
    six.reraise(*sys.exc_info())
  File "C:\Users\houk\Desktop\msws\env_new\lib\site-packages\six.py", line 703, in reraise
    raise value
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\__init__.py", line 688, in _run_job
    result = cmd_copy(params)
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\__init__.py", line 325, in __call__
    return self.handler(*args, **kwargs)
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\arm.py", line 756, in handler
    show_exception_handler(ex)
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\arm.py", line 772, in show_exception_handler
    raise ex
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli-core\azure\cli\core\commands\arm.py", line 754, in handler
    return getter(**args)
  File "c:\users\houk\desktop\msws\azure-cli\src\azure-cli\azure\cli\command_modules\vm\custom.py", line 1728, in show_vm_image
    publisher, offer, sku, version = urn.split(":")
ValueError: not enough values to unpack (expected 4, got 3)

After
UsageError: --urn should be in the format of publisher:offer:sku:version

Case2: Run az vm image show --urn a:b:c -p d
Before
ValidationError: usage error: --plan STRING --offer STRING --publish STRING --version STRING | --urn STRING

After
UsageError: If using --urn, do not specify any of --publisher, --offer, --sku, --version
Try to use --urn publisher:offer:sku:version only

Error improvement for VM

The PR title should start with {Compute}, not {VM}. And error updates for compute modules are much less than what I expected, are you sure all the work for Compute are done?

Of course not, we should do that iteratively. This PR is only for ValueError.

I suggest create subclass of each error type.
usage: raise UsageError(error_msg)
Developer doesn't need to specify error prefix explicitly

/azp run

/azp run

#14987


Using I2C functions

Maybe I am misunderstanding correct usage of I2C functions provided by bonescript but from what I understand, the correct usage is along the lines of
b.i2cOpen(PORT, PWR_CHIP);
b.i2cReadBytes(PORT, STATUS, 1, function(data){...})

I assume the thinking is that the ReadBytes is always preceded by the i2cOpen function within the same function scope. If the i2cOpen function was, for example, in static part of code, and the ReadBytes was in a function then you could end up with wrong results.
Example.
i2cOpen('/dev/i2c-1', 0x20);

function func1() {
  i2cReadBytes .....
}

In this case if any other function anywhere called i2cOpen and then you called func1() you'd be reading bytes of the last i2cOpen function.
Is there a way to use these functions similar to the way it is used in i2c which is basis for bonescript i2c functions? Where method returned by i2cOpen is used as 'parent' (sorry, can't think of right word to use) to ReadBytes call?
Just looking for direction, thanks

This issue was moved to beagleboard/bonescript#28


[1.20.6 Paper #130] the plugin doesn't load

When I was on 1.20.4 everything was working fine, but updating to 1.20.6 and the plugin no longer works
https://mclo.gs/Nsc9dYs
also I cannot join the discord, ether the invite links are bad or I have been banned years ago.

I am unable to reproduce, and so this is a support matter that would need to be addressed on Discord. In the exceptional circumstance in which you've been banned, we can no longer provide any help to you for using the plugin.
Thank you for your understanding.


Fix: include uppercase characters when normalising plugin id

What this PR does / why we need it:
Users can type all sorts into the prompts when scaffolding a new plugin. Right now the normalizeId function strips uppercase characters which creates incorrect IDs (see path of directory created below):
success Installed "<EMAIL_ADDRESS>with binaries:
      - create-plugin
? What is going to be the name of your plugin? My Plugin
? What is the organization name of your plugin? HeyWesty
? How would you describe your plugin?
? What kind of plugin would you like?  panel
? Do you want to add Github CI and Release workflows? Yes
? Do you want to add a Github workflow for automatically checking "Grafana API compatibility" on PRs? Yes
✔  ++ /Users/jackwestbrook/Sandbox/plugin-tools-tests/eyesty-ylugin-panel/.config/.eslintrc

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Should'nt we instead .toLowerCase() them?

I think we should in:

normalize_id make everything lowecase as we use it in plugin.json -> id which is the plugin slug, that has to be lowecase, no spaces, etc. https://github.com/grafana/plugin-tools/blob/main/packages/create-plugin/templates/panel/src/plugin.json#L5
Outside of normalize_id orgName being any case should be allowed https://github.com/grafana/plugin-tools/blob/main/packages/create-plugin/templates/panel/src/plugin.json#L10
Same for pluginName it can be any case


Error upgrading deb package from VS Code Insiders repository

VSCode version: Code - Insiders 1.18.0-insider (4b01451cea60f32412098735709fddcac567b33d, 2017-10-19T08:25:22.140Z)
OS version: Ubuntu 17.04 (Linux x64 4.10.0-38-generic)
Extensions:

Extension
Author (truncated)
Version

matlab
Gim
0.7.1

latex-workshop
Jam
3.5.5

Steps to reproduce:
Running sudo apt update && sudo apt upgrade to upgrade the VS Code Insiders build gives the following messages:
Preparing to unpack .../code-insiders_1.18.0-1508736309_amd64.deb ...
Unpacking code-insiders (1.18.0-1508736309) over (1.18.0-1508401646) ...
dpkg-deb (subprocess): decompressing archive member: lzma error: compressed data is corrupt
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/code-insiders_1.18.0-1508736309_amd64.deb (--unpack):
 cannot copy extracted data for './usr/share/code-insiders/resources/app/extensions/node_modules/typescript/lib/tsserverlibrary.js' to '/usr/share/code-insiders/resources/app/extensions/node_modules/typescript/lib/tsserverlibrary.js.dpkg-new': unexpected end of file or stream
Errors were encountered while processing:
 /var/cache/apt/archives/code-insiders_1.18.0-1508736309_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Reproduces without extensions: Yes

This looks like https://github.com/Microsoft/vscode/issues/35703 all over again.

yup, facing the same issue here

Same issue here.

I just tried to update again and it looks like the problem has been automagically fixed.


docs: Fix Twitter URL

You were linking to Twitter.com instead of your profile.

Thank you. That's very kind of you!


golden test ci

Work on Golden test rendering ci action
Initial Work on getting an helm rendering action

the diff-rendering-completed job will be used in the repo settings to set it as required
we cannot set a matrix job as required because their name is dynamic and will change if we change the list of values file we use to test


[2.4] Auth configuration of OpenLDAP fails with error "Error creating ssl connection: LDAP Result Code 200 "": EOF"

back port for https://github.com/rancher/rancher/issues/29153
gz#12435

Backend PRs merged, needs UI: https://github.com/rancher/rancher/issues/30617

OpenLDAP was validated in  #30617
Working on getting AD and FreeIPA with StartTLS.

OpenLDAP was validated in  #30617
Working on getting AD and FreeIPA with StartTLS.

Rancher version: v2.4-head (01/12/2020) 8e9977805
Basic P1 use cases for authentication covered in all cases.
Encryption options:

None
TLS
STARTTLS

I tested the three encryption options with Active Directory and self-signed certs (this option must provide a CA cert for TLS and STARTTLS).
For FreeIPA and OpenLDAP I used test environments that have valid Letsencrypt certs. None, TLS and StartTLS worked.

Rancher version: v2.4-head (01/12/2020) 8e9977805
Basic P1 use cases for authentication covered in all cases.
Encryption options:

None
TLS
STARTTLS

I tested the three encryption options with Active Directory and self-signed certs (this option must provide a CA cert for TLS and STARTTLS).
For FreeIPA and OpenLDAP I used test environments that have valid Letsencrypt certs. None, TLS and StartTLS worked.

v2.5-head and master-head testing will be covered in #29810

v2.5-head and master-head testing will be covered in #29810


Remove default variables for public and private subnets

If a specific use case requires only public or private subnets and hence does not pass variables for the other subnet, the default subnet takes effect, although the use case does not require it. So, to address it, I'm taking the option of not specifying the default value. That way, the resource will be created if the values are passed.

Also, removing the default variable value for vpc_cidr


bootkube support for GCE as cloud provider

enabling GCE as cloud provider gives such error:
kubelet_node_status.go:73] Unable to construct v1.Node object for kubelet: failed to get external ID from cloud provider: googleapi: Error 403: Insufficient Permission, insufficientPermissions

So PVCs, no LBs can be created.
Instances have full API access.

adding scopes as below did not help:
gcloud compute instances create ${CLUSTER_PREFIX}-core1 \
  --image-project coreos-cloud --image-family coreos-stable \
  --zone ${ZONE} --machine-type n1-standard-1 --scopes cloud-platform,storage-rw,compute-rw,logging-write,monitoring,monitoring-write,service-control,service-management,sql,sql-admin,storage-full,taskqueue

You may want to read through https://github.com/kubernetes-incubator/bootkube/issues/463

oh, upstream bug, not really easy to solve then :(

I'm going to close this as a duplicate of https://github.com/kubernetes-incubator/bootkube/issues/463 so we can keep discussion in one place.


Does not looks compatible with Rails 3.1.0rc2

When trying to start Rails I am getting the following error:
https://gist.github.com/1014249
I am on Mac OS X Snow Leo with ruby 1.9.2p274 (2011-06-06 revision 31932) [x86_64-darwin10.7.0]. The versions in my Gemfile:
[andrey-mbp ~/projects/rails/alt12-site rails3]$ bundle show rails
<EMAIL_ADDRESS>[andrey-mbp ~/projects/rails/alt12-site rails3]$ bundle show prototype-rails
<EMAIL_ADDRESS>

I'm running into this as well. I think the problem is that while the patch to fix it has been applied, it was applied to master and there was no version bump. Now that 3.1.0 is out, it would be good if there was an official version of this that was compatible.

It was an easy fix, I converted every prototype script to jQuery. Took me a couple of hours!

The fix was pushed to master in June, and version 3.1.0 of the gem was published in August together with Rails 3.1.0. Are you still having this problem?

I am not because I went the route @mhenrixon went and just converted it to a jQuery site. It seemed to be the path of least resistance for my particular project.


Bugfix: Outdated dependencies and problems running #34

Nodewebkit was renamed to nw, so I updated the dependency. The edit menu is now only shown on a native mac menubar, so the error mentioned in #34 appear. I used the native menubar to fix it

+1

hey @antiboredom this looks good to me, thoughts about merging this one in?

Looks great thanks!


Dbms basics docs added

Related Issue
Fixed : #638
Description

i have added new Tutorial on "DBMS"

and added this files

added image according to topic

added tables to more readable for user

table with diagram

added another note like stuff also

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / Videos (if applicable)
https://github.com/CodeHarborHub/codeharborhub.github.io/assets/127659443/78ee4df7-75ff-4ba3-a02c-7a047fd85d54
Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Here are some resources that may be helpful as you contribute to CodeHarborHub:

Code Harbor Hub Community Features
Docusaurus Documentation
React.js Documentation
Markdown Guide
MDX Documentation
Mermaid Documentation

Resources for DSA Features on Our Site:

Tabs: Switch Languages
Line Numbering
Math Equations

hey @Ajay-Dhangar , i have table , note ,diagram  and table with diagram like stuff to make it professional as you suggest.
after review it if you want please make it level 3

@Vipullakum007 Great but If you want to use mermaid diagram then you can also, used for best practice because our site in fully supported to mermaid diagram and check out https://mermaid.js.org/ or try some code https://mermaid.js.org/syntax/entityRelationshipDiagram.html for ER - Diagram and more....

@Vipullakum007 Great but If you want to use mermaid diagram then you can also, used for best practice because our site in fully supported to mermaid diagram and check out https://mermaid.js.org/ or try some code https://mermaid.js.org/syntax/entityRelationshipDiagram.html for ER - Diagram and more....

@Vipullakum007, would you be interested in working on this? Using images can slow down our site's performance. Instead, we can use Mermaid to generate diagrams with code. This approach will help make our site faster and more optimized.

@Vipullakum007 Great but If you want to use mermaid diagram then you can also, used for best practice because our site in fully supported to mermaid diagram and check out https://mermaid.js.org/ or try some code https://mermaid.js.org/syntax/entityRelationshipDiagram.html for ER - Diagram and more....

@Vipullakum007, would you be interested in working on this? Using images can slow down our site's performance. Instead, we can use Mermaid to generate diagrams with code. This approach will help make our site faster and more optimized.

If you want to level3 then work on it.

@Vipullakum007 Great but If you want to use mermaid diagram then you can also, used for best practice because our site in fully supported to mermaid diagram and check out https://mermaid.js.org/ or try some code https://mermaid.js.org/syntax/entityRelationshipDiagram.html for ER - Diagram and more....

@Vipullakum007, would you be interested in working on this? Using images can slow down our site's performance. Instead, we can use Mermaid to generate diagrams with code. This approach will help make our site faster and more optimized.

If you want to level3 then work on it.

hey @Ajay-Dhangar  , i have added mermaid diagram you can review it thx for your information i don't have idea about this tool this very helpful @Ajay-Dhangar Thank you again. you can make it level 3

done
hey @Ajay-Dhangar , done but you forgot to make it level 3.


Enable inference mode for evaluation

What does this PR do?

Fixes #11530, #11018
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @borda

We previously had support for this but needed to revert it: https://github.com/PyTorchLightning/pytorch-lightning/issues/8499
https://github.com/PyTorchLightning/pytorch-lightning/pull/9443
have you confirmed this is safe to roll out now?

we have extensive tests that seem to be passing with this change, so a good indicator that this is safe. I have also confirmed that it's working with the example shared in the issue that caused the revert last time. But even if it still has some issues, we should explore the issue more in-depth rather than reverting it just like last time. I couldn't find anything related in the PyTorch docs that some backend like gloo is not supported or any other limitation. So I think it's safe to roll out now and explore the issue more next time if any comes up.

We previously had support for this but needed to revert it: #8499 #9443
have you confirmed this is safe to roll out now?

we have extensive tests that seem to be passing with this change, so a good indicator that this is safe. I have also confirmed that it's working with the example shared in the issue that caused the revert last time. But even if it still has some issues, we should explore the issue more in-depth rather than reverting it just like last time. I couldn't find anything related in the PyTorch docs that some backend like gloo is not supported or any other limitation. So I think it's safe to roll out now and explore the issue more next time if any comes up.


Adjust collector extension log level

All logs in AWS Lambda output to one CloudWatch log group, the collector extension logs will mess up with user's Lambda application logs.
Collector extension should support adjust collector log level. So, user can enable/disable collector log by configuration.

I would like to contribute to this issue, can you please provide more Information on expected solution, should it be something similar to using this library / zap and logs based on the level such as info , error .

@vasireddy99 https://github.com/open-telemetry/opentelemetry-lambda/issues/230

We are facing same issue.. Is  their anything being done about it..

Implementation to address this issue is currently in progress. Any information regarding that will be updated here in this issue. Thanks for following up.

This is tracked at https://github.com/open-telemetry/opentelemetry-lambda/issues/230


code-insiders.sh prompts me for WSL although I do want to start the Linux version

###Setup

WSL 2
add support to run graphical apps in WSL2 (xlibs, ...)
install an xserver on Windows side
install code insiders in Linux
try to run code insiders
you get

To use VS Code with the Windows Subsystem for Linux, please install VS Code in Windows and uninstall the Linux version in WSL. You can then use the 'Visual Studio Code - Insiders' command in a WSL terminal just as you would in a normal command prompt.
Do you want to continue anyways ? [y/N] y

I would like to have the ability to start the Linux version as well. Couple of ideas to achieve that:

check the origin of code-insider.sh. If on a Windows drive the start the WSL version. If on a Linux share then start the Linux version
check if the environment has a DISPLAY variable set and if so start the Linux version directly.

@joaomoreno FYI.

I would like to have the ability to start the Linux version as well.

The question is, how often do you run on the WSL side. Is it just for testing?
I would think running on the Windows side still has more advantages and we want to promote that, no?

Agree, but IMO we can detect what to do. If the code.sh comes from a windows drive (e.g. /mnt/c/Users/xxxx/AppData/Local/Programs/Microsoft VS Code Insiders/bin/code-insiders) then it is clear to start the Windows application. If code.sh comes from the Linux part and a DISPLAY variable is set then I think you want to start the Linux version.

When you see the error message, it's already clear that you called code.sh from a VSCode linux install (only that code.sh has the WSL check with the error message).
And even when we see the DISPLAY variable, we still want to inform the user that installing VSCode in WSL is not the best choice. IMO we should show the message at least once.
Did I miss a good use case why someone would install a Linux VSCode in WSL? If it is a problem with running integration tests, we could also add an additional command line parameter, or a env variable that we test for.

It is not about running tests. That I have under control now :-). It is to verify things under Linux. You remember the extension I gave you for testing. To make sure it is working in pure Linux I install Linux into WSL as well.

I would be happy to have a switch --forcePlatfrom or something. The I would add a alias to my bashrc.

There's already an env variable that you can set to avoid the warning:
DONT_PROMPT_WSL_INSTALL=1 code-insiders should do the trick.
I'll add a message to the script to tell you that.


Add UI options for setting the export batch sizes

See discussion in PR #126

Implemeted with PR #137. Kudos to @yaozhihang


How to chamfer extruded text

How to chamfer an extruded text? I want to chamfer all edges of the top-face. This works fine for a simple box, but not for text.
from build123d import *
from ocp_vscode import *

set_port(3939)

b   = Pos(0,30,0)*Box(10,10,10)
c1  = Pos(0,15,0)*chamfer(b.edges().group_by(Axis.Z)[-1],1)

t2d = Text("ABCD",font_size=50,font_style=FontStyle.BOLD)
t3d = extrude(t2d,10)

c2  = Pos(0,-30,0)*chamfer(t3d.edges().group_by(Axis.Z)[-1],1)  # trouble

show_all()

The line marked with "trouble" generates various errors (see below):

Your code works for me (on Ubuntu 23.04) which almost certainly narrows the problem down to the font you are using. Text is notoriously difficult to work with as what looks look often doesn't work in a CAD system - short or intersecting edges are often the problem. Hopefully by selecting another font (i.e. set the font= parameter) you'll find one you're happy with.

We use different platforms, I have run he code on Windows 11 Home (see below):

It could findout which fonts are installed, most of them are not so pleasant for my purpose. If possible, I want to keep the default-font ("ARIAL"). During my further investigations, I have replaced chamfer() by filet(),
from build123d import *
from ocp_vscode import *

set_port(3939)
show_clear()

b   = Pos(0,30,0)*Box(10,10,10)
c1  = Pos(0,15,0)*chamfer(b.edges().group_by(Axis.Z)[-1],1)

t2d = Text("ABCD",font="Arial",font_size=24,font_style=FontStyle.BOLD)
t3d = extrude(t2d,2)

#c2  = Pos(0,-30,0)*chamfer(t3d.edges().group_by(Axis.Z)[-1],1)  # bad
c3  = Pos(0,-25,0)*fillet(t3d.edges().group_by(Axis.Z)[-1],1)          # good

show_all()

and the code runs fine! I can live with this alternative (rounded edges).

Due to this experiment, I would conclude that the root-cause is not font related, but somewhere hidden inside the chamfer()-routine.


Code reviews wanted

Hi Adam, I am really liking Nicholas. The repo says there are RSS and JSON feeds.
I looked and in footer.php there is code to create the link
<a href="<?= $config['base_url'] ?>/rss/">RSS
But I do not see how the content of the RSS and JSON feeds are created.
I do not see anything in home.php calling anything to generate the feeds.


feat(AudioPlayer): Add AudioPlayer component (#993)

Closes #993
Description

Add a brief description

Creation of the AudioPlayer component. It can take custom icons, titles, can show the duration and the current time stamp, can be used with a slider to move the timeline, can change background color and border color and can be muted with a mute button.
Current behavior (updates)

Please describe the current behavior that you are modifying

New behavior

Please describe the behavior or changes this PR adds

Is this a breaking change (Yes/No):

Additional Information

Given that I cannot use Yamada-UI components such as Button and Slider, I do not think it is worth to continue this PR. The entire feature revolved around using components from the same project. Thank you.


Feed generated with --dummy flag does not validate

I just ran feedvalidator.py from Google's transitfeed project on the generated zipfile and it displays 24821 errors and 17117 warnings!
Here are the commands:
$ osmtogtfs resources/osm/bremen-latest.osm.pbf  --dummy --zipfile o.zip
$ python2.7 feedvalidator.py o.zip

@carocad here is the output. Most of the errors are about missing values, e.g. agency_url.
validation-results.zip

@mehdisadeghi nice thing to have this tool already there
It is very helpful !
A quick manual check on the bremen results shows that they are right. We are using the same trip id for week and weekend so I guess that is wrong. Although I cannot think of a good way to solve that right now since we use the same underlying relation id for that 😞

@carocad I fixed some of those errors, see #27 please. This is an updated validation check:
validation-results.zip

Done in #39


🐛 Fix "log.SetLogger(...) was never called" in wrok-webhook

Summary
Related issue(s)
Fixes #490

/approve

/lgtm


Somber news

Guys,
I am sending you this message with a heavy heart. My ex-colleague and team member and contributor to this and many other open source repos - Adi Reddy Mora has sadly passed away yesterday. This came very suddenly.  He left behind his wife and two young children.
https://www.facebook.com/TDFUKEU/posts/1728641237229242
Gary

It is so sad that he gave what little time he had to help everyone.  I am sorry for your loss Gary, and I hope his wife and kids keep strong.

@GoodBoyDigital & @bigtimebuddy would be nice to add @notboring to this official repository since he made a fork up to date! https://github.com/notboring/pixi-haxe

@GoodBoyDigital & @bigtimebuddy please can you chime in here.

I have added @notboring as a maintainer to this repo.

Hey all, apologies for not jumping on this sooner. I get so many github pixi emails, sometimes they slip through my net. Thanks for adding him as a maintainer @bigtimebuddy. He was a super friendly dude, always very helpful on the the repo. He is missed.

Thank you for the invite. I'll be submitting my changes into the official reposity asap. Might take a few days though, since I am chasing deadlines at the moment.

@notboring That's wonderful news! Question, do you by accident have pixi.js 5 externs?
I did some changes in my fork too, feel free to pick some from there if you want https://github.com/markknol/pixi-haxe/commits/dev

I commited the changes from my fork to the dev branch and made a pixijs 5 issue.
Sorry for the long delay, I had to get my projects straight after a forced multi week break. Things are mostly on track now, so I should be able to look at pixi 5 and haxe 4 issues next week.
@markknol The commits from your fork have always been part of my fork, so they are part of dev branch now. Thanks.


Bart add custom title to secondary nav

It adds option to add custom title (html_safe) to be displayed instead of selected item. We'd like use it in Community to save some precious space.
It's backwards compatible, won't blow anything anywhere up (I hope so :trolleybus:).
Before:

After:

Seems legit.


New Locus View plot (long-term solution)

A long-term solution to the dense regions issue in the Locus View plot

@ElaineMcA to schedule meeting w/c 07Jan to discuss technical options and approach w/ @iandunham @peatroot @mkarmona @edm1 and @andrewhercules.

Pending refresh of data for V2.0 release to resolve "too dense regions" issue.
Plot work should be based upon clear use cases provided by Genetics team.


move font above css include

I noticed fonts are included just after the css, I think it's better to include it before to avoid FOUC.

Excellent point, sorry for missing this PR!


fixed alignment issue of Avatar initials

Description
fixed alignment issue of Avatar initials

Issue Ticket Number
Fixes #407

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes needed to the documentation

Output

Congrats @kheersagar 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


Remove unused test data

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @aaltay PTAL

LGTM

I'll let altay proceed with merge hto.


Help installing RenderDoc on Ubuntu 18.04 LTS

Description
Hi there. I'm new to github and I've never compiled anything from source before.  I checked my dependencies were up to date, so there should be no issues there.
Steps to reproduce
I downloaded the renderdoc_1.7.tar.gz tarball but I get lost at the next step:
cmake -DCMAKE_BUILD_TYPE=Debug -Bbuild -H.
make -C build
First, where should I put the tarball for installation?
Second, do I have to extract it first, or do those compilation commands work on a zipped tar?
Environment

RenderDoc version: 1.7
Operating System: 18.04 LTS
Graphics API: OpenGL, version unknown

Any help for a struggling newbie would be greatly appreciated! My ultimate goal is to compile a Blender add-on from source which uses data extracted from RenderDoc to build 3D models. It's open source but it's only available for Windows, so I thought I'd give it a go, but the first step is to get RenderDoc working!
Cheers.

I know which blender add-on you're talking about, and I will not provide any support related to it at all. RenderDoc is only intended for capturing and debugging your own programs. Illegally extracting copyrighted assets using RenderDoc is absolutely not endorsed or supported.

Hello, well I must have missed something there then. The video didn't give me the impression there was anything illegal about it; it looked legit to me. Sorry for any misunderstanding and all the best with your project.


themeBuilder being called multiple times?

I noticed (via tracing) that my MaterialApp is being rebuild every so often .. the culprit appears to be themeWidgetBuilder -- here is the code:
  @override
  Widget build(BuildContext context) {
    print('[Main - build()');
    return DynamicTheme(
      defaultBrightness:
          globals.isDarkTheme ? Brightness.dark : Brightness.light,
      data: (Brightness brightness) => buildTheme(brightness),
      themedWidgetBuilder: (BuildContext context, ThemeData theme) {
        print('[Main - build() - DynamicTheme()] - fired!');
        return MaterialApp(
          title: 'Welcome to Metro eSports League!',
          theme: theme,
          initialRoute: '/',
          onGenerateRoute: globals.router.generator,
          navigatorKey: globals.navigatorKey,
        );
      },
    );
  }

and here is some trace data showing it being called and the whole tree being rebuilt..
Performing hot restart...
Restarted application in 1,382ms.
flutter: [auth - authenticatedUser()] - currentUser is MjK3eS4ryffMfxBQ5XBn6WdBT2o2
flutter: [Main - build()
flutter: [Theme - _buildDarkTheme()
flutter: [Theme - _buildDarkTheme()
flutter: [Main - build() - DynamicTheme()] - fired!
flutter: [RootPage - initState()]
flutter: [RootPage - initState()] - authStatus is AuthStatus.signedIn
flutter: [RootPage - build()
flutter: [Loading - initState()
flutter: [Loading - build()] - userStatus is UserStatus.loading
flutter: [Theme - _buildDarkTheme()
flutter: [Main - build() - DynamicTheme()] - fired!
flutter: [RootPage - build()
flutter: [Loading - build()] - userStatus is UserStatus.loading
flutter: [Loading - build()] - userStatus is UserStatus.returningUser

Any ideas on this?

Hey - sorry for the late response, was a pretty busy month for me.
I just tried it with the example in this repository and it seems to work as intended for me. Every time the theme or the brightness is changed it rebuilds exactly once.
Are you still facing this issue or were you able to resolve it?

You know -- I haven't looked at this issue in a while -- let me check it out again and see what the behavior is like now ..

I'm having this issue too


Add cache adapters for Dalli, Rails, and Redis.

Re: #545 - rather than asking users to copy-paste the glue from the README, this provides the cache adapters for using Dalli, Rails.cache, and Redis, which should cover most cases I think? @i0rek what do you think?

@isaacseymour this looks great! Looking at the code and the structure I was wondering if it would be worth it to put the caches into their own module and folder. Like Typhoeus::Cache::Dalli would live in lib/typhoeus/cache/dalli.rb. What do you think about that?

I couldn't decide, but looking at it again I'd agree it should go into a
separate module. Will update in the morning. Thanks for the speedy
response! :)
On Mon, 7 Nov 2016, 20:41 Hans Hasselberg<EMAIL_ADDRESS>wrote:

@isaacseymour https://github.com/isaacseymour this looks great! Looking
at the code and the structure I was wondering if it would be worth it to
put the caches into their own module and folder. Like
Typhoeus::Cache::Dalli would live in lib/typhoeus/cache/dalli.rb. What do
you think about that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/typhoeus/typhoeus/pull/546#issuecomment-258956185,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABv8QSQ1gyZSJ0DXX6g5L6oAQ0oD4vPkks5q740NgaJpZM4KrgNN
.

@i0rek Updated. CI is failing because:

Dalli doesn't support Ruby < 1.9 (which is very discontinued, so maybe support can be removed from Typhoeus?)
Rubinius seems to not be working on Travis at all

So not really sure what to do about those.

@isaacseymour thank you! I would like to maintain ruby 1.8 compat as long as it is not a big deal. In this case I don't think the reasons are compelling enough. Can we not load the dalli adapter in ruby 1.8? Rbx tests don't work atm :(

What's the reasoning for keeping 1.8 support? It was EOLed over 2 years ago now (by which point it was <2% market share)! I'm happy to conditionally load the Dalli adapter only on 1.9+, but seems kinda crazy to keep supporting such an old Ruby version.

I don't want to screw ppl who are still using ruby 1.8. There are also very few things that cause problems with these old versions. Basically, this is just me trying to be nice :).

I'd argue it's not nice to allow people to use software that's not received security patches in several years, but can see the other argument. I'll make the Dalli-tests skip on Ruby 1.8 this evening.

Alright, had to disable installing Faraday on 1.8 too (they've dropped support for <1.9), but all the tests except rbx-2 are passing 💪

Thank you very much!

Yes, great job @isaacseymour !