Vue-info breaks knob addon

Describe the bug
@pocka I really like your addon, however there seems to be a problem.
The storybook knobs addon seems not to work with the vue-info addon. When changing a prop by using a knob it has no effect on the rendered component's prop.
Currently I'm using vue-info version 1.0.0-beta.0, knobs 4.1.11 together with storybook version 4.1.11.
To Reproduce
.storybook/addons.js
import 'storybook-addon-vue-info/lib/register'
import '@storybook/addon-knobs/register';
.storybook/config.js
import { configure, addDecorator   } from "@storybook/vue";
import { withKnobs } from '@storybook/addon-knobs';
import { withInfo } from 'storybook-addon-vue-info'
import Vue from "vue";
import Vuex from "vuex";
Vue.use(Vuex);
const req = require.context('../src/components', true, /\.story\.js$/)
function loadStories() {
req.keys().forEach((filename) => req(filename))
}
addDecorator(withInfo);
addDecorator(withKnobs);
configure(loadStories, module);
/src/components/Label.vue
<template>

Hello{{ description }}

</template>

/src/components/Label.story.vue
import { storiesOf } from '@storybook/vue'
import { text } from '@storybook/addon-knobs'
import Label from './Label.vue'
storiesOf('Wizard', module).add(
	'with info and knobs',
	() => ({
		components: { Label },
		props: {
			description: {
				type: String,
				default: text('Description', 'This should work.')
			}
		},
		template: ''
	}),
	{
		info: {}
	}
)
Expected behavior
When changing a prop via knob the related prop should be changed and rerendered.

<EMAIL_ADDRESS>has an issue with story decorators and knobs addon (https://github.com/storybooks/storybook/issues/5048). That issue was fixed in<EMAIL_ADDRESS>Our example uses<EMAIL_ADDRESS>FYI. Please try >=<EMAIL_ADDRESS>


#hacktoberfest2018

Hello, everyone!
Let's contribute to Hacktoberfest while refreshing our data structures and algorithms knowledge.
Implement your favorite data structure/algorithm/crazy programming magic and make a Pull Request.
It can be anything! Maybe graphs? Sorting algorithms, dynamic programming, greedy algorithms, everything is welcome.
Any programming language is welcome.
If you need help, this is a good place to start:
https://akrabat.com/the-beginners-guide-to-contributing-to-a-github-project/#summary

Will add programs soon

Like to add Bucket sorting program in cpp

Like to add Merge sort in c

Heap sort in c#

Thanks, everyone!
PvP is ready for another Hacktoberfest.
We'll see you guys in a month.


Comprehensions do not split as far as they can go, which preserves long line lengths

Keywords
Line length, comprehension
Example
Before ruff --fix
really_really_really_long_dict_name = {"foo": "bar"}

dict_with_really_long_names = {really_really_really_long_key_name: really_really_really_long_key_value for really_really_really_long_key_name, really_really_really_long_key_value in really_really_really_long_dict_name.items()}

After ruff --fix (Both the "before ruff fix" and "manual attempt below" lead to this)
dict_with_really_long_names = {
    really_really_really_long_key_name: really_really_really_long_key_value
    for really_really_really_long_key_name, really_really_really_long_key_value in really_really_really_long_dict_name.items()
}

Expected (or Proposed) after ruff --fix (running ruff on this also leads back to the after case)
dict_with_really_long_names = {
    really_really_really_long_key_name: really_really_really_long_key_value
    for really_really_really_long_key_name, really_really_really_long_key_value
    in really_really_really_long_dict_name.items()
}

That for/in line is 127 characters long, but it could come under the line length (default of 88, not set here) by splitting the for/in statements, which does not affect behavior in this case.
Version/Command
Using ruff v0.5.1 with pre-commit calling ruff --fix.
Comparison with black
Currently, this runs with the same behavior as black.
Another user brought up a similar suggestion here: https://github.com/psf/black/issues/3498

To clarify. Are you running ruff format or ruff check --fix? I  suspect it's the former because E501 doesn't come with an autofix.

Thanks.  Yeah, it is then the formatter that doesn't split the comprehension further.
The main question here is what should happen when the comprehension does break over multiple lines:
 lcomp3 = [
         # This one is actually too long to fit in a single line.
         element.split("\n", 1)[0]
         yup
-        for element in collection.select_elements()
+        for element
+        in collection.select_elements()
         # right
         if element is not None
 ]

Because this does look worse. The desired result is probably that the for ... in should be kept together if possible

I think my biggest concern is that it hurts readability if there are multiple generators
[
    [
        x
        for x
        in bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
        for y
        in xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxdxxxxxxxxxxxxxxxxxxxxxxxx
    ]
]

Thanks for linking to the relevant black issue. This is very helpful for both projects :)

There are surprisingly few differences in the ecosystem check of a naive implementation.
I'm not convinced that this looks better overall. It would require more refined rules. E.g. don't split if the left side is a simple expression like an identifier.

Thanks for giving this issue some thought @MichaReiser !

The desired result is probably that the for ... in should be kept together if possible

I agree. If the for ... in can be kept to one line, it absolutely should. I'm purely thinking of cases where doing so would improve the soft adherence to the line length setting.

There are surprisingly few differences in the https://github.com/astral-sh/ruff/pull/12908#issuecomment-2291695892.

I'm not convinced that this looks better overall. It would require more refined rules. E.g. don't split if the left side is a simple expression like an identifier.

Interesting, thanks for doing that prototyping! Yeah, I assume most folks aren't using unnecessarily long variable or iterable variable names like I am (likely shoddy choices on my part), but the cases your implementation covers do seem to cover subset where the code has parentheses in the for (...) in ... and the parentheses get split out, perhaps unnecessarily.
For the prefect one, I think ideally, it could be the following, where trying to keep the in with the for led to the parentheses splitting out line-wise. (So the change was effective, but perhaps it could compress the earlier lines.) That might start needing some extra logic though, and I lack the intuition in this codebase to know if that's feasible and even stylistically reasonable.
            for (block_schema, _, parent_block_schema_id)
            in block_schemas_with_references

likely shoddy choices on my part), but the cases your implementation covers do seem to cover subset where the code has parentheses in the for (...) in ... and the parentheses get split out, perhaps unnecessarily.

I think the reason why the parentheses get split out is because the tuple contains a trailing comma. But I think the style could do better by trying to keep the closing ) and the in keyword on the same line.


set inventory_is_zeroed to false for preview

 Bugfix for "Accept a maximum number of orders per day" - ensure a preview action renders, even if inventory has already been cleared for the day


Added LWJGL to the "Unnoficial Ports" Section

lwjgl3 is a Java game library not a "port" of meow_hash.


Option to disable generation of samba_locks_per_share_count.

Good morning.
Would it be possible to add an option, like -not-expose-client-data, to disable the generation of the samba_locks_per_share_count metric?
Depending on the number of shares of the SAMBA server, the share= label can generate a high cardinality. In my case, in a professional environment, I have samba servers exposing more than 50 shares.

@crocchietta you can try the feature with V1.32.1-pre

Good morning.
thank you for this addition. I don't have an environment available to compile GO language.
Do you have an idea of a date for the next version?
Otherwise in general, it would be good to systematically provide an option allowing you to choose or not to generate metrics that could result in high cardinality. While allowing the generation of summary metrics.

I hadn't noticed that the preview versions were also compiled...

@crocchietta

I hadn't noticed that the pre release were also compiled...+

Yes, on the page of V1.32.1-pre you can find installable packages.

Otherwise in general, it would be good to systematically provide an option allowing you to choose or not to generate metrics that could result in high cardinality. While allowing the generation of summary metrics.

So you suggest a new option that sets all -not-expose-*  parameters to true?

No. I suggest that for future metrics that may generate high cardinality due to labels, to always consider adding an option to disable this metrics or just these labels (depending on the cases).

Is this change included in the new version 1.32.9?

@crocchietta yes it is

Fix released with V1.32.9


Fix doubleTap events on touch devices

This builds on the work done in https://github.com/Leaflet/Leaflet/pull/5881, but adds an extra check that resolves all of the issues mentioned by users in the comments section.
It also introduces a level of stability. For ex, if a newer version of Chrome does start to fire native dblclick events, the functionality will not break
Tested on Mobile: Chrome, Firefox, Safari, Opera, Samsung Internet, Edge
Desktop Chrome, IE 9 - IE 11, Firefox, Safari, Opera, Edge

@perliedman let me know your thoughts please! For now planning to use it in my own plugin https://github.com/publiclab/Leaflet.DistortableImage so would love to ensure it passes standards

Hi @sashadev-sky! Happy to see someone taking this on where I left off.
I am sorry to say that I have long since lost track of the issue as well as the possible fix, it looks like I opened the PR like two years ago. Also, I have stepped away a bit from Leaflet maintenance since then, so unfortunately I have little feedback to give at this point, and my current situation makes it hard to find the time to do a proper review.
I can just hope that maybe @cherniavskii (or someone else who is an active maintainer?) can have a look. Given that #5881 passed review I guess it should not be too much work to get this approved.
Sorry to not be more helpful!

