Shaders do not work with Control and his children

Godot version: v3.2.4.rc2.official
OS/device including version: Linux 5.10.13-2-MANJARO
Issue description: Shader does not work for the source node and his childrens being attached to Control.
Steps to reproduce:

Create new scene witn Control root node;
Add some childs like Texture, NinePatch, ColorRect, etc.;
Add ShaderMaterial for root Control node;
Create simple fade shader with gradient;

Minimal reproduction project: debug.zip

Just tested with v3.2.4.rc2.official, this is not an issue. If you go to child material settings you can select the Use Parent Material.
I think it makes sense that themes get inherited by default, but for materials you have to manually select for material to get inherited.

@menip Should we amend the documentation to clarify this? If so, which page/class reference should we modify?

Just tested with v3.2.4.rc2.official, this is not an issue. If you go to child material settings you can select the Use Parent Material.

This remains a problem in more complex node systems where, for example, I want to adjust the transparency of the ScrollContainer to smoothly display/hide its child subcenes. In this case, "Use the parent material" works exactly one nesting level away from it and only for ColorRect/TextureRect: debug.zip

@toby3d in your child scene, you enabled for Child to use parent material, but did not enable Background to use parent material. If you enable, then it works.
@toby3d I would suggest you ask in Godot discord Help/UI channel about your specific implementation problem.
After this test I conclude the issue posted in the original post does not exist in Godot.

Should we amend the documentation to clarify this? If so, which page/class reference should we modify?

@Calinou The canvas item class reference lists talks about the use_parent_material property. I couldn't find any other places where it would make sense to talk about this. There is the GUI Skinning tutorial that talks about Themes, but doesn't mention CanvasItem shaders, so I think it's a weird place to put this info. The CanvasItem shader page talks only about shaders, not CanvasItem materials, so also doesn't go there.
My conclusion is there is not an existing page to which we should ask this. My personal opinion is that the CanvasItem class reference provides enough information. Perhaps we can ask Nathan if this information should be included in some tutorial.

in your child scene, you enabled for Child to use parent material, but did not enable Background to use parent material. If you enable, then it works.

First of all: it's not intuitive. In order to guarantee that it works, I have to include the use of the parent material ALL nodes that could potentially be children of the parent with the shader?
First of all: it's not intuitive. In order to guarantee that it works, I have to include the use of the parent material ALL nodes that could potentially be children of the parent with the shader?
Second: as I wrote above - this only works with textures and ColorRect. If I add Label or other Control-nodes to the child scene, no setting will allow it to "hide" through the shader.
I always thought that the shader automatically treated everything in the parent as one layer/frame, which the shader distorts based on its parameters, as if it were applied to a TextureRect or ColorRect.

Checking from 2024. I'm running into this same problem in 4.3dev2. Could someone please point me in the direction of the most-accepted workaround?

@gregkrsak Please review https://docs.godotengine.org/en/stable/classes/class_canvasgroup.html


