If statement will not run for valueUrl

The exercise for the if statement wiki page doesn't give the proper results. I included the prefix: "sdmx-code": "http://purl.org/linked-data/sdmx/2009/code#" in the cow_person_example.csv JSON schema, and replaced the "male" column with the following code:
 {
    "name": "male",
    "datatype": "string",
    "@id": "https://iisg.amsterdam/cow_person_example.csv/column/male",
    "dc:description": "The state of being male or female",
    "titles": ["male"],
    "propertyUrl": "sdmx-code:sex",
    "valueUrl": "sdmx-code:{% if male == '0' %}sex-F{% else %}sex-M{% endif %}"
  },

The valueUrl does not seem to accept the if statement, while a "csvw:value" with the same code does run without issues.

This might be related to #148 .
I did a brief look and am wondering whether this feature is even supported. The part of the code that is responsible for processing the valueUrl begins and ends on line 587 and 625, respectively, yet that section only seems to handle virtual columns, collections, and inSchema elements. I could be mistaken of course, but it looks as if there is no code to process these conditional values.

Tried to replicate and I get the same issue: runs fine with csvw:value, but no triples are generated when using valueUrl. I don't recall issues with this previously.

Hi @wxwilcke , though it could be that the output was always missing and we never noticed...

Could this potentially be solved relatively easily by moving a line like https://github.com/CLARIAH/COW/blob/base/src/converter/csvw.py#L629 ? Or is there a lot more complexity to that?