I have a humble request. Can you add fixing #6817 to this PR? You are fixing basically the same stuff. Whole #6817 thread is pretty self explanatory and the solution is easy.


fix: release shouldn't fail on a project that references itself

yes, ignoring file: and link:  would work as well. I will update this.

Isnt the changeset and test description somewhat wrong now after the change has been made to ignore stuff based on file and link protocols?

It is not wrong, it just describes a subset of what was fixed.

You could possibly have "self-reference" but pointing to a version or something else, right? This is often done in tools dog-fooding their own tools (for example transpiling Babel's source with Babel). OTOH this (depending on a version from registry) probably is not supported by changesets anyway 🤔


DatePicker / DateTimePicker not displaying on RTL (RightToLeft) Mode

This function solves the problem (这个功能解决的问题)
DatePicker / DateTimePicker not displaying on RTL (RightToLeft) Mode
Expected API (期望的 API)

You can tracking the issue here.
https://github.com/TuSimple/naive-ui/issues/97
If you need it soon, you can give us a priority list (maybe top 5 or 10) so that we can have a goal to target at.
(We can implement in a priority order but it may still take some time.)

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


CDC support for Opensearch

Is your idea related to a problem? Please describe.
To the best of my knowledge, when using DataWrangler for CDC from RDS to Redshift, it works like a charm without needing to manually handle the operation code (I, U, D) passed to the .csv file. When trying to perform CDC from RDS to Opensearch it breaks and cannot index the new documents passed to Opensearch.
Describe the solution you'd like
I believe that it would be really helpful if DataWrangler handled operation codes internally, without forcing the engineer using it to do this manually. Below you may find the code that could be used to reproduce the aforementioned behavior.
import os
import pandas as pd
import awswrangler as wr

# The first insertion of data, lets say the "Full Load" operation
FIRST_INSERT = pd.DataFrame([{"id": 1, "data_value": 10}])
# The .csv file should look like: I,2,20 where I is OP, 2 is the id and 20
# is the data_value
SECOND_INSERT = pd.DataFrame([{"id": "I", "data_value": 2}])

if __name__ == "__main__":
    HOST = os.getenv("HOST_IP")
    USERNAME = os.getenv("USERNAME")
    PASSWORD = os.getenv("PASSWORD")

    table_name = "test_table"

    opensearch_client = wr.opensearch.connect(
        host=HOST,
        username=USERNAME,
        password=PASSWORD,
    )
    wr.opensearch.index_df(client=opensearch_client, df=FIRST_INSERT, index=table_name)
    # This should break and display an error like the following:
    # [ERROR] Exception: ('1 document(s) failed to index.', [{'index': {'_index': 'test_table', '_type': '_doc', '_id':
    # 'df186dec-5e2d-483e-ae81-d313d7086592', 'status': 400, 'error': {'type': 'mapper_parsing_exception', 'reason':
    # "failed to parse field [id] of type [long] in document with id 'df186dec-5e2d-483e-ae81-d313d7086592'.
    # Preview of field's value: 'I'", 'caused_by': {'type': 'illegal_argument_exception', 'reason':
    # 'For input string: "I"'}}, 'data': {'id': 'I', 'data_value': 2}}}])
    wr.opensearch.index_df(client=opensearch_client, df=SECOND_INSERT, index=table_name)
    opensearch_client.close()

@snikolakis thank you for the enhancement suggestion.
Can you please elaborate on RDS->Redshift CDC? where do you see this in the code?
If we move forward with this enhancement to OpenSearch we'd like to provide a consistent experience.

Thank you for your response @AssafMentzer . I cannot really respond to where this exists inside the data-wrangler code, however I can describe my use case and how this works in case it helps you better understand. Suppose we are performing data migration between a RDS DB and Redshift and we need logical replication enabled in order to keep "listening" for changes and migrate them, as well, to our Redshift cluster.
In my use case, I need to perform some transformations in a AWS Lambda Function before copying the data to Redshift. So let's say in the full load I am having this file:
1,Full-load,"{full,load}",2022-04-21 12:18:00.000000,2022-04-21 12:18:00.000000

I send this file to a S3 bucket, read it with data-wrangler:
chunks = wr.s3.read_csv(
    path=input_file, names=["id", "name", "keys", "created_at", "updated_at"], chunksize=1000
)

Then, I transform the chunk changing {full, load} array ("keys" column) to two different rows each containing one item of the list and then copy the DataFrame to Redshift:
wr.redshift.copy(
    df=df,
    path=s3_path,
    con=redshift_conn,
    table="table",
    schema="public",
    iam_role=arn::..........,
    primary_keys=["id"],
)

And it correctly creates a table with two rows in Redshift:
1,Full-load,2022-04-21 12:18:00.000000,2022-04-21 12:18:00.000000,full
1,Full-load,2022-04-21 12:18:00.000000,2022-04-21 12:18:00.000000,load

Afterwards, I am performing the same operation for a file produced again by AWS DMS, but now the file is created because of CDC, which means that an operation code is also inserted in the beginning of the .csv row, e.g.:
I,2,Test,"{Test,test}",2022-04-21 12:19:00.000000,2022-04-21 12:19:00.000000

By performing the same operation it still adds two rows to the Redshift table, ignoring the operation code "I":
1,Full-load,2022-04-21 12:18:00.000000,2022-04-21 12:18:00.000000,full
1,Full-load,2022-04-21 12:18:00.000000,2022-04-21 12:18:00.000000,load
2,Test,2022-04-21 12:19:00.000000,2022-04-21 12:19:00.000000,Test
2,Test,2022-04-21 12:19:00.000000,2022-04-21 12:19:00.000000,test

This does not work with "U" operations, leading to new rows insertions though. However, when trying to perform data migration from RDS to Opensearch, the "I" operation code breaks the insertion to the Opensearch step and thus, cannot perform CDC with RDS and Opensearch.
It feels weird that when migrating data to Redshift it seems to ignore the operation code (I have personally only used Inserts and Updates) while not the same happens for Opensearch.
I hope this helps clarifying a bit your question? From my understanding and my latest experiments I gather that data-wrangler does not handle operation codes and it is the responsibility of the engineer to do so. But, maybe, could the data-wrangler actually handle this?

Data Wrangler does not handle change data capture in any of its services at the moment.
To be honest, not quite sure why "I" column is ignored in your case, perhaps because it's not part of the schema and the default behaviour is to ignore the unknown fields.
You should be able to handle updates/deletes by specifying update/delete operation (that goes in the doc_type field I think) when indexing.


Using Qhull for halfspace intersection : segfault

As the title says, Qhull support computing halfspace intersections via its H option or the dedicated qhalfprogram.
One should give a list of halfspaces of the form:

Ax + b <= 0

And an interior (feasible) point. Then, Qhull will compute all the vertices forming this polyhedron. Unfortunately, this is bugged for now, even for a simple example
I will investigate a bit, but the program crashes when calling Qhull.get_simplex_facet_array(), meaning that in H mode, some assumptions are not valid.
At a quick glance, I'd say this is related to the fact that get_simplex_facet_array() uses self.ndim and self.numpoints but those are not the dimensions of the input array in H mode.

Ok, I started working on this on my fork. It appears that correctly setting ndim and num_points solves the issue. Indeed, the above test now passes.
Unfortunately, one more point needs to be dealt with. Whenever working with halfspaces, Qhull works in the dual space of the original problem. Meaning that:

Neither points nor halfspaces correspond to the input
The real intersection points have to be computed separately (see qhull/io.c:1239) using the simple formula:

My question is thus, what is the best way to introduce this ?

The half-space computation probably should be considered a separate
"major mode" similar to Delaunay. (That ConvexHull accepts the H flags
at all is probably a bug.)
.
You can either add a new method to the _QHull class for pulling out the
half-space information, or adjust one of the existing ones to suit this,
if only small changes are needed. E.g. via adding a new keyword argument
half_space=False that toggles between modes.
.
The H flags should not be passed via qhull_options, since it's a major
mode. I haven't used this mode, but perhaps the qhull API has a way to
pass in the points in an array rather than having to go via strings.

After tinkering with it a bit, I think a major mode will be necessary: in halfspace mode, Qhull does not compute at all the triangulation of the intersections, and I am afraid we will encounter a lot of confusion by putting different things in the same container.
I'll look into it and try to submit a patch sometime this week!
For the second option, it seems that it is possible when using a file (you can specify the interior point first, then specify the halfspaces), so I'll check which method they call to set it.

For completeness, here's the test case from the OP's gist:
n [16]: A = np.array(([[-1, 0, 0],
   ....:                [0, -1, 0],
   ....:                [1, 0, -1],
   ....:                [0, 1, -1]]))

In [17]:

In [17]: hull = spatial.ConvexHull(A, qhull_options='H0.5,0.5')
Segmentation fault (core dumped)


[0.7.5] Amibiguous error message when version name in directory and version in mod.json is different

Steps to reproduce:

Enable a mod in-game
Close the game
Change the version number in the directory name of the mod
Open the game

Alternative steps to reproduce

Enable a mod in-game
Exit the game
Open the game
Edit the mod's mod.json and change the version number.
Exit and re-enter the mod menu
Toggle on and off the mod
Exit the game
Open the game
Toggle on the mod
Exit the game
Open the game

The ambiguous error message given is "expect any JSON5 value, but actually <EOF>".

In v0.7.5, both of file open error and JSON5 syntax error are reported as JSON5 error as described. It was fixed by the commit: 0fa817e5015e50e546f818e2988bf25e04251a6b
New error message:

failed to open <path to elonafoobar>/mod/<mod>-<version>/mod.json to read

It reports that a mod folder with the version specified by profile/<profile name>/mods.json does not exist in mod directory.


Accessibility testing upload page

Not sure if this is meant to be ready for review, but these changes have affected the unit tests, so these will need updating.


Overkiz RTS Shutters

Hello,
Im searching for a way to set positioning of my dumb RTS shutters.
Overkiz + tahomav2 + rts shutter:
RTS Shutter have 4 buttons in HA: "open" / "stop" / "close" / "favorite position"
Do you think I can use this integration for my use case?
I want to know if the shutter is closed/opened or in the "favorite position" and using time, the % position.
Thank you in advance

Assuming that "favorite position" turns up/down to a specific position (by turning on the relevant switches), the rest should work.

Assuming that "favorite position" turns up/down to a specific position (by turning on the relevant switches), the rest should work.

It works, but the status of the covers are always "unknown". So I don't know if they are closed, open or in the favorite position.

That is because either the Up or Down switch is unavailable, and so it turns the whole cover as unavailable. This can happen if Zigbee switches are disconnected, for example.

I never talked about ZigBee switchs, I don't have any.
My question was to virtually create the open/close and favourite position as state of the cover, instead of having it as unknown

If you have any entity (kind switch, light, or any other supported) in Home Assistant, regardless of being virtual or not, and it is available, then the cover should not appear as unknown.
If you are currently facing any problem, please provide more details to understand whether this is a bug or not.


[dnm] demonstrate that dead code hits assertions

In https://github.com/cockroachdb/apd/pull/103, I'm looking into hooking up gcassert to CI. It's pretty magical to be able to add these assertions in and protect against regressions in carefully tuned code. I'd like to start using it in more places.
Unfortunately, I'm running into the problem that platform-specific conditional logic that leads to compile-time dead code can cause assertion failures if one of these assertions lands in the dead code. I'm not quite sure what to do about that, so I figured I'd open up a PR to demonstrate the problem.

I'm not quite sure what to do about this either, unless there's a way to access the dead code analysis pass somehow.

Yeah, I looked into whether there was a way to get debug information from either the branch elimination or (many) dead code analysis passes of gc, but from what I could see, neither export anything.
I found a way to restructure the code to work around this in cockroachdb/apd, so it's no longer blocking that project, but this may come up in other places in the future. One potential workaround is to allow callers to selectively opt-out of function-wide //gcassert:inline directives at specific callsites. Something like a //gcassert:ignore directive.

That would work, though wouldn't it have the problem where you wouldn't know which one to ignore if there are 2 should-inline callsites in 2 mutually exclusive compile time if branches?

That does seem like a problem. How does //gcassert:inline work when added to a line with two function calls?

I think that it would pass if either of the function calls got inlined. There's just a line number to boolean map for the inline check, it looks like.

https://github.com/jordanlewis/gcassert/blob/master/gcassert.go#L211-L214


readonly is a @property

Coverage decreased (-0.1%) to 80.106% when pulling e3c3c2fe75d0eee037bdc22b4f2e2817c0e14010 on readonly_as_derived_prop into b980c4b940465b2171bddd7b54a6231e62eb9178 on master.

Coverage decreased (-0.1%) to 80.106% when pulling e3c3c2fe75d0eee037bdc22b4f2e2817c0e14010 on readonly_as_derived_prop into b980c4b940465b2171bddd7b54a6231e62eb9178 on master.

Coverage decreased (-0.1%) to 80.106% when pulling e3c3c2fe75d0eee037bdc22b4f2e2817c0e14010 on readonly_as_derived_prop into b980c4b940465b2171bddd7b54a6231e62eb9178 on master.


How to prevent duplicate entries?

In /etc/crontab, we want to change the cron hourly, daily, weekly and monthly.
They are defined by default, so new entries managed by Ansible are added (#Ansible: ).
The problem is this crons will now be executed twice.
One way to solve this is to use a template instead the standard cron module, which is kind of a pity.

I guess we have to remove the file when creating the VM image to solve the issue.

Hi, sorry for the late reply.
Yes, this role doesn't manage the /etc/crontab file yet but PR are always welcome!


do we need pString / PString?

My slow march through the Vega-Lite gallery continues. Today's adventure is https://vega.github.io/vega-lite/examples/layer_bar_annotations.html which includes
        "encoding": {
          "x": {
            "value": "width"
          },

I think this means there should be a pStr : String -> PositionChannel to match pNum (or some similar name), but maybe I'm missing something really obvious.

Elm-vegalite has functions pWidth and pHeight that are used to reference a plot's width and height positions. This seemed safer than a general pStr option, but if you spot a case where arbitrary strings are required, feel free to reopen.


Fix build on macOS

utils.c:49:9: error: use of undeclared identifier 'mach_clk'

Thank @ChinYikMing for contributing! You might consider adding macOS builds to the CI pipelines to ensure that both semu and rv32emu can be built on macOS for major configurations.


Implement primitive-based QuantumKernel

What should we add?
In this epic we plan to implement a new version of QuantumKernel that will leverage the primitives introduced in Qiskit Terra:

[x] Implement new QuantumKernel. #437
[x] Update QSVC/QSVR and PegasosQSVC. #437
[x] Write a new or update the existing tutorial. #488
[x] Deprecate the existing quantum kernel implementation. #482

Closing the epic as all tasks are done.


[WiP] Disable failing tests in windows

Purpose
Disable failing tests in windows

Codecov Report

Merging #15190 into master will decrease coverage by 11.82%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #15190       +/-   ##
=============================================
- Coverage     23.05%   11.23%   -11.83%
+ Complexity     4996        5     -4991
=============================================
  Files          1342       43     -1299
  Lines         66958     1211    -65747
  Branches       9094      195     -8899
=============================================
- Hits          15439      136    -15303
+ Misses        49818     1061    -48757
+ Partials       1701       14     -1687

Impacted Files
Coverage Δ
Complexity Δ

...lerinalang/stdlib/filepath/nativeimpl/Resolve.java
0% <0%> (-83.34%)
0% <0%> (-2%)

...erinalang/stdlib/filepath/nativeimpl/Absolute.java
0% <0%> (-75%)
0% <0%> (-2%)

...lerinalang/stdlib/filepath/nativeimpl/Matches.java
0% <0%> (-68.75%)
0% <0%> (-2%)

.../org/ballerinalang/stdlib/time/util/TimeUtils.java

...g/compiler/tree/expressions/BLangTableLiteral.java

...ang/compiler/parser/BLangAnonymousModelHelper.java

...ontext/ParserRuleDefinitionCompletionProvider.java

...llerinalang/net/http/nativeimpl/session/GetId.java

...va/org/ballerinalang/net/grpc/OutboundMessage.java

...rg/ballerinalang/mime/nativeimpl/SetBodyParts.java

... and 1292 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b5bbf42...204c579. Read the comment docs.


Resolve bug where overlay wizard scrolling is sluggish

Supports https://github.com/openshift/origin-web-console/issues/2761
Note:  .landing and .landing-side-bar benefit from this same fix;
however, the application of the fix causes .landing-side-bar to
disappear as -webkit-overflow-scrolling: touch changes the behavior of
position: fixed.  I will work to see if I can find a workaround and
open a separate PR.

Feel free to merge when travis passes


readme gripe: metadata isn't really a fingerprint

The readme explains that the metadata of a runtime can be used as a fingerprint for a runtime. While I agree this can be useful for a quick-n-dirty comparisons it really offers limited guarantees that the extrinsic signatures and some other superficial things look the same.
Two runtimes could have the same metadata but different behavior.

You are right, I will review that part.


[bug] Coinbase Wallet connection redirects fail on Chrome iOS

Is there an existing issue for this?

[X] I have searched the existing issues

RainbowKit Version
2.1.3
wagmi Version
2.9.2
Current Behavior
Coinbase Wallet redirects seem to be unreliable in some mobile WebKit browsers, including Chrome for iOS
Expected Behavior
No response
Steps To Reproduce

Visit dApp in Chrome for iOS
Connect with Coinbase Wallet
Follow redirect and choose Already have a wallet
Deep link or universal link redirect fails, tab closes. No console logs reporter

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

I'm experiencing the same problem, from Chrome/Safari.

@DanielSinclair @Samuele458
Do you have an environment I can use for testing? Either your dapps/applications or a sandbox, anything is great.
Pretty likely it is an issue on our side, looking into it.

@spencerstock Yes, you can use our example dApp at https://rainbowkit-example.vercel.app/

@DanielSinclair I'm currently unable to repro, if you're able to hop into a meet with me - https://meet.google.com/rpu-bqto-avr
I'll hold this meet open for an hour if you happen to be available
Other things to that will help us isolate the issue:
Does the issue persist in an incognito tab?

I still haven't been able to repro, but I have seen other repro's of this problem. Working on a fix in the keys.coinbase.com popup that should get this sorted out. (we've tried other approaches but it's still not all the way solved)

Closing this issue since it seems like it no longer can be reproduced.


KSTREAMS-5765: Port the assignor package to streams

interfaces in assignor package ported to a streams-specific package
implementation of a simple working assignor with unit tests

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@cadonna PTAL


About the video model

Thanks for such a wonderful work! I'm curious about the video model. What are the datasets used for the training of the video model? In my opinion, in the dmc setting, the video model will use expert trajectories of all dmc tasks, like walker-walk, and cheetah-run. Is it right? If so, how can the model generate videos of different tasks with the same embodiment (like walker-stand and walker-walk)?
Thanks again!

The video model samples consecutive frames so sampled trajectories for the same embodiment will represent different tasks. One can condition on a task ID or text to sample a video of a particular task.


DMN XML not correctly updated when changing IDs of Tables

Describe the Bug

When changing IDs of Tables in a DMN, the relations get lost on the diagram but remain in the XML.
Steps to Reproduce

Expected Behavior

When changing the IDs of an element, all relations get updated correctly.
Environment

Camunda Modeler Version: all versions

Related to SUPPORT-7040

This popped up in support. I linked relevant support case in issue description

@barmac Is there a chance that we can backport this to<EMAIL_ADDRESS>

@barmac Is there a chance that we can backport this to<EMAIL_ADDRESS>
We can do that.


[PWA] (2/2) Add service worker

@captbaritone PTAL.

We should consider disabling the "load from dropbox" option when in offline mode, or at least adding some kind of error notification to inform users why the option would not work.
Getting super excited about this! The recent change I made which makes jsmediatags lazily loaded is extra cool now, since it will be automatically pre-fetched in the background.

Ah, I think I've answered my own question, regarding cache-busting service workers:

From https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle#waiting
I'll look into ways to support shorter TTLs on CloudFlare.

Okay, I was able to disable caching of webamp.org/service-worker.js on CloudFlare's side.

This is live on https://webamp.org now.

First of all, yes, using different names for the service worker is a bad idea. That's why I wrote in https://github.com/captbaritone/winamp2-js/issues/500#issuecomment-373365911 that using hashes in the names of built files is not a good practice.
Secondly, if your server returns a Cache-Control header with your service worker file, some browsers will cache your service worker file in the HTTP cache. Future requests for your service worker file will check the HTTP cache, which can cause some confusion while developing locally or after publishing a new service worker and changes don't seem to be taking effect.
So make sure that the Cache-Control header for the service worker is set to no-cache, forcing browsers to always check the server for a new service worker file.
(The browser will only cache a service worker file for a maximum of 24 hours, so if users are on an old service worker, it will take at most a day before they'll get the latest service worker.)

what happens if we want to make an update to this file?

A common UX pattern for progressive web apps is to show a banner when a service worker has updated and waiting to install: https://developers.google.com/web/tools/workbox/guides/advanced-recipes#offer_a_page_reload_for_users

After I merge, I'll wrap this in an 'if' block so that it's only included in the prod index.html

Actually, you don't need this. ;-) Just create a stub service-worker.js with the following content:
console.info('Service worker disabled for development, will be generated at build time.');

It will be used while developing locally (it doesn't precache files and does not interfere with live reload). At the build time it will be overwritten by Workbox.

We should consider disabling the "load from dropbox" option when in offline mode, or at least adding some kind of error notification to inform users why the option would not work.

Regarding https://www.dropbox.com/static/api/2/dropins.js file, you can handle third-party requests at runtime. ;-)
Disabling UI elements for features that can't work offline is a good practice.

The recent change I made which makes jsmediatags lazily loaded is extra cool now, since it will be automatically pre-fetched in the background.

Just read about PRPL pattern. :wink:
There is a large field for performance optimizing from loading only what is needed for a route to render or offline work to changing priorities of lazy (async) loading of assets.
E.g., a good idea is not to precache llama-2.91.mp3 and *.wsz skins (maybe except base-2.91.wsz) to reduce cache time and size.

Looks like cache-control is currently 600 from CloudFlare. I'll look into setting this to no-cache. We might also need to see what the header coming from GitHub Pages is, since that's what CloudFlare will be seeing.
I think, for now, it's probably fine to just update the service worker on reload. Keeping the name the same, and getting the right cache-control header should make this work. I don't think people are currently leaving Winamp2-js for days on end.
What advantage would we get from handling dropins.js in the service worker? Avoid downloading on reload/second visit? Is there a known way to check if we are offline? I just realized that my current approach to hiding the Dropbox menu option is flawed if you open Winamp2-js and the go offline without reloading.
If we don't precache all the skins, I guess we need to disable those options when offline? Regarding precaching llama-2.91.mp3, I guess it boils down to: Does the user need/expect the demo file in offline mode?

We might also need to see what the header coming from GitHub Pages is

I highly recommend you to use a Firebase Hosting. :wink:
BTW, Firebase Hosting supports HTTP/2.
Also you can easily integrate firebase deploy task into your continuous integration pipeline.

Is there a known way to check if we are offline?

Yes, you can use online and offline events and the navigator.onLine property to see current status: https://stackoverflow.com/a/44766737.
There is also a Network Information API to detect poor internet connection, but that's a different story… :stuck_out_tongue_winking_eye:

If we don't precache all the skins, I guess we need to disable those options when offline?

Can users use skins files from the device storage while offline?

Does the user need/expect the demo file in offline mode?

I believe not, because the demo is needed only for when the user opens the app for the first time. But the very first visit is always online and can not be offline. :smile:


New issue automation fix: convert the jobs into steps to share env variables

Description

The first part of the workflow, Add new issue to project, passed 🎉
The second one failed because the variables were not available. The GITHUB_ENV variables can only be shared between steps, so I converted the jobs into steps here.

You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the GITHUB_ENV environment file. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access.

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable
Testing Instructions

Merge and see
Checklist

[x] My pull request has a descriptive title (not a vague title like
Update index.md).
[x] My pull request targets the default branch of the repository (main) or
a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible
errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

It is possible to keep them as separate jobs and use the output of one from the needs of another [docs]. It depends on how coupled the two are to each other conceptually.

Looks fine, I have one note about the technical feasibility in keeping them as separate jobs: It is possible to keep them as separate jobs and use the output of one from the needs of another [docs]. It depends on how coupled the two are to each other conceptually.

Thank you for this note, @dhruvkb ! I think we could keep these steps as a single job for now, and split in the future, if  more less-coupled steps need to be added.


adds escrow clearing

@m00sey or @kentbull can you please resolve the conflicts here?

yes, I'll fix these right away.

Thanks @kentbull


tslib: "TypeError: Cannot redefine property:" Bug Appears To Have Returned

Bug Report
Version 1.13.0 fixed the bug referenced here:
https://github.com/microsoft/tslib/issues/102
But, in moving to either 2.0.0 or 2.1.0 - the bug is happening again.
🔎 Search Terms
tslib
TypeError: Cannot redefine property:
🕗 Version & Regression Information
This is fixed in 1.13.0 - but broke again in both version 2.0.0 and 2.1.0

This prevents us from using tsconfig aliased paths in conjuncture with jest spyOn(..).  We can work around this by providing the relative paths instead of the paths as determined by the tsconfig - but this is against our code policy.
This changed between versions 1.13.0 and 2.0.0

💻 Code
internal/business functions/directories scrubbed from the following code snippet - but in case this makes it more clear
import * as Utils from '@some-platform/core/libs/utils/support';

describe( 'test tslib compatibility with aliased imports', () => {

	it( 'jest spyOn', async () => {

		// test that we don't get the following error (tslib 2.0 and 2.1 will cause this):
		// TypeError: Cannot redefine property: foobar
		// at Function.defineProperty (<anonymous>)
		const foobarSpy = jest.spyOn( Utils, 'foobar' );

		const imported = await Utils.foobar( );

		expect( foobarSpy ).toHaveBeenCalled();
	} );
} );

🙁 Actual behavior
We're forced to use relative paths when we use jest spyOn type functionality - instead of the aliased paths from tsconfig.
🙂 Expected behavior
We shouldn't have to update our paths to be relative paths.

I'm having the same issue when mocking node's path library return value:
import * as path from 'path';

describe('test path', () => {
  it('should mock path.resolve', () => {
    const pathSpy = jest.spyOn(path, 'resolve').mockReturnValue('/');
    path.resolve('my/unexisting/path');
    expect(pathSpy).toHaveBeenCalledWith('my/unexisting/path');
  });
});

Will throw: TypeError: Cannot redefine property: resolve
Changing the way that Typescript imports the module:
import path from 'path'

instead of
import * as path from 'path'

With this change the test passes but a jest error is thrown, not related to this issue:
Test suite failed to run

    Cannot find module 'jest-util'
    Require stack:
    - /test-project/node_modules/jest-runtime/build/index.js
    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    - /test-project/node_modules/jest-cli/build/cli/index.js
    - /test-project/node_modules/jest-cli/bin/jest.js
    - /test-project/node_modules/jest/bin/jest.js

      at _jestUtil (node_modules/jest-runtime/build/index.js:164:16)

So consider importing just what you need (named imports) instead of importing all (*) from a module.

One solution is not use star exports as suggested by @source-transformer. Another one is a workaround : destructuring assignment of the imported object into new object.
import * as tempPath from 'path';
const path = {...tempPath};
describe('test path', () => {
  it('should mock path.resolve', () => {
    const pathSpy = jest.spyOn(path, 'resolve').mockReturnValue('/');
    path.resolve('my/unexisting/path');
    expect(pathSpy).toHaveBeenCalledWith('my/unexisting/path');
  });
});

This approach will remove the constraints that are applied during transpiling.

Hi, Any updates on the fix for this bug ? This is preventing us from upgrading tslib and typescript as we have 1000+ tests which would need to have a workaround with jest

This is especially problematic because I find jest.mock() to be a black box of buggy behavior.

I got this everywhere in my code and look forward to when I can delete it
// delete when resolved: https://github.com/microsoft/TypeScript/issues/43081
// eslint-disable-next-line @typescript-eslint/no-unsafe-return
jest.mock('foo', () => ({
  __esModule: true,
  ...jest.requireActual('foo'),
}));

It looks like the issue is that the __createBinding helper needs to have configurable: true so that Jest can overwrite the property. @weswigham do you see any reason why making these properties configurable would be a problem?

Following discussion in the Design Meeting, we've decided not to take a fix for this as we would be inconsistent with esbuild, babel, et al. There are already workarounds for this, such as using jest.unstable_moduleMock, and this seems like an issue Jest would need to address in their mock implementation so as to be compatible with other transpilers, such as replacing the module object, introducing a Proxy, etc.


Pr split interface IMetricObserver

What check is failing? I do not have access to see the error? All tests are green on my machine

@kbilsted I've restarted the build, as it failed while downloading some of the build tools.


Kubectl plugin for listing objects

What would you like to be added:
A kubectl plugin that allows to list Jobs and ClusterQueues with comprehensive information.
And a kubectl describe equivalent for Jobs that includes Workload information.
Other useful helpers:

Manually admit a workload.

Why is this needed:
The basic view of kubectl get can't include details such as whether a workload is admitted or why it's pending, because the information is present in compound objects. Similarly, it can't tell the status of a ClusterQueue if it's misconfigured.
Furthermore, when listing Jobs, you wouldn't see the details of the accompanying Workload.
Completion requirements:
This enhancement requires the following artifacts:

[X] Design doc
[X] API change: the command line interface is an API.
[X] Docs update

The artifacts should be linked in subsequent comments.

/remove-lifecycle stale

/remove-lifecycle stale

Here is a design document for what I am thinking: https://gist.github.com/vsoch/954d8c95bdb71bcca92b438bbc879eca. Let me know if you'd like that as a Google document instead. Some notes:

It will be more advantageous to have this scoped to be a command line tool for kueue, and one that folds into being a plugin if desired. I actually think the first use case (where someone could essentially interact with kueue via the command line and not with kubectl) would be hugely great for the converged computing use case - folks are used to command line tools to interact with / manage jobs, and we could provide similar interactions to it.
I've proposed a set of subcommands to start, and additional ones I think would be useful.

And it's assumed that the implementation would be in Go.

oh, we actually have a place for this in the repo itself :)
https://github.com/kubernetes-sigs/kueue/tree/main/keps
Either a PR or a google doc works better as we can comment on specific sections of the design.
I like the idea of a tool that works both standalone and as a plugin. To be fair, a plugin is not much more than a CLI that happens to start with kubectl- :)

All set! https://github.com/kubernetes-sigs/kueue/pull/977

Hey is there a status update here? I made my first plugin last weekend and it was fairly simple so I could jump in to help if the current assignee is low on bandwidth.

Hey is there a status update here? I made my first plugin last weekend and it was fairly simple so I could jump in to help if the current assignee is low on bandwidth.

@vsoch Thank you for offering help. @yaroslava-serdiuk is working on the KEP.
/remove-lifecycle stale

Checking in again - this is still a WIP?

I'm currently not working on it, but AFAIK this should be picked up soon.
@mwielgus do you have any update on it?

I originally couldn't do it because we didn't have a proper CLA, but we do now, in case help is still wanted. Let me know!

/close
I see that @mwielgus created an updated issue.


mgmt: mcumgr: Add iterable section to register MCUmgr handlers

First commit can be ignored.
mgmt: mcumgr: Add iterable section to register MCUmgr handlers

This replaces the requirement for applications to manually
register MCUmgr handlers by having an iterable section which
then automatically registers the handlers at boot time.

[X] Update code
[X] Update samples
[ ] Documentation update There is no documentation about creating handlers, we should probably add this some time
[x] Release notes update

Should probably make all the registration functions static too


Output breaks with lists

when using the following inputs, the output put one list inside the other
Version 1:

a title

a text

Version 2:

other title

other text

Result:

aother title

aother text

It's probably because your HTML is invalid (no closing
 tags)

according to the spec, LI tags do not have to be closed

The end tag can be omitted if the list item is immediately followed by another li element, or if there is no more content in its parent element.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/li


Add fire to the requirement.txt

Added fire module to the requirement.txt due to the dependencies change of other library.
(fire was installed implicitly as a dependency of other libraries, but it is not now.)

Rebased on master due to reflect the pre-commit fix. https://github.com/GoogleCloudPlatform/asl-ml-immersion/pull/454


documentation added for how to install the app generator on AWS Docker

Fixes #1268
Changes: documentation added for how to install the app generator on AWS Docker
Documentation link

Codecov Report

Merging #1269 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development    #1269   +/-   ##
============================================
  Coverage        65.46%   65.46%
============================================
  Files                9        9
  Lines             1523     1523
  Branches           225      225
============================================
  Hits               997      997
  Misses             526      526

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf03fad...84af1c4. Read the comment docs.

Good job. Thanks.


Support for  Qos > 0  for Publisher now ?

Hello Mr Nick,
Does pub support Qos > 0 now? How to work around the issue of not having Qos 1 or 2 for publish?
Without acknowledgment and confirmation, it can be rather problematic to build things.

No it doesn't support >0 publishing. Sorry.

No it doesn't support >0 publishing. Sorry.

Thanks


feat: add value prop to elements create and update objects

Description

Adds value prop to creation object for all Elements.

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.50.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Solar Panels: Create a new Solar Panels entity + SolarPanelsStorage to Create/Update/Delete Solar Panels

Solar Panel is an Asset


Incompatible with Textile Backup

Is it a mod compatibility issue?
Yes
Minecraft version
1.20.1
Describe the issue
The latest Aug 4 Update is no longer compatible with Textile Backup Mod.

https://github.com/Szum123321/textile_backup/tree/2.x

The cause is that Textile Backup is doing non-thread-safe operations. ImmPtl's assertion is triggered in that non-thread-safe operation and cause the backup process to abort. This is primarily an issue of Textile Backup, but manifests when ImmPtl is installed. Even without ImmPtl, the non-thread-safe operation could cause rare bugs in Textile Backup (the change of bugs are very rare so it's usually unnoticed).

In the latest version, the assertion has been changed to non-exception-throwing. So the issue does not manifest. But the thread safety of Textile Backup still exists.


In reset password email i receive token, how do I extract timestamp and signature from it?

For the https://frontend-url/reset-password/ I receive a url like this:
http://localhost:8000/c/eJwVj81uhCAUhZ9Gd5J7-RFYuBg7cdE-RIOCIxkRBrU2ffoyydl9J_nOsZ0wxjFW-44CKuDYImMaWoJEKaTIea9R9hI1VhzCg6zRbH_Ex3rpQClhlAI6GQvSKsUch9GNOFrJOZX12i3HkSp2q-hQsp5PtzUpR0sWl-PzNCmRKYaCstvd0SSz71fM9l1nw7m7_O1txe6WUzPPGpq2xanh2kFTFKYRI6NgteazaCvaHj64_TChGO8oKCvzNBcF7P6xmePMrgAVR7A_-vdcaP85fcivS76uFxtg4HXuUlz9FgMClLePYPz6HvgPYxNXhA

How do I extract timestamp and signature form it to be able to send to:
POST /api/v1/accounts/reset-password/
?

This is all I have:
    REST_REGISTRATION = {
        'REGISTER_VERIFICATION_ENABLED': True,
        "REGISTER_VERIFICATION_URL": "/verify-account/",

        'RESET_PASSWORD_VERIFICATION_URL': '/reset-password/',

        'REGISTER_EMAIL_VERIFICATION_ENABLED': True,
        'VERIFICATION_FROM_EMAIL'<EMAIL_ADDRESS>        "REGISTER_EMAIL_VERIFICATION_URL": "/verify-email/",
        "PROFILE_SERIALIZER_CLASS":
            "custome.users.serializers.UserProfileSerializer"
    }

Ohh.. sorry man, now I understand. mailgun is trying to track my links so it is encoding it and redirects this through it's own link tracker.


Adding test on real-world example

Please consider adding test on real-world example. Thanks!

Please consider contributing one ;-)