Trying again in 2.00 seconds...
`

Just need some modifications for your code.
Take the Factory Example in README
# extensions.py
from flask_celery import Celery

celery = Celery()

# application.py
from flask import Flask
from extensions import celery

def create_app():
    app = Flask(__name__)
    app.config['CELERY_IMPORTS'] = ('tasks.add_together', )
    app.config['CELERY_BROKER_URL'] = 'redis://localhost'
    app.config['CELERY_RESULT_BACKEND'] = 'redis://localhost'
    celery.init_app(app)

    # Make configured Celery instance attach to Flask
    app.celery = celery

    return app

# tasks.py
from extensions import celery

@celery.task()
def add_together(a, b):
    return a + b

# manage.py
from application import create_app

app = create_app()

# Use `celery -A manage.celery worker` to start celery worker
celery = app.celery

app.run()

This works for me.


Ability to run only particular regexes rule(s)

Might be overlooking but cannot find a way to run gitleaks with selected regexes rules.
The first use case is tuning our custom rules, testing on a smaller amount of data, ensuring that a particular rule works as needed:
# gitleaks.toml

title = "gitleaks config"

[[regexes]]
description = "rule-1"
regex = '''....'''

# adding your own
[[regexes]]
description = "rule-2"
regex = '''....''

It would be nice if we could do this in order to simplify rule tuning
gitleaks --rule rule-1 my-test-repo
expect 5 positives against test repo, assess with Pester/ServerSpec, etc

gitleaks --rule rule-2  my-test-repo
expect 16 positives against test repo, assess with Pester/ServerSpec, etc

The second use case is running a subset of the rules. For example, consider naming convention for all rules (or tags as in the other ticket). We have several subsets to address severe problems and get some insights on the source code (simply, hardcoded URLs, for example). Here is the config:
# gitleaks.toml

[[regexes]]
description = "mandatory.security.rule1"
regex = '''....'''

[[regexes]]
description = "mandatory.security.rule2"
regex = '''....'''

[[regexes]]
description = "optional.info.rule1"
regex = '''....'''

[[regexes]]
description = "optional.info.rule2"
regex = '''....'''

Now, we can say this:
# this must fail the build, mandatory checks
gitleaks --rule-ids "mandatory*" my-test-repo

# this kinda optional, info only
gitleaks --rule-ids "optional*" my-test-repo

Such an approach gives the ability to maintain and organize rules in a better way. Moreover, CLI becomes very powerful allowing pick and choose which rules to run and hence tune the behaviour needed. Just think about how we can organize and manage 50-150 rules in a better way.
Thoughts?

Hey @zricethezav, there was a great progress on tags and severity and even entropy in https://github.com/zricethezav/gitleaks/issues/193
Did you have plan to implement this feature? Executing a single rule would have been a great win.

I don't plan on adding this feature since it is possible to test rules using a custom config. This is a bit more work for the end user but has the benefit of not cluttering the cli


fix: convert emits to props

fixes vuejs/vue#13104, based on vuejs/language-tools#3351
Actually this is a vue 2.7 type issue: it doesn't convert emits to props. However vue 2.7 seemed to be unmaintained, I fix it in language-tools. Also improves JSX compactibility

I'm looking at the changes and I don't quite see how it's related to #3351. Maybe it does handle the "emits" case but I don't see how it would handle class, style, etc.

Thanks for investigating this, but I think we should avoid bypassing the problem in language tools, otherwise vue repo will never fix it.

Thanks, I'll rewrite this PR to contain some vue2-related test changes.


cant open variable data

Description
What steps will reproduce the problem?

Every time I open the data in the variable explorer, it notices me that spyder has encountered an internal problem. I checked the details, and there are two errors:
if not editor.setup_and_check(value, title=key, readonly=readonly):

File "/home/dj/software/anaconda3/lib/python3.7/site-packages/spyder/widgets/variableexplorer/arrayeditor.py", line 620, in setup_and_check
self.data.flags.writeable = True
ValueError: cannot set WRITEABLE flag to True of this array
How to solve the problem?
Traceback
  File "/home/dj/software/anaconda3/lib/python3.7/site-packages/spyder/widgets/variableexplorer/collectionseditor.py", line 482, in createEditor
    if not editor.setup_and_check(value, title=key, readonly=readonly):
  File "/home/dj/software/anaconda3/lib/python3.7/site-packages/spyder/widgets/variableexplorer/arrayeditor.py", line 620, in setup_and_check
    self.data.flags.writeable = True
ValueError: cannot set WRITEABLE flag to True of this array
WARNING:spyder.widgets.github.backend:Failed to send bug report on Github. response={'code': 401, 'json': {'message': 'Bad credentials', 'documentation_url': 'https://developer.github.com/v3'}}

Versions

Spyder version: 3.3.2
Python version: 3.7.1
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Linux 4.15.0-48-generic

Dependencies
pyflakes >=0.6.0  :  2.0.0 (OK)
pycodestyle >=2.3 :  2.4.0 (OK)
pygments >=2.0    :  2.3.1 (OK)
sphinx >=0.6.6    :  1.8.2 (OK)
rope >=0.9.4      :  0.11.0 (OK)
jedi >=0.9.0      :  0.13.2 (OK)
psutil >=0.3      :  5.4.8 (OK)
nbconvert >=4.0   :  5.4.0 (OK)
pandas >=0.13.1   :  0.23.4 (OK)
numpy >=1.7       :  1.16.3 (OK)
sympy >=0.7.3     :  1.3 (OK)
cython >=0.21     :  0.29.2 (OK)
qtconsole >=4.2.0 :  4.4.3 (OK)
IPython >=4.0     :  7.2.0 (OK)
matplotlib >=2.0.0:  3.0.2 (OK)
pylint >=0.25     :  2.2.2 (OK)

This is fixed in our latest version. Please update by opening a terminal and running there
conda install spyder=3.3.4


Question on layout.

Importing a certain file type and creating the nodes + their connections programatically. Is there a way to auto-layout them so they aren't on top of each other upon creation based off connections?

Word. I'll look into figuring it out. This would be a huge feature especially since I'm creating import/export functions. Export doesn't matter, but import I need the nodes to be placed neatly. :/

Implemented in v3.1.0. See here for more info.

Props dude, that "LayoutAsync" demo looks like pure WitchCraft :)


Feature request: Team drives support

Google introduced Team Drives to Google Drive. However, we are unable to use Drive Music Player with files inside Team Drives. Apps must be updated in order to support these drives.
I believe these are some of the changes that have to be made in order to support Team Drives:
https://developers.google.com/drive/v3/web/enable-teamdrives
We hope these changes are possible :)
Kinds regards,
Happy Drive Music Player users

Hi!
Same here! Team Drive support would be very very welcome!

I'd like to add my "plus one" to this request. I just uploaded 100 Gigs of audio to a team drive, only to discover I couldn't play them.

I forked the project and in my version, I added Team Drive support. I also migrated the Google Drive API from 'v2' to 'v3'.
The "playlist" function is disabled, because realtime API is deprecated.  I'm not a professional developer, so the best I could come up with is to create a bookmark from the url with the file ID's in it...
You can try my version here:
https://musicplayer.sgfv.be/
The github project is here:
https://github.com/jaspercuvelier/drive-music-player
If you see serious errors/security problems, please give me a heads up.


Conflict when running DSE CCM nodes on machine with DSE installed

I'm trying to run a single DSE CCM node (v 4.8.8) on a virtual machine. This VM also has package install of DSE 4.8.8. Since the package install of DSE starts up as the VM starts, I make sure it's shut down:
service dse stop

I create the DSE CCM cluster in such a way:
ccm create test --dse --dse-username=x --dse-password=x -v 4.8.8 -n 1

And start up CCM:
 ccm start --verbose

I then get the following error:
Found multiple DSE core jar files in /root/.ccm/repository/4.8.8/lib /root/.ccm/repository/4.8.8/resources/dse/lib /usr/share/dse /usr/share/dse/common . Please make sure there is only one.

@mike-tr-adamson Is this something we're able to support?

@ptnapoleon I'll take a look and let you know. We ought to be able to run if the installed DSE on the VM isn't running.

@beccam I am slightly wary of pushing a fix for this without a lot more investigation but I do have a workaround in the mean time:
export DSE_LIB "/root/.ccm/repository/4.8.8/lib /root/.ccm/repository/4.8.8/resources/dse/lib"
ccm start

This specifically sets the DSE_LIB and stops the launch script for looking from alternative locations.

@mike-tr-adamson Looks like we are getting close, but when I try to run 2 nodes, I'm getting this error:
Traceback (most recent call last):
  File "/usr/local/bin/ccm", line 86, in <module>
    cmd.run()
  File "/usr/local/lib/python2.7/dist-packages/ccmlib/cmds/node_cmds.py", line 267, in run
    stdout, stderr = self.node.nodetool(" ".join(self.args[1:]))
  File "/usr/local/lib/python2.7/dist-packages/ccmlib/dse_node.py", line 264, in nodetool
    raise NodetoolError(" ".join(args), exit_status, stdout, stderr)
ccmlib.node.NodetoolError: Nodetool command '/root/.ccm/repository/4.8.8/bin/nodetool -h localhost -p 7100 status' failed; exit status: 1; stdout: Location pointed by DSERC_ENV not readable:


Support for Mamba (SSM)

Feature request
Allow inference (even if only in bf16) for Mamba architecture models.
Motivation
Mamba architecture effectively allows for attention to be compressed into a state, allowing a per token time that is constant with context length.
Seems all of the benefits of attention are built into the trainable linear selection done within the state, so probably these models take over transformers?
Your contribution
I'm not sure how complex it would be to integrate. Inference works well with transformers, but I know TGI isn't built on transformers.

Hi @RonanKMcGovern there is current a work in progress in this PR https://github.com/huggingface/text-generation-inference/pull/1480
The model still has a couple of issues to be resolved but should be included in the near future.
Going to close this issue for now, but please free to follow up on the PR 🙂


Note Manager Init/Run Ready State

in noteManager_Ready_State.cpp update the init() and Run() methods
In init()
Set control data of all motors:
Elevator: Set to positionInch
launcherTop: velocityRPS
launcherBottom: velocityRPS
launcherAngle: positionDeg
Everything else set to percentOutput
Set all motors to brake mode
In Run()
N/A
Look at/copy implementation from noteManager_backupManualLaunch_State.cpp/Example below
m_mechanism->Elevator->SetControlConstants(0, *m_mechanism->percentOutput);
To set brake mode Example:
m_mechanism->Transfer->EnableBrakeMode(true);

Don't need to set control data in the init function


Formatting code

Since I can include something like zprint inside Conjure it'll mean we can run code through that within Conjure's JVM to format it. How neat! Not sure if I'll definitely use zprint yet but it's a good candidate.

Not going to do this just yet, will close. Not a primary concern and there's other better CLI tools floating about. I don't want to commit to a tool before the community decides. There's ongoing work to decide what standard people should use and how it should be enforced.

Popping in here, to summarize a recent discussion on Slack.
Option A: call cljfmt directly from vim
One quick way to format code right now, is by using cljfmt like so
 * in vimrc nmap <leader>f :!clj -M:cljfmt %<CR>
 * in deps.edn {:aliases {:cljfmt {:extra-deps {cljfmt/cljfmt {:mvn/version "0.7.0"}} :main-opts ["-m" "cljfmt.main" "fix"]}}}

Option B: Use clojure-lsp
If you use coc + clojure-lsp, you can get code-formatting out of the box. See this guide for adding it: https://clojure-lsp.github.io/clojure-lsp/clients/#vim
Option C: Add support for code-formatting in Conjure
CIDER already uses nREPL. From Olical:
"""
I want to add support for the newer nREPL 0.8 operations + refactor/debug/format tools in CIDER (when they're present) but time. If anyone wants to have a go at contributing these things (wouldn't be too hard for some of them!) I'd be happy to review / guide / carry PRs across the line
There's a LOT of untapped power in CIDER right now, low hanging fruit in some cases. Although things like a stepping debugger (anything stateful) will require some UI / UX work that I'll try to handle since I have a bigger view of the system.
Formatting should be a case of

extract form under cursor
send off to CIDER
replace form range with result

All of which have prior art in Conjure and Fennel modules / functions dedicated to performing this extraction / replacement in a buffer. It's how e! works after all.
I actually format data sometimes by just running e! on it since the source data gets replaced by a pretty printed version
My personal motivation for formatting is quite low since I've never relied on one for Clojure in years of professional development with it. No single formatting tool ever sat with me as "perfect", but I know for some teams it's a great thing to have as common ground. Not opposed to the idea, just not super driven to solve it right now, personally. Just some context :slightly_smiling_face:
"""

Hey there! Great work, folks!
Is this something we still want for the project?

Hey! Yep, I would argue that this could be reopened or a new issue created to call out to newer nREPL ops that format code nicely. I wouldn't want to shell out to cljfmt or clojure-lsp though, only nREPL+CIDER since I want to keep Conjure focussed on that.
Personally though, I'd still recommend people get LSP set up and rely on that, it's really good for this sort of thing. Conjure is for talking to your running programs, getting stuff like formatting is a non-essential nice to have since there's other ways to do it in my opinion. So it's optional if it's easy to do it well from Conjure, but I don't want Conjure to be a "all in one" Clojure tool, it's just one part of your toolset, static analysis with LSP is another one etc.
So, if we think nREPL has a great hook for this these days, a new issue to implement that op could be good.


Move Azure IPAM out of beta

test-docs

I'm marking this as ready-to-merge without full CI tests as the PR is only touching documentation


The first card in the search results is not aligned with the top of the rest of the cards

Describe the bug
The top card is always slightly higher than the subsequent cards on the first row.
Environment

AEM Version: All
Asset Share Commons Version: 3.5.4+
Author, Publish or both? both

Fixed in 3.8.10


[BUG] The new IPerfEvent is using Date.now() which is not supported in an ES3 environment

Date.now() is only supported from IE9 -> so we need to provide a polyfill helper
additionally, performance.now() is also only available from IE 10-> so this also needs a polyfill helper.
Will

add helper functions
add additional checks in the es3 checking tool

v2.5.8 is now fully deployed


common crate for wasm shims

#1366  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Output as *.mid file parameters for a generations of a chorale of length 100

Hi,
I tried the following command after installing all the dependencies and the DeepBach code:
python3 deepBach.py -l 100 -o deepBach.mid
Here is the error I get:
Traceback (most recent call last):
  File "deepBach.py", line 847, in <module>
    main()
  File "deepBach.py", line 775, in main
    voice_ids=[0, 1, 2, 3])
  File "/Users/shyamalsuhanachandra/DeepBach/data_utils.py", line 582, in initialization
    metadatas=metadatas)
  File "/Users/shyamalsuhanachandra/DeepBach/data_utils.py", line 247, in make_dataset
    pickle.dump(dataset, open(dataset_name, 'wb'), pickle.HIGHEST_PROTOCOL)
FileNotFoundError: [Errno 2] No such file or directory: 'datasets/raw_dataset/bach_dataset.pickle'
I see the following code inside deepBach.py:

It seems that the dataset/raw_dataset/back_dataset.pickle is missing.  Will you be providing that file in the future?  If there is no file, it uses the constant BACH_DATASET instead and fails.
    if output_file:
        mf = midi.translate.music21ObjectToMidiFile(score)
        mf.open(output_file, 'wb')
        mf.write()
        mf.close()
        print("File " + output_file + " written")

I checked out the indexed_chorale_to_score function from data_utils library before this snippet of code above.  The code for that function is the following:
def indexed_chorale_to_score(seq, pickled_dataset):
    _, _, _, index2notes, note2indexes, _ = pickle.load(open(pickled_dataset, 'rb'))
    num_pitches = list(map(len, index2notes))
    slur_indexes = list(map(lambda d: d[SLUR_SYMBOL], note2indexes))

    score = stream.Score()
    for voice_index, v in enumerate(seq):
        part = stream.Part(id='part' + str(voice_index))
        dur = 0
        f = note.Rest()
        for k, n in enumerate(v):
            # if it is a played note
            if not n == slur_indexes[voice_index]:
                # add previous note
                if dur > 0:
                    f.duration = duration.Duration(dur / SUBDIVISION)
                    part.append(f)

                dur = 1
                f = standard_note(index2notes[voice_index][n])
            else:
                dur += 1
        # add last note
        f.duration = duration.Duration(dur / SUBDIVISION)
        part.append(f)
        score.insert(part)
    return score

There is also a function that converts the score into midi that uses the output of the previous function for the score variable on line 55 of deepBach.py.  Do I need to make any mods?
def music21ObjectToMidiFile(music21Object):
    '''
    Either calls streamToMidiFile on the music21Object or
    puts a copy of that object into a Stream (so as
    not to change activeSites, etc.) and calls streamToMidiFile on
    that object.
    '''
    classes = music21Object.classes
    if 'Stream' in classes:
        return streamToMidiFile(music21Object)
    else:
        m21ObjectCopy = copy.deepcopy(music21Object)
        s = stream.Stream()
        s.insert(0, m21ObjectCopy)
        return streamToMidiFile(s)

What should I do?  Can you provide the pretrained dataset or a dataset of MIDIs?

Default dataset is the Bach Chorales dataset obtained from music21 by corpus.getBachChorales function.
For the moment, create the 'datasets/raw_dataset' folders in DeepBach folder. Calling the program should preprocess, pickle and save the Bach Chorales dataset at location BACH_DATASET
Pickled datasets as well as pretrained models will be available soon

I couldn't find the Bach Chorales dataset from music21.  Do you have the links?

Please see function music21.corpus.getBachChorales(fileExtensions='xml')
http://web.mit.edu/music21/doc/moduleReference/moduleCorpus.html

Note that the pre-trained model and pre-processed dataset is already available for download:
See the README. Get it from Dropbox manually or have it downloaded/extracted by a script:
./download_pretrained_data.sh

Since pre-processing all the chorales from music21 takes about an hour this might be good for a quick start.


Question: Is it possible to preview .pdf or .docs files?

Hi danialfarid, thanks a lot for this awesome bundle.
I got a simple question:
after reading the doc and playing with the code, I wasn't able to preview a .pdf file (ie: the first page). Do you think it would be possible to do this easily - or does it require another bundle?

Not yet but I will consider adding the feature to the next version.

That would be so nice!
Thank you so much for the fast answer.

The file that ng-model is bound to is a File object, which is a subclass of Blob. This means you can construct an URL for it with URL.createObjectUrl(). You can then set the src of an iframe to that URL and if the Browser supports PDF previews it will show a preview in that iframe.

You can use 'Upload.dataUrl(file).then(function(url) {...})` to get the data url of the file.