After a lot of testing I discovered that the recent versions of the rdflib json-ld parser won't process URIs with white space in it. This would normally be a good thing, but for some reason COW reads the metadata.json file as a json-ld file. Hence, the jinja pattern in the valueUrl tag gets ignored and is replaced by the base URI:
>>> import rdflib
>>> metadata_graph = rdflib.Graph()
>>> metadata_graph.load('../test/cow_person_example.csv-metadata.json', format='json-ld')
<Graph identifier=N9cadb1c623b84947975324b58c3ce06b (<class 'rdflib.graph.Graph'>)>
>>> for t in metadata_graph.triples((rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'),None,None)):
...     print(t)
...
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#name'), rdflib.term.Literal('male'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#datatype'), rdflib.term.URIRef('http://www.w3.org/2001/XMLSchema#string'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://purl.org/dc/terms/description'), rdflib.term.Literal('The state of being male or female', lang='en'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#title'), rdflib.term.Literal('male', lang='en'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#propertyUrl'), rdflib.term.URIRef('http://purl.org/linked-data/sdmx/2009/code#sex'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#valueUrl'), rdflib.term.URIRef('https://example.com/id/'))

Ideally, COW gets rewritten to read the file as plain json, but this would require quite a bit of work. Instead, I fixed the issue by adding some code that replaces underscores ('_') by white spaces. However, the metadata file now has to be updated by replacing all white space in the valueUrl value by underscores:
{
    "name": "male",
    "datatype": "string",
    "@id": "https://iisg.amsterdam/cow_person_example.csv/column/male",
    "dc:description": "The state of being male or female",
    "titles": ["male"],
    "propertyUrl": "sdmx-code:sex",
    "valueUrl": "sdmx-code:{%_if_male_==_'0'_%}sex-F{%_else_%}sex-M{%_endif_%}"
   },

This allows the jinja patterns to be read by the json-ld parser:
>>> metadata_graph = rdflib.Graph()
>>> metadata_graph.load('../test/cow_person_example.csv-metadata.json', format='json-ld')
<Graph identifier=Nac44aa43f124410492df49bdc00fa9ad (<class 'rdflib.graph.Graph'>)>
>>> for t in metadata_graph.triples((rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'),None,None)):
...     print(t)
...
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#name'), rdflib.term.Literal('male'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#datatype'), rdflib.term.URIRef('http://www.w3.org/2001/XMLSchema#string'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://purl.org/dc/terms/description'), rdflib.term.Literal('The state of being male or female', lang='en'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#title'), rdflib.term.Literal('male', lang='en'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#propertyUrl'), rdflib.term.URIRef('http://purl.org/linked-data/sdmx/2009/code#sex'))
(rdflib.term.URIRef('https://iisg.amsterdam/cow_person_example.csv/column/male'), rdflib.term.URIRef('http://www.w3.org/ns/csvw#valueUrl'), rdflib.term.URIRef("http://purl.org/linked-data/sdmx/2009/code#{%_if_male_==_'0'_%}sex-F{%_else_%}sex-M{%_endif_%}"))

I've uploaded the fix as branch issue148. Could you try the fix please? Instead of installing it using pip, clone the branch and call the csvw_tool.py directly:
./COW/src/csvw_tool.py build cow_person_example.csv
./COW/src/csvw_tool.py convert cow_person_example.csv


Introduce service task stats

Introduce service task stats - this is needed to implement the service debug tab.
/cc @mlunoe

Reviewer: @Poltergeist

LGTM 💯 minus the conflicts!

Awesome work :) especially liking the jsdoc on TaskStats.

Awesome work as mentioned before awesome work on the JSdoc thanks for going the extra mile on that one! LGTM feel free to merge if you are ready.


[vm/ffi]: Passing opaque pointer as Pointer and retrieve it later

I've created bindings for librdkafka using ffigen and building a wrapper library on top of it. There's a C function that takes void *opaque and I can retrieve that opaque pointer in here.
I can use this opaque pointer to pass the context and retrieve it later to use on callbacks.
For example I have to following abstract class that defines the context
abstract class ClientContext {
  void log(RDKafkaLogLevel level, String fac, String message) {
    // Handle logs
  }

  void stats(Statistics statistics) {
    info("Client stats: $statistics");
  }

  void statsRaw(List<int> stats);

  void error(KafkaError error, String reason) {
    error("$error $reason");
  }
}

When creating a client I could do something like
void rd_kafka_conf_set_opaque(
  ffi.Pointer<rd_kafka_conf_t> conf,
  ffi.Pointer<ffi.Void> opaque,
) {
  return _rd_kafka_conf_set_opaque(
    conf,
    opaque,
  );
}
...
final callback = malloc<Void>();
kafkaFFI
  ..rd_kafka_conf_set_opaque(nativeConfig.ptr, callback) // pass it here
  ..rd_kafka_conf_set_log_cb(nativeConfig.ptr, Pointer.fromFunction(nativeLogCb));

void nativeLogCb(Pointer<RDKafka> client, int level, Pointer<Char> fac, Pointer<Char> buf) {
  final $fac = fac.cast<Utf8>().toDartString();
  final logMessage = buf.cast<Utf8>().toDartString();

  final context = kafkaFFI.rd_kafka_opaque(client) as ClientContext; // use here
  context.log(RDKafkaLogLevel.fromInt(level), $fac.trim(), logMessage.trim());
}

Other libraries don't seem to follow this other than rust-rdkafka. I don't really need to pass the context here but doing it might have some befits. It seems not possible or is there any way of doing this?.

I am not entirely sure that I understood your request / question correctly, but if you want to store a reference to the Dart object on the native side the correct way to do it is to create persistent handle and store that. Then you can unwrap the handle and take the reference out whenever you need it.
BTW, I happened to notice that rd_kafka_conf_set_log_cb is documented to call the passed callback on an arbitrary internal thread - this is not going to work with Dart.
/cc @dcharkes

BTW, I happened to notice that rd_kafka_conf_set_log_cb is documented to call the passed callback on an arbitrary internal thread - this is not going to work with Dart.

Tracked in:

https://github.com/dart-lang/sdk/issues/37022


Error log event not saving data in DocumentDB

Using this serilog sink to write into Azure DocumentDB, there seams to be some issue with the sinking for Error event type i.e. in case of passing Exception object.
Here is the code snippet:
 public IActionResult Index()
        {
            try
            {
                int.Parse("s");
            }
            catch (Exception exception)
            {
                _logger.Error("Test error");
                _logger.Error(exception, "Test error");
                throw;
            }
            _logger.Information("test");
            return View();
        }

In the above code:
_logger.Error("Test error"); This works well as we are not passing the exception object.
Whereas _logger.Error(exception, "Test error"); dont log any entry in document DB as we are passing the exception object.
Is there any work-around for this, so that the exception details can be logged into DocumentDB.

@kumprek, thanks for reporting issue with reproducible code. I see that sink had issue with circular references, in this case exception object when used with .net core. Please try http://www.nuget.org/packages/Serilog.Sinks.AzureDocumentDb/3.6.8-dev-00142 and let me know if it fixes issue.

Perfect, this specific Nuget Package works exactly the way expected.


Typescript syntax highlighting issue

Hi! I found a syntax highlighting condition that breaks highlighting for all subsequent blocks of code. Please let me know if you need more information.
Sublime Text 3: 3.2.1 build 3207
TypeScript plugin: v3.4.1
Image:

Code:
if (something) {
    // if the function param is broken onto a new line then the following block's syntax is highlighted correctly
    _.each([], (item) => {
        if (item) { count++; }
    });
}

// here to demonstrate that syntax highlighting works as expected
if (invalid) {
    let something = true;
    const something = true;
    this.something = true;
}

// the problematic line has to be within a block to demonstrate the issue
if (something) {
    // if the function param is all in one line then the following blocks lose syntax highlighting
    _.each([], (item) => { if (item) { count++; } });
    // sytax highlighting still works for the current block
    let something = true;
    const something = true;
    this.something = true;
}

// here to demonstrate that syntax highlighting does NOT work as expected
if (invalid) {
    let something = true;
    const something = true;
    this.something = true;
}

Does it cause your Sublime Text 2 to almost completely freeze and crash? If so I'm getting this too.

I checked out 3.1.0 and it seems to be working. It seems to be a bug with something that was added later.

I am using Sublime Text 3: 3.2.1 build 3207. It does not cause a crash, but simply breaks syntax highlighting for lines after the line that causes the issue as demonstrated in the attached screenshot.
I did not check in Sublime Text 2, but if it causes a freeze and crash then that's more important than syntax highlighting issues.

It definitely causes a crash in 3.3.3333 and 3.4.1. Those are the last two versions I used.

Done. Tested again and created issue #718.


[UPDATE BONUS GUIDE] Update lnbits.md

Adding extra headers for the proxy forwarded.
lnurlw failed without these headers.
Got this from https://github.com/TrezorHannes/vps-lnbits
I don't have a 100% raspibolt environment, so these headers should be verified.

This is correct. At TunnelSats, we have the following proxy settings:
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
                proxy_connect_timeout      140;
                proxy_send_timeout         180;
                proxy_read_timeout         180;
                proxy_http_version 1.1;

Where do we stand on this one? I've a couple of other quick updates that can be incorporated into this PR. Though happy to do another PR but figured we could just group them together.
Minor update to the initial installation:
$ git clone --branch 0.9.7 https://github.com/lnbits/lnbits
Addition to the uninstall steps:
$ sudo rm -r /data/lnbits


The save option is ambiguous in the extension configuration process.

When I click save on the settings tab, I don't get any alerts that the settings have been saved. In fact, I get an alert that notifications are disabled.
The situation is ambiguous because it seems that the configuration was not saved, as it does not allow messages

Hello Joao, I understand your problem and it really makes sense. If the user has checked the option to not receive messages then this shouldn't be seen as a problem. Thanks for the feedback. I will make a request to change this.
Regarding the alert regarding the information saving status, there is no input because the save button itself changes its text when clicked.

Also, a notification message is sent, if notifications are enabled, in the browser and whatsapp via CallMeBot.

I will close this issue. This PR (#27) brings improvements in the control of messages by the user that possibly match your request.


feature: differentiate in vs out validators

Codecov Report

Merging #30 (b923658) into 0.4.0 (dc5958a) will decrease coverage by 1.25%.
The diff coverage is 51.51%.

@@            Coverage Diff             @@
##            0.4.0      #30      +/-   ##
==========================================
- Coverage   86.48%   85.23%   -1.26%
==========================================
  Files          22       22
  Lines         962      982      +20
==========================================
+ Hits          832      837       +5
- Misses         91      106      +15
  Partials       39       39

Impacted Files
Coverage Δ

internal/config/config.go
71.57% <11.76%> (-13.43%)
:arrow_down:

internal/config/service.go
84.71% <85.71%> (ø)

builder.go
94.93% <100.00%> (+0.34%)
:arrow_up:

Continue to review full report at Codecov.

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


STORM-2265: Incorrectly Serialized JSON in TransactionalState causes Worker to Die

@hmcl
I filed STORM-2264, and thought about this approach before.
This approach makes GlobalPartitionInformation serialized well, but the type is lost when deserializing. Deserialized object is not GlobalPartitionInformation.
I haven't deeply look into storm-kafka Trident implementation so hard to guess how this affects.
If we're not sure, just replacing JSONValue.parseWithException to JSONValue.parse only from TransactionalState rolls back the problem. It's just hiding an long ago issue again so need to find out clearer way but given that it is critical, we may need quick fix first.

@HeartSaVioR JSONValue.parse will simply return null if there is a serialization exception. How can that be better than this approach? Isn't anything other than null better than null?

@hmcl
What I'm saying is, given that we've had no issue regarding this and we don't have clear and safe approach, it would be better to roll back to previous.
Two things should be clear:

What's the type of deserialized value of GlobalPartitionInformation? (Please note that JSONValue doesn't guarantee restoring origin type.)
Is it guaranteed for all the paths to use the value from TransactionalState as that type?

And there's compile failure on your change. Please check the Travis CI result.

@HeartSaVioR I agree with you. Let's merge STORM-2264 and keep this open to explore a more compelling fix. If we find out that the work around the Stream API will make this fix unnecessary, we can then close this PR and the associated JIRA.


Importer UI: Display number of missing or unmatched tracks

When importing, it would be nice to add to the "Missing tracks: " line the following :
"Missing tracks (nb or missing tracks / nb of total tracks - percentage of missing tracks %) : "
In my usecase this would help me decide if I should skip (and re-RIP) or import a partial album (I have a bunch of data corruption in some old RIPs).

Looks great! Many people will be happy about this. :sparkles:


vscode-extensons.github.github-vscode-theme: init at 1.1.5

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 109209 1

1 package built:

vscode-extensions.github.github-vscode-theme

Result of nixpkgs-review pr 109209 1

1 package built:

vscode-extensions.github.github-vscode-theme

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109209 run on x86_64-linux 1

1 package built:

vscode-extensions.github.github-vscode-theme

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109209 run on x86_64-linux 1

1 package built:

vscode-extensions.github.github-vscode-theme

@ofborg eval

@ofborg eval


PyPI doesn't provide the arm64 wheels

In #39, the project now builds wheels for arm64 (aarch64) platform, which is great :tada:
However, PyPI only contains the amd64 (x86_64) variants: would it be possible to also provide all the wheels from the latest releases directly through PyPI?
I had a look both at the Travis and GitHub Actions workflow, but I couldn't find if the upload to PyPI was automated or not.
Let me know if I can help!

When you try to upload it to the pypi you catch the error cause the pypi doesn't support it.

When you try to upload it to the pypi you catch the error cause the pypi doesn't support it.

Oh :(
Could you share the command you are using to upload to PyPI and the error message you have (if you still have it)?
There are some packages which (MarkupSafe, PyYAML to name those I know) which provide these wheels, I'd be happy to help and give it a try on my personal PyPI :+1:

Uploading distributions to https://upload.pypi.org/legacy/
Uploading cysystemd-1.4.8-cp39-cp39-linux_aarch64.whl
100%|██████████████████████████████████| 1.85M/1.85M [00:02<00:00, 752kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
Binary wheel 'cysystemd-1.4.8-cp39-cp39-linux_aarch64.whl' has an unsupported platform tag 'linux_aarch64'.


datapath/linux: Refactor device controller tests to use scripttest

This moves test logic previously written in Golang into script language provided by github.com/cilium/hive/script.
Covers all cases tested by the Go tests and additionally exercises all indexes provided by the statedb tables managed by the device controller (devices, routes and neighbors tables).
Stress-tested:
stress -p 30 ./dc.test -test.run=TestDevicesController
5s: 60 runs so far, 0 failures, 30 active
10s: 120 runs so far, 0 failures, 30 active
15s: 180 runs so far, 0 failures, 30 active
...
5m0s: 3790 runs so far, 0 failures, 30 active

/test


⚠ Bofrost.de has degraded performance

In 98a2b5c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1139 ms

Resolved: Bofrost.de performance has improved in 8b2798d after 29 minutes.


Add className prop to series

#101

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Alternatively, you can use the classnames package, so you can avoid doing any string concat operation.


PySide6 and teardown support.

PR to address some of the issues found.

PySide6 (shiboken6) support.
Modified word boundary matching (matches [error] but not -error).
Traceback stack block also ends on next  matched rule.
Plugin teardown support.
Performance improvements (including only adding highlighter to widgets without one).

Also added .mod file for loading alternative (less disruptive to users local setup).
Requires additional testing on earlier Maya versions.

thanks for this PR, tested and works 👍


Add integration with Stable Audio for audio generation

A function that adds audio generated from https://stableaudio.com as audio of a video based on the user's prompt.

There is no API for stable audio available (yet). Unless I missed something.


Question: Going Live?

Can we go live with this podcast plugin? If not, is there a way to integrate this feature?

Not sure, if I understand your questions correctly.
You might have seen, we are on Version 0.9.12. According to semantic versioning this is a beta.
On integrating, we are using MIT license. Follow the link for details.

Going live means that I would record and broadcast at the same time. People can call in, talk to me and it would upload as a recording after the show.

Jekyll-Octopod is neither audio recording software nor audio broadcasting software. It's podcast publishing software. A podcast is audio files distributed via RSS feeds.


Failing Test

When running the test suite, this test fails:
  1) Contract: Bounty Against broken contract claims reward:
     AssertionError: expected '1000000000000000000' to equal<PHONE_NUMBER>000000000
      at _callee5$ (test/Bounty.test.js:96:16)

Hi @elie222, thanks for reporting. The test isn't failing in Travis CI and I can't reproduce the issue on my computer either.
Are you sure you're running the tests on an unmodified repo? Can you tell us more about your setup? Thanks!

I'm going to close this. Not sure how it could have happened. I ran the tests again now and all 743 pass. Not sure what happened that time. Not sure if it was truffle acting up...


Go 1.23 upgrade.

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

Project coverage is 74.10%. Comparing base (6c77757) to head (b09fc51).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
+ Coverage   73.53%   74.10%   +0.56%
==========================================
  Files           6        6
  Lines        1058     1058
==========================================
+ Hits          778      784       +6
+ Misses        200      196       -4
+ Partials       80       78       -2

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


Unable to initialize operation details for swagger based operation

Describe the Bug with repro steps

it happens when the user does not have logic app contributor role.
The issue does not happen if the same user opens the history with the classic designer.

What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
Chrome
Additional context
No response
AB#25091314

i have similar issue with SAP managed connector (When a message is received - trigger) used in Logic app standard.

Also have similar issue: Unable to initialize operation details for swagger based operation - Execute_a_SQL_query_(V2). Error details - Error: Incomplete information for operation 'Execute_a_SQL_query_(V2)'
This occurred after moving API managed connection to new resource group. Logic app was moved previously, but API connections are not supported when trying to use portal to move to new resource group. So I created a new managed API connection to an Azure SQL DB, and then went back into workflow designer and get above error.
Any ideas?

Same issue here:

Sharepoint Connection which was newly created after move of the Logic App to a new Resource Group / Subscription. The 'General availably designer' does not show an error an can work with the logic app, only the 'preview' Designer shows the error.

Closing this issue to track here #3271

Closing this issue to track here #3271

Hey @hartra344 , it looks like you linked back to this issue. I was expecting a link that referenced a different issue in this repo or a related issue in another repo.
Did you intend to close this issue without a link to a spot where it's being tracked?


Make belongs_to an alias of has_one

Looking at the code, there's no real difference for an association being belongs_to and  has_one. Instead, is a source for problems (two places with the same code are two places you can forget to place a fix.. have you noticed the default serializer is obtained differently?). Both do the same thing, and both cause the same consequences in the serialization core.
Also, the jsonapi doesn't care about the direction of a 1-to-1 association.
How about:

Removing the belongs_to method in object_serializer.rb
Adding belongs_to as an alias of has_one, so it is backwards-compatible.

@vovimayhem That is a very nice way to refactor some of the repetition we have in the code today. You are right as far JSON:API is concerned i don't think there is any distinction between belongs_to and has_one. I think we should work on this idea.

I think I can help with this. I will open a PR soon :+1:

Hey
I've got a commit with that on another PR (Sorry!)

c5295e6

No problem. Good work 👍

This should be released in version 1.2 of the gem

I think this is a big problem when has_one and belongs_to are aliased they are logically different and it should be implemented:
A belongs_to B means A has b_id attribute
A has_one B means B has a_id attribute
Current implementation when you have to provide additional attribute for has_one relation is pretty inconvenient

I agree with @ababich and created #257 for consideration

@ababich @abevoelker IMHO the direction/cardinality of the association in the database shouldn't be relevant on the serialization part of JSONAPI.
In both cases, you get the associated object's id and type, regardless if the ActiveRecord/ORM model your'e serializing has it implemented as a belongs_to or a has_one. There should be no extra attributes/options required to declare on the serializer.

@vovimayhem
fast_jsonapi always expects _id field in model A which is inconvenient in lots of one-to-one associations
for example:
we have base model A and with one-to-one relation with model AHeavyDatails and model AStats
both AHeavyDatails and AStats have a_id field
Having a_id in "extension" models is more scalable, etc. but, anyway, this is existing DB design
to describe this design, belongs_to and has_one are used in all popular ORM which helps to describe this logic
I see no reason why fast_jsonapi cannot follow similar convention
what's more, in terms of API it is very convenient to requiest model A and optionally include AHeavyDatails and/or AStats from example above.


Run rustfmt

Somehow I missed that..

@JohnTitor: no appropriate reviewer found, use r? to override


Scherma property type "string" gets rendered incorrectly when followed by enum

Hi @mrin9,
When the property type is string and it is followed by a list of enum the type gets incorrectly rendered in the schema as enum instead of string like in the example below:

Using openapi: 3.1.0
I was wondering if there is any quick fix for this? Thanks in advance!

this is more of a feature than a bug. When the schema has more than just the type  such as enum, format or is it nullable etc, we prefer showing more specific one. This is what we found is desired in most cases.

Thanks for the quick reply and for the explanation. I can see why that's preferred in many of the cases listed.
Is there any workaround to still display the type as string but also use the enum to list the allowed options?
Thanks!

there is none at the moment.
I have added this question in our next internal user-survey. will keep this issue it open for some time for our community user to vote on it

closing as we did not get much traction on it


добавлен просмотр профиля и написан соответствующий юнит-тест

Codecov Report

Merging #2 (934a20a) into master (fb2f222) will decrease coverage by 3.42%.
The diff coverage is 10.00%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
- Coverage   23.88%   20.45%   -3.43%
==========================================
  Files           6       11       +5
  Lines          67      132      +65
==========================================
+ Hits           16       27      +11
- Misses         51      105      +54

Impacted Files
Coverage Δ

app/controllers/AuthController.scala
0.00% <ø> (ø)

app/controllers/ProfileController.scala
0.00% <0.00%> (ø)

app/dao/AuthDaoImpl.scala
0.00% <ø> (ø)

app/dao/ProfileDaoImpl.scala
0.00% <0.00%> (ø)

app/dao/table/EducationInfoTable.scala
0.00% <0.00%> (ø)

app/dao/table/EducationalGroupTable.scala
0.00% <0.00%> (ø)

app/domain/service/AuthServiceImpl.scala
85.71% <0.00%> (-14.29%)
:arrow_down:

app/domain/service/ProfileServiceImpl.scala
100.00% <100.00%> (ø)

... and 4 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 fb2f222...934a20a. Read the comment docs.


Html Link to journal is possible?

Hi , I'm interested if is possible to put a link to open foundryvtt journal and how ?
Thanks

I did it:
window.parent.game.journal.get(id_of_the_journal).sheet.render(true);


multilora_inference调用qwen2-1.5b报错

📚 The doc issue
用examples/multilora_inference.py 调用qwen2-1.5b时，保错 -  RuntimeError: No suitable kernel. h_in=16 h_out=8960 dtype=Float out_dtype=BFloat16
Suggest a potential alternative/fix
No response

https://github.com/vllm-project/vllm/pull/5441 should be able to resolve this issue.

This should be resolved with the new landed Triton kernels https://github.com/vllm-project/vllm/pull/5036


skip msgpack if using SQLLAB_BACKEND_PERSISTENCE and returning results

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

SQLLAB_BACKEND_PERSISTENCE feature stores the results in the results backend which is used to rehydrate tab states. Data is incorrectly being returned in serialized binary form due to the assumption that if we're storing results the query is being executed asynchronously. This pr fixes that assumption by also checking if we're looking to return results (in which case we don't want to serialize).
TEST PLAN

[x] tested locally that sqllab works with SQLLAB_BACKEND_PERSISTENCE feature enabled
[x] tested locally that sqllab works with SQLLAB_BACKEND_PERSISTENCE feature disabled

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@robdiciuccio @betodealmeida

Ideally, we'll always want to serialize to msgpack (vs json) when persisting to the results backend due to the performance gains. Instead of skipping msgpack serialization, can the logic used to fetch stored results and rehydrate the tab state perform the proper deserialization?
I'm still not clear where the issue lies with synchronous queries returning bad data. Is msgpack modifying the payload dict passed into _serialize_payload?
Previously, RESULTS_BACKEND was only used for async queries. What is the expected behavior of server-persisted tab state if no results backend is configured? Should we update the documentation to explain this new use case?

Codecov Report

Merging #9102 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #9102   +/-   ##
======================================
  Coverage    59.1%   59.1%
======================================
  Files         372     372
  Lines       11922   11922
  Branches     2919    2919
======================================
  Hits         7046    7046
  Misses       4694    4694
  Partials      182     182

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 a005e45...460b46d. Read the comment docs.

@robdiciuccio Looks like it's the pyarrow data that's getting sent to the frontend, thus it ends up as '[bytes]' for that key. As for if the feature flag is on and no results backend is configured the following is displayed to the user:


feat(EU): Missing ServiceTemporaryUnavailable Exception in KiaUvoApiEU.py #267

It appears that in KiaUvoApiEU.py errorcode 5031: "Unavailable remote control - Service Temporary Unavailable" is mapped to the generic APIError:
"5031": APIError,

I expected a specific exception in exception.py, e.g. ServiceTemporaryUnavailable so I could catch that specific exception too and could add to my code:
        except exceptions.ServiceTemporaryUnavailable as ex:
            retries = handle_exception(ex, retries)

Thank you for this!


increase amount of garbage allocated in TimeZones

Otherwise this benchmark triggers barely no GC in some machines with larger amounts of RAM.

CSV precompile failure seems unrelated.


Integration and n+1 issues

Project requirements
n+1

Make sure that the N+1 problem is solved when fetching all posts and their comments for a user.

Do not use the bullet gem in this exercise - instead analyze the logs as showed in this article
In your PR description include the screenshots of your app's logs before and after the fix

Integration specs

Use Capybara to write integration tests for each view in your project.

Think on the flow of things and group the tests of page in a way that makes sense. For example, one test would check for the things in the page and another test for clicking links on it.

User index page:

I can see the username of all other users.
I can see the profile picture for each user.
I can see the number of posts each user has written.
When I click on a user, I am redirected to that user's show page.

user show page:

I can see the user's profile picture.
I can see the user's username.
I can see the number of posts the user has written.
I can see the user's bio.
I can see the user's first 3 posts.
I can see a button that lets me view all of a user's posts.
When I click a user's post, it redirects me to that post's show page.
When I click to see all posts, it redirects me to the user's post's index page.

User post index page:

I can see the user's profile picture.
I can see the user's username.
I can see the number of posts the user has written.
I can see a post's title.
I can see some of the post's body.
I can see the first comments on a post.
I can see how many comments a post has.
I can see how many likes a post has.
I can see a section for pagination if there are more posts than fit on the view.
When I click on a post, it redirects me to that post's show page.

Post show page:

I can see the post's title.
I can see who wrote the post.
I can see how many comments it has.
I can see how many likes it has.
I can see the post body.
I can see the username of each commentor.
I can see the comment each commentor left.

@Shedrack-Sunday @NahnahAJ, I've mistakenly submitted my partner's project in my dashboard how can I fix that?

Hello @matee-safi Do you mean this same PR was submitted for the second time by you or it was submitted for the first and second review by you?

Hello @NahnahAJ, I think the first time by me but I'm not sure

@matee-safi Don’t worry the first time when I reviewed, it was your partner who submitted but the second review that received a review from @Shedrack-Sunday was sent by you. So let me ask about this situation from my superiors and get back to you.
This means your PR haven’t been reviewed at all right since this PR doesn’t belong to you?

Yes, this PR doesn't belong to me, Thank you so much!

Hello @matee-safi The review will be reverted on your dashboard so you can resubmit for a first review so kindly be patient and also check your work and submission modes carefully before submitting so as to avoid cases like this 😄

I'll definitely be more careful in the future, I apologize for the inconvenience, thank you so much

Hello @NahnahAJ, My issue still hasn't been fixed

Good morning @matee-safi. A ticket has been created to get that fixed. Because it was late yesterday, it has to be this morning. Kindly be patient while the team resumes work today and handles the ticket. Thank you

@Shedrack-Sunday Got it, thank you  so much

Hello @Shedrack-Sunday, my problem is still not fixed, what should I do?

Hello @matee-safi , but the PR is approved

@matee-safi you need to request a code review request on your dashboard using your own PR.

@Shedrack-Sunday @enniopo my dashboard still says "Changes Required"


Updated StatusField to work with django 1.9 #187

StatusField choices are not set correctly in django 1.9a1.
Would fix #187

Hi, thanks for the contribution! Unfortunately this seems to break the test suite on all pre-1.9 Django versions (see Travis).
I would be more inclined to merge a PR with fixes for Django 1.9 if it actually fixed all the issues with Django 1.9 and made the test suite pass. There are a number of other problems with 1.9 currently: https://travis-ci.org/carljm/django-model-utils/jobs/71797830

Patch is not backward compatible, I'll have to fix it tomorrow. Any suggestions?

ok @carljm

I haven't had time to keep working on the entire task. I'm not aware if anybody else has solved this specific issue or not. Should I close this or send the suggested changes?

The test suite is running on Django 1.9 successfully now, so this is the only 1.9 incompatibility I am aware of. So if the patch is updated to pass on all supported Django versions I will certainly merge it. Thanks!

@carljm could you test the code I propose in my comment ? It should work fine but I have no time to test it at the moment.

@gustavi Sorry I'm short on time too, and don't use StatusField anymore myself. I'll be happy to merge a PR that passes all the tests (and adds a new one that fails before this change and passes after it), but I don't have time to do more than that.

This change is not necessary anymore, another patch was merged to fix this issue.
See the current code:

https://github.com/carljm/django-model-utils/blob/master/model_utils/fields.py#L73-L75
https://github.com/carljm/django-model-utils/blob/master/model_utils/fields.py#L63-L64

Perfect ! Could you make a realease ?

@nemesisdesign Ha, sorry about that! I guess I merged a fix for this in some other PR and didn't even realize it.
@gustavi 2.4 was released a couple weeks ago, and already includes that fix.

@carljm no problem, thanks.


Create a logo for advertisement

Probably, something that combines the logos of OpenEmbedded and ROS

There is no need for an own logo. Using the OpenEmbedded-Core logo on the ROS wiki pages suffices.


pure def is not guaranteed to be referentialy transparent

Due to lack of static checks on the use of nondet, it is easy to write a pure operator that is not referentially tranparent:
>>> pure def f(x) = nondet y = oneOf(1.to(10)); y

>>> f(1)
10
>>> f(1)
4
>>> f(1)
2

IMO, this is a problem from a specification and correctness angle.
My suggestion to address this is to track nondeterminism in the effect system. iirc, this is something @bugarela and I have been planning on for a long while. I'm filing this issue so that the problem is known, but I don't think is changes our priorities at the moment.

Totally, we are missing checks for nondet


Code workflow

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kamilbednarczyk sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Bug-12482] [Master] check for dependency task instance need failover…

closed by #12482

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.8-prepare@b2d682e). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.8-prepare   #12513   +/-   ##
================================================
  Coverage                 ?   20.78%
  Complexity               ?     1602
================================================
  Files                    ?      540
  Lines                    ?    22984
  Branches                 ?     2743
================================================
  Hits                     ?     4778
  Misses                   ?    17716
  Partials                 ?      490

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi @SbloodyS , do you know why the check fails? How can I fix these failures? Thanks

Hi @SbloodyS , do you know why the check fails? How can I fix these failures? Thanks

The CI detection of 2.0. X branch is not complete. Please ignore it temporarily.

OK, I need to test it


Implement a macro generating example tests

Hi there!
While studying the documentation, I came across an outstanding question in the Examples over Testing chapter:

How long until we have a macro that automatically registers examples so they can be run with mix test?

I thought this might be a good first task to work on, as it seems relatively straightforward and would help me get familiar with the codebase and the contribution process.
Please let me know if you find it useful. I'm happy to adjust or expand on it if needed.

Thank you for your work, we all appreciate this macro

Cool, I'm glad it is useful. Since it was included in 'next', shall I close the PR?

ok, done ✅


Feature: Checklist is inconvenient for touch devices

With a touch device, it is very difficult to check and uncheck the checkbox, and it is not possible to operate naturally.
I would like follow-up such as not focusing when checking and taking a large click range.

We can take inspiration from Google Keep:

I like @im-adithya's suggestion of increasing the touchable area around the check box.
Closing this as I don't think there are any underlying bugs with core. The padding of the check box, and any additional pseudo elements to increase the touchable surface, can be controlled via the developer's own styling choices.


Hotfix Windows Packaging

These files are not released on Windows anymore

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-windows-packaging' into 'develop'.

👍


fix doc build pipeline

Description
Fix docs build pipeline

Codecov Report

Merging #748 (37f5ee9) into master (076c99e) will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #748      +/-   ##
============================================
+ Coverage     70.02%   70.04%   +0.02%
- Complexity     4925     4928       +3
============================================
  Files           484      484
  Lines         21793    21788       -5
  Branches       2287     2287
============================================
+ Hits          15260    15262       +2
- Misses         5300     5307       +7
+ Partials       1233     1219      -14

Impacted Files
Coverage Δ
Complexity Δ

...gine/src/main/java/ai/djl/dlr/engine/DlrModel.java
53.12% <0.00%> (-3.13%)
4.00% <0.00%> (ø%)

api/src/main/java/ai/djl/util/Platform.java
46.51% <0.00%> (-2.33%)
8.00% <0.00%> (ø%)

...g/src/main/java/ai/djl/serving/util/Connector.java
55.40% <0.00%> (-1.36%)
21.00% <0.00%> (ø%)

...ngine/src/main/java/ai/djl/mxnet/jna/LibUtils.java
45.39% <0.00%> (-1.23%)
16.00% <0.00%> (ø%)

...ain/java/ai/djl/tensorflow/engine/TfNDManager.java
78.77% <0.00%> (-1.12%)
43.00% <0.00%> (-1.00%)

...ne/src/main/java/ai/djl/dlr/engine/DlrNDArray.java
30.76% <0.00%> (-0.81%)
4.00% <0.00%> (ø%)

api/src/main/java/ai/djl/nn/Parameter.java
79.34% <0.00%> (-0.66%)
20.00% <0.00%> (ø%)

api/src/main/java/ai/djl/nn/core/Embedding.java
44.62% <0.00%> (-0.09%)
12.00% <0.00%> (ø%)

.../main/java/ai/djl/tensorflow/engine/TfNDArray.java
81.69% <0.00%> (-0.03%)
203.00% <0.00%> (-1.00%)

...i/src/main/java/ai/djl/ndarray/NDArrayAdapter.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

... and 9 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 076c99e...37f5ee9. Read the comment docs.


feat: get email from git config

Use template for email in pubspec.yaml, as same as author

@kwalrath ?

Nice change! Could you please go to https://cla.developers.google.com/about/google-individual and sign the CLA, so we can accept your PR?

Seems I signed it previously as an individual contributor. Is that OK? @kwalrath

@pd4d10 for some reason our CLA-checking tool isn't recognizing your GitHub ID. Did you have a different email account when you signed? Did you try signing again?

@kwalrath The two email addresses are the same.
I clicked 'I Agree' button at CLA page again. Is the status updated?

@kwalrath The two email addresses are the same.
I clicked 'I Agree' button at CLA page again. Is the status updated?

Yes! I don't know what the issue was, but we're good to go now.


[Question] Is there some index accross dictionaries ?

I want to build a very simple translator using dictionaries, my concerned languages are English, French and Arabic.
Imagine the following dictionaries:
French
[bourgeois, brunette, contraire, ]
English
[bourgeois, brunette, contrary, ]
If there is an index between the meaning of terms than I can map words easily.
Thanks a lot !

No, there is no index.
These dictionaries contain code to figure out whether a word is valid or not. There is no "meaning" of words


Problem: there is no way to query for transactions via GraphQL

Add the transaction resolver to support the call the mina-block-explorer uses for the frontend.
https://github.com/Granola-Team/mina-block-explorer/blob/main/graphql/queries/transactions.graphql

Closed via #769.


Auto corrected by following Lint Ruby Performance/StringReplacement

Auto corrected by following Lint Ruby Performance/StringReplacement
Click here to configure it on awesomecode.io

Coverage remained the same at 77.759% when pulling 8fce954a97a218efd12e5cb28fc4f2468c6cf6c7 on awesomecode-lint-ruby-performance-stringreplacement-48670 into 828bcc4aec0309bf4417d0304d22e4a3b9750f32 on master.


Switch from StructOpt to Clap in trin-types

What was wrong?
Related to #627. A tiny PR of #651.
How was it fixed?
Switched from StructOpt to Clap in trin-types.
To-Do

[x] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history

superseded by https://github.com/ethereum/trin/pull/740


tdlib fails to compile on Big-endian platforms

Description:
This is not a bug in nchat, it is a bug in tdlib. However, maybe you or someone will be interested to help fixing it. So I will appreciate if this is allowed to be open for the time-being.
[  8%] Building CXX object lib/ncutil/CMakeFiles/ncutil.dir/src/timeutil.cpp.o
cd /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/build/lib/ncutil && ccache /opt/local/bin/ccache /opt/local/bin/g++-mp-14 -DHAVE_EXECINFO_H=1 -D_XOPEN_SOURCE_EXTENDED -Dncutil_EXPORTS -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../ncutil/src -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../common/src -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../../ext/apathy -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../../ext/sqlite_modern_cpp/hdr -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../../ext/clip -I/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/../../ext/cereal/include -isystem /opt/local/include -pipe -I/opt/local/libexec/openssl3/include -Os -DNDEBUG -I/opt/local/libexec/openssl3/include -isystem/opt/local/include/LegacySupport -isystem/opt/local/include -D_GLIBCXX_USE_CXX11_ABI=0 -std=gnu++14 -arch ppc -mmacosx-version-min=10.6 -fPIC -Wall -Wextra -Wpedantic -Wshadow -Wpointer-arith                        -Wcast-qual -Wno-missing-braces -Wswitch-default                        -Wunreachable-code -Wundef -Wuninitialized                        -Wcast-align -MD -MT lib/ncutil/CMakeFiles/ncutil.dir/src/timeutil.cpp.o -MF CMakeFiles/ncutil.dir/src/timeutil.cpp.o.d -o CMakeFiles/ncutil.dir/src/timeutil.cpp.o -c /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/nchat-5.3.5/lib/ncutil/src/timeutil.cpp
/bin/sh: line 1: 39461 Abort trap              /opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/build/bin/generate_common
make[2]: *** [lib/tgchat/ext/td/td/generate/CMakeFiles/tl_generate_common] Error 134
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_PPCSnowLeopardPorts_net_nchat/nchat/work/build'
make[1]: *** [lib/tgchat/ext/td/td/generate/CMakeFiles/tl_generate_common.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

How to reproduce it:
Try building on a Big-endian platform (AFAIK, Linux or *BSD will do, this is not Darwin-specific bug).
Environment:

Version: 10.6
OS / distro: macOS
(However, the issue affects all Big-endian platforms, specific OS is irrelevant.)

Upstream issue: https://github.com/tdlib/td/issues/364 (but with no solution there)

Hi @barracuda156 - I have checked the tdlib code a bit now and it's not a trivial fix to add support for big-endian.
There's quite a bit of low-level message packing/parsing, and it's all assuming little-endian / network byte order.
I can leave this issue open for a while for visibility though.
One thing to consider - nchat could auto-disable Telegram support for big-endian platforms (until tdlib adds support) if that would be useful? At least it would allow building nchat out-of-the-box on such platforms.

@d99kris Thank you very much for looking into that, I appreciate it. (If you or someone will ever consider fixing that in tdlib upstream, I will test that, but perhaps it is not something I am able to fix myself, unfortunately.)
Keeping the issue open is worth, IMO, since it is generally relevant (i.e. not only for an old macOS, but for current *BSD and Linux as well).

One thing to consider - nchat could auto-disable Telegram support for big-endian platforms (until tdlib adds support) if that would be useful?

I am note sure WhatsApp part will build on any powerpc (or arm BE, or mips, or sparc), but perhaps it is sensible. On ppc32 without Telegram there is nothing to build, since WhatsApp here needs Go, and Go is broken (it is broken even on not-too-recent macOS x86_64).
P. S. @glaubitz Just in case, have you looked into tdlib, or maybe someone already fixed it in Debian?

I am note sure WhatsApp part will build on any powerpc (or arm BE, or mips, or sparc), but perhaps it is sensible. On ppc32 without Telegram there is nothing to build, since WhatsApp here needs Go, and Go is broken (it is broken even on not-too-recent macOS x86_64).

I tested on Debian s390x (in qemu) and nchat with WhatsApp builds fine there. So there would be some rationale for disabling tdlib under BE, but yeah I would not expect many actual users on this platform.

@d99kris Re WhatsApp, have you seen this lib? https://github.com/rodarima/libwa
Could it work to drop depending on Go?


Documentation for Datadog Multi-Query Support

Documentation to support the Datadog Multi-Query Support added in https://github.com/kedacore/keda/pull/3550
Checklist

[X] Commits are signed with Developer Certificate of Origin (DCO)

Fixes #3423

OK i screwed this PR up; will re-raise 😅


Fixed #24340 -- Added nested deconstruction for list, tuple and dict values

Nested deconstruction should recursively deconstruct items within list, tuple and dict values.
Supersedes #4129
https://code.djangoproject.com/ticket/24340

Hi Matt and Markus, please see #24340 for a regression introduced by this change and let me know your thoughts about how we could resolve it. Thanks!

The regression is explained in #25280


/auth/me/ not working on production

In my local Django server, I can retrieve the user from  /auth/me/ without any problem. But in production I recieve 401 (Unauthorized) error.
Do I need some special setting server-side to make it work properly? Thank you

Solution is documented here. You can check if your server is running apache using the next command:
sudo lsof -nPi | grep ":80 (LISTEN)"


DRF renderers ignored

https://github.com/AltSchool/dynamic-rest/blob/master/dynamic_rest/viewsets.py#L78 overrides the REST_FRAMEWORK['DEFAULT_RENDERER_CLASSES'] setting. Why? Also, why is there a DYNAMIC_REST setting to disable the browsable API?
I think the easier solution would be using the DRF settings. To enable the dynamic browsable API, just add it to these settings. Like:
    'DEFAULT_RENDERER_CLASSES': (
        'rest_framework.renderers.JSONRenderer',
        'dynamic_rest.renderers.DynamicBrowsableAPIRenderer',
        'myproject.renderers.MyRenderer',
    ),

:+1: to removing renderer_classes. Can you submit a PR?
The setting to disable the browsable API is meant to be used in production environments where performance of the browsable API could be an issue

Wow, that was a fast reply :-) I'm just working on the PR.
To disable the browsable API in prod makes total sense. But that can also be done with the DEFAULT_RENDERER_CLASSES.
I like to split my settings by environment. So here's two ways to do it:
settings/base.py
# dynamic_rest way to do it
DYNAMIC_REST = {
    'ENABLE_BROWSABLE_API': False,
}

# DRF way to do it
REST_FRAMEWORK = {
    'DEFAULT_RENDERER_CLASSES': [
        'rest_framework.renderers.JSONRenderer',
        'myproject.renderers.MyRenderer',
    ],
}

settings/dev.py
# dynamic_rest way to do it
DYNAMIC_REST['ENABLE_BROWSABLE_API'] = True

# DRF way to do it
REST_FRAMEWORK ['DEFAULT_RENDERER_CLASSES'].append('dynamic_rest.renderers.DynamicBrowsableAPIRenderer')

@masterfloda that makes sense, but I would like to keep ENABLE_BROWSABLE_API since this is an additive feature that does not interfere with DRF settings in default configuration (unlike the viewset.renderer_classes override). I do think we should remove the explicit override of renderer_classes at the viewset level.


[hud] Divide by zero error in GhostRunner

Game: GhostRunnder via Wine+Steam
The issue appears as a LOST_DEVICE error, however its cause by a divide by zero error.
Commit 6814ad45d45406c2d2f1cc26360026aa58cc6cf2
[hud] Fix positioning of compiler item when scaled
Adds this line

   { position.x, renderer.surfaceSize().height / renderer.scale() - 20.0f },

Because m_scale value is initialized to zero, and isn't changed ingame, it causes a divide by zero error.
Initializing the value to 1 stops the error occurring but I'm not sure if that is the  proper solution.
Either "renderer.scale() - 20.0f" needs brackets, or the function scale needs to return a non-zero value.

As mentioned, I can't reproduce this at all, and the question would be how scale can possibly be zero at the time this gets called, because we always set it to a non-zero value in HudRenderer::beginFrame, and we always call that before trying to render the HUD items. Under normal circumstances, this should be impossible.
I guess initializing it to 1 is some sort of band-aid that'll work for now, but there's a big problem somewhere.

Filling in some details
Debian (bullseye).
OpenGL renderer string: GeForce GTX 670/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.45.01

As of commit 03f11baf570cb0ca57e84c239695d3f083d96d31, GhostRunner works.

Just a wild guess, but maybe when you are living in Europe and are trying to use a comma as decimal separator like this:
DXVK_HUD=devinfo,fps,scale=0,5
which gets interpreted as scale=0

Good try, but I haven't explicitly set that.


Documentation

Is there a documentation page with config sample for connection to mariaDB (or is it not possible at all)?
Also, I get a lot of error messages when I try to install the program; maybe, the documentation page contains hints for troubleshooting!?

hi @BeckeBauer
App uses sequelize as a proxy to DB and looks like MariaDB is supported, so the app should work.
To configure I would suggest checkout out what needs to be passed to get connection to mariaBD here https://sequelize.org/master/manual/getting-started.html
And update db.json config in the same manner with relevant to your case values: https://github.com/timeoff-management/application/blob/master/config/db.json
Whatever is under development/staging/production section in that config goes straight into Sequelize
Regarding errors, you might want to use older node versions v6.14.4 - it should work on that version.

Thank you vpp, I managed to install it as docker image (with slightly different configuration in the Dockerfile). I can confirm that it works with MariaDB 10.xx. My configuration in db.json:
{"development/test/production": {
   "username": "Username created in MariaDB",
   "password": "Password created in MariaDB",
   "database": "Name of database created in MariaDB",
   "host": "IP address of MariaDB",
   "port": 3307,
   "dialect": "mysql"
 }


Function parameter not renamed in JSDoc

VSCode Version: 143.1
OS Version: Windows 10

Steps to Reproduce:

Create a JS file with the function

function MyClass() {

  /**
   * @param {number} p1
   */
 this.test = function (p1) {
      return p1;
  };
}

Place cursor on "p1" in the JSDoc
Press F2, rename the parameter

Actual result: Parameter will be renamed in method signature and body, but not in JSDoc.
Edit Actually this works in plain functions, but not in "class methods" glued to "this" inside class constructor functions. We used this pattern a lot in our old code base. VSCode recognizes the parameter name when cursor is placed inside the JSDoc, but does not include it in the rename action.

Possible duplicate of https://github.com/microsoft/TypeScript/issues/32069


Unable to commit to flutter/plugins master

https://github.com/flutter/plugins/pull/4584 was landed to flutter/plugins main instead of master, due to a bot redirect that I didn't notice when reviewing. That commit doesn't actually exist on main though, nor is that the branch we are currently using—perhaps the mirroring overwrote it?
I tried opening a new copy of that PR, and a bot immediately re-targeted it to main. We need the ability to open and land PRs against master, since we haven't switched to main yet.

I have verified that this is happening to any new branch I try to open. It looks like the last unaffected PR was opened 15 hours ago, and the first bad PR 11 hours ago.

I found the UI to fix PR targets (I looked before, but missed it somehow), so this can be downgraded. Having a bot trying to sabotage every new PR to land on a branch that will silently eat the PR is still pretty bad though.

I guess the culprit is https://github.com/flutter/cocoon/pull/1493, which somehow changes the behavior of plugins repo.
/cc @CaseyHillers  could you help take a look?

The fix has been deployed. I'll monitor to see if this is still occurring.

The fix has been deployed. I'll monitor to see if this is still occurring.

Verified it is fixed: https://github.com/flutter/plugins/pull/4592. Thanks!


Linked Scopes

When multiple Scopes are specified in Name Definition, the first picked name from this Definition should fulfill all scopes and do not look those names further.

This will only work for Titles and Obscurity for now. Obscurity will use Title if Name Definition from where Title was picked also defines Obscuring scope


add release notes for 0.2.10

Description
This PR adds release notes for 0.2.10

Approved, with some optional minor comments!

Thanks @jni - changes made. I will merge once tests all pass, and then make 0.2.10rc0


Handle structural ensembles containing multiple models

Is your feature request related to a problem? Please describe.
Now that biopandas 0.4.0 is out (:partying_face:) we can moire easily select models from PDBs containing structural ensembles.

Supported in 1.5.0


⚠ SpeakUpConference.com has degraded performance

In 4373b80, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 9654 ms

Resolved: SpeakUpConference.com performance has improved in 2d9af44 after 11 minutes.


Update README.md

I came to this library but It took me a while to understand that is only available for iOS

@hecontreraso This library is available to android and you can use it. At the start it doesn't run because in LocationSwitchPackage has the createJSModules method with @override. Just delete the override annotation and it works to android.

Closed by https://github.com/timfpark/react-native-location/commit/1e16b8f26c17c219c8e5393dd77fbbb368727641


Problem installing Outline.

Describe the bug
Installation fails, with the message "let us know that OutlineService failed to install". The odd thing is, the program appears to be installed, because I can open it after exiting the error window, but it can't connect to any server.
To Reproduce
Uninstall Outline then try to reinstall it.
Expected behavior
Working installation
Screenshots
https://i.imgur.com/ZTGKPcG.png
Client System (please complete the following information):

1.7.1
Windows 10

The only component that seems to have failed in installing was the service, as it wasn't present in the list.

Thanks @Tosh0kan. Did the service files successfully copied to the destination? (the default locations are:)

C:\Program Files (x86)\Outline\OutlineService.exe
C:\Program Files (x86)\Outline\install_windows_service.bat

The second file (install_windows_service.bat) is our installation script to register OutlineService.exe to Windows as a service. We had some reports saying that it might be blocked by some anti-virus software. But to double confirm, could you please run it manually and to see whether there are any errors.

Both files were in the aforementioned folder. When I ran the batch file, the service wouldn't start, but after trying it again, but this time using the "run as administrator" option, it worked and now OutlineServiceshows up in the services list and now I can connect to servers just fine. Thank you!

Thanks @Tosh0kan for the confirmation. I will resolve this issue now.

Happened to me and could not connect to server due to admin permission
After running the bat file, t started to working.
Running on windows


WIP: btrfs-subvol support impermanence on provision

Currently you have to boot the system once before you can convert it to impermanence, manually creating your persistent data subvol and then after switching to it, deleting the @ subvol.
This is suboptimal, and it should be possible to directly provision with impermanence.
First up, the RAMIFY tooling is annoying, and now that btrfs-progs will (soon) support subvol creation during mkfs, throw that all away and use it instead, removing the risk of the metadata allocation filling up during the shuffle and throwing ENOSPC.  As the in-line override is only used during the build of the sdImage, it's contained away from everything else enough I'm happy to do this for now, I expect it'll be able to be removed in a month.
Second with impermanence, / won't be around, so we need to pick someplace that will be persistent to hold nix-path-registration.  All of /nix is probably persistent, and I don't really want to stuff it into /nix/store, so into /nix it goes.  It's a bootstrap detail, so it's created during sdImage creation and used on first-boot, we can change its location however we want without breaking live systems.
Finally, we work out the subvolMap passed to the forked make-btrfs-fs from config.system.build.fileSystems(?) so / can be a tmpfs.  It could use some more asserts for sanity checking, but is otherwise ready to go.
Last patch is not boot tested yet, as the first pass missed re-sizing, so I need to re-run that.
Ref: #18

This has been merged in merge-commit 987002c6781d2fdffb9eef8d2e844a0ab405d925


"Source Dataset" tweaks

Report View: Polishing "Source Dataset" Section
Removed a typo ("source," not "sourced") and added plural, so a report with multiple datasets will label this section "Source Datasets." Also changed the wording when no dataset has been registered.

Read through, looks good


[v1alpha2] Sync commits with v1alpha1

[ ]  Use headless services for Training jobs (#471)

jlewi@ created #574 to track this

[ ] fix field selectors in controller (#465)
[x] Fix dashboard + proxy incompatibility (#441)
[ ]  Create PDB of TFReplicaSet for gang scheduling by kube-arbitrator (#452)

jlewi@ created #575 to track this

There are 4 commits and we should sync them in v1alpha2. #452 #465 #471 needs to be re-implemented and #441 could be cherry-picked.

Yes, we can create new PR for this after merge v1alpha2 to master.

What does sync commits mean? Are we maintaining multiple branches?
I thought per the discussion in #492 the plan was to have 2 different binaries in master 1 for v1alpha2 and 1 for v1alpha1?
So is this issue about keeping both implementations in master in sync? or is this about keeping branches in sync?
I think it will be much better if we keep both implementations on master. Then if there are bits of code that should be the same for both implementations we can just create a function or some other mechanism to allow code reuse.

The commits implements some new features in v1alpha1 and I think we could support it in v1alpha2, too. Then we need to re-implement it in v1alpha2.

@jlewi PTAL #492 and I think we could merge it to continue the development.
We keep two implementations in the PR #492 and I think we should deprecate v1alpha1 when downstream updates to the new API.

@mitake  Now the v1alpha2 is merged and I think you are not blocked now :tada:

@gaocegege @ScorpioCPH I'd like to replace this issue with finer grained issues so its easier to track and assign the actual work items.
I created the issues

#574 to support headless services in v1alpha2
#575 to support gang scheduling

Regarding the PRs mentioned in the first comment

#452 this is about gang scheduling and covered by #575
#471  headless services is covered by #574
#441 Cherrypick fixes to dasbhoard

I believe this is unnecessary because this change is already on master and development of v1alpha2 is on master now so there's now reason to cherry pick this into the old development branch for v1alpha2.

So I think the only remaining issue is

#465 Fix field selectors; is this an issue in v1alpha2? I think we are taking a different approach in v1alpha2?

If its still an issue can we open up a separate issue for it and close this one?

@jlewi Thanks, LGTM, we can close this one.


HOCS-4632: support GRO triaging allocation

Changes to the POGR and the POGR_REGISTRATION flows to support the
movement of a case through to the triaging stages. For GRO cases a new
screen is shown that allows for the selection of a triaging team.

This needs the base changing to main before merging - #669 needs to be merged first.


Add vmlist API

Description
This PR adds the vmlist API to the SDK.
Release Note
Release note for CHANGELOG:

- vmlist API added to SDK

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

/ok-to-test sha=acfdc68

@kstiehl Looks good to me. You can merge this.


Update TV interface

Closes #77
Proposed Changes

Move validate_input and adjust_dimensions to the total_variation function
Call total_variation with all required checks from TVLoss
Adjust tests

@denproc done

@denproc done


Fetch announcements SETTLEMENT_INTERVAL + 2

For a rollover to happen successfully we need to know the oracle announcement details.
Our actor is checking if a new announcement can be fetched every SYNC_ANNOUNCEMENTS_INTERVAL and
ANNOUNCEMENT_LOOKAHEAD hours into the future. Given we rollover every for
hour model::SETTLEMENT_INTERVAL into the future, we want to have at least model::SETTLEMENT_INTERVAL
announcements ready. Due to sync interval coincidence, it might happen that we do not have
synced for a specific announcement yet. Hence, we need to fetch more announcements.
We fetch model::SETTLEMENT_INTERVAL + 2 announcement into the future because of this example:
Assume the last fetch was at 01.01.2022 00:59:55, i.e. 5 seconds before midnight and we would
have synced for model::SETTLEMENT_INTERVAL+1 we would have synced announcements until 02.01.2022
01:00:00. A rollover request happening exactly at 01.01.2022 01:00:00 would ask for the
announcement at 02.01.2022 02:00:00 because of how olivia::next_announcement_after works. Note:
even if the underlying logic of olivia::next_announcement_after changes, fetching model::
SETTLEMENT_INTERVAL + 2 won't hurt.
resolves #2264

bors r+


[NCLS-6564] Set custom logging format when process running

Here process is the CLI process we run for alignment
All Submissions:

[ ] Have you added a note in the CHANGELOG wiki for your change?
[ ] Have you added unit tests for your change?

retest this please


Proposal: Standard Base Image Annotations

I'd like to propose adding two new standard annotations to the spec, to describe information about an image's base image.
(This was previously briefly inquired about in https://github.com/opencontainers/image-spec/issues/783)
Motivation
In general, it can be useful to users to be able to answer the question, "what is this image based on", or even for registry hosts to answer "which images are based on [this image]".
Use cases include being able to:

quickly determine images based on vulnerable base images, without resorting to full image scans.
quickly determine whether an image is based on an image for which a newer version is available.
in certain cases, automatically "rebase" higher-up layers on top of updated base image layers.

In the case of (3), this is known not to be universally safe, but in certain constrained use cases, for example Buildpacks, this can be made to be more safe such that safely rebasing is possible. Being able to produce many updated images at once using only registry API operations can greatly decrease the time it takes to roll out a fix for a vulnerability.
Proposal
To accomplish this, I'm proposing two new layer annotations:

org.opencontainers.image.base.digest digest of the image this image was based on.
org.opencontainers.image.base.ref.name image reference of the image this image is based on, at the time it was built.

If both annotations are provided, the value of base.ref.name is assumed to refer to the same object (image manifest or manifest list) as base.digest refers to at the time the image was built.
Examples
1. Identifying Vulnerable Base Images
Say a vulnerability is found in an image, base-image:v6, with digest base-image@sha256:abcdef12. A patch is applied and rolled out, tagged as base-image:v6 with digest base-image@sha256:deadb33f.
Given an image annotated as above (assuming that annotation is correct), I can trivially tell whether it was based on the vulnerable image, if its image.base.digest annotation is sha256:abcdef12.
2. Identifying Updated Base Images
Say I have an image, my-app:latest, annotated with:

org.opencontainers.image.base.digest: sha256:deadb33f
org.opencontainers.image.base.ref.name: base-image:v6

I can at any point query the registry to determine the current digest of base-image:v6, and if it doesn't match the image.base.digest, I can know that my image is not based on the current base-image:v6 image. Knowing this, I can perform a rebuild to pick up this latest base image to ensure I have the latest base image.
For this to be efficient, base.ref.name and base.digest are assumed to refer to the same object, so clients only need to HEAD the base ref and compare the resulting digest, and not GET a manifest list and HEAD each child manifest.
3. Rebasing Updated Base Images
If I know, due to how my image was built, that my app's layers will be compatible with new layers in my base image, I don't even need to rebuild -- I can rebase.
That is, I can take the layers in my-app:latest, remove the base layers shared in base-image@sha256:deadb33f, and substitute them with the layers in base-image:v6, then push that image back to the registry for further validation and delivery.
This requires being able to identify a "base image seam", that is, which layers in an image belong to the base image, and which belong above the base image.
Rebasing is not guaranteed to produce valid images in all cases. But if the top-most app layers don't assume specific details of the lower base layers, this can be made to be safe.
More thorough examples and documentation in crane and Buildpacks.
Alternatives Considered
Annotating Multiple Base Images
An image might have multiple layers of base images -- e.g., a tagged whole app image, based on a tagged shared base image containing some OS packages, based on a bare OS image.
+-------------------+ <--- my-app:latest
| sha256:abc        |
+-------------------+
| sha256:def        |
+-------------------+ <--- base-packages:v6
| sha256:123        |
+-------------------+
| sha256:456        |
+-------------------+
| sha256:789        |
+-------------------+ <--- base-os:v6
| sha256:000        |
+-------------------+
| sha256:111        |
+-------------------+

One could therefore annotate the image to describe any number of base images. However, this adds complexity, both to the naming and semantics of the annotations (org.containers.image.base[N].digest ?) and in being able to constructively solve any of the motivating use cases listed above.
Instead, I propose only describing one base image seam per image, and if that image itself describes a base image seam of its own, and so on, so be it. In a situation where the base OS image fixes a vulnerability, the intermediate OS-packages base image can address it, producing a new tagged image, which will in turn signal to downstream app images that they are in need of an update.
Layer Index Annotation
Instead of annotating the image with the digest of the base image, one could annotate an integer index into the list of layers that represents the base layer seam. This is relatively straightforward, and still supports rebase scenarios, but it loses valuable provenance information. In this approach you wouldn't be able to answer "is this image based on a vulnerable base image", or "is this image based on an out-of-date base image".
topLayer Annotation
Instead of annotating the image manifest with the digest of the base image, Buildpacks annotates the image with the digest of the "top layer", that is, the top layer of the base image. Layers above this layer are preserved when rebasing.
The disadvantage of this approach is in handling images containing duplicated layers. Perfectly valid images might include the same layer contents (meaning the same layer digest) multiple times, perhaps non-consecutively, which can make identifying the base layer seam using the "top layer digest" approach ambiguous and harder to specify.
It's worth noting that a topLayer annotation, and an integer layer index annotation, both have the benefit of being able to describe the base image seam without needing to consult a registry, though neither can communicate base image provenance. Buildpacks expresses base image provenance information through another annotation mechanism.
Layer Descriptor Annotation
Instead of annotating the manifest with base image information, one could annotate the layer descriptors, to describe the base image seam. This would make it simpler to describe multiple base image seams, but as that's a non-goal (see above), this is not necessary, and having to validate that only one layer is annotated as a base image seam adds complexity.

cc @jonjohnsonjr @ekcasey @sclevine

In practice, this would be most useful if we took it all the way to the extreme of storing a full "tree" of references (given that a single "base" isn't always accurate), wouldn't it?
For example:
FROM golang:alpine AS build
# ... build the thing statically ...
FROM scratch
COPY --from=build ...

Now imagine a critical musl vulnerability that warrants a rebuild of alpine:xxx, which warrants a rebuild of golang:alpine, which then warrants a rebuild of my image.
In a more complex example, you might have something like this:
FROM foo
COPY --from=bar ...
COPY --from=baz ...

# then, separately
FROM that
COPY --from=buzz ...

given that a single "base" isn't always accurate

I've discussed this a bit before with @ImJasonH and we decided to simplify this a bit by just starting with the single base image use case. I think it's definitely possible to adapt the proposal to suit multiple base images, but the semantics get a bit tricky.
The final image has multiple bases, some of which are ephemeral intermediary images that would never get pushed anywhere (with multi-stage builds), so we couldn't reference them directly, but we could capture their base images, which would allow you to detect when a build needs re-triggering.
For some of these cases, you might be able to just annotate a layer -- "this layer derives (eventually) from this base image".
But for more complex cases, there's not an obvious way to represent this... one annotation per layer wouldn't work if a single layer somehow derived from multiple base images, e.g. imagine flattening an image. We could try to force this by having delimiters and multiple values within an annotation (honestly, not horrible), or we could have a fit-for-purpose separate tree data structure that gets attached to the image to indicate its pedigree, not unlike SBOM or signature use cases.
For single-base images,  you get a nice tree structure by default. E.g. you could imagine that I have several images based on ubuntu, and ubuntu might be based on debian (it's not, but imagine it). A rebuild of debian would trigger a rebuild of ubuntu which would trigger a rebuild of my images.
Thinking about it more, a flattened list of base image dependencies sounds like it might actually work. The only change we'd need to make is adding a delimiter for both annotations so that they can support multiple values. I would expect len(base.digest) == len(base.ref) to always be true, which would make correlating the ref and digest trivial, but I'm interested in any cases where that might not be true?
A list of direct base dependencies would allow me to answer all the questions I'd care about, and kind of ducks the definition of what a "base" image really is, if there's only one. We can say that they're just images that this image depends on at build time.
I doubt that I'd ever want to attempt to automatically rebase a multi-based image, as that feels really unsafe, but you'd still get the benefit of knowing where some stuff came from and whether or not an image is up to date.
@ImJasonH WDYT? Anything I'm missing?

some of the annotations are flexible to be used in more than just descriptors. This proposal is very specific to descriptors, and may need particular docs of when it does not make sense i.e. if the blob has been "squashed" such that the base image is no longer fetched for a rebuild. But even as i'm typing that, in the case of a "squashed" image, i would like to know the digest that the image was originally built upon.
i think i'm supportive of the use-case, just trying to get a heads up on all the ways this will get abused. :-D

very specific to descriptors

I think what we settled on in the PR is a single top-level annotation in a manifest, pointing to the base image ref/digest.
The language in the PR seems generic enough to abuse however we'd like :P

then the references seem too spindly to me. :thinking:

The annotations spec already contains this text suggesting that the annotation keys are intended for manifests and image indexes:

This specification defines the following annotation keys, intended for but not limited to image index and image manifest authors:

We obviously can't stop people from annotating anything however they want, but IMO this text helps forestall bug reports where someone applied the annotation to their toaster or whatever and it caught fire.

@vbatts can you expand on the spindly-ness?

Just the clients that pull through an image-index, and go straight to the architecture of their host,
And then handling a list of references.
After thinking about this, there is nothing that will blow up due to this. Fishing with dynamite 🧨


getaddrinfo ENOTFOUND vs https registry

When trying to install this particular package ied does a bit of work, then fails with a weird getaddrinfo ENOTFOUND error:
> ied install css-loader
[==============================] 100.00%/usr/local/lib/node_modules/ied/lib/install_cmd.js:65
        if (err) throw err
                 ^

Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:80
    at errnoException (dns.js:26:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:77:26)
>

Switching to the https registry does work though:
> ied install --registry=https://registry.npmjs.org/ css-loader
>

edit: not sure switching the --registry actually fixed anything, seems intermittent.
Regardless of this bug, perhaps should default to the https endpoint.
> ied --version
ied version 0.3.4
> node --version
v4.2.2

Uhh that is strange. I can't really explain it, but yes, we should use of course use HTTPS.
This might have also produced an inconsistent node_modules directory (problem with way we currently prevent deadlocks), therefore you might have to blow away node_modules after ied failed.

Not sure this was actually resolved… the ENOTFOUND persists regardless of the https or not… but the error doesn't make sense to me so I looked elsewhere for possible workarounds…
So I found a weird way to get it to work though, by setting the http/https agent to keepAlive connections for 5s in  [lib/protocol_to_agent.js](https://github.com/alexanderGugel/ied/blob/master/lib/protocol_to_agent.js#L16-L20):
var agentConfig = {
  keepAlive: true,
  keepAliveMsecs: 5000
}

var protocolToAgent = {
  'http:': httpProxy || new http.Agent(agentConfig),
  'https:': httpsProxy || new https.Agent(agentConfig)
}

I have seen the ENOTFOUND once since setting this, so apparently it doesn't cure it entirely, but after multiple clean installs I have only seen the issue return once.

Would be interested to see if this has any negative or positive performance impact, because this was blocking me from installing anything, I have no baseline to compare against, other than npm itself.
Compare ied and npm installing the same package.json:
ied
> rm -Rf ./node_modules && rm -Rf ~/.ied_cache
> time ied install
ied install  8.33s user 3.32s system 95% cpu 12.204 total

npm 2.14.7
> rm -rf ./node_modules # not cleaning npm cache because slow enough as-is.
> time npm install
npm install --silent  51.60s user 20.30s system 114% cpu 1:02.74 total

Uhh that is weird. Yeah, maybe we just need to use keepAlive.

I'm also experiencing this issue sporadically with ied version 0.3.6

@alexanderGugel please reopen, this was accidentally re-closed in a rebase I think.

I'm having this issue with 0.3.6 too:
❯ time ied install jus
[==============================] 99.93%/usr/local/lib/node_modules/ied/lib/install_cmd.js:65
        if (err) throw err
                 ^

Error: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
    at errnoException (dns.js:27:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:26)
ied install jus  2.73s user 0.70s system 79% cpu 4.340 total

❯ ied -v
ied version 0.3.6

I guess that add retry request can help here.

Still getting this intermittently. It was on the first install using IED, but was on a random module after a bunch of others succeeded. A retry would be great.

Since 0.4.0 we are using got for request. It makes up to 5 retries on errors.
@Qix- you can help if you run ied install with NODE_DEBUG=fetch environment property set and send console output here. Maybe we can figure out something.

Unfortunately I ran into other issues with ied, namely when trying to use electron-prebuilt. Had to switch back to npm.

I guess it was because postinstall scripts do not work here now. Sorry.
@alexanderGugel do we have an issue about npm lifecycle scripts? It helps guys to keep tracking it.

❯ ied -v
ied version 0.4.3

❯ node -v
v5.3.0

❯ ied install jus
[==============================] 100.00%
/usr/local/lib/node_modules/ied/lib/install_cmd.js:65
        if (err) throw err
                 ^
RequestError: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:80
    at ClientRequest.<anonymous> (/usr/local/lib/node_modules/ied/node_modules/got/index.js:68:21)
    at ClientRequest.g (events.js:260:16)
    at emitOne (events.js:77:13)
    at ClientRequest.emit (events.js:169:7)
    at Socket.socketErrorListener (_http_client.js:265:9)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at connectErrorNT (net.js:998:8)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)

Hitting the same problem

@alexanderGugel @zeke I wonder if it's possible that the sheer number of requests is overloading the local network hardware?

Though… npm somehow gets around this.

If it was overloading the local hardware it shouldn't be getting DNS misses, it'd be either a refusal or a timeout I would imagine.

@Qix- yeah you're probably right, the dns entries should be in the local cache anyway. Perhaps it's an issue with OS X's dns handling? @Qix- Any other ideas what could cause this?

Not a clue. Seems random at best and non-reproducible at worst. :/ My favorite kind of bug. /s

@Qix- Yes, we're using got, but will be moving away from it in the RxJS rewrite. Looked through their source, but shouldn't affect timeout.

I'm getting hit by the same bug - though I think its a kernel issue..
If i run a ping command at the same time, i get the following error(s) at the same time ied  fails to download
64 bytes from <IP_ADDRESS>: icmp_req=332 ttl=63 time=27525 ms
64 bytes from <IP_ADDRESS>: icmp_req=333 ttl=63 time=26547 ms
64 bytes from <IP_ADDRESS>: icmp_req=334 ttl=63 time=25559 ms
64 bytes from <IP_ADDRESS>: icmp_req=335 ttl=63 time=24574 ms
64 bytes from <IP_ADDRESS>: icmp_req=336 ttl=63 time=23583 ms
WARNING: kernel is not very fresh, upgrade is recommended.
From <IP_ADDRESS>: icmp_seq=345 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=346 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=347 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=348 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=349 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=350 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=351 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=352 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=353 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=354 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=355 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=356 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=357 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=358 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=359 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=360 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=361 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=362 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=363 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=364 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=365 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=366 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=367 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=368 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=369 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=370 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=371 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=372 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=373 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=374 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=375 Destination Host Unreachable
From <IP_ADDRESS>: icmp_seq=376 Destination Host Unreachable
64 bytes from <IP_ADDRESS>: icmp_req=377 ttl=63 time=2164 ms
``


[Branch View] code format

part of PR https://github.com/go-gitea/gitea/pull/7520
and issue https://github.com/go-gitea/gitea/issues/7454

Codecov Report

Merging #7603 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7603      +/-   ##
==========================================
- Coverage   41.24%   41.24%   -0.01%
==========================================
  Files         469      469
  Lines       63608    63608
==========================================
- Hits        26236    26232       -4
- Misses      33952    33957       +5
+ Partials     3420     3419       -1

Impacted Files
Coverage Δ

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

routers/repo/view.go
42.23% <0%> (-1.02%)
:arrow_down:

modules/log/event.go
65.64% <0%> (+1.02%)
:arrow_up:

Continue to review full report at Codecov.

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

This is change does not really warrant classing as a PR.
Surely this could be folded into a different PR?

i can add it to https://github.com/go-gitea/gitea/pull/7602 or the once wich will folow?

Oh I agree about having good code formatting but I think you're changing all the lines nearby this in another pr - so just put it there. Small formatting PRs are just noise.

-> https://github.com/go-gitea/gitea/pull/7622


Upgrade Capybara and switch to ChromeDriver

https://trello.com/c/MmkirLrD/76-3-switch-from-phantomjs-to-chrome
PhantomJS is end-of-life, we want to switch to a supported driver and ChromeDriver seems the most feature rich, fast and stable.
This PR takes a 'big bang' approach because the latest version of Capybara makes ChromeDriver more stable but this breaks backwards compatibility with PhantomJS:

Upgrade to latest version of Capybara
Remove all conditional logic and makes Chrome/ChromeDriver sole supported engine
Assorted fixes to support these changes (see commit messages for details)

As this is 'big bang' it can be reverted in its entirety if we want to go back to the old behaviour.
I have run several builds on Jenkins to check for flakiness and it seems stable: https://ci.marketplace.team/job/Functional Tests - ChromeDriver/

This looks sensible to me and I agree making one big change is the right thing to do here.
In cddabac the commit message says about upgrading to Capybara 3.0.3 but actually changes to 3.7.2, and in 2ad6401 you upgrade again to 3.35.3. Is that what you were intending to do?

In cddabac the commit message says about upgrading to Capybara 3.0.3 but actually changes to 3.7.2, and in 2ad6401 you upgrade again to 3.35.3. Is that what you were intending to do?

Ah, good spot @alex9smith I think this reflects the evolution of this PR. @bjgill went to the minimum version which had a fix he wanted but I just went to the latest version, which is the approach we decided on now with this 'big bang' there are not concerns about retaining backwards compatibility. I will see if the commit history can be cleaned up at all.

Makes sense - I hadn't realised it'd started out as a minimum possible change. Happy to approve once you've sorted that!

@alex9smith ...OK I've dropped that first commit now and re-worded the other one, so hopefully the commit history makes more sense now.


[Suggestion] Detailed tutorial on Cheat injection / discovery

Is anyone willing to publish one?
I'll be more than happy to link it in the README.
A detailed tutorial on PS4Cheat or NetCheatPS4 is something we all really need...

HaRDHaCkPS3 on psxhax seems to have done a YouTube video.
Anymore contributions are welcome.


⚠ Beulah Revival Network has degraded performance

In dee86f3, Beulah Revival Network (https://beulah.clicki.digital) experienced degraded performance:

HTTP code: 200
Response time: 5756 ms

Resolved: Beulah Revival Network performance has improved in c85aaeb.


Make og-tags.php work with screenshot.png or .jpg

Currently the og-tags.php file only works with screenshot.png, but sometimes we upload a .jpg instead, and forget to change the code. We should make it check for the .png, and if not there, fallback to a .jpg extension.

We also need to fix this on schema.php too.

Added in 12353af!


Initial release

This issue will track the progress of the 1.0.0 release
1st Level Features
Features that must be launched with

[ ] YAML config (partially complete)
[x] Work on globs/file paths as well as data streams

Pluggable rules
2nd Level Features
Features that would be nice to have for initial release, but not blockers

[x] .sass support (dependent upon scssparse or other AST parser Gonzales)

CLI (being able to integrate with other tools higher priority)
Plugin compatibility with ESLint plugins (dependent upon scssparse AST)
Rules
These are the rules we're aiming to support for 1.0.0 as per the discussion in https://github.com/Snugug/sass-lint/issues/3#issuecomment-91764822. Reference

[x] Extends before Mixins
[x] Extends before Declarations
[x] Mixins before Declarations
[ ] EmptyLineBetweenBlocks
[x] EmptyRule
[x] FinalNewline
[x] IdSelector
[ ] Indentation
[x] LeadingZero
[ ] NameFormat
[x] NestingDepth
[x] PlaceholderInExtend
[ ] PropertySortOrder
[ ] PropertySpelling
[x] SelectorDepth
[ ] Shorthand
[x] SingleLinePerProperty
[ ] SingleLinePerSelector
[x] SpaceAfterComma
[x] SpaceAfterPropertyColon
[x] SpaceAfterPropertyName
[ ] SpaceBetweenParens
[ ] SpaceBeforeBrace
[x] TrailingSemicolon

MergeableSelector (this requires significant work - scheduled to a future release)

This comment is not related at all but I am really glad I stumbled across this project, as I just started the boilerplate for the same thing. I am glad that someone else thought of this as well. Will try help out where I can

How is this release tracking? Is there an initial release date?

Rest assured this is still under active development. We're working on the underlying tooling at the moment. I'm holidays trying to crank this out :)

Awesome :shipit: !

Just to add that that is great news! Really looking forward to this. Thanks for all the hard work :+1:

I wonder if it might be possible to start porting some of the existing scss-lint linters by compiling Ruby to JavaScript using https://github.com/opal/opal? Just a pie-in-the-sky naive idea, but maybe it's worth a shot?
Then again using the ESLint plugin system sounds like a good idea too. :)

Looking forward to this greatly! :+1: :shipit:

:+1: :shipit:

Apologies for the radio silence. Work is still happening here. I'm currently a bit bogged down with an upcoming LibSass release but this is happening!

Thanks for the update! I'm sure I speak for the larger libSass community when I say we are REALLY looking forward to this. As far as I can tell there is still not a  Ruby-free system for linting Sass at build-time so I'm very excited about this project.

Update
We will have a 0.x release before a full 1.x release. That release will not include the following:

CLI
Pluggable Rules (although the groundwork is being laid to allow for them)
ESLint Compatibility (we're releasing with Gomez, so no compatibility. Closer to CSS Comb)
A subset of the above rules, with the hope of allowing individuals to start contributing their own

Looking forward to test it! Thanks for great work!

First of all thanks for your work, this looks awesome. I just wonder if it will be also pluggable to a Grunt project?

@Razenbull I don't use Grunt so I would be uncomfortable maintaining a plugin for it, but it's possible to plug it in. If someone would like to write a Grunt plugin for it, though, go for it!

All done for the things we're tracking here! Just cleanup and proper tests left to write!


updated to support python3.3 and python3.4 in addition to python2.7

As promised I made a python3 compatible version of whole-llvm with a minimum of changes.
This has been tested with every test cases plus some real programs (apache, pbzip)

Did this get tested with dragonegg?  I'm trying (for the very first time) to get a dragonegg build
working for travis ci, and I crash (configuring httpd-2.4.12) with:
configure:5285: checking whether the C compiler works
configure:5307: wllvm   -pthread   -DLINUX -D_REENTRANT -D_GNU_SOURCE   conftest.c  >&5
Traceback (most recent call last):
  File "/home/vagrant/whole-program-llvm/driver/as", line 15, in <module>
    from .utils import *
ValueError: Attempted relative import in non-package
WARNING:Failed to generate bitcode ".conftest.o.bc" for "conftest.c"
configure:5311: $? = 1
configure:5349: result: no