update qobj examples

Summary
This is another follow up to #1373, making the header changes propagated elsewhere. Mostly in qobj examples. This commit may actually belong to #1373, whatever @diego-plan9 decides.
Fixes #1066, Fixes #1087
Collectively these commits make some progress in making the various local simulators conform to the specs (in parsing qobj, and reporting result).

Qiskit now puts memory_slots and n_qubits in the config of each single experiment. Although the schema has them as optional, the simulators do need it. This ensures that none of the backends use the info in header to conduct the experiment, only the config and instructions.

The qobj header of each experiment now contains n_qubits, memory_slots, clbit_labels, qubit_labels, clreg_sizes, qureg_sizes, which are helpful for reconstructing the result according to the original circuit specs. The schema and the rest of the codebase have been updated accordingly.

closing this, adding the commits to #1373


add docs on nouns in route

Writing #8140 made me realise there is a rule for how we decide on the correct route for a badge which we follow (mostly? :grimacing: ) but is not expressed in the documentation.

Messages

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against f4930d6ad7828bc5c526ca0bc7abec0d13d1e0f8


BRouter.damsy.net - Segment data link and CSV download

I have noticed the DATA tab disappeared in the mobile web version.
I supposed it is intended to be accessible via link Segment data, ( eventually below the uploaded custom profile.).
But the link seems inactive.  Neither the CSV download provides downloading of wanted CSV file.
I suppose it may be just not implemented yet, so the isue may hang around until done.