I was able to use ngf-src="uploadFile" in an iframe for a preview with the uploadFile being a .pdf file in scope

Question, It seems that the plugin can't even detect PDF or any non-image file type?
This is the jsfiddle I'm looking at: http://jsfiddle.net/danialfarid/0mz6ff9o/135/

Is there some setting I'm missing?

^ Ah nevermind! Just changed this accept="images/*" to accept="/*"

I am unable to load pdf in IE but it works in chrome.
@BenMGilman Did it work in IE as well.


Updated doc - added missing PoC

Description
Updated doc - added missing PoC
Type of change

Documentation update

Testing steps
N/A
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch and project coverage have no change.

Comparison is base (b21ed09) 4.90% compared to head (074e874) 4.90%.

Additional details and impacted files
@@          Coverage Diff           @@
##           master    #390   +/-   ##
======================================
  Coverage    4.90%   4.90%
======================================
  Files          16      16
  Lines         999     999
======================================
  Hits           49      49
  Misses        950     950

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Can't escape the search box.

whatever i input, i can't get the focus away from the search box
when i press enter, tab, the arrow keys.. literally anything but valid letters it just gets printed like this:
<Enter>
How am i supposed to use this?

Ahh sorry this is largely unfinished. I'll have a stable version out sometime before 2021 but right now the search box isn't implemented. I'll also have clearer instructions on how to use it as is along with some other details in the README later today.

OK cool! can't wait.


How do you select a specific parent to use jcf on?

What do I do if I want to select a specific div or section element to use jcf on? Will I have to select all elements in my div/section or are there options for jcf.replaceAll( [context] ) or jcf.replace( elements [, moduleName] [, customOptions] ) to do so?
Edit: I found the answer. I read poorly:
This should work:
var myDiv = $('#div');
jcf.replaceAll( myDiv );
This should also work:
var myClasses = $('.myClass');
jcf.replaceAll( myClasses );
Correct me if I'm wrong.

@Puddingboy yes, that is correct :)


DATAJDBC-175 - Supports single types as return type for annotated methods

I've fixed a part of DATAJDBC-175.
Please review.
Thanks.

I will reconsider.


Provide .tool-versions with current go do elixir/erlang versions

Interested to see how people feel about this.
a) Not everyone uses asdf so not directly affected
b) if you know where to look (travis) you already have a place to
get an overview of supported versions. Should also be in the
README but is probably missing atm ;P
c) potentially high churn (ideally it'll be updated rather quickly
for every new elixr/erlang release)
So, does it provide value - yay or nay?

If we're going to support multiple versions of Elixir and Erlang, why would we want to make sure folks working on Benchee (and who use asdf) are using a certain version of Elixir and Erlang? I'm not opposed to this, but I genuinely just don't know what advantage we'd get from this.

@PragTob I do use asdf, so 👍
I think there's value anyway, because even if I used something else, at least I could see what versions of elixir and erlang I should have installed

@devonestes I agree it seems unlikely that a contributor would have incompatible versions installed, but for a new contributor, it still might provide some guidance

Guidance for new developers make sense. I hadn't thought of that. Fine by me, then!

Uh, what is a .tool-versions file?  And what is wrong with just the elixir version in mix.exs?

@OvermindDL1 It's a file used by asdf where you can specify versions of everything aka elixir, erlang, node, ruby, postgres etc... it automatically switches to that version.
Yeah I'm not super sure if it has big advantages (it shouldn't have any downsides though) for library development, as you don't want to/need to enforce same versions for all contributors

No too strong opinions from either side and if you don't use them you won't be affected so... merging this


Cursor.Delete followed by Next skips the next k/v pair

After fighting an inexplicable bug in a package that makes heavy use of bolt behind one of our own interfaces, I've finally nailed down the issue to what appears to be a bug with bolt's cursors, where the next k/v pair is always skipped when iterating over keys, and while each key is deleted during the iteration.  Based on my understanding of the bolt documentation, deleting items using the cursor is the only modification that can be performed to the database during cursor iteration without invalidating the cursor.
I added a test, which fails, to my current project that exposes the issue (sorry, it's late and I've been fighting this issue all day, and to top it all off GitHub has lost this issue twice now as I was writing it up, so I don't yet have an isolated test that doesn't consume any of our own code):
https://github.com/jrick/btcwallet/blob/95ae8a42a9b8b2d70a9ab2289f3f05511cf27bf3/wtxmgr/db_test.go#L80
=== RUN   TestBoltDBCursorDeletion
--- FAIL: TestBoltDBCursorDeletion (0.01s)
	db_test.go:137: Expected to iterate over and delete four k/v pairs, but iterated 2 time(s)
	db_test.go:142: bucket still has key 1812fefbbfe53afef21762bcb138d77e600416541e0235c2554435063f21292b00000001 value 000000000bebc2001e82000000000000000000000000
	db_test.go:142: bucket still has key 1812fefbbfe53afef21762bcb138d77e600416541e0235c2554435063f21292b00000003 value<PHONE_NUMBER>d784001e82000000000000000000000000

As you can see, it successfully removed the first and third keys (ending in 00000000 and 00000002, but left the two keys ending in 00000001 and 00000003).
We use glide to maintain our dependencies and currently have bolt locked to commit 583e8937c61f1af6513608ccc75c97b6abdf4ff9 (version 1.3.0).

After c.Delete() the cursor automatically moves to next item. after that c.Next() moves to further one item.
Changing to c.First() should fix your testcase.
c = b.Cursor()
		for k, _ := c.Seek(txHash[:]); bytes.HasPrefix(k, txHash[:]); k, _ = c.First() {
			err = c.Delete()
			if err != nil {
				return err
			}
			iterations++
}

Sorry but that API is borderline unusable if that is how it is intended to work.  We need to inspect the k/v to determine whether to delete it before moving onto the next item, and there is no way to access that next k/v after deleting item pointed to by the cursor.  Resetting the cursor back to the beginning only works when all items are being deleted.

Is this still the way the API works? I have a similar situation, where I am iterating on a cursor and conditionally deleting items. Do we need to account for the position of the cursor just after we delete, such as calling Prev() to allow the for-loop to advance as normal?

Be really hard to tell if the bug is in your iterator, or in BoltDB. I have this exact use case implemented, but I use Bucket.Delete() while the iterator walks. In this way, it doesn't change my iterators position as I conditionally walk the bucket and delete. I have tested and validated the pattern.

@chuckg the bug isn't in my iterator wrapper apis but in bolt itself.  The linked test is testing the bolt apis without using any of our projects db wrappers over it.
Modifying the bucket while it is being iterated over invalidates the cursor, except through Cursor.Delete (and Cursor.Delete is buggy), invalidates the cursor and you may receive unexpected results.

From the README, the only mention of deletes is Use the Bucket.Delete() function to delete a key from the bucket. I suspect that calling Bucket.Delete() spins up a new Cursor and as long as I don't try to walk back into the data I've just deleted, my current cursor remains valid.
The reason I said it might be your API is that I don't see you using basic bolt functions in your test:
ns := dbtx.ReadWriteBucket(wtxmgrNamespaceKey)
....
....
// Test the iterator iterates over each.
it := makeUnminedCreditIterator(ns, txHash)

Those don't seem like current Bolt primitives. In the interest of giving the Bolt authors some fodder to work with, can you refactor your test to only use the bolt API?

The function i linked directly to (TestBoltDBCursorDeletion) only calls bolt APIs on the bolt database.  It is using some of my project's functions for keys and values but that is unrelated.

This should probably help
for k, _ := c.Seek(txHash[:]); bytes.HasPrefix(k, txHash[:]); k, _ = c.Seek(txHash[:]) {
	err = c.Delete()
	if err != nil {
		return err
	}
	iterations++
}


feat: refacto github/gitlab clients

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 36.09023% with 255 lines in your changes missing coverage. Please review.

Project coverage is 50.25%. Comparing base (d1a7ba6) to head (9900f2e).

Files with missing lines
Patch %
Lines

internal/runner/repository.go
22.44%
72 Missing and 4 partials :warning:

internal/webhook/webhook.go
0.00%
46 Missing :warning:

...ontrollers/terraformpullrequest/github/provider.go
0.00%
43 Missing :warning:

...nal/controllers/terraformpullrequest/controller.go
48.27%
23 Missing and 7 partials :warning:

internal/server/server.go
0.00%
26 Missing :warning:

...ontrollers/terraformpullrequest/gitlab/provider.go
0.00%
13 Missing :warning:

internal/webhook/github/provider.go
50.00%
5 Missing and 4 partials :warning:

internal/webhook/gitlab/provider.go
50.00%
5 Missing and 4 partials :warning:

internal/testing/loading.go
77.77%
1 Missing and 1 partial :warning:

...nternal/controllers/terraformpullrequest/states.go
50.00%
0 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #413      +/-   ##
==========================================
- Coverage   50.99%   50.25%   -0.75%
==========================================
  Files          73       73
  Lines        4334     4599     +265
==========================================
+ Hits         2210     2311     +101
- Misses       1935     2085     +150
- Partials      189      203      +14

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


New Paldean Pokemon are missing their egg groups

current egg group info is returning an empty array.
Anything thats #906 and up.
For example, Sprigatito should return field and grass.

Which endpoint? Can you share an example? I see the egg groups returning.
Example: https://pokeapi.co/api/v2/pokemon-species/1000/

I just double checked but the link you sent me is returning null, if you put in lets say mewtwo for example. that will still give you an array with a string of "no-eggs" inside of it


