Getting started: solving kata

Please take a look if it goes in good direction. I am wondering if it needs screenshots, or links to UI docs will suffice?

Ugh, the output of TextLint is not helpful. I'll look for a way to integrate with GitHub Actions better, but you have a misspelled word on line 23.

Yeah it's kinda confusing, but until now I somehow managed to understand it. I will fix the typo tomorrow

there was still no preview available, so I made a small change/commit.

I split "solving" and "solved" parts into two separate pages. Please let me know what you think.

at the root, the gridsome.config.js file needs to be update (for the sidebar) :
...
{
        name: "getting-started",
        sections: [
          {
            title: "Getting Started",
            items: [
              "/getting-started/",
              "/getting-started/registering/",
              "/getting-started/setting-up/",
              "/getting-started/finding-kata/",
              "/getting-started/solving-kata/",
              "/getting-started/kata-solved/",
              "/getting-started/solutions/",
              "/getting-started/community/",
            ],
          },
        ],
      },
...

at the root, the gridsome.config.js file needs to be update (for the sidebar) :

Done

It seems there are images at different levels in the folder (07 is outside getting-started/img/) =>?

It got submitted accidentally, sorry. It's to be removed.

would be better to update the images right now with dark/light versions, no? (see #74)

Does it work already?

Does it work already?

actually yes. I forgot to update the title of the section... XD (corrected)

Maybe change the title of the new page to "When kata get solved"? (because other titles are plural, that looks a bit weird in the sidebar)

Maybe change the title of the new page to "When kata get solved"? (because other titles are plural, that looks a bit weird in the sidebar)

I tried to fix capitalization, maybe it looks better now.

would be better to update the images right now with dark/light versions, no? (see #74)

Created #86

I tried to fix capitalization, maybe it looks better now.

:+1:
that was it, actually :)

@hobovsky You can merge this if you want. I already left my review yesterday. https://github.com/codewars/docs/pull/72#pullrequestreview-453634748
We can improve this after merging because all the comments are becoming difficult to keep track.

I've already started working on your suggestions, so if you'd want to review my updates, then go ahead, and if you think it;s ok, you can merge it. I will get back to it tomorrow, so if you still think things are good, I will merge my changes. But you can still leave some remarks if you have any, or just merge if you think all is ok.


Unable to convert bed to States Data (multivec) file using clodius bedfile-to-multivec

Hi Developers,
I am trying to convert a bed file to States Data (multivec) file, ingest the multivec file to my higlass server and try to display the tracks on the website. However, the multivec, the output of clodius bed_to_multivec, cannot be loaded correctly on my Higlass website.
I was using the example bed file and row info file as the input of clodius bed_to_multivec and trying to get the example output using the following command:
clodius convert bedfile-to-multivec states_format_input_testfile.bed.gz \ --format states \ --row-infos-filename states_format_test_row_infos.txt \ --assembly mm9 \ --starting-resolution 200 \ --num-rows 10
I used diff to check if my output states_format_input_testfile.bed.multires.mv5 differs from the example output and they are different. And after I ingested my output to my Hilglass webpage, it keeps loading and cannot display the track.
Can you check what is the reason. I used pip3 install clodius to install and the convert command of my clodius is bedfile-to-multivec instead of what the tutorial command bedfile_to_multivec. Is my issue due to  the clodius version difference? Thank you very much.
Best,
Haoting

Hi, sorry for the delayed response. Could you take a screenshot of your browser console and post it here?
Also what version of clodius are you using?  You can find out by doing this:
python -c "import clodius; print(clodius.__version__)"

Thank you. Here is a screenshot and my version is 0.18.1.
The upper track is from ingesting the original example successfully.
The lower track is from ingesting the multivec i got using clodius convert.

Sorry, could you post a screenshot of the browser console? If you're on a mac, you can open it using   i. Otherwise you can find a link in your browser menu. It should look like this:

Thank you. Here is the console screenshot of the tracks condition.

Are you running higlass locally, could you try to load that dataset again and then paste the last few lines of the ~/hg-data/log/hgs.log file?
I'm pretty sure I've reproduced the issue locally but want to make sure.

Thank you. Here is my error after loading.
[29/May/2022 21:36:50] ERROR [django.request:222] Internal Server Error: /api/v1/tileset_info/ Traceback (most recent call last):   File "/usr/local/lib/python3.8/dist-packages/django/core/handlers/exception.py", line 34, in inner     response = get_response(request)   File "/usr/local/lib/python3.8/dist-packages/django/core/handlers/base.py", line 115, in _get_response     response = self.process_exception_by_middleware(e, request)   File "/usr/local/lib/python3.8/dist-packages/django/core/handlers/base.py", line 113, in _get_response     response = wrapped_callback(request, *callback_args, **callback_kwargs)   File "/usr/local/lib/python3.8/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view     return view_func(*args, **kwargs)   File "/usr/local/lib/python3.8/dist-packages/django/views/generic/base.py", line 71, in view     return self.dispatch(request, *args, **kwargs)   File "/usr/local/lib/python3.8/dist-packages/rest_framework/views.py", line 505, in dispatch     response = self.handle_exception(exc)   File "/usr/local/lib/python3.8/dist-packages/rest_framework/views.py", line 465, in handle_exception     self.raise_uncaught_exception(exc)   File "/usr/local/lib/python3.8/dist-packages/rest_framework/views.py", line 476, in raise_uncaught_exception     raise exc   File "/usr/local/lib/python3.8/dist-packages/rest_framework/views.py", line 502, in dispatch     response = handler(request, *args, **kwargs)   File "/usr/local/lib/python3.8/dist-packages/rest_framework/decorators.py", line 50, in handler     return func(*args, **kwargs)   File "/home/higlass/projects/higlass-server/./tilesets/views.py", line 681, in tileset_info     tileset_infos[tileset_uuid] = hgmu.tileset_info(   File "/usr/local/lib/python3.8/dist-packages/clodius/tiles/multivec.py", line 262, in tileset_info     tileset_info["row_infos"] = [r.decode("utf8") for r in row_infos]   File "/usr/local/lib/python3.8/dist-packages/clodius/tiles/multivec.py", line 262, in <listcomp>     tileset_info["row_infos"] = [r.decode("utf8") for r in row_infos] AttributeError: 'str' object has no attribute 'decode'

As I suspected. I just created a PR that should fix this: https://github.com/higlass/clodius/pull/145
I'll try to get it merged and issue a new release tomorrow.

Could you try v0.10.5 of the higlass-docker container? It should be fixed there.

Thank you. But I still have problem using higlass-manage. I updated clodius to v0.19.0. I repeated steps of clodius bed-to-multivec and used higlass-manage ingest. The issue is still the same. Should I use higlass-docker or is there a way i need to do to update higlass-manage? Thank you.

Wonderful!
Another way to do that is to specify the docker container version in higlass-manage: higlass-manage start -v v0.10.5


[Help]: sbas.topo_ra_parallel() taking too long

Processing with 32 cpu / 128 GB RAM / 2 SSD RAID 0 on Jupyter.
3 SS from 151 SLC.
Dem is set to 15m resolution.

sbas.topo_ra_parallel() running very slowly. It has been about 2 hours and only 15%.

Notebook becomes stuck at 15%. Error in NotebookApp:

The logged error is not related to PyGMTSAR, see
https://github.com/tornadoweb/tornado/issues/2271
https://github.com/python/cpython/issues/85269
To resolve it, try to upgrade all your python libraries (especially tornado). Also, do you use chunk size 1024 (instead of default 512) and dask distributed LocalCluster with tcp and connect timeouts 60s? For the reference, an example configuration for 2 stitched scenes 15m for pygmtsar-large Docker image available on GitHub: https://github.com/mobigroup/YamchiDam/tree/main/notebooks

Yes, I am using chunk size 1024:

It took about 12 hours.

Not only does sbas.topo_ra_parallel() take very long, it is called a second time in sbas.geocode_parallel(). Is this really necessary? It would only make sense on the condition that sbas.get_topo_ra() is empty.
`class SBAS_geocode(SBAS_sbas):
def geocode_parallel(self, pairs=None):
    # find any one interferogram to build the geocoding matrices
    if pairs is None:
        pairs = self.find_pairs()
    # build trans_dat and topo_ra grids
    self.topo_ra_parallel()
    # define the target interferogram grid
    intf_grid = self.open_grids(pairs, 'phasefilt').min('pair').astype(bool)
    # build geographic coordinates transformation matrix for landmask and other grids
    self.intf_ll2ra_matrix_parallel(intf_grid)
    # build radar coordinates transformation matrix for the interferograms grid stack
    self.intf_ra2ll_matrix_parallel(intf_grid)`

geocode_parallel() should be called after merge_parallel() when all the subswaths merged together and so it builds the topography matrix for the merged grid. That's possible to enhance it combining single subswath matrices but for now merge_parallel result is unpredictable sometime (GMTSAR binary is used to do it).
Timeouts can be tuned by this code (see the large Docker image or the same notebooks on GitHub):
import dask, dask.distributed
# increase timeouts to work using default chunk size (512) even on large areas
dask.config.set({'distributed.comm.timeouts.tcp': '60s'})
#print (dask.config.get("distributed.comm.timeouts.tcp"))
dask.config.set({'distributed.comm.timeouts.connect': '60s'})
#print (dask.config.get("distributed.comm.timeouts.connect"))

from dask.distributed import Client, LocalCluster
cluster = LocalCluster(n_workers=1)
client = Client(cluster)
client

I think sbas.topo_ra_parallel() requires about 1 hour on 8 core Apple Air laptop for a single scene topography processing using 15m resolution. So for your case it would be about 15 minutes in case you use all the cores (check your "client" variable output). "LocalCluster(n_workers=1)" can be not optimal for your hardware (I use it to limit the used RAM as possible because 2GB RAM per core is not enough for 2 stitched scenes processing by common way and the trick is required), try just "LocalCluster()".

Using larger cluster seems to make this faster.


fix: allows to use options configuration

Fixes #79

@kbond don't you think we could make methods TestTransport::isIntercepting(), isCatchingExceptions() and so on public? this way we could test this PR

@aegypius, could you fix the deprecations in TestTransportFactoryTest?

Working on it

Should not self::$supportDelayStamp be resetted too ?  https://github.com/aegypius/messenger-test/blob/allows-options-based-configuration/src/Transport/TestTransport.php#L337

Should not self::$supportDelayStamp be resetted too

I'm thinking yes but @nikophil, can you confirm?

I think that indeed, we should do that!
but I'm wondering why we need two separate methods TestTransport::resetAll() and TestTransport::initialize()?
There is another PR opened about this: https://github.com/zenstruck/messenger-test/pull/77
let's just add $supportDelayStamp to resetAll() and we'll clean this in the other PR

not sure this is needed:

Ok, let's leave as is for now.


promtool: Add debug flag for rule tests

This makes it print out the tsdb state (both input_series and rules that
are run) at the end of a test, making reasoning about tests much easier.
Signed-off-by: David Leadbeater<EMAIL_ADDRESS>

cc @dgl are you willing to rebase this pull request? Thanks!

@roidelapluie I'd totally forgotten about this one, but yes, this is still useful!

Superseded by #15196 . Took these commits and merged main and resolved conflicts.


Research Design best practice and design session with David Elisma on site menu

[ ] Research design best practices for site menu and navigation
[x] Schedule session with David Elisma to learn about DTO changes to site menu and header
[ ] Document design best practices for site menu and navigation and share with team

Research links for documentation work :
(https://insidegovuk.blog.gov.uk/2021/11/11/launching-gov-uks-new-menu-bar/)
(https://design-patterns.service.justice.gov.uk/components/side-navigation/)
Fixed sidebar, W3 schools: (https://www.w3schools.com/howto/howto_css_fixed_sidebar.asp)
Response sidebar, W3 schools: (https://www.w3schools.com/howto/howto_css_sidebar_responsive.asp)
Left-side vertical nav, NN: (https://www.nngroup.com/articles/vertical-nav/)
Multiple nav landmarks, what no to do, Canada.ca example: (https://www.aditus.io/patterns/multiple-navigation-landmarks/)
Types of navigation, information seeking behaviours, O’Reily: (https://www.oreilly.com/library/view/designing-web-navigation/9780596528102/ch04.html#:~:text=CONTEXTUAL NAVIGATION,-Also called%3A associative&text=It's situational.,the content of a page.)
IRCC DS navigation: (https://www.figma.com/file/scmNcZkQomZSrwBbQU1bvn/Documentation?node-id=4-33&t=LtX26Frt48lAyiCj-0)
(https://www.systeme-de-design.gouv.fr/utilisation-et-organisation/)
(https://www.systeme-de-design.gouv.fr/elements-d-interface/composants)


🎁 Adding indices to Bulkrax Tables

Note: this is a best guess of what could use indexing.  The guess is based on my recent querying.

add_index :bulkrax_entries, :identifier :: because the identifier is an important concept for an import.

add_index :bulkrax_entries, :type :: because filtering on the type of an entry is important.

add_index :bulkrax_entries, [:importerexporter_id, :importerexporter_type], name: 'bulkrax_entries_importerexporter_idx :: this is a foreign key for the entries relationship to the importer/exporter.

add_index :bulkrax_pending_relationships, :parent_id :: a foreign key

add_index :bulkrax_pending_relationships, :child_id  :: a foreign key

add_index :bulkrax_statuses, [:statusable_id, :statusable_type], name: 'bulkrax_statuses_statusable_idx' :: a foreign key

add_index :bulkrax_statuses, [:runnable_id, :runnable_type], name: 'bulkrax_statuses_runnable_idx' :: a foreign key

add_index :bulkrax_statuses, :error_class :: when querying what's in error, this index is helpful; also one used for grouping.

consider removing coverage task


custom domain message to create cname is broken

Version information

OS: docker Ubuntu 20.04
Branch: development
commit: 59ff07cf80c61c273b067abce18704f0a8542f1d
Browser: Version 84.0.4147.125 (Official Build) (64-bit)
explorer: testnet

Commit_ID b66bb44f5f640eaa2414ca2a0902cada139b6a56 , Branch  development


Make transport simulator bot

We need a bot that can simulate a transporter. I think that bot should work the same way the taxi bot does, but use slightly different need descriptions.
As we progress with the conversation state machine, this bot needs to generate events about the transport as prescribed by the state machine - but that is for later.

moved to our internal kanbanboard


Advancing 1.20.1 release to status: admiral

Advancing 1.20.1 release to status: admiral

Ignore this, testing something


Encode/decode problems

Hello.
I have some problems with consuming messages from kafka which were encoded using eavro.
I encode message, send it to kafka and then I'm trying to consume it using confluent's kafka-avro-console-consumer from http://docs.confluent.io/1.0/quickstart.html
The problem is that once message is sent, consumer dies while trying to consume the message without any errors, just with Consumed 0 messages.
To investigate the issue I tried to consume message from kafka using elixir's kafka_ex consumer. After consuming a message I decoded it and saw that it has extra empty string at the end of the message. Then I run example from the README and got the following:
12> Msg = eavro:encode(Schema, [<<"John">>, 23, true]).
<<8,74,111,104,110,46,1>>
13> eavro:decode(Schema, Msg).
{[<<"John">>,23,true],<<>>}

As you can see there <<>> at the end of the decoded message.
Since kafka-avro-console-consumer tries to validate decoded message against schema I assume that it dies because of this extra empty string. Is there a way to encode original message the way that after decoding it doesn't have this extra empty string?
Thanks!

Hello,
it seems you slightly misunderstand the format of a result returned by eavro:decode. The eavro:decode accept schema and a binary buffer, and returns a tuple containing data decoded at the first element, and the rest of a buffer at the second element, i.e. {Result, Buff1} = eavro:decode(Schema, Buff0). This is the way this decoder is working: it takes a schema and a byte buffer, decodes some first bytes according to schema, and returns a decoded result and a rest of the buffer to be able to continue further. So, decoder have returned a <<>> at the second element of a tuple this just means that there is no data any more, the decoding is finished!
Nevertheless, I admit that the problem you experiencing still may be caused by bug in decoder. It may be good idea to encode the problematic message by codec used by Kafka, and to send the byte array as is just right here?

Hello.
First of all, thanks for the quick answer and for the great explanation!
So I used Kafka REST Proxy http://docs.confluent.io/1.0/kafka-rest/docs/intro.html to emit a message encoded using Kafka's avro codec:
# Produce a message using Avro embedded data, including the schema which will
# be registered with the schema registry and used to validate and serialize
# before storing the data in Kafka
$ curl -X POST -H "Content-Type: application/vnd.kafka.avro.v1+json" \
      --data '{"value_schema": "{\"type\": \"record\", \"name\": \"User\", \"fields\": [{\"name\": \"name\", \"type\": \"string\"}]}", "records": [{"value": {"name": "testUser"}}]}' \
      "http://localhost:8082/topics/avrotest"
  {"offsets":[{"partition":0,"offset":0,"error_code":null,"error":null}],"key_schema_id":null,"value_schema_id":21}

Then I fetched it(output from elixir console):
KafkaEx.fetch("avrotest", 0)
[%KafkaEx.Protocol.Fetch.Response{partitions: [%{error_code: 0,
     hw_mark_offset: 1, last_offset: 0,
     message_set: [%{attributes: 0, crc: 22894542, key: nil, offset: 0,
        value: <<0, 0, 0, 0, 17, 16, 116, 101, 115, 116, 85, 115, 101, 114>>}],
     partition: 0}], topic: "avrotest"}]

then I extracted :value into variable and performed decoding:
iex(7)> msg = List.first(m)[:value]
<<0, 0, 0, 0, 17, 16, 116, 101, 115, 116, 85, 115, 101, 114>>
iex(8)> schema = :eavro.read_schema('schema.avsc')
{:avro_record, :User, [{"name", :string}]}
iex(9)> :eavro.decode(schema, msg)
{[""], <<0, 0, 0, 17, 16, 116, 101, 115, 116, 85, 115, 101, 114>>}

I got this.
It's not related to eavro I guess(I haven't checked yet) but most probably the reason why eavro couldn't decode message which were sent by confluent kafka producer and why conflient kafka consumer couldn't consume message which was encoded by eavro is the following: there are to ways of telling to avro registry which schema should be used to decode a message. Schema id could be encoded within a message itself or schema could be specified during decoding. So when I was trying to decode message which were sent by avro producer, eavro couldn't decode it because first 5 bytes are reserved by schema id and I guess eavro isn't aware of it. And when I was trying to consume a message(which were encoded by eavro) using confluent kafka consumer I should have specified schema to decode message because as I understand eavro doesn't include schema in the encoded message.
That's a theory, I'll try to prove it today's evening.

So I added 'magic byte' plus schema id as 4 bytes and avro consumer started to consume and decode messages!
<<0>> <> <<schema_id :: size(32)>> <> encoded_message_by_eavro

Yes ,the magic byte (0) and schema ID (4 byte integer), are actually a header which is added (if I correctly understand) by Kafka producer, and should be striped by Kafka consumer. So this header is not a part of an Avro format, it is just a trick to make it possible to deserialize Avro message later, using schema registry (Zookeeper?). Here http://stackoverflow.com/a/31206063 I've found some explanations conserning to this topic.
Hence I consider this issue closed.

I thought it might be useful https://github.com/SIfoxDevTeam/eavro/pull/13


Bug 1934637: Honor all subscriptions to a package

Cherry-pick of #2009 to release-4.6.

/hold

/bugzilla refresh

/hold cancel

/lgtm

/retest

/lgtm cancel

/lgtm

CI failed six times in a row. @benluddy could you take a look?

Hmmm, aside from the first failure, these seem to be related to a recent CI outage.

/retest

/retest

/retest


LdapDnsProviderTest should associate with one issue

In the problem list, one test should associate with one issue. Please updated LdapDnsProviderTest to associate with https://github.com/adoptium/aqa-tests/issues/2355 Only. We should remove https://github.com/adoptium/aqa-tests/issues/2350
https://github.com/adoptium/aqa-tests/blob/57b6ea136264168339c54d4bbfdfff017986c1e8/openjdk/excludes/ProblemList_openjdk8.txt#L425
https://github.com/adoptium/aqa-tests/blob/57b6ea136264168339c54d4bbfdfff017986c1e8/openjdk/excludes/ProblemList_openjdk8-openj9.txt#L350
Related: https://github.com/adoptium/aqa-tests/issues/3378#issuecomment-1061270944

Hi, I am Abhijeet Jejurkar, a contributor to OpenForce 2022. I would like to work on this issue. I would be making a PR as soon as I am done with resolving the issue. Thank you


add placeholder screen when program has not run yet

make it clear on startup that you have to run code to make the world visible

done


chore: update eslint-config-liferay to v11.0.1

New:

destructure-requires
imports-first (this one was in eslint-config-liferay v10.0.0 but not turned on by default).
no-require-and-call

Just started reviewing :)


WSL + ubuntu 18.04 bulid errors

Hi, when i am trying to build npiperelay.exe under WSL+Ubuntu 18.04 i get error below:
➜  ~ go get -d github.com/jstarks/npiperelay
go/src/github.com/jstarks/npiperelay/npiperelay.go:12:2: build constraints exclude all Go files in /home/pvm/go/src/golang.org/x/sys/windows
Please advise if there any workaround.

I did this to get it to work.
env GOOS=windows GOARCH=amd64 go get -d github.com/jstarks/npiperelay
env GOOS=windows GOARCH=amd64 go build -o /mnt/c/Users/username/bin/npiperelay.exe github.com/jstarks/npiperelay

I ended up git sync the entire repo and then ran the build command from that directory to get it to work.  The go get -d didn't work for me for some reason.


MethodError: no method matching get_layout_at!(::GridPosition; createmissing=true)

Based on https://discourse.julialang.org/t/in-makie-when-should-a-function-accept-fig-1-1-as-input-vs-an-axis/57399:
using AbstractPlotting # v0.15.25
function make_heatmap!(ax)
    x = range(0,1; length=100)
    y = 1:100
    heatmap!(ax, x, y, rand(100,100))
end
function make_colorbar!(fig)
    Colorbar(fig, width = 25)
end
function make_heatmap_with_colorbar!(fig)
    ax = Axis(fig[1,1])
    make_heatmap!(ax)
    make_colorbar!(fig[1,2])
    return ax
end
fig = Figure()
fig1 = fig[1,1]
make_heatmap_with_colorbar!(fig1[1,1])

yields
ERROR: MethodError: no method matching get_layout_at!(::GridPosition; createmissing=true)
Closest candidates are:
  get_layout_at!(::AbstractPlotting.FigurePosition; createmissing) at /Users/eph/.julia/packages/AbstractPlotting/l5lsp/src/figures.jl:142
  get_layout_at!(::AbstractPlotting.FigureSubposition; createmissing) at /Users/eph/.julia/packages/AbstractPlotting/l5lsp/src/figures.jl:158
Stacktrace:
 [1] get_layout_at!(fsp::AbstractPlotting.FigureSubposition{AbstractPlotting.FigurePosition}; createmissing::Bool)
   @ AbstractPlotting ~/.julia/packages/AbstractPlotting/l5lsp/src/figures.jl:161
 [2] setindex!(parent::AbstractPlotting.FigureSubposition{AbstractPlotting.FigureSubposition{AbstractPlotting.FigurePosition}}, obj::Axis)
   @ AbstractPlotting ~/.julia/packages/AbstractPlotting/l5lsp/src/figures.jl:132
 [3] #_layoutable#10
   @ ~/.julia/packages/AbstractPlotting/l5lsp/src/makielayout/layoutables.jl:56 [inlined]
 [4] _layoutable
   @ ~/.julia/packages/AbstractPlotting/l5lsp/src/makielayout/layoutables.jl:55 [inlined]
 [5] #_#9
   @ ~/.julia/packages/AbstractPlotting/l5lsp/src/makielayout/layoutables.jl:49 [inlined]
 [6] Layoutable
   @ ~/.julia/packages/AbstractPlotting/l5lsp/src/makielayout/layoutables.jl:49 [inlined]
 [7] make_heatmap_with_colorbar!(fig::AbstractPlotting.FigureSubposition{AbstractPlotting.FigurePosition})
   @ Main ./REPL[6]:2
 [8] top-level scope
   @ REPL[9]:1

I think this is supposed to work?

MWE:
fig = Figure()
Axis(fig[1,1][1,1][1,1])

Definitely looks like a bug ;)

I'll check it out, probably indexed a .layout somewhere which turns everything into gridpositions (which don't have a reference to the figure)

Actually I was thinking about adding a parent field to GridLayout again, which could be either nothing, GridLayout or something like Figure. Then I could remove the duplication of GridPosition and FigurePosition, which kind of do the same thing, just one has a Figure on top and therefore can be plotted into. Currently, if you manually create a gridlayout and put that into a layout of a figure, you can't plot into that gridlayout directly because it doesn't know it's in a Figure's layout

do you know of a workaround for now, by the way?

this should fix it https://github.com/JuliaPlots/AbstractPlotting.jl/pull/662


Added 'next' to error handler

Wihtout next parameter, the handler won't fire!

Nice catch. I was thinking one thing that it may throw error as after sending the response, we should not go forward for anything else. So the next param is fine. And obviously its needed otherwise it'll not match the signature. But the calling of next() may cause problem. isn't it?


Partial preemption for groups with multiple sequences

Partial preemption for groups with multiple sequences.
Fixed a bug in can_append_stots()

Ticket: 140648

LGTM


appprovider: return a map on /app/list

This is to restore the previous behavior on which the ownCloud web was developed (cf. example).
The return structure of the HTTP gateway for the AppProvider ListMimeTypes is now:
'application/fileFormat1': {
    mime_type: 'application/fileFormat1',
    name: 'App Format 1',
    icon: 'https://www.example-mimetypes.com/assets/icon-fileformat1.png',
    description: 'Application Format 1 File',
    app_providers: [
      { name: 'ExampleApp1Name', icon: 'https://www.example-app1.com/assets/icon.png' }
      { name: 'ExampleApp2Name', icon: 'https://www.example-app2.com/assets/icon.png' }
    ],
    default_app: 'ExampleApp1Name',
  },
...

LGTM!

@ishank011 @glpatcern
Do we really need this?
My test setup works and returns something like this on /app/list:
{
  "mime-types": [
    {
      "mime_type": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
      "ext": "xlsx",
      "app_providers": [
        {
          "name": "Collabora",
          "icon": "https://www.collaboraoffice.com/wp-content/uploads/2019/01/CP-icon.png"
        }
      ],
      "name": "Microsoft Excel",
      "description": "Microsoft Excel document"
    },
    ....
    ```

@wkloucek I was actually wondering how it did not break for you, given that the structure is different (list vs map) and Lisa had issues with that when merging the new frontend...

@wkloucek found this older structure in the tests: https://github.com/owncloud/web/blob/master/packages/web-app-files/tests/fixtures/mimeTypes.js
export default {   'application/fileFormat1': {     app_providers: [       { name: 'ExampleApp1Name', icon: 'https://www.example-app.com/assets/icon1.png' }     ]   },   'application/fileFormat2': {     app_providers: [       { name: 'ExampleApp2Name', icon: 'https://www.example-app.com/assets/icon2.png' }     ]   },   'application/fileFormat3': {     app_providers: [       { name: 'ExampleApp1Name', icon: 'https://www.example-app.com/assets/icon1.png' },       { name: 'ExampleApp2Name', icon: 'https://www.example-app.com/assets/icon2.png' }     ]   } }
Can @pascalwengerter  maybe say, which one we should use?

This is to restore the previous behavior on which the ownCloud web was developed (cf. example).
The return structure of the HTTP gateway for the AppProvider ListMimeTypes is now:
'application/fileFormat1': {
    mime_type: 'application/fileFormat1',
    name: 'App Format 1',
    icon: 'https://www.example-mimetypes.com/assets/icon-fileformat1.png',
    description: 'Application Format 1 File',
    app_providers: [
      { name: 'ExampleApp1Name', icon: 'https://www.example-app1.com/assets/icon.png' }
      { name: 'ExampleApp2Name', icon: 'https://www.example-app2.com/assets/icon.png' }
    ],
    default_app: 'ExampleApp1Name',
  },
...

Author

This is to restore the previous behavior on which the ownCloud web was developed (cf. example).
The return structure of the HTTP gateway for the AppProvider ListMimeTypes is now:
'application/fileFormat1': {
    mime_type: 'application/fileFormat1',
    name: 'App Format 1',
    icon: 'https://www.example-mimetypes.com/assets/icon-fileformat1.png',
    description: 'Application Format 1 File',
    app_providers: [
      { name: 'ExampleApp1Name', icon: 'https://www.example-app1.com/assets/icon.png' }
      { name: 'ExampleApp2Name', icon: 'https://www.example-app2.com/assets/icon.png' }
    ],
    default_app: 'ExampleApp1Name',
  },
...

Please note that the linked example is a fixture I'm using internally for unit tests in web, and which refers to the Vuex store where I'm saving the mimeTypes server response into an object.
Below is the server response I currently get on /app/list (basically same as @wkloucek's) and against which I developed the AppProvider in the current web master - it's an object that contains an array of objects. Not sure why this change is suggested here as it would (from my current understanding) need adjustments in web, too


feat: don't generate license if not explicitly asked

Also fix invalid tests.
Fixes #7703

@helderco I'm closing this PR for now and will open a new one when we got an issue for it.


Spell Parsing needs Refactoring

As Spells are now created as embedded items after actor creation, stuff happening in spellparsing where values are written to dataoutput get not translated (fully) to the actor.

Closed. Spell-parsing will be re-integrated in 3.2


Error while loading DP

purpur 1.21
[14:58:11 ERROR]: Couldn't parse element minecraft:loot_table/jmmf:eating/teacup - Failed to parse either. First: Unknown registry key in ResourceKey[minecraft:root / minecraft:loot_function_type]: minecraft:set_nbt; Second: Not a json array: {"function":"set_nbt","tag":"{smithed:{id:'jmmf:teacup'}}"}; Failed to parse either. First: Unknown registry key in ResourceKey[minecraft:root / minecraft:loot_function_type]: minecraft:set_nbt; Second: Not a json array: {"function":"set_nbt","tag":"{CustomModelData:481004}"}

found the issue, it was an old file from an older version I forgot to remove, will fix in a bit

Should now be resolved on the most recent version


add support for k6n10 factor family

Added support for K6N10 family with soft adder carry chain and True Dual Port BRAM
Signed-off-by: Tarachand Pagarani<EMAIL_ADDRESS>

@kgugala, @mkurc-ant please review and merge this PR

@mkurc-ant, i have taken care of review comments from you as well as updated the tests for k6n10f. Kindly review and merge.


Arch package requires semantic_version

Hi,
Just tried toinstall etesync-dav on a new laptop using pikaur on Arch Linux (pikaur -Syu etesync-dav).
I got a ModuleNotFoundError: No module named 'semantic_version' error during the build of the python-etebase AUR package.
I have python-semantic-version installed globally but I guess it's not in the build env?
I presume it just needs to be added as a dependency?
P.S. Sorry for the lack of traceback, said new laptop doesn't have a GUI yet.

It's needed by python-setuptools-rust which has it as a dep: https://aur.archlinux.org/packages/python-setuptools-rust/
Which is why I guess you have it installed. I'm not sure why it's not finding it for you. It works for people and it works for me.
Try running Python and then: import semantic_version, does that work?

Okay, my bad. This looks like a python 3.9 issue - my upgrade to 3.9 means the system thinks I have all these packages but they're actually installed in the python 3.8 libs. Solved now, thanks.


[orchestra2md] Redundant newline for conversion of DC terms

DC terms table is not created correctly in Tablature v1.0.2. The values of the meta-data elements are created as new lines in markdown instead of continuing on the same line as the element name. The resulting table cannot be rendered correctly, e.g. by Pandoc.
| Term        | Value                                                             |
|-------------|-------------------------------------------------------------------|
| title       |
            FIX.Latest_EP272                                     |
| created     |
            2022-08-15T16:15:49.035692                           |
| date        |
            2022-08-04T15:17:49Z                                 |
| rights      |
            Copyright (c) FIX Protocol Ltd. All Rights Reserved. |
| conformsTo  |
            Orchestra v1.0                                       |
| source      |
            FIX Unified Repository 2010 Edition                  |
| contributor | playlist
                                                         |
| date        | 2022-09-05T18:39:31.877Z
                                         |

The table should be created as follows in markdown:
| Term        | Value                                                |
|-------------|------------------------------------------------------|
| title       | FIX.Latest_EP272                                     |
| created     | 2022-08-15T16:15:49.035692                           |
| date        | 2022-08-04T15:17:49Z                                 |
| rights      | Copyright (c) FIX Protocol Ltd. All Rights Reserved. |
| conformsTo  | Orchestra v1.0                                       |
| source      | FIX Unified Repository 2010 Edition                  |
| contributor | playlist                                             |
| date        | 2022-09-05T18:39:31.877Z                             |

Problem not reproduced in unit test
| Term      | Value                                                |
|-----------|------------------------------------------------------|
| title     | Orchestra                                            |
| creator   | unified2orchestra.xslt script                        |
| publisher | FIX Trading Community                                |
| date      | 2020-07-19T09:28:08.308Z                             |
| format    | Orchestra schema                                     |
| source    | FIX Unified Repository                               |
| rights    | Copyright (c) FIX Protocol Ltd. All Rights Reserved. |

I think you used the XML created by the XSLT script, not by Python. Please try again with the XML below:
    <fixr:metadata>
        <dcterms:title>
            FIX.Latest_EP273</dcterms:title>
        <dcterms:created>
            2022-08-29T14:23:11.894478</dcterms:created>
        <dcterms:date>
            2022-08-23T13:14:11Z</dcterms:date>
        <dcterms:rights>
            Copyright (c) FIX Protocol Ltd. All Rights Reserved.</dcterms:rights>
        <dcterms:conformsTo>
            Orchestra v1.0</dcterms:conformsTo>
        <dcterms:source>
            FIX Unified Repository 2010 Edition</dcterms:source>
    </fixr:metadata>


fix typo?

I'm making the assumption this was unintentional. Apologies if I'm wrong!

:o nice catch! thanks!


Update http4s-circe, http4s-dsl, ... to 0.21.19

Updates

org.http4s:http4s-circe
org.http4s:http4s-dsl
org.http4s:http4s-server

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

Applied Migrations

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5

Documentation:

https://github.com/http4s/http4s/releases/tag/v0.21.5

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

labels: library-update, semver-patch, scalafix-migrations

@ChristopherDavenport hi!
I wanted to ask, what is the status of this library, is it still under active development?

cc @hrhino @rsoeldner

Superseded by #350.


Add a way to generate a frr with webhooks on ocp manifest

We add a local overlay and we clone metallb to build a full manifest with the webhook settings for metallb so we don't tamper metallb with ocp specific content. The operator is already aware of openshift.

/lgtm

Thanks @fedepaol , this would help #179 to generate manifests for openshift and all the CI failures would be fixed there.

Merging this with failing CI, the changes are not related to the failures and the fix for lint is in @pperiyasamy's pr


dnsproxy: 0.39.2 -> 0.39.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AdguardTeam/dnsproxy/releases.
meta.description for dnsproxy is: "Simple DNS proxy with DoH, DoT, and DNSCrypt support"
meta.homepage for dnsproxy is: "https://github.com/AdguardTeam/dnsproxy"
meta.changelog for dnsproxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4/bin/dnsproxy passed the binary check.

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

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

found 0.39.4 with grep in /nix/store/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4

found 0.39.4 in filename of file in /nix/store/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4

directory tree listing: https://gist.github.com/38972c63556a4cafdc56998168aa8823

du listing: https://gist.github.com/d326b3d6ff21dda53e9b0770f3a3cfad

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
dnsproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dnsproxy https://github.com/r-ryantm/nixpkgs/archive/4f9e77d17cfb4fb9f93bdc7db92763771c3ededb.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/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4
ls -la /nix/store/ywfnc1xxa1bxkv5y7cr4qfima7rya9la-dnsproxy-0.39.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dnsproxy

Maintainer pings
cc @contrun @kalbasit for testing.

Result of nixpkgs-review pr 136000 at 4f9e77d1 run on aarch64-linux 1

1 package built successfully:

dnsproxy

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/networking/dnsproxy/default.nix:21:5:
   |
21 |     license = licenses.gpl3;
   |     ^


all: remove unnecessary type conversions

This is going to cause conflicts with #3966, can you revert the promql changes for now?

@brian-brazil Updated.

Thanks!


Update/Add cdklocal

Tool name
cdkocal
Tool license
Apache-2.0
Add or update?

[X] Add
[ ] Update

Desired version
latest
Approximate size
27.5 kB
Brief description of tool
This project provides a thin wrapper script cdklocal for using the AWS CDK library against local APIs provided by LocalStack.
LocalStack is a cloud service emulator that runs in a single container on your laptop or in your CI environment. With LocalStack, you can run your AWS applications or Lambdas entirely on your local machine without connecting to a remote cloud provider! Whether you are testing complex CDK applications or Terraform configurations, or just beginning to learn about AWS services, LocalStack helps speed up and simplify your testing and development workflow.
This tool can be used with the localstack/localstack as a service container.
URL for tool's homepage
https://www.npmjs.com/package/aws-cdk-local
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Virtual environments where you need the tool

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
# install LocalStack cli and awslocal
pip install localstack awscli-local

Tool installation time in runtime
lest than 10 seconds
Are you willing to submit a PR?
if needed

Hey @Simonl9l.
Considering the fact that tool is pretty small and can be installed in runtime, we wouldn't like to bake it into the image due to maintenance concerns


Enable updating request status in sandbox mode

As of right now there is no PUT method provided for the /request endpoint. Documented here: https://developer.uber.com/docs/sandbox

Added with commit 112244b8ea0a4fe00920a08368fa044d8df93dba


Component props default value/type error

Vue version
latest
Link to minimal reproduction
https://sfc.vuejs.org/#eNrlVUuPmzAQ/itTLqRSAtpLVVESabuXHlfqoYe6BxKchBXYlj2hWVH+e8cPCEn21b02l+CZb57fZ+iiW6WS9sCjLMrNRlcKwXA8qBUTVaOkRuhA8+1c82KDVcuhh62WDcQUE4+Y+0JzgcGTpP5o0xKEiY0UBqExO1jaXLP4G69rCT+krssP8ccTZCt14zC+1qxjAgC5wQxiytQTNE99l9QfHZA3qi6Q0wkg39+sus7V6fs8pZOzVkIdENpFI0teL1lEfhY5l3OH1jNbm7z2j0WQEiBPx/TRPPKTLppCJQ9GCtqX644Fh2FRBs5ibTS5PbNoj6hMlqZmu7HreDCJ1LuUnhJ9EFg1POGmWay1/G24psQsmk9ypGRsuV5QhyXXXL+U8wJ6ldem7WmHNMqJngnrdSF2yxhNfMn/3b6qy5FadwrMTgG3QuKe63NcMAa451hpqQyRXPJtJfi9PeVub3bzboUMGXrSDepK7IbOV7NRKrLmSS13M5cssZFziJVn0oZaUT2NS6z7GvysrBjmZdV6ubhH2NSFMaSUtTwGHdnfiPI/v7Q7SRsSto6bc8SmU/Bo9TEkRBl06HolMWbrQl+YrD4vU/1jdwNjb2+SYWhyCH1vr8PT5Ia5vRt8rDmYjVS8dMCExgiXai01CTuDG3UE4rUqv3i7KsqSRJJ9VsdgaQq9q8QCpcpuPgUr6YcotuntXR5F/KL+X9WrHBQKf6g90lpBQzCkDWTDmTyDiL1+3yK0S76oEuCj4nQ7Ovcgt87W01QBkq/1uOcQ0Rb1wYd4bBDamWL2p6jzkjTDVUlre76k9Z5KeuxVySeIH+iYvCvex4r/WjhWgmT8AD+/OwLm8NVT8svpwb1mHVPn4ACag4/y4Fc+PWfU/Vfc9X8Bc0+1bg==
Steps to reproduce

In order to restore my case more realistically, I created one more file, maybe it is not a minimal copy, sorry.

I defined the child component with type boolean or string, and i use it in initial. I found that it wasn't using the value I passed in when I initialized.
I guess this playground can explain everything, hope it is meaning enough.
What is expected?
Although I pass in an empty string when initializing, i want subcomponet use the porps value from parent continue. Instead of subcomponents transforming themselves.
What is actually happening?
I don't quite understand why it converts the value by itself.
It seems to be related to the order of the prop types written.
System Info
No response
Any additional comments?
I don't know if there is a related issue in this case, please forgive me for not looking for similar cases and reporting directly.

I think this may be a bug. During the normalization process of props, when the type is boolean or string, the incoming value of the string type will be prioritized as a boolean type for normalization

It is indeed a bug that violates the documented behavior, but in the opposite way than you might have expected:

When a prop is declared to allow multiple types, e.g.
export default {
  props: {
    disabled: [Boolean, Number]
  }
}

The casting rules for Boolean will apply regardless of type appearance order.

https://vuejs.org/guide/components/props.html#boolean-casting

This is documented behavior now - it is intentional behavior for the current version range. Whether this should change will have to wait until a major version.


TextField Pixel overflow

I have an input box, and when I select a piece of text in the input box, the pixels on the right overflow.

Hi @yousaywhat
could you please provide your updated  flutter doctor -v
and a minimal code sample to reproduce the problem?
Thank you

@iapicca

Can someone help me with this problem

Hi @yousaywhat
Not able to reproduce this issue on latest dev channel

flutter doctor -v
[✓] Flutter (Channel dev, v1.18.0-8.0.pre, on Mac OS X 10.15.4 19E287, locale
    en-GB)
    • Flutter version 1.18.0-8.0.pre at /Users/taha/Code/flutter_dev
    • Framework revision e0c63cd35e (12 days ago), 2020-04-23 22:29:01 -0400
    • Engine revision d2ec21221e
    • Dart version 2.9.0 (build 2.9.0-3.0.dev b0d35855d8)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.44.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.1

[✓] Connected device (5 available)
    • SM M305F      • 32003c30dc19668f          • android-arm64  • Android 10
      (API 29)
    • Taha’s iPhone • 00008020-001059882212002E • ios            • iOS 13.4.1
    • macOS         • macOS                     • darwin-x64     • Mac OS X
      10.15.4 19E287
    • Web Server    • web-server                • web-javascript • Flutter Tools
    • Chrome        • chrome                    • web-javascript • Google Chrome
      81.0.4044.129

• No issues found!

if you're still experiencing this problem, please create a new issue and provide the information
required in the template.
Thank you


Bidscoin 3.7.0 menu entry

@stebo85 Just verifying whether the menu entry went through or if I still need to do something?
Do I need to wait until tomorrow to see the new menu entry in neurodesktop, in neurodesktop-dev ? or can I already test it now?
Please update the instructions in https://neurodesk.github.io/developers/new_tools/add_tool/ so it will be clear to developers. If the standard process is that the developer receives an error message (like I did: "[NeuroDesk/neurocommand] PR run failed: Neurocommand CI/CD - Bidscoin 3.7.0 menu entry (fd0faab)"), and only then you/Aswin intervene to make things work, please mention it there. That would be super useful.

The new menu entry will be available after 24 hours in neurodesktop:latest and will be announced publicly with the next release. I add this to the documentation.
I fixed the error you saw in the CI just now.


[FancyZones] Favorites hotkey

I find myself wanting to switch layouts quickly, especially if I'm collaborating with someone, virtually. (Oh, I need to take some notes, let's stop using focused grid 3 and start using standard grid 2.)
One idea of how to implement this would be a way to assign a half-dozen hotkeys so that the user could hit, say, "Win-'-1", "Win-'-2", etc. to quickly switch to frequently used layouts. A new, read-only tab should be added to show the hotkeyed layouts.

This would be very nice for quickly changing the arrangement of windows. Just allow assigning any hotkey to select a grid layout with the possibility of rearranging windows accordingly when it is selected.

@jburkett @laxu
the tracker for this issue is https://github.com/microsoft/PowerToys/issues/1411
Closing this as duplicate.
Thanks.


binding.open yarn cache problem

Another deploy, another error. It worked a few days ago. Now:
[3/5] Fetching packages...
02/04 05:10 AM (5m)
info There appears to be trouble with your network connection. Retrying...
02/04 05:11 AM (5m)
info There appears to be trouble with your network connection. Retrying...
02/04 05:11 AM (4m)
info There appears to be trouble with your network connection. Retrying...
02/04 05:12 AM (4m)
info There appears to be trouble with your network connection. Retrying...
02/04 05:12 AM (3m)
fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/tmp/.cache/yarn/v4/npm-react-native-web-0.10.0-7c67a25d1262f01d462b3a11cc603aef47537d18/node_modules/react-native-web/dist/cjs/exports/StyleSheet/StyleSheetValidation.js'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.writeFileSync (fs.js:1299:33)
    at Object.fs.createWriteStream.args [as createWriteStream] (/tmp/utils/node_modules/@now/build-utils/fs/bootstrap-yarn.js:30:6)
    at onfile (/var/task/bin/yarn:45435:20)
    at /var/task/bin/yarn:45467:31
    at /var/task/bin/yarn:45499:7
    at /var/task/bin/yarn:52814:26
    at FSReqWrap.oncomplete (fs.js:153:5)
02/04 05:12 AM (3m)
Error: Exited with 1
    at ChildProcess.child.on (/tmp/utils/node_modules/@now/build-utils/fs/run-user-scripts.js:14:16)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at maybeClose (internal/child_process.js:925:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
02/04 05:12 AM (3m)
patching https://api-bru1.zeit.co/v2/now/deployments/dpl_5mejKJk65L4ac33dSx9jPtzkNf2R/builds/bld_kqvf6hmd1 with {"readyState":"ERROR","errorCode":"BUILD_FAILED_2"}

The issue is supposed to be fixed. Please try again. Feel free to reopen if something is still wrong.


Type checks on some ill-formed record operators crashes with an uncaught TypeError

I first noticed this in the simulator
>>> {a: 1}.field()
node:internal/readline/emitKeypressEvents:74
            throw err;
            ^

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at fieldConstraints (/apalache/quint/quint/dist/src/types/specialConstraints.js:71:29)
    at specialConstraints (/apalache/quint/quint/dist/src/types/specialConstraints.js:36:20)
    at /apalache/quint/quint/dist/src/types/constraintGenerator.js:102:73
    at EitherConstructor.chain (/apalache/quint/quint/node_modules/@sweet-monads/either/cjs/index.js:108:16)
    at TypeInferrer.exitApp (/apalache/quint/quint/dist/src/types/constraintGenerator.js:99:35)
    at walkExpression (/apalache/quint/quint/dist/src/IRVisitor.js:291:25)
    at walkDefinition (/apalache/quint/quint/dist/src/IRVisitor.js:209:13)
    at /apalache/quint/quint/dist/src/types/inferrer.js:26:44
    at Array.forEach (<anonymous>)
    at TypeInferrer.inferTypes (/home/sf/Sync/informal-systems/apalache/quint/quint/dist/src/types/inferrer.js:25:14)

Node.js v19.6.0

But (as the stack trace indicates), it's a crash during typechecking:
$  cat t.qnt
module t {
    def r() = Rec("a")
}

$  quint typecheck t.qnt
quint typecheck <input>

check types and effects of a Quint specification

Options:
  --help     Show help                                                 [boolean]
  --version  Show version number                                       [boolean]
  --out      output file (suppresses all console output)                [string]

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))

This is related to #1054, but comes specifically from the unguarded array accessing in the record operators, e.g.:
https://github.com/informalsystems/quint/blob/123a237513bbc92d7b629566a5573f3b076f66ab/quint/src/types/specialConstraints.ts#L91-L96
Which will give us an undefined value for the second set of bindings thanks to this lovely behavior in JS:
> const [a, b] = []
undefined
> a
undefined
> b

I agree that we should handle errors a bit more user-friendly. At least in the CLI. Perhaps, this is what we actually want to see in the plugin output.

This is fixed with #1078
>>> {a:1}.field()
static analysis error: error: [QNT000] Operator expects 2 arguments but was given 1
Checking arity for application of field
Generating constraints for 1

{a:1}.field()
^^^^^^^^^^^^^

compile error: error: Not enough arguments
{a:1}.field()

The more general issue of uncaught exceptions is tracked in another ticket.


PZEM-004 vs PZEM-004T

Hi,
I have these two versions with their documentations.
At first I thought they are the same, 004 has display 7seg, 004T doesn’t have display.
But it’s wrong, the protocol between 004 and 004T is different, 004T I use Modbus-RTU
And the protocol you describe in your readme match to the PZEM-004.
So your library should be named PZEM-004
Or maybe they have changed the protocol without modify the name, I hope not ???
There is on internet a lot of confusion with this two modules.

Hi, I guess they change versions as they want (
The library was written for the board like on the image below. It says "V1.0" - maybe that's the key.

I just got information from Peacefair
From 004T v3.0 protocol is Modbus-RTU, previous version was not !
So they changed the protocol without modifying the name ! So bad!

And the icing on the cake:
PZEM-004 v3.0 with display doesn’t  have Modbus-RTU protocol !


Repeatable migrations that were updated in a newer version should be marked as future

Which version and edition of Flyway are you using?
4.2.0
If this is not the latest version, can you reproduce the issue with the latest one as well?
I haven't tested on the latest as 4.2.0 is the latest w/ JDK 7 compat (we can't afford enterprise).
But it appears looking at the code and documentation the behavior should be the same.
If really desired I could setup a project w/ the latest.
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java and Maven
Which database are you using (type & version)?
Postgresql
Which operating system are you using?
Linux
What did you do?
Ran flywaydb (maven and java) on a schema with a future migrations already applied w/ the default of ignoreFutureMigrations = true
What did you expect to see?
While I expected the application not to fail fast given ignoreFutureMigrations doc I didn't expect the old repeatable migrations to be applied.
What did you see instead?
See above.
I didn't even know about ignoreFutureMigrations allowing repeatable migrations to run being  the default till we had extremely unusual behavior in production where we were systematically updating and sort of canary testing images. Older images were needed to be run albeit rebooted while new images were working with a new schema.
Unfortunately one of the older images kept migrating a stored procedure back (in hindsight we should have put that in a different repeatable SQL script but we still probably would have had the issue).
Now we enforce ignoreFutureMigrations to false almost everywhere but I'm still extremely shocked about the above behavior and how little its documented.
This could have been far more damaging but luckily was not.
If a new migration is present and ignoreFutureMigrations is true I would expect the flywaydb to do nothing if run on an older version and not migrate anything.
Give that some people are possibly expecting this behavior (backwards compatibility) it seems new configuration is required to enable what we were originally trying to do in production.

This is really a tricky one.
A. Your situation is as follows:

one had an original repeatable migration in V1 of the software
updated it for V2
wasn't happy with the changes and reverted the software to V1
expected the migration to not be reapplied and instead of having it being marked as future.

B. The very same situation could also be interpreted very differently:

one had an original repeatable migration in V1 of the software
updated it for V2
wasn't happy with the changes and reverted them for V3
fully expecting them to be applied as part of the V3 rollout instead of having the migration being marked as future

Since Flyway doesn't have access to the application version, both of these appear identical with no way to automatically decide which variant should used.
Flyway currently always chooses the B variant which is the correct choice in the overwhelming majority of the cases. Until we find a clean way to differentiate, I don't see how we could support the A variant.

As Axel's comment says, Flyway has an opinionated workflow. Unfortunately we can't support every case.


feat: add interface to produce blocks with custom timestamps

This PR adds a new method produceBlocks to the Provider class that lets users produce blocks with custom parameters.
Closes #697

I have noted that a test is failing here. It is passing locally 🤔


Custom Commands

Hello, I have the signed NDA from novastar, can someone help me with how to implement  custom commands for h series?
e.g. Fade to Black or Take?

Did they send you the H series protocols document?

On Sep 3, 2023, at 12:20 AM, kman1898 @.***> wrote:
rom novastar, can someone help me with how to implement custom commands for h series?
e.g. Fade to Black or Take?

Yes, I’ve got it for a few different nova products h series included.
but I don’t want to send the incorrect command and the commands are a bit daunting to the uninitiated

Never mind. Apparently I was looking at the wrong command document. The h series one is very detailed in how these commands are made.


Added screenshot_root_directory

This enhancement is to better support PageObjects as discussed here.
These changes are not necessarily final and reviews are welcome.
This PR would essentially provides a new argument for S2L called screenshot_root_directory which can be provided to set the default root directory that screenshots will be stored in. Subdirectories should still be managed by the relevant keywords.
By default the screenshot_root_directory argument is set to None and will use RF's log directory as the root directory for screenshots. If one is trying to run a screenshot keyword while RF isn't running and fails to provide screenshot_root_directory then the current working directory will be used instead.
Pre-merge checklist

[x] Import RobotNotRunningError
[ ] Add a test to use screenshot_root_directory
[x] Add Documentation
[x] Update changelog

@pekkaklarck, do you have any advice on testing this feature? Is there a way to "unload" a library?

Would Reload Library keyword, available since RF 2.9 alpha 2, work in this case? See robotframework/robotframework#293 and http://robotframework.org/robotframework/2.9rc1/libraries/BuiltIn.html#Reload Library for details.

Oooops, sorry for accidentally closing this. Having close and comment buttons next to each others is super annoying.

I don't think so... I may just create a keyword to change the screenshot directory from within the test... Though that could lead to issues I suppose...
Hmmm.. I'll think on it.

You should actually be able to import the library with different arguments. You just need to use the WITH NAME syntax to give custom name to the libraries you import. You'll also get a conflict with each keyword, so you need to use the LibName.Keyword Name syntax with each keyword or use Set Library Search Order to make one of the imported libraries the default library.
Having a keyword to change the screenshot directory might still be a good idea, though.


LS: Review "Definition of Done" in Wiki & shift to md file

Please review all criteria in Wiki and review the below for recommendations.

Code changes reviewed -  Agreement on # of reviewers?
Testing is automated  -- - recommend add "add additional testing for new capability (A/N)"
Build and deployment of change is automated -- Currently in Bluebell vs public repo, how do we want to define?

Closed with PR #66


Comments: Go to Next Comment Thread in Files

The design of Go To Next Comment Thread was discussed in https://github.com/microsoft/vscode/issues/110408. The command jumps to the next comment in the same file. Quite often, code review comments are spread among multiple files. It would be useful to be able to jump to the next comment, even when it's in a different file.
I notice there are two commands for the problems:

Go to Next Problem in Files (Error, Warning, Info)
Go to Next Problem (Error, Warning, Info)

So we could go for a similar approach. As mentioned in https://github.com/microsoft/vscode/issues/127473, being able to jump to the next unresolved comment would be very nice.
I'm not sure how many commands we should add, but what I'd find the most useful is "Go to Next Unresolved Comment Thread in Files". The workflow would be just like F8: jump to the next unresolved comment, resolve it, and iterate until every is resolved.

There's also been discussion of being able to jump to the next expanded comment: https://github.com/microsoft/vscode/issues/158414#issuecomment-1233068275
How about a command for Go To Next Expanded Comment Thread in Files?  Expanded is a more commonly used property than unresolved state so it might get some more utility.

Good point, "expanded" should work well

A Go To Next Expanded Comment Thread in Files command would greatly decrease the need for using a mouse while reviewing a PR 👍

:up: I back up this, the Go to next problem *in files* was the most useful command I discovered ; it's great to be able to see the review comments and toggle expand those, really wish there was also an in files alternative for comments as the single file command isn't really that useful. Because of this I still prefer having a github PR tab opened to check out the next comment location.

@lucas-teks you might find the Comments view helpful (command Comments: Focus on Comments View).


Support alternative Linux distributions

such as ponyc-x86-64-unknown-linux-ubuntu18.04

@Theodus are you thinking that we hardcode the alternatives into ponyup and if a new alternative is added, then you have to update ponyc?
I'm thinking 3 options

list of alternatives is compiled into ponyup

list of alternatives is in a file that can be updated without updating ponyup

list of alternatives comes from querying cloudsmith

while momentarily appealing seems like a bad idea as the alternatives will show up forever even when we stop supporting them and want to remove

seems nice, but also a lot of extra work that might not be all that valuable anytime soon

seems like the best idea for us as long as adding new alternatives is straightforward.

A list of target platforms for setting defaults would likely come from querying Clousmith, since that's how most things are done in ponyup. This issue is primarily concerned with making sure the code for parsing target triples is adapted to work with the new distros in the abi field.

Doesn't that mean that we are stuck with anything that ever goes in? That seems problematic.

It can be filtered or ordered by version/date by default, with an option to show all available

So they could see for example that they can only get up to 0.28.0 and some nightly from the past? I guess that is a place to start and we can see how folks react to that.

@Theodus can this be closed?

Yes


Should list format for "digital" also switch from "narrow" to "short"

In https://github.com/tc39/proposal-intl-duration-format/issues/85 TG2 decided to switch the "Digital Default" for years, months, weeks and days from "narrow" to
"short"
Currently, in https://tc39.es/proposal-intl-duration-format/#sec-partitiondurationformatpattern we have
6. Let listStyle be durationFormat.[[Style]].
7. If listStyle is "digital", then
a. Set listStyle to "narrow".

The question is should the listStyle set by step 7-a also swap from "narrow" to "short" for "digital" or should we keep it as "narrow" ?
@sffc @ryzokuken @ptomato

I believe this is not a good path for us. This isn't something that makes much of a difference implementation-wise, and is purely a design decision. Besides, it's unclear how much "better" it would make the output so it's clearly just a "what if".
With all that in mind, and given that the proposal is in Stage 3, I'd strongly recommend we avoid changes like these as much as we can.

I am not stronlgy suggest us to change it. It is just this is related to the https://github.com/tc39/proposal-intl-duration-format/issues/85 and I would like TG2 to clarify since the decision in https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-09-01.md#should-the-default-digital-non-numeric-style-be-short-or-narrow-85 and this logic in combination may produce unexpected output and I think we should think through about it.
Here is why I ask this question, it is not about the implementation, but the oddness of the output.
If the durationFormat.[[Style]] is "digital"
The only item could be formated  by the list format are only up to (could be less) 5 items

years, 2) months, 3) weeks, 4) days, 5) the combination of hours, minutes, seconds and fractional seconds.

notice, currently the digital default is "short" , not "narrow" therefore, each of the 1) years, 2) months, 3) weeks, 4) days are formatted by the number formatter in the form of "short".
But with the current spec text which change listStyle to "narrow", it will be using the "narrow" pattern to put these 5 thing together.
Consider the following
d8> d = {years: 1, days: 5, hours: 3}
{years: 1, days: 5, hours: 3}
d8> (new Intl.DurationFormat("en")).format(d)
"1 yr, 5 days, 3 hr"
d8> (new Intl.DurationFormat("en", {style: "short"})).format(d)
"1 yr, 5 days, 3 hr"
d8> (new Intl.DurationFormat("en", {style: "narrow"})).format(d)
"1y 5d 3h"

Now, what should be the output of
d8> (new Intl.DurationFormat("en", {style: "digital"})).format(d)

If we use "narrow" for the list format style, it will be
"1 yr 5 days 3:00:00"

If we use "short" for the list format style, it will be
"1 yr, 5 days, 3:00:00"

We had already settled the question about ListFormat length being the same as DurationFormat unit length. Given the choice to switch Digital to short units, it should also change to short list style.

The two changes should happen in tandem, at the same time, ideally in the same PR. It is a bug if they get out of sync.

I didn't do so in https://github.com/tc39/proposal-intl-duration-format/pull/123/ so I will fill a PR for the list style.

TG2 discussion: https://github.com/tc39/ecma402/blob/master/meetings/notes-2022-10-06.md#should-list-format-for-digital-also-switch-from-narrow-to-short-125
@Constellation and @FrankYFTang, who have started implementing Intl.DurationFormat, both agreed that this is a reasonable change to improve consistency. I am also strongly in favor and see it as a bug in the spec.
@ryzokuken, how do you feel?

@sffc alright, I understand that the group was in consensus over this being a bug so I'll go ahead and approve it, then present it to the committee.


JsonSerializerSettings defaults documentation

Reading the documentation, I don't see what the JsonSerializerSettings defaults are. I started at the JsonConvert class, and it doesn't mention what settings it uses if you don't specify any. Going to the JsonSerializerSettings class, it doesn't seem to say what the defaults are either. Without trial and error, one can't know what settings need to be changed without knowing what the defaults are. For example, CheckAdditionalContent, DateFormatHandling, and MissingMemberHandling are some settings that don't say what their default is. It would be helpful having this information in the documentation.

They're here - http://www.newtonsoft.com/json/help/html/SerializationSettings.htm
Feel free to create a PR adding them to JsonSerializerSettings properties.

Done - https://github.com/JamesNK/Newtonsoft.Json/commit/be032b562e05192c6ca7feb634a3fee11810ef3a
Thanks to @sebasrp


Clean up extension build mechanism and extension location

This PR

moves C++ source to dedicated directory torchaudio/csrc
change the library name to _torchaudio.so under torchaudio directory
always include codecs to _torchaudio.so so that it does not depend on external SoX.
automatically builds codecs when extension is built.
also add python setup.py clean command to remove library files.

These changes follow the identical pattern as https://github.com/pytorch/text/pull/755 .
No BC breaking change is intended.

change the library name to _torchaudio.so under torchaudio directory

Can that be BC breaking?

change the library name to _torchaudio.so under torchaudio directory

Can that be BC breaking?

I do not think so.

Python naming convention tells that _torch_sox.so is not intended for external use.
We do not have any header file, so it is not possible to link against _torch_sox.so.

Added the list of things changed by PR in the description.

I think we should consider breaking this into a few more PRs. Changes like the move of the files or the rename of the library could be separated from the build scripts, etc. and make for a more manageable / revertable changeset.

Sounds good. Will work on.
Moto 🛵
On Tue, May 12, 2020, 00:30 cpuhrsch<EMAIL_ADDRESS>wrote:

I think we should consider breaking this into a few more PRs. Changes like
the move of the files or the rename of the library could be separated from
the build scripts, etc. and make for a more manageable / revertable
changeset. They will also be quicker to merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pytorch/audio/pull/625#issuecomment-627101092, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGQ6CQYOQJCQTMRW7VQKC3RRDGETANCNFSM4M4PWWEA
.

offline discussion with @mthrok -- how about compilation on the internal systems? e.g. internal

cc @seemethere for awareness

offline discussion with @mthrok -- how about compilation on the internal systems? e.g. internal

I added bypass for the internal. In internal, nothing about dependencies changes. This PR cannot address T53444370.


End a Round prematurely after a generator has failed enough times in a row

A generator that constructs and outputs instances dynamically for a given instance size may not be optimized to run to completion in time if the given instance size is too large. In an iterated battle, it is assumed that this does not automatically disqualify the generator as it may well be randomized and produce output on the next higher increment.
I would like to keep giving the generator additional chances for higher instance sizes, but would like to advocate cutting it of after a given number of repeating failures due to a timeout.
Without this cutoff, battles currently run very slowly towards the iteration cap, as the generator is granted the maximum allowed running time for each step even if one can rather safely assume that no sane output will be generated for subsequent iteration sizes. My suggestion is to introduce a new configuration option that sets the number of tolerated generator failures in a row before the solving team is awarded its current iteration cap value. It should however still be possible to accept an arbitrary number of failures.

Implemented with #124


mimalloc is incompatible with musl libc on arm64 device

hi there, fellow gentoo user here.
musl is a very lean and fast alternative libc to the bloaty and unhealthy glibc. This is the projects website: https://www.musl-libc.org/ and git: https://git.musl-libc.org/cgit/musl/
mold is a new super fast linker, it can be found here: https://github.com/rui314/
I initially tested the compile of mold against mimalloc with amd64, where it works perfectly fine. On arm64, the compile is working but the resulting binary flakes immediately:
/usr/bin/mold -v

mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: error: unable to allocate memory (72704 bytes)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: warning: unable to allocate OS memory (67108864 bytes, error code: 12, address: 0, large only: 0, allow large: 1)
mimalloc: error: unable to allocate memory (36 bytes)
mimalloc: error: out of memory in 'new'Aborted

this issue was first filled here: https://github.com/rui314/mold/issues/281

There is a gentoo arm64-musl image available through https://github.com/gentoo/gentoo-docker-images , which helped the author of mold to work with the issue.

We recently did work to support musl (and arm64) so this is surprising -- but I would love to see mold use mimalloc and work well with musl. Can you provide more info how you linked mimalloc with mold? (it seems that using LD_PRELOAD worked so I wonder if that has something to do with it).
(I am currently traveling until next week so may not respond right away)

also, I See libtbb in the trace -- perhaps it also tries to override malloc?

are you talking to me or to @12101111?

Ah I did not notice @stefson. I went through the mold issue and it seems that TBB is only used for concurrency but not for the allocator. It is strange @12101111 is not seeing the error using LD_PRELOAD -- what could be the cause of this?.
I think I will need to try to run the docker image to debug this -- I can get to this next week I hope.

Finally got around to running Gentoo linux with musl libc on arm64; I could reproduce the error but then noticed that the mimalloc included in the mold/thirdparty sources is v2.0.3 while the musl support was added in v2.0.5.  Updating to v2.0.5 fixed the issue and mold worked fine again :-)
(This is also why the LD_PRELOAD worked as that was done with a more recent version)

so your advise is to update the internal fork of mimalloc to 2.0.5, or update the system mimalloc to 2.0.5 to solve this issue?

Updating the fork of mimalloc in the mold sources from v2.0.3 to v2.0.5 worked for me.
I am not sure what you mean with the "system mimalloc" ?

I compile mold like this:
make -j1 'CFLAGS=-O2 -pipe' 'CXXFLAGS=-O2 -pipe' SYSTEM_TBB=1 SYSTEM_MIMALLOC=1 STRIP=true LIBDIR=/usr/lib

it means to build against the system-wide install of mimalloc, rather than use the internal fork inside of third_party/mimalloc.

ah I see. Both solutions work as long as mimalloc is recent :-)


Fix link in doc comment

Thanks, good catch!
I don't know what's going on with CI -- all three checks failed entirely at first, no output. I reran them, and then two passed fine, but the formatting check again failed with no output. I'll let this sit for a bit in case they're having infrastructure issues, then I'll try again.

bors r+


Defer creating DispatchResult to intrinsics

Motivation

This makes it more clear what is an in parameter and what is an out parameter by
simply taking an input and returning an output (instead of treating the
DispatchResult &res parameter as an in/out parameter).
This gets us closer to being able to change the representation of
DispatchResult to be a tree of DispatchCopmonent instead of a linked list.
Test plan

Existing tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_R51tBFC9KE00GB
→ https://go/builds/bui_R51ty2Ctke5NMX
→ https://go/builds/bui_R51tuuDpicHOlH


Add support for decoding timestamps with a UTC offset

Describe the feature
https://github.com/aws/aws-sdk-java-v2/issues/2477
Use Case
To properly support the AWS Pinpoint service
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

We already support parsing iso 8601 dates with timezone offset


"Your video card does not support any of the supported OpenGL versions" on Ubuntu 16.04LTS

Issue description
I have Godot 3.2.3-stable downloaded to my computer. After download, I could successfully create projects and fiddle with it for some time, but after I restarted my computer, an error message appeared which said:

Your video card does not support any of the supported OpenGL versions. Please  update your drivers or if you have a very old integrated GPU upgrade it.

I have my nvidia drivers up to date and glxinfo | grep version outputs the following:
GLX version: 1.4
OpenGL core profile version string: 4.5.0 NVIDIA 384.130
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL version string: 4.5.0 NVIDIA 384.130
OpenGL shading language version string: 4.50 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 384.130
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I tried to run it from terminal to see the debug info and I got the following output:
Godot Engine v3.2.3.stable.official - https://godotengine.org
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
ERROR: initialize: Condition "!fbc" is true. Returned: ERR_UNCONFIGURED
  At: platform/x11/context_gl_x11.cpp:158.
ERROR: initialize: Condition "!fbc" is true. Returned: ERR_UNCONFIGURED
  At: platform/x11/context_gl_x11.cpp:158.
ERROR: is_viable: Error initializing GLAD
  At: drivers/gles2/rasterizer_gles2.cpp:166.

Maybe you should say how nix/nixpkgs is related to that? Did you install godot via nix?


Communication

@julienschmidt Sorry for posting here but I couldn't find a way to communicate, can you give me informations in order to communicate with you (gitter, a chat, an active e-mail) or contact with me via twitter in order to solve the contradistinction between us? otherwise I think that we are ok now. I didnt understand your last sentence, I told you I am not native english, you have to explain me directly

You can contact me via email: floss at julienschmidt dot com. We can find a more convenient communication channel via email then.

Julien Schmitt is a Fashion Editor and Stylist based in Paris. He studied at Studio Berçot in Paris. Right after his graduation, he assists Marie-Amélie Sauvé for ...


Calling service media_player/turn_off generates error with Google Cast

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version): 0.40.0
Python release (python3 --version): 3.4.2
Component/platform: media_player / Google cast
Description of problem: Calling service media_player/turn_off (without any specified entity_id) does not turn off the google cast devices and errors out with a NotConnected-error.
Expected:
Turning off all currently turned on media_player devices
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):
17-03-12 09:30:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/core.py", line 1010, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/__init__.py", line 365, in async_service_handler
    yield from getattr(player, method['method'])(**params)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/media_player/cast.py", line 271, in turn_off
    self.cast.quit_app()
  File "/home/hass/.homeassistant/deps/pychromecast/__init__.py", line 273, in quit_app
    self.socket_client.receiver_controller.stop_app()
  File "/home/hass/.homeassistant/deps/pychromecast/socket_client.py", line 843, in stop_app
    inc_session_id=True, callback_function=callback_function_param)
  File "/home/hass/.homeassistant/deps/pychromecast/controllers/__init__.py", line 84, in send_message
    self.namespace, data, inc_session_id, callback_function)
  File "/home/hass/.homeassistant/deps/pychromecast/socket_client.py", line 602, in send_platform_message
    inc_session_id, callback_function_param)
  File "/home/hass/.homeassistant/deps/pychromecast/socket_client.py", line 589, in send_message
    raise NotConnected("Chromecast is connecting...")
pychromecast.error.NotConnected: Chromecast is connecting...

Additional info:

This seems to be related to the discovery component finding 2 instances of a google cast group. One of the instances works fine to turn_off whereas the other one throws this error.
Any idea about how to get rid of these multiple group entries?

Opened an issue in the repo of the dependency instead and will close this one.
balloob/pychromecast#165


Confd doesn't connect to second consul node

confd ist started as:
confd -interval=10 -backend consul -node srv1:8500 -node srv2:8500

When srv1 is not running, it never connects to srv2:
2018-08-29T13:20:04Z 8b5f83a42179 confd[1]: INFO Backend set to consul
2018-08-29T13:20:04Z 8b5f83a42179 confd[1]: INFO Starting confd
2018-08-29T13:20:04Z 8b5f83a42179 confd[1]: INFO Backend source(s) set to srv1:8500, srv2:8500
2018-08-29T13:20:04Z 8b5f83a42179 confd[1]: ERROR Get http://srv1:8500/v1/kv/service/pgcluster/members?recurse=: dial tcp <IP_ADDRESS>:8500: connect: connection refused
2018-08-29T13:21:28Z 6617f4459e15 confd[1]: ERROR Get http://srv1:8500/v1/kv/service/pgcluster/members?recurse=: dial tcp <IP_ADDRESS>:8500: connect: connection refused
2018-08-29T13:21:38Z 6617f4459e15 confd[1]: ERROR Get http://srv1:8500/v1/kv/service/pgcluster/members?recurse=: dial tcp <IP_ADDRESS>:8500: connect: connection refused
....

I would expect confd will failover to srv2, but it doesn't.

@HelgeHesse this seems related to #745. The timing of both these issues makes me wonder if a recent change in the Consul API package could have caused the connection issues.

The Consul version used is 1.2.2.

I am able to duplicate this problem. Doesn't seem to be Consul version dependent.
I believe the problem may lie here...
https://github.com/kelseyhightower/confd/blob/cccd334562329858feac719ad94b75aa87968a99/backends/consul/client.go#L21-L23

@HelgeHesse... having looked into this further I believe Confd is working the way that it should for the Consul backend.
If the -node option is not configured for the Consul backend the Consul API client defaults to <IP_ADDRESS>:8500. It does this because there is an expectation that it will connect to a local Consul Agent running in client mode. The Consul Agent would maintain the connections with the Consul Servers as they come and go.
An alternate approach could be to utilize a load balancer for a cluster of Consul Servers. Strategies for that are documented here... https://www.hashicorp.com/blog/load-balancing-strategies-for-consul

@abtreece For etcd there are multiple nodes allowed, for consul only one. From the users (confd) perspective, there should be no difference (IMHO). Both are HA KV-stores.
Using a load balancer to use more than one consul does not makes sense, since I am configuring exactly such one (ha-proxy).
I think there is a real benefit of supporting more than one consul: less components and simpler architecture.
But if really only one is supported, confd should not allow to configure more than one.


Add content on structures in C++

Select the Day of Content
Day 12
What information is missing?
Topics I would like to add

What are Structures and Declaration of structures.
Passing Structures to functions
Pointers for Structure

Can you please assign me this under ggsoc'24?

I want to work on this issue under GSSoC'24. I'll add content in structures.md along with example programs and questions that will close this issue. Please assign it to me.


Sanitize RSR 5e Crit Damage merges incorrectly with multiple damage rolls

If a creature rolls a critical hit, and the "Sanitize Ready Set Roll 5e Crit Damage" option is enabled, the merged damage is displayed incorrectly in two ways:

Both damage values are identical
The damage values are equal to the first-rolled damage concatenated with itself

Example
GM View:

Player View:

Should be resolved in v0.15.3


fix(ResizableBox.jsx): Unknown prop onResize

"Unknown prop onResize on <div> tag" reported by React 15.x.
This should be released as a hotfix.

Thanks!

Wow, that was quick! Thanks for the library & greetings from your neighbors in Madison.
Will this be published as 1.4.3?

Yep, this is 1.4.3, live now, snuck some Flow fixes in there too. Come to MKE, we have 🍻 . 👋

Indeed you do. I closed Wolski's :beers:

Aha, not far from here at all. We do JS meetups now & then (http://www.meetup.com/milwaukeejs/) - lmk if you're around town.


Support for Reanimated 3

Current Behavior
I tried Expo 49 which comes with Reanimated 3. So the tanimations from the docs won't work.
Expected Behavior
Animations with Reanimated 3 should work
Tamagui Version
1.36.6

Reproduction
Just use example section from the docs: https://tamagui.dev/docs/core/animations#animatepresence-and-exitstyle

System Info
No response

they do work, i've tested them just today using the moti driver (new docs from today). lmk more specifically what doesnt work

Looks like web support is broken for react-native-reanimated v3.4.2. Getting:
[ERROR] No matching export in "node_modules/react-native-reanimated/lib/module/reanimated2/animation/decay.js" for import "WithDecayConfig"
when running yarn web
v3.4.1 works.

they are fixing it in 3.4 https://github.com/software-mansion/react-native-reanimated/issues/4645#issuecomment-1671875388


Is Flutter web not capable of being published to a sub-folder?

I have my web app deployed into www.domain.com/app and I'm getting these errors in Chrome
GET https://www.domain.com/manifest.json 404 (Not Found)
Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('https://www.domain.com/') with script ('https://www.domain.com/flutter_service_worker.js'): A bad HTTP response code (404) was received when fetching the script.
As you can see it's trying to look for files in the root instead of the folder. So are there any configuration files or options to the build command to change this? The docs about deploying web apps don't mention anything like it

Steps to Reproduce

Run flutter build web.
Upload files into a sub-folder in a server
See errors in console

Expected results:
Everything should work
Actual results:

Logs

flutter analyze
Analyzing rpm...
No issues found! (ran in 9.6s)

[✓] Flutter (Channel beta, v1.15.17, on Mac OS X 10.15.3 19D76, locale en-US)
    • Flutter version 1.15.17 at /Users/jan/flutter
    • Framework revision 2294d75bfa (13 days ago), 2020-03-07 00:28:38 +0900
    • Engine revision 5aff311948
    • Dart version 2.8.0 (build 2.8.0-dev.12.0 9983424a3c)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/jan/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.8.4

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 43.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] VS Code (version 1.42.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • iPad Pro (9.7-inch) • 196939CF-6CE1-42D9-A844-ACCAE2DC81F2 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-3
      (simulator)
    • Chrome              • chrome                               • web-javascript • Google Chrome 80.0.3987.149
    • Web Server          • web-server                           • web-javascript • Flutter Tools

! Doctor found issues in 1 category.

Duplicate of https://github.com/flutter/flutter/issues/50580


Overhaul the Flexbox documentation

Test plan: just run the docs website & look at it
OK so what we had before was a weird doc named "Flexbox" tacked on to the end of APIs with autogenerated-but-not-useful content. A couple problems with that. First, this was actually being generated from the "LayoutPropTypes" file, which is not really public or useful directly, but happens to be a list of all of the core-component-props that relate to layout. It is not the same as flexbox - it's actually a superset, because it also contains all the non-Flexbox layout stuff like position: absolute, setting margin and border, z index, all sorts of rando stuff. So, I renamed the doc to "Layout Props" since that is what it is - the props that relate to layout, not just the flexbox ones. I renamed the other props doc "Shadow Props" since that's also a more accurate statement of what it is. I renamed the "Layout" doc a bit to indicate that it talks abotu flexbox, since it's actually a better flexbox-centric description of flexbox than the doc named "Flexbox" was.
So after that reorganizationy stuff, I also wrote a little blurb for each prop. The vast majority are something that's just like something in CSS, although often renamed or slightly tweaked. So I link out a whole lot. css-tricks was voted better for Flexbox than other referencey sites, and I agree, so I linked there for flexboxy ones. Otherwise I just checked on Google for something that seemed useful and standardy. I documented the differences I could find - stuff like, RN always uses logical pixels not % or em or cm, some defaults are different, the "flex" parameter just works totally different, yeah.
I could use peoples' help looking through and checking for minor errors and omissions because I am certain there are going to be a number of them - I'm not actually an expert in all the gotchas of React Native CSS ;-)

By analyzing the blame information on this pull request, we identified @caabernathy and @dabbott to be potential reviewers.

Looks way better.
I'll double check the absolute positioning thing now

This is a huge improvement.

OK I responded to all comments so far. Keep em coming if you got em

LGTM

Thanks for importing. If you are an FB employee go to Phabricator to review.


Always use spack install --verbose --source

Is your feature request related to a problem? Please describe.
Turns out that I (try to, unless I forget) install every spack environment with the options --source (install source code with package, needed for debugging) and --verbose (convenient to look at logs).
But I do forget this every so often, mostly when an installation fails halfway, I fix something and then restart in between. This creates inconsistent environments, where some packages have the source code, some don't.
Describe the solution you'd like
It would be good to always use this options as default. I tried changing the defaults in spack/lib/... but this led to so many unit test failures for spack that it wasn't feasible. I am wondering if we should create a spack command extension such as spack stack install ... that basically translates into spack install --verbose --source ...
Other ideas? If at all possible, I want to get this into the current release<EMAIL_ADDRESS>Additional context
n/a

@climbfuji Any interest in adding --fail-fast as well? I could go either way, but I'd lean toward adding it as it's especially useful in a CI context.

I am undecided about fail-fast (actually voted against it in the slack poll), but no strong preference. We can add it.

sorry -- i lost track of this! @AlexanderRichert-NOAA are you handling this now? if not, i will try to get something together.

Note. We discussed with the spack developers that these options should also be controllable in the spack yaml config section (similar to some other options that can be set either as a cmd line argument or in the yaml).

@ulmononian I was thinking of looking at this if I have extra time this week. Have you already looked at how to implement? I'll be more or less starting from scratch.

@climbfuji good to know -- thank you.
@AlexanderRichert-NOAA i haven't looked into this in any extended detail yet, so i'd also be starting from scratch here. if you want to tackle it, feel free. i forgot it was assigned to me until you commented here, but wanted to express that i would be glad to try and do it now that it is back on my radar lol. no pressure either way here :) your call.

@ulmononian I'll look into it later this week, and if I get horribly lost with it I'll let you know :)

I think we can try to follow how other options are implemented that can be set through the command line or the spack yaml .

@ulmononian I'll look into it later this week, and if I get horribly lost with it I'll let you know :)

sounds good!
@climbfuji "I think we can try to follow how other options are implemented that can be set through the command line or the spack yaml ." --> makes sense to me.

@ulmononian Any update on this?

What is the status of this issue? @ulmononian

I don't think this is needed. We've gotten used to running spack install --verbose on the HPCs, no need to over-engineer a solution unless @ulmononian already has something ready to go.

sorry for the dearth of updates, but i never found an elegant way to do this. i'd second what @climbfuji said.

Let's not do this then.


chore(package): update model-attributes to version 2.2.3

https://greenkeeper.io/

Current coverage is 70.58% (diff: 100%)

Merging #31 into master will not change coverage

@@             master        #31   diff @@
==========================================
  Files             1          1
  Lines            17         17
  Methods           3          3
  Messages          0          0
  Branches          0          0
==========================================
  Hits             12         12
  Misses            5          5
  Partials          0          0

Powered by Codecov. Last update d9b3c44...9d670fb