Wasn't aware of the issue because I personally do not use the DATA tab at all, so I only now roughly how it works. I'll fix this then, thanks.

It may not be that useful for end users, but is very valueable for profile developers.

@poutnikl Would you mind sharing a screenshot of what is missing actually? I cannot find the issue - for me data (the table) is still available below custom profile upload:

I believe you are talking about something else?

Huh, strange, I would bet I did create a route, but it seems I did not.
With the route created, it works and both segment data and CSV download are available.
I close it as non existent issue, I am sorry for the confusion. :-)

Having the data below the whole custom profile and having the horizontal slide bar below the whole segment data is somewhat inconvenient. I use it often even as an end user, to review quality of roads.
But I can live with that.

The goal is to have the best possible user experience for all users; I'll think about how to address these issues, so let's keep it open for now.

When a custom profile is used,
but then the profile data are Cleared by button and standard Trekking profile is chosen,
the long empty text field with now empty profile remains.
It should IMHO shrink to the previous standard size.


style: center map automatically when data changes

Description
Resolve #726

Center the map to the mean of all available data points whenever new data is loaded to the map
Fix some typos in CONTRIBUTING.md
Add .prettierrc file for a smooth prettier development experience

You're correct - the thing is this useEffect needs to sit inside the map context in order for the setView to work properly - For that we must use one of our own components, i.e. the MapIndex component or introduce a new one with a clear name and a single purpose being the centering mechanism.
What do you think @NoamGaash ?