adding of more frontend options like vue, angular, svelte etc  or api option

Tell us about your feature request
adding option for more frontend options may be in future
if api option is available then it will be easy to use other frontend guide me
Disclaimer

[X] I agree

Everything is possible :)

created a pr for svelte #343


Add files via upload

czech version of that image, I am going to use it in czech translation. If this is the way, how to add screenshots in my language I will upload more of them.

Hi, after a pulled this request, I found this page https://nick-tallguy.github.io/en/contribute/translator-images/#uploading-the-image and follow these instructions. So I pulled request on https://nick-tallguy.github.io with same picture. Should I continue with uploading new images there?

Hi,
no need to duplicate work. It basically does not matter where you issue pull requests. We prefer to receive issues and pull requests in this repository for the main LearnOSM site but pull requests to the staging site will find attention as well.

thank you for your answer, I will upload to staging site, because of testing on pages, if its ok.


Replace pylint + isort by ruff

Motivation

Our CI workflows take quite a while, mostly due to the tests, but also pylint is taking a considerable amount of time.
I think we could reduce this by migrating from pylint to ruff:

Proposed Solution

Replace pylint and isort by ruff
Check whether there's an automated tool which can migrate the pylint: disable= statements

Alternatives

Maybe it isn't worth the effort...
Additional Context

Pylint is not completely implemented by ruff yet (see https://github.com/astral-sh/ruff/issues/970), so we would loose a few rules (but also ruff has a lot of extra checks that pylint doesn't, mostly those of flake8)...

Not yet fully resolved. The following steps are still needed:

[ ] enable ruff format
[ ] enabled option to sort imports via extend-select = ["I"]

We also need to drop the pylint leftovers to close this ticket.


Add a clustering example with Docker Swarm

What does this PR do?
Add a clustering example in the user-guide documentation
Motivation
The first time I check what the cluster mode do, I can't find the information.
I think it's a really cool feature and adding more information about it, it is important.
More

[x] Added/updated documentation

Additional Notes
It's base on my blog post: https://jmaitrehenry.ca/2017/12/15/using-traefik-with-docker-swarm-and-consul-as-your-load-balancer/ but I change the format and rewrite a good part of it for the documentation.
In the beginning, I would like to improve the Clustering/HA user-guide, but, as this example use Docker Swarm and Consul with a specific docker-compose file for Docker Swarm, I think it's better to have a page just for it.
Fixes #1200, #736

@ldez Done!

Hello @nmandery, thanks for your feedback.
I have a question about using traefik 1.5-rc3. If this page will merge with the release of traefik-1.5 why not just use 1.5 in the documentation?
Else, we will need to update the documentation once the 1.5 version will be out.

@jmaitrehenry
Yes you're right, 1.5 is better than the full version name :+1:

I made the changes asked.
One of the change is:
-If you don't use Let's Encrypt with Traefik, you may not need Traefik cluster/HA.
-But, if you use Let's Encrypt, you need to store certificates somewhere shared by all the Traefik instances.
+If you want to use Let's Encrypt with Traefik, sharing configuration or TLS certificates, you need Traefik cluster/HA.

What do you think?

+If you want to use Let's Encrypt with Traefik, sharing configuration or TLS certificates, you need Traefik cluster/HA.

Can you add sharing configuration or TLS certificates betwwen many Træfik instances?

@nmandery done!

Why do we still this traefik_init ... We won't that, why it could not simply work with k/v store directly? Instead of start traefik with json file, and a traefik "init" that push json file into kv. It's so complicated. There is a way to simplify that ? Direct bind K/v to traefik without that init vodoo hack traefik init. Traefik could not init itself when booting with kv options enabled ?

I won't mind the hack provided it works in swarm mode.  To date I haven't gotten traefik working in HA mode in Swarm.


Add Remove Trailing Whitespace editor option

The editor settings now include an option to remove the trailing whitespace before an inserted newline. This option is disabled by default in order to prevent the sudden change of the editor's indent functionality.

In Action

The boxes signify lines where there was a leftover indent after a newline command. Once enabling remove trailing whitespace, new lines have their indents set to nothing. Lines with anything besides whitespace will not be effected. The newline will continue to have it's indent.
Note
This should be pretty easy to write a spec for if it is approved as a good change. This closes #7828.

Awesome! :tada:
What do you think about renaming the option? It might be a little confusing because there's already a "Remove Trailing Whitespace" option in the whitespace package, which does something slightly different.

And actually, now that I think about it, this enhancement seems like it belongs in the whitespace package, rather than core. What do you think?

So that is where it was. A developer did comment that there was a remove trailing whitespace option. I didn't see it in the editor settings so I was confused.
It could go in the whitespace package. I'll have to take a look at the whitespace package and see where a good place for it might be. Though this feature seems like it belongs with 'Auto Indent' since it is more like an 'Auto Remove Indent on Newline'.
As for a new name, how about 'Conservative Auto Indent' or 'Strip Whitespace on Blank Line'. The name needs work. Another option is to attach it to the 'Remove Trailing Whitespace' option that is already there.

@jeremyramin Thanks for this :+1:.
/cc @atom/feedback
I'd personally be ok with just always doing this, and not even having a setting, at least for now. If you really wanted to create a line w/ only whitespace, you'd have to type the whitespace and then move your cursor away without hitting 'enter'.
This only affects blank lines right, not all trailing whitespace? So if we do make an option, i'd suggest a name like Clear Blank Lines on Newline.

I'm :+1: for this change, but a setting might still be needed because some people seem to like trailing whitespace.
Also :+1: on moving it into atom/whitespace.

I agree with @maxbrunsfeld, that we should just always do this and let people's current whitespace settings handle the fallout. For example:

I want to remove the leading whitespace on blank lines

Set Remove Trailing Whitespace to true
Set Ignore Whitespace Only Lines to false

I want to leave leading whitespace on blank lines

Set Remove Trailing Whitespace to either true or false
Set Ignore Whitespace Only Lines to true

The only problem that this could cause is if there is a discrepancy in the whitespace standard between old code and new code, i.e. leaving trailing whitespace on lines where it already exists but I don't want to allow trailing whitespace on lines that are new or modified. But we already have this problem ... and I don't believe this change would make things any worse.

The only place I've seen anyone care about trailing whitespace is Markdown files.  And even then, it only matters when it follows printable chars.  So, having this patch always on sounds fine to me.
Maybe grammar files could repair the few places that actually need nonzero-length all-blank lines?

@bronson If you want to see examples of people who care very deeply about whitespace, check https://github.com/atom/whitespace/issues/10

@lee-dohm thanks for that link.  I totally agree with #10: Atom should never EVER make sweeping changes to my files.  That's just wrong.  The Atom team needs to reconsider their position.
However, fixing up the lines that I'm editing anyway?  That seems OK to me.

@maxbrunsfeld It checks to see if the user entered a newline, then it checks if the previous line has anything in it besides whitespace. If there is anything that doesn't match the whitespace regex class then the line isn't modified.

@lee-dohm I like that configuration setup, very intuitive. From a user's perspective though, I had no idea the whitespace package existed for adjusting the whitespace settings. If the next update stopped suddenly stopped leaving the whitespace since 'Ignore Blank Lines' is off by default, I think some people would be confused.
If anything, atom/whitespace#10 shows that many people rarely ever see the internal package settings like whitespace. If this feature will attach to the whitespace settings, it would probably be best to figure out a way to have these settings more apparent and visible.

it would probably be best to figure out a way to have these settings more apparent and visible.

Yeah, I strongly agree. There's an open issue for this: https://github.com/atom/settings-view/issues/284. We should probably prioritize this soon.

Is there anyway to just not add the whitespace? I ask it like this because of linter warnings about trailing whitespace would still show up while I'm typing if all this does is remove it after I hit enter.
What I'd prefer is that until I start typing non-whitespace the cursor moves but does not actually insert whitespace.

@mehcode No, there is currently no support for "virtual whitespace" in the Atom data model. There is/was an Issue for adding it, but I can't find it right now.

the cursor moves but does not actually insert whitespace

I think this would add a lot of complexity, both in the implementation and for the user and package author.
An alternative solution might be to pass the current cursor positions to the linter so that it can filter out warnings about whitespace on the lines where the cursors are.

Going to make an issue for this with those two things mentioned @lee-dohm and @maxbrunsfeld. One of the primary things that bugs me about having the linter on a change interval instead of on save.

Just to clarify, I should close this pull request and move the changes to the whitespace package?

Closing in favor of atom/whitespace#91.


Returned merged facilities in contributor searches

Overview
Facility matches in the MERGED status were not returned in filter by
contributor searches because the filter_by_query_params method only
allowed matches with a status of AUTOMATIC or CONFIRMED. Allows MERGED
facilities to be returned from the contributor search.
Connects #1366
Testing Instructions

On develop, run ./scripts/server and login as<EMAIL_ADDRESS>Merge VN202114667Y223 (belonging to Civil Society Organization A) into JO2021146CS21Q8 (belonging to Auditor A)
Search for the facility while filtering by Civil Society Organization A. The facility won't be found.
Checkout this branch, and Search for the facility while filtering by Civil Society Organization A. The facility will be found.

Checklist

[x] fixup! commits have been squashed
[x] CI passes after rebase
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Merging to expedite a release.


the model was not compiled

ipython agegender_demo.py
Using TensorFlow backend.
2019-02-03 18:48:51.822535: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
/usr/local/lib/python3.6/site-packages/keras/engine/saving.py:292: UserWarning: No training configuration found in save file: the model was *not* compiled. Compile it manually.
  warnings.warn('No training configuration found in save file:

I've exactly the same problem.

Use 1.0 version pretrained model can fix this problem.


Refactor Create Flow Tabs and Updating State

Purpose
Moved each tab content in the create flow (i.e all the stuff inside each of the tabs) to their own components. From those components, the appropriate selection panels are being rendered
Also refactored the function to update LinodesCreate state so that it requires that the key already exists in State so that it can be safely passed down to children.

Coverage decreased (-0.1%) to 25.756% when pulling ecd9d205d32c0c50117d6cd26f12f2e12865e63b on martinmckenna:M3-468-create-from-stackscript into 8ace06e4af405af1c5c1c537f7a810144ba83a11 on linode:develop.

"Clone from Existing" Linode selection doesn't work, either the state isn't being updated or selected isn't pointing at the right state.

made some more small changes and now is ready for real review. Looks like we have a bunch of types that are either out-of-date or just inaccurate (mostly just properties that can come back from the API as null), so that's definitely something to look out for in the future
@asauber @rjstires


blocked by CORS

Hi There,
I have implemented this and it works great in Unity, however when my game is compiled to WebGL and called it is giving me  'has been blocked by CORS policy' error in the browser console.
Any quick fixes for this?
Thanks
:)

Hi Dean,
Ah, I see. It looks like WebGL platform has some restrictions on web requests or there's another way to do this. I've tested this code on iOS, macOS, Windows, Linux, Android, and Nintendo Switch. Unfortunately, I can't help with this now, please, let me know if you find a solution :)
Best regards,
Mikhail Shagin

6 апр. 2021 г., в 02:37, Dean Harry @.***> написал(а):
Hi There,
I have implemented this and it works great in Unity, however when my game is compiled to WebGL and called it is giving me 'has been blocked by CORS policy' error in the browser console.
Any quick fixes for this?
Thanks
:)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/fiftytwo/MailChimpSubscriber/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABS6SVP35DQFJ4KIGY6YXD3THJCSDANCNFSM42NULRVA.

Thanks Mikhail,
It's taken me most of the day but I have managed to get it working :) I ended up having to build a proxy service to handle the request to Mailchimp. The issue is that a webgl (or web site) will expose the API key which would be a security concern.
If anyone else hit's this problem with WebGL then this article helped be a lot!
https://kheohyeewei.medium.com/use-serverless-to-work-with-mailchimp-api-6870fc29bcf1
Cheers
Dean

Wow, that's a nice solution, thank you for sharing! 👍
Best regards,
Mikhail Shagin

6 апр. 2021 г., в 13:56, Dean Harry @.***> написал(а):
Thanks Mikhail,
It's taken me most of the day but I have managed to get it working :) I ended up having to build a proxy service to handle the request to Mailchimp. The issue is that a webgl (or web site) will expose the API key which would be a security concern.
If anyone else hit's this problem with WebGL then this article helped be a lot!
https://kheohyeewei.medium.com/use-serverless-to-work-with-mailchimp-api-6870fc29bcf1 https://kheohyeewei.medium.com/use-serverless-to-work-with-mailchimp-api-6870fc29bcf1
Cheers
Dean
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/fiftytwo/MailChimpSubscriber/issues/3#issuecomment-814026661, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABS6SVN3UPSWNRA4IKGWO53THLSEHANCNFSM42NULRVA.


Remove delay when unticking checkbox

There is a delay when the onCheck handler is called after unticking the checkbox. I guess, it is fired when the unticking animation is complete.
<Checkbox
  ...
  onCheck = ...
/>

This delay makes the UI we are building feel awkward. Because we are disabling other UI parts when unticked and that should happen asap without the delay.
Can we either remove the delay and fire onCheck right away or introduce a new event like onUncheck or so?
PS: that delay does not occur when ticking. Hence I believe that the behavior is inconsistent.

I agree with this - it's a really awkward delay! If I use a regular checkbox my UI feels much more responsive.

Looks fine on material-ui docs website. Closing this issue for now. If you feel that the issue needs further addressing leave a comment below and I will open it again.


Template url DO NOT WORK (error 404)

In the readme.md - the URL to the TEMPLATE examples - DO NOT WORK:
Template S/4HANA2020 input for installation
Template S/4HANA Install
Template S/4HANA Restore
Sample S/4HANA2020 input for distributed / high availability installation (ASCS, ERS, DBCI, PAS)
Sample S/4HANA distributed
Sample Solman 7.2 input installation
ABAP Solman 7.2
Java Solman 7.2

Old format from initial commit, good spot.
Removed and replaced by clearer explanation of default parameters and samples, please see same sap_swpm README in release 1.2.0


import scanner.cc - transpile C++ to javascript

manually translating scanner.cc to tokens.js was too boring
so i started a domain-specific C++ to javascript transpiler ...
aka: why write 100 lines, when i can write 1000 lines?
currently this can transpile the trivial case,
where we have only one "entrypoint"
= only one value in enum TokenType
example: tree-sitter-cpp/src/scanner.cc
enum TokenType {
  RAW_STRING_LITERAL,
};

generated: scanner.js
handwritten: @lezer/cpp/src/tokens.js
detail: instead of marker: string i generate delimiter: number[]
maybe my version is 1% faster, because i avoid marker.charCodeAt(i)
but then sizeof(number) > sizeof(char) so ... gotta benchmark
next steps
so currently im trying to solve the complex case
where the Scanner.scan function acts as a "router" for multiple TokenType
probably will be something with treeshaking and function inlining ...
enum TokenType {
  HEREDOC_START,
  HEREDOC_BODY_BEGINNING,
  HEREDOC_BODY_MIDDLE,
  HEREDOC_BODY_END,
  CONCAT,
  // ...
};

struct Scanner {
  bool scan(TSLexer *lexer, const bool *valid_symbols) {
    if (valid_symbols[CONCAT]) {
      return scan_concat(lexer);
    }
    if (valid_symbols[HEREDOC_START]) {
      return scan_heredoc_start(lexer);
    }
    if (valid_symbols[HEREDOC_BODY_BEGINNING] && !heredoc_delimiter.empty() && !started_heredoc) {
      return scan_heredoc_content(lexer, HEREDOC_BODY_BEGINNING, SIMPLE_HEREDOC_BODY);
    }
    if (valid_symbols[HEREDOC_BODY_MIDDLE] && !heredoc_delimiter.empty() && started_heredoc) {
      return scan_heredoc_content(lexer, HEREDOC_BODY_MIDDLE, HEREDOC_BODY_END);
    }
    // ...
  }
}

my code is far from "ready to merge" ... lots of dead code, debug stuff, comments

This is not something that I'm interested in maintaining, so I don't think it should live in this repository.

understandable
moving to https://github.com/milahu/lezer-parser-import-tree-sitter-scanner


Switch ronn to a maintained fork