Check out the error being thrown when I try to do as you suggest:

I see. Have you tried editing center={position.loc}?


Replacing phusion/baseimage to sunfoxcz/baseimage

sunfoxcz/baseimage is based on Ubuntu Xenial 16.4 since the official phusion/baseimage has not support it yet. It's also referencing issue #53

@matriphe thanks for your contribution. I'm glad this works for you.
I don't think it's recommended to use apt-get upgrade since it takes a lot of time!
And I prefer to keep using phusion/baseimage as it's widely supported. Will address that issue in a different way without changing the base image.
Thanks again and keep considering sending PR's.
Regards,

Yes. I agree to wait the official support of phusion/baseimage for Ubuntu Xenial but for now it worked for me. thanks!
FYI, the apt-get upgrade on the freshly Ubuntu Xenial (docker) only upgrade 5 packages, dpkg libsystemd0 libudev1 systemd systemd-sysv and it took lesser time rather than apt-update-ing.. :D


The word "administration" is misspelled

Hi,
The word "administration" is misspelled in this section (see screenshot below):
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/deploy/deploy-and-operate-dynamics-365-on-premises?view=op-9-1#a-deployment-administrator-cant-perform-deployment-adminstration-tasks

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

ID: 40a04598-43c8-b607-f343-98e58bb27423
Version Independent ID: b638d8d2-c0b5-29ec-4fc4-507bce93f830
Content: Deploy and operate Dynamics 365 Customer Engagement (on-premises)
Content Source: ce/customerengagement/on-premises/deploy/deploy-and-operate-dynamics-365-on-premises.md
Product: d365ce-op
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @wikky. This issue has been assigned to the doc author for review.

@wikky - Thank you for your feedback. The article has been revised to fix the spelling issue.
Closing issue.


Typo in the Translation script

Hey, thank you so much for the scripts. When I was looking at the translation script, I noticed a typo: metric= "sacreblue". It should be sacrebleu. Additionally, I noticed that the dataset split is not specified when loading the dataset, which will probably throw an error, it should be like this load_dataset(dataset_name, language_set). Also result = metric.compute(predictions=decoded_preds, references=decoded_labels) should be result = sacrebleu.compute(predictions=decoded_preds, references=decoded_labels). If needed, I can also create a PR with the fixes.

A PR would be great! Otherwise I’ll get to them tommorow 🤗
(will be doing some modifications to ensure all scripts can be ran in <5-10 min tops)


Release v0.1.0

Release first version of the package and publish to pipy and anaconda

Release v0.1.0 succesfully published in pypi
For conda it didn't work with make release :-(
conda publishing will be in another issue because the version then will change


ADD multiple kafka cluster endpoints

you can now add multiple kafka nodes to the broker list.
it will not break existing functionality as long as the clusters already have their ports in there
example:
host: "kafka-10.development.foobar.com:9092,kafka-21.development.foobar.com:9092,kafka-22.development.foobar.com:9092"

Thank you, it's looking good.


Fix links in data page cards

Describe your changes and why you are making these changes
This PR fixes the issue where we didn't apply the right link for cards in data/ page.
Related issue number (if any)
ENG-1503
Checklist before requesting a review
Before: https://www.loom.com/share/f9b4a7957c84445aabb8fb129de1e24d
After: https://www.loom.com/share/2b5a51b53f71432cb364de4fcd979aa0

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

LGTM


Feat/nullable enums

With this PR now custom Enums have a nullable structure like all the sql.NullXXXX
The Null structure is generated for every Enum.
When enums are present on the model we import database/sql/driver
The database type matching is a little bit dirty I think something better can be done, let me know if you have an idea.
Also, how should I go about creating tests for this?

I'll try to get those examples sorted out 👍

I've added the examples on sqlc/internal/endtoend/testdata/enum

Please excuse the unsolicited comment but: Thanks for doing this!  I hit exactly this problem tonight when testing the new sqlc.narg() functionality with an enum type.  I pulled your branch, built it, and I can confirm that your fix seemed to cleanly solve this problem for my query, which looks like this:
 SELECT *
 FROM sessions
WHERE
  sqlc.narg('Status')::session_status IS NULL OR status = sqlc.narg('Status')
...

I really appreciate this.

@danielbprice Thanks for your comment, I got scared that there was a bug on the first two sentences hahaha.
@kyleconroy Do you think you can have a look at this PR? The changes you requested have been done :)

Also recently ran into this issue and looking forward to this PR. If there is anything I can do to contribute (code-wise or testing) let me know.

I'll fork ya and see if I have any luck

@sbres I've fixed the failing test on a PR into your branch, but I'm unsure if that's all the issue was or not.

@sbres Have you a chance to look at my PR. I'm still not sure if it's sufficient, but would love to see this get merged.

@tinyzimmer I've merged it the PR on the forked repo did not have the CI/CD let's see if it gets resolved

@kyleconroy curious if you'll have time in the future to re-review. Assuming the test fixes are appropriate along with everything else.

@kyleconroy Can you please have a look at this, the requested changes have been done in April.
I'm coming close to delivering a project at work and I can't say "just use my forked branch".

@sbres Currently traveling, but will have some time to review in the next few days

@sbres Sorry this took so long to review, but I'm quite happy where it ended up.


fix link & typo