The original ronn has long been unmaintained. There is a fork that introduces new command-line arguments, that are already being used in the wild (e.g. #168089). We might want to switch our package to that fork like Alpine and Debian already did.
Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name: ronn

current version: 0.7.3
desired version: 0.9.0
Notify maintainers

maintainers: @nicknovitski @zimbatm
Note for maintainers
Please tag this issue in your PR.

Sounds good, following what Debian does is an easy sell for me.

Opened https://github.com/NixOS/nixpkgs/pull/169617.


fixed responsiveness on teams page

Account Number : 9187ea0cb3a966a0c21204a6ad3e3c87a4bda807f83061f23d6f2816ac4026c1

@Linzo99 This design is not approved. Thanks for your effort. I'll fix it.


Remove the deprecated '--configure-cbr0='

The flag --configure-cbr0= has been removed since v1.5 (https://github.com/kubernetes/kubernetes/pull/34906) but the doc still has it.
Related issues:

https://github.com/kubernetes/kubernetes/issues/59257
https://github.com/kubernetes/website/issues/6827
https://github.com/kubernetes/website/issues/5285
https://github.com/kubernetes/website/issues/3200
https://github.com/kubernetes/website/issues/7481

@luxas Is it ok to remove this part, or reserve the maual part?
Do Network Plugins complete this job?
/cc @aburdenthehand

This change is

/assign @thockin @luxas

/lgtm
/approve

/lgtm


Add tf2_ros namespace fix demo to Galactic release notes.

Precisely what the title says. Connected to #1466.

@Mergifyio backport rolling foxy dashing


ReadableStream as Response.body causes function to stall

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
With Supabase CLI 1.57.4, the edge-runtime version 1.2.19 was rolled out.
This includes a fix for sending back null values in the HTTP 204 status code, which rquired no body to be sent. (See issue https://github.com/supabase/cli/issues/1071 and its fix)
I suspect that with this change, the support for ReadableStreams has been broken, as they don't contain a .size and thus might be treated incorrectly by the fix.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to https://github.com/zcei/supabase-response-stream-bug
Clone repository & setup supabase
Serve functions
Issue the two requests from the bottom of the README

Expected behavior
Both requests should work: one serves back a 204 with no content and the other a 200 with the text content of the stream.
~Screenshots~
~If applicable, add screenshots to help explain your problem.~
System information

OS: macOS
~Browser (if applies) [e.g. chrome, safari]~ reproducible with Browsers as with cURL
Version of supabase-js: 1.58.1
Version of Node.js: 18.14.1

Additional context
I suspect that the line to fix it (see here) does not account for all cases. e.g. I don't think a ReadableStream can have a .size property when it's not clear yet whether someone will write to that stream.
I was trying to hop through Deno with the debugger, but as this is my first sparring with Deno, sadly to no great success.
Some pointers that may help, or could be red herrings:

The 204 requests used to fail with the error that is raised here
This error happens when bodyWithType is not null (see here)
The body is created by hopping through a few layers of webidl.converters, which is where I lost track with my current debugger setup 😞 . From looking at the code in GitHub, there's a chance that converters.DOMString is called which could return 'null' rather than null.
Tried to reproduce with plain Deno (without supabase) but the function seems to have worked there. So I'm not sure whether Deno fixed it in their latest version already, or I chased down an incorrect assumption.

Taking a look


Potential problem with notifications

See this thread:
https://www.traccar.org/forums/topic/receiving-email-notifications-for-all-devices/

It uses function getDeviceUsers https://github.com/tananaev/traccar/blob/master/src/org/traccar/database/NotificationManager.java#L56
same as in ConnectionManager
https://github.com/tananaev/traccar/blob/master/src/org/traccar/database/ConnectionManager.java#L128
https://github.com/tananaev/traccar/blob/master/src/org/traccar/database/ConnectionManager.java#L140
I do not think it works incorrectly.

OK, let's close it for now. We can reopen it later.

Oh, but there is a problem. Not connected to notifications but...
I have unlinked device from admin, refreshed the page, run test, and got device updates in websocked. Looks like some cashed permissions was not updated correctly.
Will investigate it tomorrow.


Refactor AeroSurface3D.calculate_forces() to return a positioned impulse, for use as the center of pressure.

Getting the center of pressure is trivial, as a positioned impulse corresponds to it.
Related #4

Unnecessary, as you can use the AeroInfluencer3D's position as the positioned impulse.


Huey DB encounters race condition when Flask server is under load

Getting errors when launching many jobs in one go.
  File "D:\Users\abdul.siddiqui\venvs\ripple-py312\Lib\site-packages\huey\storage.py", line 650, in db
    if commit: cursor.execute(self.begin_sql)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sqlite3.OperationalError: database is locked

SQLite can have only one write connection at a time, which might be the cause of this error, there should be one connection object only and it must be passed around to different functions.

This becoming a pain point. The API can't handle as low as 10 to 20 requests at a time.

@ar-siddiqui to clarify, are you referring to huey processing 10 to 20 concurrent processing jobs, or referring to flask responding to 10 to 20 concurrent requests (such as job status GET requests)?  If the latter, what is the request rate?


MA-1709 update icons for iphone 6/6+

make the things look better on big phones.
There's still a few pages with fixed layout, but I tried to make them passable for now.

:+1: Filed https://openedx.atlassian.net/browse/MA-1713 as follow up


Remote Cache import/export API Proposal

There was an earlier extremely provisional implementation of this to give a quick solution for a user who wanted it on a short term basis: https://github.com/dagger/dagger/pull/3543
There was then some discussion in that PR on how to best approach this in the long term, using this issue to continue that discussion and get consensus.
API vs. Client Config
To start, there are different options in terms of whether we make cache import/export be part of the actual API or whether we make it more of a client config.
Client Config
This could take the form of something like:

DAGGER_CACHE_EXPORT and DAGGER_CACHE_IMPORT env vars that get interpreted by each SDK and applied to the build
Arguments to dagger.Connect for setting cache imports and exports

The implementation would need to do something like set this configuration in headers that get read by the router and applied to the build.
Similar to the previous v0.2 implementation, this would need to be implemented by including every LLB vertex that occurs across the client instance in the cache exports, so fine grain control and buildkit's min/max cache settings won't be usable.
Pros:

If you want the same cache settings to apply to every vertex in a number of builds you only need to set an env var or apply a setting when you create your client

Cons:

Requires re-implementing support in each SDK rather than just picking it up as part of codegen
Have to come up with a schema for configuring this that is different than our graphql schema

Also need it to be flexible enough to handle more import export backends and configuration in the future

Can't reuse our secret support for providing credentials to the cache backends (i.e. gha tokens, s3 api creds, etc.)
Can't choose what gets exported or choose between min/max exports

Selecting what gets exported is important because exporting cache adds overhead, so it's often not beneficial to just export everything.
See for example the problems that our CI started having after we enabled GHA caching for our whole CI builds in v0.2: https://github.com/dagger/dagger/issues/2365
If we support import export of cache mounts in the future (an often requested feature), getting fine grain control over this will be even more important as those cache mounts have huge tradeoffs in terms of whether they are efficient to remotely export vs just redownloading their contents on a cache miss.

No clear route to adding cache management apis (i.e. query how much storage is being used, pruning it, etc.) if we wanted to in the future

API
This approach would put cache import/export config in the actual API. This could take many forms (and one proposal exists below) but the idea is that:

The cache config for different export/import targets (and the options within each target) are all defined in our graphql schema
You can pick and choose what to actually export as part of the API (i.e. which Containers or Directorys)

Additionally, if we want, we could also optionally support "global" settings that apply to the whole build too (e.g. withCacheImports(...) Query! type APIs), so we retain flexibility
This would also enable min/max settings that buildkit supports

Pros:

SDKs don't have to do any extra work on top of their existing codegen
Re-uses existing mechanisms for defining schemas
Can re-use secret support for providing credentials
Flexible enough to support "global" settings for cache import/exports but also easily able to support fine grain control when users need optimization (which they often do when it comes to remote caching)
Gives routes to supporting APIs for querying remote cache state like storage usage + pruning

Cons:

Requires explicit usage of an API by users rather than just having them set an env var and then picking that up from there.

API Proposal (provisional)
My opinion is that we should go the API route rather than client config, so including a proposal for that API here.
There's many many possibilities here and I'm very open to bikeshedding or completely different approaches.
This proposal makes use of some graphql features we've previously not used like interfaces+enums, so there will be a little bit of overhead to update our codegen clients to support this. I think that's just work we'll want to do anyways and thus worth it, but I am also okay with different approaches to this API if we don't think that's a good tradeoff.
To be honest, I'm not totally convinced by this entirely, but gotta start somewhere and there are a few appealing aspects of it mentioned below. Will wait to get others thoughts before making more adjustments.
extend type Query {
  # namespace for remoteCache backends. Optional, can skip this at cost of polluting top level namespace
  remoteCache: RemoteCache!
}

# The supported cache backends (options are mostly derived from docs here https://github.com/moby/buildkit#cache)
type RemoteCache {
  githubActions(scope: String, url: String, token: Secret!): RemoteCacheBackend!

  s3(
    bucket: String!
    region: String!
    accessKeyId: Secret!
    secretAccessKey: Secret!
    sessionToken: Secret
    blobsPrefix: String = "blobs/"
    manifestsPrefix: String = "manifests/"
    manifestName: String = "dagger"
    endpointUrl: String
    usePathStyle: Boolean
  ): RemoteCacheBackend!

  registry(ref: String!): RemoteCacheBackend!

  # TODO: others like azure + local
}

# common interface across all remote cache backends (registry, gha, s3, etc.)
interface RemoteCacheBackend {
  # use the imports of this backend as cache sources for the rest of the query
  useImports: Query!

  # push the provided containers, directories, and files with the given min/max mode to this cache backend
  pushExports(
    containers: [ContainerID!]
    directories: [DirectoryID!]
    files: [FileID!]
    mode: CacheExportMode = MIN
  ): Boolean!

  # if we want, we can also configure global cache exports for the build too with something like this
  # useExports(mode: CacheExportMode = MIN): Query!

  # Someday could add APIs for managing cache like
  # usageBytes: Integer!
  # prune(since: DateTime!): Boolean!
}

enum CacheExportMode {
  MIN
  MAX
}

Example usage
c, _ := dagger.Connect()

ghaCache := c.RemoteCache().GithubActions(
  c.Host().EnvVariable("GHA_TOKEN").Secret(),
  dagger.GithubActionsOptions{
    Scope: "my-cool-scope",
  })
)

// wrap the rest of the operations with cache imports
c = ghaCache.UseImports()

// do something that's worth caching remotely, it will use the previously configured cache imports
ctr := c.Container().From("alpine").Exec([]string{"some", "expensive", "operation"})
output, _ := ctr.Stdout(ctx)

// export the cache too now
_, err := ghaCache.PushExports(containers: []*dagger.Container{ctr}, dagger.PushExportOpts{
  Mode: dagger.CacheExportModeMax,
})

Overall I like the fact that it becomes really easy to blanket whole sets of queries with cache imports but then pick and choose what you want to export (while still making it easy to combine a lot of exports into one by having the interface accept multiple containers, directories and files). I think that reflects the reality of what you currently need to do to use buildkit remote caching effectively.
I also like that the remote backends have their unique options in the schema while still combining them behind a common interface after the unique configuration is applied. This seems like it should support the addition of more backends in the future while also not exploding the API in size more than necessary.

cc @aluzzardi @vito @shykes

Anything I can do to help move this proposal along? Trying to bring dagger to a wider audience in my org but not having the speed gains from leveraging a remote cache via sdk is kind of holding that back

Anything I can do to help move this proposal along? Trying to bring dagger to a wider audience in my org but not having the speed gains from leveraging a remote cache via sdk is kind of holding that back

@cpdeethree sorry about that. This feature is held up in a design discussion on the best way to expose it. I will try to soeedyit along. While discussing we found a potentially better way to persist cache (import/export has fundamental limitations regardless of how it’s exposed). We actually have a prototype of this alternative solution that we could demo to you, if that interesting. Ok if I contact you privately to discuss your use case and how we can help?

Sure! I will ping you on discord.

@sipsma resuming this discussion... My feeling is that we should not expose this in the API, but rather configure it at the engine config level (not at the client config level!). This is because IMO configuring cache is an operator concern, not a client concern.

That doesn't mean those APIs are wrong... just that they should be private to the engine. Either compiled in the engine binary, or perhaps loaded dynamically as a new kind of "caching backend".

@shykes I agree, my thinking on this has evolved since I originally wrote it. Part of the reasoning behind the proposal was that it let pipeline developers pick and choose when it was beneficial to use remote caches and when it wasn't based on their knowledge of the pipeline. But I think we (as Dagger devs) should try to make a system that enables automatic decisions on caching in combination w/ engine operator configuration. Just a much better DX.
It's certainly a hard problem but I think it's worth a shot. If we give good guidance and users set up fast cache backends then the need for finer grain optimization will shrink somewhat. That'll give us room to start simple and introduce more advanced features over time. The idea of being able to specify a Service that serves an API for deciding what to cache and where, similar-ish to the whole secret provider idea, is pretty intriguing in the long run.

I'm not sure if this is precisely what you were imagining or not, but the general idea of there being an API for engine operators separate from the core api came up here too and probably could be used in all sorts of different ways (e.g. configuring bootstrap services).
A cache config API for the engine can easily fit into that. It would be nice since it would keep this out of pipeline code but still allow us to reuse types from the core API as desired (e.g. secrets for configuring cache backends).
I think I will start there in terms of prototyping the implementation of this (since the need for it is imminent) but let me know if you were imagining something different or if I'm not being clear.

@gerhard This issue does not seem stuck, but just waiting for an actual implementation, should we move it to ready for work?

Things have changed significantly since this issue was opened... The main change is that we have lost confidence in the synchronous cache import/export model for building scalable distributed caching. It sounds great in theory, but in practice there are too many caveats.
We still have to find the right balance between 1) not sending users down a path they will regret, and 2) still allowing an "escape hatch" for buildkit power users who understand the downsides, and still want to access the low-level buildkit feature.
I would also like to get the opinion of @sipsma and @aluzzardi on what I said above. Do you agree with me that bk import/export doesn't meet the bar for us to make it a first-class feature in Dagger? Or do you think that is excessive, and there is room for it in a production setting?

Do you agree with me that bk import/export doesn't meet the bar for us to make it a first-class feature in Dagger? Or do you think that is excessive, and there is room for it in a production setting?

I think that is right. Just in terms of documentation and time spent troubleshooting w/ users, it would get to be a huge burden; not only for us at Dagger but also for users. The subtleties, limitations and various performance problems once you get beyond the simplest use cases are so much that it's hard to justify outside of the "escape" hatch approach for power-users who know what they are doing already.

Closing for clarity. Let's open a new one specifically for the buildkit escape hatch.


Add more tools for debugging

Some basic tools for debugging should be added:

curl
top
atop
htop
netcat-openbsd
sysstat
nmap
socat

please add more in the comment

can be installed manually => Closing


Adding already built Nuxt Module

Hi @orestbida,
I have created a nuxt module for cookieconsent :)
https://github.com/raphaelbernhart/nuxtjs-cookieconsent
I would love to see the module in the README 😄
If it would help I would also make a PR to do this!
Just waiting on your reply to finish this.
PS: README and other changes for the developer experience (in the module repo) will be added soon.

I don't mind it as long as you place it at the bottom of the Readme!


TEN-154 added in auth connector for deprecated route

https://github.com/hmrc/auth/blob/51d78de48c0a9aa11095058bce0d78d00f20c3d1/it/auth/legacy/authority/LegacyAuthorityControllerISpec.scala#L358
https://github.com/hmrc/auth/blob/09e3b831752bfb0e820be4361806ba7b7f3051a5/app/auth/legacy/authority/AuthorityController.scala#L80


Loading AJAX-heavy sites can completely stall with https proxyspecs

Loading AJAX-heavy sites through SSLsplit can cause browsers to stall completely, seemingly loading forever without any progress. I suspect this has to do with the fact that SSLsplit downgrades Connection: keep-alive to Connection: close and removes other headers related to performance-improving HTTP features such as chunking. SSLsplit does that in order to get nice and clean, uncompressed and unencoded, straightforward loggable and tweakable HTTP requests and responses. However, this puts a lot of strain on browsers, servers and SSLsplit itself since it causes the browser to send lots of requests at the same time. This definitely needs more investigation.
As a workaround, using ssl proxyspecs instead of https disables all the HTTP header munging and generally gives better performance, at the cost of reduced features (e.g. no OCSP denial, less readable logs).
SSLsplit should probably implement more of the HTTP features like chunking, pipelining etc, but this would require a major rewrite of the https connection handling code.

I cannot reproduce this anymore, assuming fixed by one of the many fixed bugs.


[BUG]: Tab Newline

Description
Tab functionality is correct.
Tabbing into newline is incorrect.
Index needs to be reset to 0.
Cursor needs to land on end of indent with correct index.
(optional) What browsers are you seeing the problem on?
Firefox
Code of Conduct

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

Found solution.

Ignore the commit above.

#389


release 0.2.0

TRAVIS-CI: download build from https://s3.amazonaws.com/test-deskpro-apps-build/DeskproApps/jira/166/NODE-8/build/app.zip


Factories, rspec tests for pipeline visualization stage_results endpoint

Factories, rspec tests for pipeline visualization stage_results endpoint