fixed a missing link to feross/standard (was displaying as [feross/standard][1])
switched to using the same link reference style as the badges for feross/standard
moved link references down to the bottom
fixed you a grammar, me

Thanks!

👍


Add representation of "switch"

Summary
This simply adds the representation of a switch statement to Terra, without any of the extra supported needed anywhere else in the package. These will come in follow-up commits.

Details and comments
It's possible there are references to a builder interface left in this PR in places - I tried to squash all of those when I rebased my original branch (I'll add the builder in a follow-up, and it still needs tests writing).  I can either fix them in this PR, or just leave it to make sense when the builder interface is added again.
There's no support added in the rest of the library for this new operation yet; I'll do that in follow-ups.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

59 of 76 (77.63%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.009%) to 85.385%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/circuit/quantumcircuit.py
1
4
25.0%

qiskit/circuit/controlflow/switch_case.py
57
71
80.28%

Files with Coverage Reduction
New Missed Lines
%

qiskit/visualization/circuit/text.py
1
94.96%

Totals

Change from base Build<PHONE_NUMBER>:
-0.009%

Covered Lines:
68077

Relevant Lines:
79729

💛  - Coveralls

From offline Slack discussions, and just for posterity (it's me typing):

for params: I put the circuit bodies in the params so that QuantumCircuit.assign_parameters could continue to work in its current form (though ideally I’d have that use ControlFlowOp.blocks), but I didn’t use the case labels there because there’s really nothing meaningful you could possibly do with them via params
any attempt to modify them would likely invalidate the data structures, and if they’re mashed into a flat structure in params, they’d be no use to the user


Segmentation Fault: 11 - Plugin crashes on iOS

This could be linked to #622, but since I don't know for sure and that one is closed anyway, I'm opening this issue...
I'm getting a Segmentation fault error on iOS, trying to upgrade my nativescript-pdf-view plugin, only when using a simulator with a 64-bit architecture.
I'm not sure at what point exactly the crash happens since there is no stack trace - only the Segmentation fault message:
com.apple.CoreSimulator.SimDevice.E0B5F5A2-42AC-4403-8CC5-D406D0AD355E.launchd_sim[23204] (UIKitApplication:com.merott.NativeScriptPDFViewDemo[0x95f8][23585]): Service exited due to signal: Segmentation fault: 11

I'm using<EMAIL_ADDRESS>iPhone 6 simulator on iOS 8.4.
To reproduce the issue, please clone the nativescript-pdf-view repository and switch to the demo-crash branch, then run:
npm run demo:ios:crash

# OR manually:
npm install
cd demo
npm install
tns platform add ios
tns run ios

Hey @Merott,
It seems that the problem comes from the new UIWebView(CGRectInfinite) call. The CGRect structure uses float types on x86 and double types on x86_64. If you try to do the same in a pure native app, the application will crash in a similar way. Changing this code to new UIWebView(UIScreen.mainScreen().bounds) seems to fix the issue.

Thank you @jasssonpet
The only problem with that is that it seems to prevent view rotation when using UIScreen.mainScreen().bounds. I don't know why, but that's a different matter. As far as ios-runtime is concerned, this issue is resolved.
And thank you for the tip on the simulator crash logs. Definitely helpful!


Release v1.0.0

Welcome to SecurePass - free open-source password manager. This is pull request of first version of application
In this version we will make:

[x] Key checker
[x] Password saver
[x] Password generator
[x] Edit password page
[x] Repository files (README, .gitignore, etc.)

This list will be replenished. Follow the development of the project!

Hooray! We're releasing 🎉🎉🎉


[feature request] Insert newline in message

Version: v0.5.0
Installation method: download binary from Github releases page
Is there a way to insert a newline in the message that I'm typing? Slack GUI has Ctrl+Enter for that.

Yeap, sending multi-line message was first thing that I tried...
Also, input field could be 2-4 lines in height - now it's not comfortable to write long message, because first words are hiding while typing new.

Oh, yes. Coming here in 2024 and trying the same.  Still not working. Project seems a bit dead to me. Pity, but I can't even write go myself :(


doc: Prevent evaluation warnings

Description of changes
Building the manual using nix-build doc previously gave a bunch of warnings because it inspects lib to figure out where all the symbols are. This relates to https://github.com/nix-community/nixdoc/issues/128.
This is not great, because these warnings are not something that can be fixed by the caller, but it causes anybody that depends on the manual build to always have to see them (e.g. as reported here).
This PR solves this by moving the step of figuring out where the symbols are to a Nix evaluation inside a derivation instead, such that the warnings only trigger during build time, and the result of it can be cached too.
Things done

Successfully ran nix-build doc on x86_64-linux

This work is sponsored by Antithesis :sparkles:
Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/suppress-warnings-for-a-derivation/49271/4


remove duplicate webpack dep under devDependencies

Remove duplicate webpack dependency in both dependencies and devDepedencies in package.json, to avoid warning:
npm WARN package.json Dependency 'webpack' exists in both dependencies and devDependencies, using<EMAIL_ADDRESS>from dependencies

@bigardone I assume there's no good reason we need slightly different webpack versions in development vs production?

P.S. Thanks for a great Phoenix-React tutorial @bigardone , making some (hopefully) helpful PRs as I go through!

Hi @soroushjp, first of all thanks for taking time for doing your PR, I didn't notice that :)
Following the official guide from Phoenix Framework, webpack must be a devDependency:
http://www.phoenixframework.org/docs/static-assets#section-using-another-asset-management-system-in-phoenix
Please leave the devDependencies one so I can merge it.
Cheers!

Sorry about the delay @bigardone. Moved to devDependency and set to version ^1.12.11, which is the version that was previously being installed when npm defaulted to the dependency version of webpack.

Hey @soroushjp no problem :)
I had to install some other packages so I finally fixed my self.
Sorry for closing it.

No worries, glad it got fixed!


DSL of IntHolder types

Description
Upgrade the stability level of the DSL for creating an instance of InHolder from experimental to alpha.

Don't forget to move the DSL into the kotools.types.number package in alpha stage!

Checklist

[x] Update the DSL.
[x] Move the DSL into the  kotools.types.number package with an alpha stability level.
[x] Refactor existing code by using this new DSL everywhere.
[x] Update Work in progress section in changelog.

Done.


fix #147

Description

GitHub Issues

And this fixes your problems?! Weird - because at the end of handleSignal() there is a call to reportFatal() which involves quite a bit of strings/streams and other STL shenanigans... Anyway - it's a simple enough change so I'll add it!
Since this PR is against the master branch and not against dev, and since it is only in the doctest.h header instead of in parts/doctest_impl.h - I decided to redo this myself - see contributing.
I won't do a proper release 2.0.1 just for this right now - I'll be unavailable for the next couple of weeks - feel free to use the dev branch:
https://github.com/onqtam/doctest/tree/dev
https://github.com/onqtam/doctest/blob/dev/doctest/doctest.h

This is just a quick and incomplete fix,and I am not sure it solves all problems.


Support multiple terraform versions

If we have a single task with the terraform version hardcoded we have to do all or nothing upgrades. Should do the following:

Rename terraform.yml to 0.10.8.yml
Add a new 0.11.0.yml.

Closed by https://github.com/TeliaSoneraNorge/divx-concourse-tasks/commit/1b0711067f2276616f1f3e85209e4f0421176f56.


macOS binary not using libc shouldn't be dynamically linked against libc++ and libz by default

Xmake Version
2.8.6+20231226
Operating System Version and Architecture
macOS Sonoma 14.2.1 - Apple M2 Max
Describe Bug
A "naked" binary (not using libc) shouldn't be dynamically linked against libc++, libz and libSystem.B.
After compiling the binary you can notice using otool that the binary is linked against several libraries (see attached project to reproduce the issue).
Moreover I'm not so sure that we should use clang++ as a linker. It's probably the reason libc++ appears in the list of dependencies
❯ xmake f -m debug
❯ xmake build -vD app
❯ otool -L build/macosx/arm64/debug/app
build/macosx/arm64/debug/app:
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1600.157.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1)

Note: libSystem is more debatable I think syscalls are not stable on Apple OS hence it's encouraged to use libSystem for your app to not break after OS update.
Expected Behavior
The binary shouldn't be linked against any libraries
❯ otool -L build/macosx/arm64/debug/app
build/macosx/arm64/debug/app:

Project Configuration
target("app")
	set_kind("binary")
	set_languages("c17")
	add_cxflags("-nolibc", "-nostdlib", "-nostdlibinc", "-nodefaultlibs", "-nostartfiles", "-Wall", "-Wpedantic", "-Wextra", "-Wno-gnu-line-marker")
	add_cxxflags("-fno-rtti", "-fno-exceptions", "-nostdlib", "-nostdlib++", "-nostdinc++")
	add_ldflags("-e __libc_start_main", {force = true})
	add_files("src/**.c")