pipeline_run_stages factory
rspec tests in samples_controller_spec.rb specific to pipeline visualization stage_results endpoint (see https://github.com/chanzuckerberg/idseq-web/pull/2287, https://github.com/chanzuckerberg/idseq-web/pull/2285)

To run tests: docker-compose run --rm web rspec -e "SamplesController"

nit: usually we keep commit and PR messages in imperative tense


[CRASH] Broken App Update 1.0.29 - Instant crash

Your Rocket.Chat.Android app version: 1.0.29
Your Rocket.Chat server version: 0.59.3
Device model (or emulator) you're running with: OnePlus 3T with Android 8.0
Steps to reproduce:
The newest Update is crashing instantly after starting the App.
For a short amout of time you can see "connection error" and then the App crashes.
I reinstalled the App and restarted the phone, but the App crashes no matter what.
There is no difference between WLAN and LTE connection - i cant start the App.
I also send a Feedback-Report after a crash.
The behavior is reproducible on another device - Moto G5 with Android 7.0

I can confirm this. it happened on my Samsung S8. I completely removed the app cache, data and then the app itself. Installed again and it worked. But still its a bug.

I also removed the app cache, the app data and the app itself, but it is still crashing instantly after reinstall.

@mmarif4u @ArchimedesFM I'm really sorry for that, we got the crash and we're working on the fix. In the meantime, if you can, please leave the "Beta" program and install our stable version. We'll probably release another fix later today and I'll let you guys know.

@mmarif4u @ArchimedesFM This is happening because you guys had 1.0.27 or 1.0.28 before, then a migration in DB is causing it. If you install the Stable and then install the Beta now, it'll work just fine.

@mmarif4u @ArchimedesFM Can you guys install the last production version, that would be 1.0.22 (this might require that you leave the Beta program first) and then enter Beta again and install version 1.0.29 and please report back again here?

For me this works. After the update from 1.0.22 directly to beta 1.0.29 i can start and use the app.

I was on 1.0.27 or 1.0.28 (cant exactly remember), but upgraded today to 1.0.29.
For me after reinstalling again, it worked. But still i guess it is a bug somehow in the migration.

Yes, the crash happens because the migration was trying to be executed in a database that already had the field.


Cannot use securely in MediaWiki

I was trying to integrate slick into MediaWiki to use sliders on a wiki. However I discovered that I cannot do it securely.
A number of data-slick params accept raw html and slick includes this in its code:
$(function(){
  $('[data-slick]').slick();
});

MediaWiki allows pages to output arbitrary data-* attributes into pages (presumed safe, and up till now, fine).
However together this means that simply including Slick in MediaWiki would allow someone to output a div with data-slick and introduce an XSS vector.

I'm not sure how I would begin to resolve this issue without seeing it in use or having a code sample.

I'm not sure how I can make it any clearer.
MediaWiki lets normal users write
...
.
Slick options such as prevArrow accept raw HTML and accepts options from data-slick.
Slick automatically runs on anything that has a data-slick attribute.

I can write JS that whitelists slick options and runs slick with just the known safe ones (and drops any data-slick argument).
But that won't work if simply including slick.js means any [data-slick] in user content will be handled by slick automatically before I can intervene.

So if I were to handle this in core, did you have a recommended solution? Strip script includes if found in a value?

Further, jQuery should be stripping out script tags. So can you actually hack an instance of slick, so I can see it happening, and then we can talk about approaches to fixing it?

The only acceptable fix would be to not automatically $(function(){ $('[data-slick]').slick(); }); so I could do that myself after whitelisting all the safe parameters.
Anything else would be playing whack a mole with the hundreds of known tricks for evading XSS blacklists. Only whitelisting works.
I'm not sure whether you want to do this as a new major release or as an alternate build that excludes the implicit handling.

Also there are two things you need to keep in mind about XSS.

jQuery does not strip out script tags. It strips them out and then executes them. (jQuery isn't doing security, all it is doing is making sure that script tags aren't accidentally re-executed when the html is messed with)
You do not even need a script tag to do XSS. As long as you can find a hole that'll let you stick an on* attribute into something you can find a way to inject an XSS attack. For example you could insert an onmouseover that'll execute something malicious as soon as the user tries to use it. And as a bonus it would be trivial to make this worse by including a style="" attribute that makes the element cover the entire viewport (so the moment your mouse enters the website to do anything, the XSS attack runs.

Usually I like to avoid publishing client staging sites, but here's a test page with a working XSS demo where I've included slick. See the XSS alert on page view (using a


feat: Avatar component

Feature request
Is your feature request related to a problem? Please describe.
Inspiration from
https://ant.design/components/avatar/
See https://github.com/supabase/ui/pull/208 thread for more details as well

Adding this here for you @galanteria01 🚀

@MildTomato
Thank you sir.

@galanteria01 as a heads up - we're going to be adding in user profile avatars into the project view in the supabase dashboard, so we'll possibly be using this component to show which team members are currently online viewing the same project.
I'll try and expand this issue above with a more detailed spec of what this component, but feel free to crack on if you are keen to get some basic functionality in place.

@MildTomato
I have made a working Avatar component with fallbacks including Image, Icon, First letter of child text and lastly a user icon with greyish background uptill now. Considering your opinion what progress i can make to create a PR?
GroupAvatar is the one I'm thinking about, Your suggestions would be helpful.
Thank you sir.

@galanteria01 yep, sounds good.
A group avatar subcomponent would be great.
something like:
<Avatar.Group>
  <Avatar />
  <Avatar />
  <Avatar />
<Avatar.Group/>

Yes sir.
And even mapping quite a lot of elements inside it would be easier. I would
implement group and test it. And a prop of onHover on the extension element
could be given as callback. If user want to do something else he can else
fallback would be dropUp.
On Tue, 1 Jun, 2021, 1:06 pm Jonathan Summers-Muir, <
@.***> wrote:

@galanteria01 https://github.com/galanteria01 yep, sounds good.
A group avatar subcomponent would be great.
something like:
<Avatar.Group>

<Avatar.Group/>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/supabase/ui/issues/210#issuecomment-851898906, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOATQIGJWLPGVLU7VINCHSLTQSEYFANCNFSM452DYKQA
.

@galanteria01 awesome, feel free to PR whenever - even a work in progress if you like.

@MildTomato
Yes sir will PR tomorrow. Cleaning up implementation with tailwindcss and separating in Module.css.

@galanteria01 are you still keen to work on this? we are looking to use this component in the next few days.
Happy to take this one if you're busy.

Hello sir. Actually it was first week of my internship so was little busy.
Tomorrow will submit patch . Sorry for delay sir.
On Tue, 15 Jun, 2021, 8:17 am Jonathan Summers-Muir, <
@.***> wrote:

@galanteria01 https://github.com/galanteria01 are you still keen to
work on this? we are looking to use this component in the next few days.
Happy to take this one if you're busy.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/supabase/ui/issues/210#issuecomment-861128040, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOATQIFWWDOHDLN3K55U6HLTS25NFANCNFSM452DYKQA
.

Closing this as the component has been started on


[Impeller] AiksInspector leaks allocated textures.

The fix:
// aiks_playground_inspector.cc

+ void AiksInspector::HackResetDueToTextureLeaks() {
+   last_picture_.reset();
+ }

// aiks_playground.cc

+ void AiksPlayground::TearDown() {
+   inspector_.HackResetDueToTextureLeaks();
+   PlaygroundTest::TearDown();
+ }

@jonahwilliams commentary:

I don't think this code is running in the right order. It might be torn down after we run shutdown of the context
because the dtors are running after shutdown
but shutdown is what tries to flush the fence waiter/resource manager

I want to fix this, but after some more pressing issues.

The hack seems reasonable?

I mean it's reasonable in that it works, but our layers are getting unmanageable IMO, we should not require arbitrary shared_ptr and resource resets in particular orders, or should design the APIs to be less brittle.

We're always going to need resource resets in a particular order.

The fact we don't know that order seems like a problem/smell though (and that it's possible to add new things, like the Inspector, that further complicate this!)

Reopened since the removal of AiksInspector was reverted in https://github.com/flutter/engine/pull/52680.


Add a reader to load the output from the STScI pipeline (_x1dints.fits) into a Rainbow.

@will-waalkes and I are working on some readers. I'll wait until we're happy with both the STScI and eureka readers before merging both into the main branch. We're starting to get somewhere...

...but there are still some bugs to work out on both sides.
Most of the development for this right now is happening on the will branch.

(See also #5 ).

Closed by #25 . It can now handle either .dat intermediate data products or .txt tables from eureka.

Closed by #25 . It can now handle either a single x1dints file, or a collection of x1dints segments.


python37Packages.astroquery: 0.3.8 -> 0.3.9

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-astroquery/versions.
meta.description for python37Packages.astroquery is: '"Functions and classes to access online data resources"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.3.9 with grep in /nix/store/k9hb90swzn7mzym8drq50kgcva1j9jhy-python3.7-astroquery-0.3.9

directory tree listing: https://gist.github.com/7e5207384ed753ae16d993b68ac09f22

du listing: https://gist.github.com/121641b999aae6567ac3d00de815dd77

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python37Packages.astroquery

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k9hb90swzn7mzym8drq50kgcva1j9jhy-python3.7-astroquery-0.3.9 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.astroquery https://github.com/r-ryantm/nixpkgs/archive/8db71e816ff1045ad9c29b33bea910062aef2c03.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k9hb90swzn7mzym8drq50kgcva1j9jhy-python3.7-astroquery-0.3.9
ls -la /nix/store/k9hb90swzn7mzym8drq50kgcva1j9jhy-python3.7-astroquery-0.3.9/bin

cc @smaret for testing.

0.3.9 is out.

@worldofpeace This is the upgrade to 0.3.9

:rofl: Maybe I shouldn't look at these update prs simultaneously


[swift-inspect][RemoteMirror] Decode job/task/actor flags.

Have RemoteMirror internally decode these flags fields and return them as separate fields in the task/actor info. Handle the structures both with and without task escalation support.
Also show when a task is the current task on a thread in swift-inspect's task listing.
rdar://88598003

Updated with most of the review feedback. I'd like to do the info about the lock owner in a separate PR afterwards. @rokhinip how's it look now?

@swift-ci please test

@swift-ci please test macos platform


Add GitHub pages site (#6)

This pull request introduces the deployment of our project's web page using GitHub Pages, a feature discussed in detail in issue #6. The primary goal of this feature is to enhance the visibility and accessibility of our project. You can view the deployed page at https://rickstaa.dev/awesome-livepeer to see the feature in action.
Implementation:

Configured the repository to deploy the site using GitHub Pages using the jerkyll-gh-pages.yml GitHub action.
Added extra CI action to safeguard the quality of the list (i.e. https://github.com/rickstaa/awesome-livepeer/blob/main/.github/workflows/lint.yaml).
Added extra release CI action which creates a new release when a new tag is pushed or the bump:patch, bump:minor or bump:major labels are attached to a PR (see https://github.com/rickstaa/awesome-livepeer/blob/44006f89e317c74e808fddfaa96fb5ce77b5cd17/.github/workflows/release.yml#L20C15-L20C20).
Fixed awesome-lint errors.
Added Logo.

Testing:

Extensive testing has been conducted to ensure seamless integration and functionality. The live deployment successfully displays our project in a user-friendly web format.

Next Steps:

Post-merge, we can link this page to the https://livepeer.cool domain. This will further enhance our project's visibility, particularly for those familiar with awesome lists.

Repository Topics:

I recommend we add the awesome and awesome-list topics to our repository once this PR is merged. These topics will improve our project's discoverability on GitHub, aligning it with other curated lists and resources.

Feedback and further suggestions are welcome and highly appreciated 🚀.

Since I also fixed some linting errors, the easiest way to review this is by going through the commits individually, starting with https://github.com/livepeer/awesome-livepeer/pull/7/commits/50cfa08e03b38cfdd28a652aa63e807da58d7773 which contains the core of this pull request.

@dob It looks like the following websites no longer exist, have expired SSL certificates or are broken (see link checking CI -> https://github.com/rickstaa/awesome-livepeer/actions/runs/7684765006/job/20941777800).
https://github.com/livepeer/awesome-livepeer/blob/521ef9d0c75d4254fae477f3d5ea35e71af17454/README.md?plain=1#L9
https://github.com/livepeer/awesome-livepeer/blob/521ef9d0c75d4254fae477f3d5ea35e71af17454/README.md?plain=1#L107
https://github.com/livepeer/awesome-livepeer/blob/521ef9d0c75d4254fae477f3d5ea35e71af17454/README.md?plain=1#L126
I contacted the developers for a fix.

I temporarily broke the styling by adding the livepeer.cool domain. I will fix it later and let you know so you can check it out 👍🏻.

I've temporarily disrupted the styling by integrating the livepeer.cool domain. I'm planning to address this issue shortly and will update you once it's resolved so you can take a look 👍🏻.

I fixed it 👍🏻. The website is now available at https://livepeer.cool. The certificate needs about 24 hours to update.

Thanks @rickstaa. A couple small items...

On the output page it says something like, "This site is open source. Improve it here." I think it might be a little bit more inviting to community members to say something less dev centric and instead focus on the list. "This list is open source and maintained by the community. Suggest an improvement to add, edit, or remove items from Awesome Livepeer."

I didn't fully follow the version bump workflow. Will the page get updated when a change is merged into the README, or does someone have to also somehow bump a version to trigger a build?

Hi @dob, thanks for sharing your insightful feedback!

On the output page it says something like, "This site is open source. Improve it here." I think it might be a little bit more inviting to community members to say something less dev centric and instead focus on the list. "This list is open source and maintained by the community. Suggest an improvement to add, edit, or remove items from Awesome Livepeer."

Regarding your first point about the website's footer message:
I completely agree that a more community-centric message would be more welcoming. The phrase "This list is open source and maintained by the community. Suggest an improvement to add, edit, or remove items from Awesome Livepeer" indeed sounds more inviting. I've initiated a pull request to address this, aiming to modify the default primer theme in a user-friendly manner. You can follow the progress of this request here: GitHub PR link. Meanwhile, to expedite the launch of https://livepeer.cool, we could consider the workaround detailed in Jake Lee's blog: Removing GitHub Pages 'Improve this page'.

I didn't fully follow the version bump workflow. Will the page get updated when a change is merged into the README, or does someone have to also somehow bump a version to trigger a build?

As for your second query about the version bump workflow:
The process is currently set up so that any merged pull request automatically updates the page. The workflow details are outlined here: GitHub Workflow link. While versioning serves as a method for maintainers to keep track of changes, I'm open to suggestions for improvements. One idea is to trigger website updates only with new version releases, which could be more orderly if multiple collaborators exist.
Another possibility is using the Release Please Action from GitHub, though it might be a bit complex for our needs. It automates changelogs and enforces the conventional commits convention, as seen in this example: Release tag link.
Currently, our release action is simple and effective, especially considering that many contributors to github.com/livepeer/awesome-livepeer may not have a software development background. However, I'm eager to hear what you think about the best approach for our release workflow. Your feedback is greatly valued! 😃

Thanks, @iameli, for your encouragement 😃! The GitHub Actions are already operational in my fork, and the results are accessible at https://livepeer.cool (details can be found at this link). Integrating them into the main repository is straightforward; it just requires merging the pull request and adjusting the Cloudflare DNS settings.
You're right about the importance of testing changes without merging; it's essential for a smooth workflow. I haven't yet included instructions for this in our documentation, but I see the value in adding it to the CONTRIBUTING.md file, which follows the template from https://github.com/jthegedus/awesome-list-template. To facilitate developer testing, we could consider several approaches:

Local Jekyll Build: Provide guidance on how to build and run the Jekyll page locally. This would allow developers to see their changes in real-time on their own machines.
Docker Container: Offer instructions for building and running the Jekyll environment using a provided Docker container. This could simplify setup and ensure a consistent environment across different systems.
GitHub Action for PR Previews: Develop a GitHub Action that automatically publishes changes from PRs to a temporary subdomain (e.g., livepeer.cool/PR323) and links this in the PR comments. This approach would enable easy viewing and testing of changes in a live environment before merging.

I'd love to hear which of these options you prefer, or if you have any other suggestions or preferences. Your feedback is invaluable in improving the development process!

@iameli, I've just conducted a swift investigation, and it appears that the native support for displaying PR page previews is not yet available within our GitHub action-based deploy pipeline. However, I have some good news! The GitHub team has already implemented this feature and is actively using it internally, as documented here: https://github.com/orgs/community/discussions/7730#discussioncomment-7603270. We can expect it to be deployed shortly.
In the meantime, I will update our CONTRIBUTING.md to provide clear instructions for maintainers on how to build the page locally or through a Docker container. This should help bridge the gap until the native support becomes available.

@iameli Since GitHub is actively developing a GitHub Pages preview function, I believe we don't have to dedicate development resources to this task ourselves. In the meantime, I have updated the CONTRIBUTION.md to provide instructions on the local build process until GitHub officially releases this feature (see https://github.com/livepeer/awesome-livepeer/pull/7/commits/dee12a5c6f704400921bbf221f4d16f1f9b7bad6).
@iameli, @dob If you have any suggestions for the [CONTRIBUTION.md](https://github.com/livepeer/awesome-livepeer/pull/7/files#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055 or the build procedure, please let me know 👍🏻.

@dob I've forked the build actions to allow us to set a custom footer in anticipation of https://github.com/pages-themes/primer/pull/85 being merged into the upstream. I've condensed your suggestion to keep it as a one-liner. If you have a new one-line footer idea, please share it. I believe we're ready to release livepeer.cool to the public. If you have any other changes you'd like me to make, please don't hesitate to reach out 😄.


Red cross permissions are not how Raquel requested

Regular users can only deliver
Advanced users can register, delivery and do overrides

Also - Adapt the distribution report to the questions that Raquel sent

This probably shouldn't have been migrated from asana actually, closing ~