Additional Information and Error Logs
❯ xmake build -vD app
checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang ... ok
checking for the c compiler (cc) ... clang
checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang ... ok
checking for flags (-fPIC) ... ok
> clang "-fPIC" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-nolibc) ... ok
> clang "-nolibc" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-nostdlib) ... ok
> clang "-nostdlib" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-nostdlibinc) ... ok
> clang "-nostdlibinc" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-nodefaultlibs) ... ok
> clang "-nodefaultlibs" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-nostartfiles) ... ok
> clang "-nostartfiles" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-Wall) ... ok
> clang "-Wall" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-Wpedantic) ... ok
> clang "-Wpedantic" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-Wextra) ... ok
> clang "-Wextra" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-Wno-gnu-line-marker) ... ok
> clang "-Wno-gnu-line-marker" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
[ 25%]: cache compiling.debug src/start.c
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -c -Qunused-arguments -target arm64-apple-macos14.2 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk -std=c17 -nolibc -nostdlib -nostdlibinc -nodefaultlibs -nostartfiles -Wall -Wpedantic -Wextra -Wno-gnu-line-marker -o build/.objs/app/macosx/arm64/debug/src/start.c.o src/start.c
checking for flags (-MMD -MF) ... ok
> clang "-MMD" "-MF" "/dev/null" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for flags (-fdiagnostics-color=always) ... ok
> clang "-fdiagnostics-color=always" "-Qunused-arguments" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk"
checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ ... ok
checking for the linker (ld) ... clang++
checking for /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ ... ok
checking for flags (-fPIC) ... ok
> clang++ "-fPIC" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk" "-stdlib=libc++" "-lz" "-target" "arm64-apple-macos14.2" "-isysroot" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk" "-stdlib=libc++" "-lz"
[ 50%]: linking.debug app
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -o build/macosx/arm64/debug/app build/.objs/app/macosx/arm64/debug/src/start.c.o -target arm64-apple-macos14.2 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk -stdlib=libc++ -lz -e __libc_start_main

build cache stats:
cache directory: build/.build_cache
cache hit rate: 0%
cache hit: 0
cache miss: 1
new cached files: 1
remote cache hit: 0
remote new cached files: 0
preprocess failed: 0
compile fallback count: 0

[100%]: build ok, spent 0.351s

you can add set_toolset("ld", "clang")

you can add set_toolset("ld", "clang")

@waruqi Thank you it removes libc++ dependency. Any idea for libz and libSystem?
build/macosx/arm64/debug/app:
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1)

you can add set_toolset("ld", "clang")

@waruqi Thank you it removes libc++ dependency. Any idea for and ?libz``libSystem
❯ otool -L build/macosx/arm64/debug/app
build/macosx/arm64/debug/app:
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.12)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.61.1)

no way now, if you want to build naked binary, you should not use macosx platform. you should use cross platform.
xmake f -p cross --toolchain=clang


ruby-build doesn't seem to find gcc even though it it installed

I'm using ruby-build 20111030 and Mac OS X (10.7.2)
$ ruby-build -v
ruby-build 20111030

When I try to build ruby 1.8.7-p249, ruby-build tells me it couldn't find a suitable gcc binary on my system
$ ruby-build 1.8.7-p249 ~/.rbenv/versions/1.8.7-p249

ERROR: This package must be compiled with GCC, and we
couldn't find a suitable `gcc' binary on your system.
Please install GCC and try again.

As of version 4.2, Xcode is LLVM-only and no longer
includes GCC. You can install GCC with these binary
packages on Mac OS X:

https://github.com/kennethreitz/osx-gcc-installer/downloads

BUILD FAILED

But it looks like gcc is correctly installed on my system :
$ which gcc
/usr/bin/gcc

$ gcc --version
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Any idea?

Please re-read ruby-build's error message and the output of gcc --version you pasted above. Your gcc is actually llvm-gcc.


Why multiply by coefficient?

Can you explain why you multiply the mean by 0.18215 in this line?
https://github.com/shaibagon/diffusers_ddim_inversion/blob/66b6ff42a04db6a0df73aa999f0df0a44ddd8223/ddim_inversion.py#L22C32-L22C39
Thanks

Hi,
I'm not exactly sure where this constant came from.
You can see similar values in, e.g.,:
https://github.com/omerbt/TokenFlow/blob/master/preprocess.py#L167
I guess this is some kind of scaling const used to train SD.
And you are right, I should have gotten this kind of "magic numbers" from the proper config files.


Apply in multi-label task

Hi, I want to know if this function can be directly applied in the multi-label task. I used to use the binary-crossentropy  as my loss function in the multi-label task , now I want to use focal loss to replace it. Should I make some changes or not  ? Anybody help?

I think you can not use it directly

@oguriq take a look at https://github.com/umbertogriffo/focal-loss-keras


Collect coverate from all packages

Summary
As discussed with @cpojer, we should to track coverage for all packages we expose.
This dramatically lowers coverage, which imply we need to write more tests.

cc @dmitriiabramov

Current coverage is 62.26% (diff: 100%)

Merging #2526 into master will decrease coverage by 25.27%

@@             master      #2526   diff @@
==========================================
  Files            40        116     +76
  Lines          1653       4802   +3149
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1447       2990   +1543
- Misses          206       1812   +1606
  Partials          0          0

Powered by Codecov. Last update 4a993aa...2bba0bf

for most of our packages it doesn't really make sense to write unit tests, because we test them using integration_tests. but unfortunately we can't collect coverage from our integration_tests (because we run another jest in subprocess).

@dmitriiabramov I'd rather have a low coverage that we can improve but is correct than a selective coverage we have to maintain over time.

@cpojer agree. honestly, i think jest is a kind of a project that won't benefit much from any coverage metric. I just like the fact that we're dogfooding our own product :)


Information about installing on Redmine 4.x

While trying to migrate either of the plugins with the manuals provided, I get the following error in red, although Bundler v2.0.1 is installed :

You must use Bundler 2 or greater with this lockfile.

Preventing these potential Bundler errors when installing either the Redmine_Base_Deface or Redmine_Maintenance_Mode plugins, I've made this small manual :

Move into Redmine plugins directory

git clone https://github.com/jbbarth/redmine_base_deface

chown -R apache:apache redmine_base_deface/

Move back into Redmine root directory

RAILS_ENV=production bundle exec rake redmine:plugins:migrate

Restart Redmine or reboot VM

Move back into Redmine plugins directory

git clone https://github.com/tofi86/redmine_maintenance_mode.git

chown -R apache:apache redmine_maintenance_mode

Move back into Redmine root directory

RAILS_ENV=production bundle exec rake redmine:plugins:migrate

Restart Redmine or reboot VM

I get the following error.. did you also run into this?

bitnami@serv:/opt/bitnami/apps/redmine/htdocs$ rake redmine:plugins:migrate RAILS_ENV=production
rake aborted!
NoMethodError: undefined method `alias_method_chain' for AccountController:Class
Did you mean?  alias_method
/opt/bitnami/apps/redmine/htdocs/plugins/redmine_login_attempts_limit/lib/redmine_login_attempts_limit/account_controller_patch.rb:5:in `block in included'
/opt/bitnami/apps/redmine/htdocs/plugins/redmine_login_attempts_limit/lib/redmine_login_attempts_limit/account_controller_patch.rb:4:in `class_eval'
/opt/bitnami/apps/redmine/htdocs/plugins/redmine_login_attempts_limit/lib/redmine_login_attempts_limit/account_controller_patch.rb:4:in `included'
/opt/bitnami/apps/redmine/htdocs/plugins/redmine_login_attempts_limit/init.rb:2:in `include'
/opt/bitnami/apps/redmine/htdocs/plugins/redmine_login_attempts_limit/init.rb:2:in `<top (required)>'
/opt/bitnami/apps/redmine/htdocs/lib/redmine/plugin.rb:181:in `block in load'
/opt/bitnami/apps/redmine/htdocs/lib/redmine/plugin.rb:172:in `each'
/opt/bitnami/apps/redmine/htdocs/lib/redmine/plugin.rb:172:in `load'
/opt/bitnami/apps/redmine/htdocs/config/initializers/30-redmine.rb:20:in `<top (required)>'
/opt/bitnami/apps/redmine/htdocs/config/environment.rb:16:in `<top (required)>'
/opt/bitnami/apps/redmine/htdocs/plugins/recurring_tasks/lib/tasks/recurring_tasks.rake:7:in `<top (required)>'
/opt/bitnami/apps/redmine/htdocs/lib/tasks/redmine.rake:202:in `block in <top (required)>'
/opt/bitnami/apps/redmine/htdocs/lib/tasks/redmine.rake:202:in `each'
/opt/bitnami/apps/redmine/htdocs/lib/tasks/redmine.rake:202:in `<top (required)>'
/opt/bitnami/apps/redmine/htdocs/Rakefile:7:in `<top (required)>'
(See full trace by running task with --trace)

hi,
any plan to migrate to 4.2?

This method is deprecated. Please use Module#prepend that comes with Ruby 2.0 or newer instead.
https://apidock.com/rails/Module/alias_method_chain