Possibly missing some ports

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
Follow the instructions, successfully deploy an IR against an active factory and wait a few days.
Any log messages given by the failure
Node vanished from factory IR. The app service deployment center logs show the container was restarted as a 'background worker' with something about ports. Sorry can't remember exact message. It did not reconnect with the factory.
Expected/desired behavior
No failure, or if restarts, correctly reconnects to the factory.
OS and Version?
Windows, as per the deployment
Versions
Using the latest SHIR (downloaded IntegrationRuntime_5.23.8324.1.msi)
Mention any other details that might be useful
It was half guess-work, but I added the following ports after the RUN line in Dockerfile:
RUN ["powershell", "C:/SHIR/build.ps1"]

ENV PORT=1433
EXPOSE $PORT

ENV PORT=8060
EXPOSE $PORT

ENV WEBSITES_PORT=443
EXPOSE $WEBSITES_PORT

It may be pure luck, but the IR has not failed in 12 days. I think before this the longest we saw was 4 days, the median maybe 3.
Is it possible to say why this might have helped? Or should I revert, and retry and see if coincidence? Or wait longer to observe current behavior? I actually hoping it would fail as usual to see the if the added ports would have made any effect.
Was also wondering, can I use this method to add multiple nodes? I tried scaling out, but this didn't seem to have any impact (no change to the registered nodes in ADF)

Thanks! We'll be in touch soon.

Ah, I need to clarify that I'm building the container locally and pushing to an existing container registry in azure, so my deployment differs a little. But the rest is the same (using the bicep to deploy the app)

Hi @bedalus, as I understand it, you shouldn't need to expose any incoming ports for the self-hosted integration runtime to work. The scenarios in which the SHIR is used are such that incoming ports usually are blocked anyway.
In any case, it sounds like your issue is unrelated to this sample (which is about how to run the container image on App Service) and is instead about the configuration of the container image. I'd suggest you do the following:

Open an Azure support case, and ask the support engineer to help you to identify why your node vanished from the factory.
If you think there needs to be a configuration change made to the container image, please open an issue or pull request against the SHIR container image repo.

I agree, after rebuilding the container without those ports, it's been running just fine for over a week now. I'll open a support case if I see the same again. Thanks

So it has failed again without these ports open, and has generated a log (found under the deployment center logs within the app):
2022_12_12_xn0sdwk000042_platform.log:
12/12/2022 09:19:49.739 ERROR - Site: udal-core-app-adf-ir-prod - [381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98] - Container entrypoint is no longer running.
12/12/2022 09:20:03.399 INFO - Site: udal-core-app-adf-ir-prod - [381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98] - Attempting to stop container: 381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98. Site udal-core-app-adf-ir-prod
12/12/2022 09:20:11.585 INFO - Site: udal-core-app-adf-ir-prod - [381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98] - Shutdown container: 381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98
12/12/2022 09:20:11.601 INFO - Site: udal-core-app-adf-ir-prod - [381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98] - Attempting to remove container: 381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98
12/12/2022 09:20:12.495 INFO - Site: udal-core-app-adf-ir-prod - [381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98] - Container removed successfully. Container Id: 381e95f87055e417364aac8edce73da32f0b873fd35af7c04f931357f52e8d98
12/12/2022 09:20:12.495 INFO - Site: udal-core-app-adf-ir-prod - Purging pending logs after stopping container
12/12/2022 09:20:15.804 INFO - Site: udal-core-app-adf-ir-prod - Creating container image
12/12/2022 09:20:15.976 INFO - Site: udal-core-app-adf-ir-prod - Verifying container image and pull image if necesary
12/12/2022 09:20:17.492 INFO - Site: udal-core-app-adf-ir-prod - Pulling container image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest. AuthType: Token
12/12/2022 09:20:18.449 INFO - Site: udal-core-app-adf-ir-prod - Image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest
Status: latest Pulling from udal-core-adf-ir-prod

12/12/2022 09:20:18.494 INFO - Site: udal-core-app-adf-ir-prod - Image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest
Status: Digest: sha256:feb3c87a16910f17a0689fa1756f61ff191c37f753e946bb75512b2e140ea196

12/12/2022 09:20:18.494 INFO - Site: udal-core-app-adf-ir-prod - Image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest
Status: Status: Image is up to date for udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest

12/12/2022 09:20:18.842 INFO - Site: udal-core-app-adf-ir-prod - Attempting to create container
12/12/2022 09:20:18.842 INFO - Site: udal-core-app-adf-ir-prod - Creating container for image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest.
12/12/2022 09:20:19.544 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Create container for image: udalcrcoreprod.azurecr.io/udal-core-adf-ir-prod:latest succeeded. Container Id 32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd
12/12/2022 09:20:19.544 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Attempting to start container. Container memory limit: 1024 MB. For more information, refer https://aka.ms/configurecontainer.
12/12/2022 09:20:50.776 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Start container succeeded.
12/12/2022 09:21:01.633 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Container has started.
12/12/2022 09:21:01.633 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Customizing the container
12/12/2022 09:21:04.446 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Container customization has completed successfully
12/12/2022 09:21:04.477 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Container has started.
12/12/2022 09:21:06.531 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Container entrypoint has started
12/12/2022 09:21:06.531 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - The container doesn't have a port exposed and it will continue running as a background worker.
12/12/2022 09:21:06.546 INFO - Site: udal-core-app-adf-ir-prod - [32a574603920f67a77ab8c3953433a1efeeeefeb5929c1b8082d8451c4eca0fd] - Container start-up and configuration completed successfully

The message "The container doesn't have a port exposed and it will continue running as a background worker" is identical to what we saw initially when I first raised this issue, and caused us to rebuild with the ports.
The automatic repair (or whatever restarts the container) does not result in a re-attach to the ADF IR. The only way that I have found to do fix is to delete the node from ADF IR, and delete the app from Azure, then redeploy it.
As it currently is, I cannot rely on this for a production process. Can you see anything here that I might have missed?

Other work(1) is using undocumented command-line arguments:

setup timeout: https://github.com/ingenii-solutions/azure-data-factory-self-hosted-runtime/blob/main/scripts/entrypoint.ps1#L61-L66
and use timeout: https://github.com/ingenii-solutions/azure-data-factory-self-hosted-runtime/blob/main/scripts/entrypoint.ps1#L74

I have not tested that code or even parameter usage because ACI does not support VNets with windows. If that's a real parameter for dmgcmd.exe -RegisterNewNode it looks like a good solution. Sadly API for SHIR registeration is not documented.
(1) https://github.com/ingenii-solutions/azure-data-factory-self-hosted-runtime

About the issue: do you have a log from data factory? At least critital, error and warning events?
I feel like ACI could be e.g. running out of memory and then instance is killed. The The container doesn't have a port exposed and it will continue running as a background worker. is probably printed for all containers not exposing ports.
SHIR itself does not handle incoming TCP connections except port for high-availability if HA is enabled. The main point of gateway component is to reverse traffic flow in order not to have requirements for incoming traffic.

I've just now performed this sequence of steps:

Delete the node (named 'AppServiceContainer') from the ADF IR
Restart the app

This has solved half the problem. With the 'AppServiceContainer' removed from ADF, it seems the restarted app is able to register with the IR again with the same name.
When the app restarts itself, action (1) does not happen.
Would it be possible for the name to be incremented each time to observe if the container restarts itself, that it is able to automatically re-register as a node with a distinct name?

Or you could try deleting node before starting SHIR: https://learn.microsoft.com/en-us/rest/api/datafactory/integration-runtime-nodes/delete?tabs=HTTP
IIRC integration runtime can have only four nodes.

@bedalus As per my earlier comment, I think the best way forward would be to open a support case.
However note that the lack of incoming ports is intentional. The SHIR is designed to work with a relay service, which means it doesn't have incoming ports opened. So I doubt that the issue you're seeing relates in any way to ports.


Python: updated pyproject and lock

Motivation and Context

replace a bunch of other package update PRs
Removed obsolete package specification for py<3.10
Description

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingTOTAL6258103184% report-only-changed-files is enabled. No files were changed during this commit :)
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1341
1 :zzz:
0 :x:
0 :fire:
13.284s :stopwatch:


Spacy is not working with the version 8.10 of click.

Environment:

Python version: 3.9 and 3.8
Click version: 8.10

See also https://github.com/explosion/spaCy/issues/10564

When reporting an issue, be sure to include a minimal reproducible example, and a description of the problem, as it relates to the library.
The referenced function was previously deprecated, and is now removed. https://werkzeug.palletsprojects.com/en/8.1.x/changes/#version-8-1-0
8.0.0:

click.get_terminal_size() is deprecated and will be removed in 8.1. Use shutil.get_terminal_size() instead. #1736

8.1.0:

Remove previously deprecated code. #2130

get_terminal_size is removed, use shutil.get_terminal_size instead.

You should use a tool like pip-tools to pin your dependencies and control when you get updates. Be sure to run tests with deprecation warnings treated as errors so that you get notified of these types of changes early.

Typer has not addressed this yet: https://github.com/tiangolo/typer/pull/375 (and duplicates) are not in yet, much yet released.
Would something like this be acceptable to provide a transition period?
def get_terminal_size(*args, **kwargs):
    msg = "Deprecated, please use shutil.get_teriminal_size instead"
    warnings.warn(msg, FutureWarning, stacklevel=2)
    from shutil import get_terminal_size
    return get_terminal_size(*args, **kwargs)

All typer apps are broken at the moment, and this is not an underscore import, like the one that broke black. Just curious. Actually, guessing from above, something like this was probably there, but probably was using a 'lesser' warning level.
FutureWarning is the correct warning to provide for a removal that is about to happen. According to PEP 0565, there are three levels of deprecation warnings, with FutureWarning being the highest level. Ideally, you step through two or three levels, but the final level should be FutureWarning, since it shows up for everyone.
Also, stating people should lock dependencies does't help if it's a library that's broken (Typer, in this case). If you start a brand new project, pip install typer is broken. Pinning via a typer app via pre-commit is broken, etc. Libraries can't lock their dependencies[^1], only apps can.
[^1]: Libraries can lock them in their own CI. But not for users.

Usages like this are breaking:
- repo: https://github.com/hadialqattan/pycln
  rev: "v1.2.5"
  hooks:
  - id: pycln
    args: [--all]

https://scikit-hep.org/developer/style#pycln
There's no way to use pip-tools with something like that. I personally already use locking (via PDM mostly) for applications where it matters to me.
I would really recommend using at least a single release of FutureWarning before removing something without an underscore - obviously, what was done wan't enough for typer, which is a major dependent library. While I like warnings as errors and recommend it (https://scikit-hep.org/developer/pytest#configuring-pytest), it's not that common - many users don't know about it or find it annoying to enable[^1]. Also, due to the despicable practice of capping dependencies (heavily pushed by Poetry), many users are just now removing/updating ^7 caps to ^8, causing them to completely miss the 8.0 release and jump to 8.1. FYI, PyTest also removes deprecated items in the .1 releases.
I've already spent two days updating 30+ packages pre-commit's to use black 22.3.0, so the 4-5 packages that needed the extra pin added to pycln was a bit annoying, but it is not an issue for me, this was just suggesting something that would be nice for the other users of click via Typer. And the fact our developer guidelines are suggesting something that is broken is also bothersome, thought our cookiecutter already has the current workaround pin. And it was technically these libraries fault for not having warnings enabled, though I like to err on "being nice" over being "correct".
[^1]: See, for example, https://github.com/scikit-hep/pyhf/pull/1773#pullrequestreview-878643489

FYI, I mentioned this to Sebastián and he replied "I'm on it!". So this hopefully will be fixed there soon. :)

Typer 0.4.1 is out. :)

Hello! I just released Typer 0.4.1 that should handle this. :rocket: :nerd_face:


fixes to time & date bugs

as seen in newer UTE UWP releases and TextPad

btw it also adds some new date/time formats :D


Standardize on pid -> PID

Good note - I'll make sure to use PID in the future.

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Update cats-effect to 3.2.9

Updates org.typelevel:cats-effect from 3.2.8 to 3.2.9.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: library-update, semver-patch

Codecov Report

Merging #11 (aa45483) into main (c6e4ed7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   68.53%   68.53%
=======================================
  Files          16       16
  Lines         178      178
  Branches        2        2
=======================================
  Hits          122      122
  Misses         56       56

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 c6e4ed7...aa45483. Read the comment docs.


2-pass encoding

Hello Im trying to implement 2-pass encoding using
ffmpeg -an -y -i "filename.mp4" -c:v libx265 -x265-params pass=1 -f null NUL
ffmpeg -i "filename.mp4" -c:v libx265 -b:v 2600k -maxrate=3M -bufsize=3M -x265-params pass=2 -c:a aac -b:a 128k "2pass-filename.MKV"
but am not sure how to do that, if at all.
for the first pass, I tried using
for file in folder:
    infile = ffmpeg.input(file)
    infile.video.output(
    'NUL',
    f='null'
    vcodec='libx265',
    video_bitrate=2600k,
    maxrate=3,
    x265-params='pass=1'
    ).run(overwrite_output=True)

and similar, though none of my attempts created the x265_2pass.log.temp file that ffmpeg creates to hand off to pass 2. Any advice?

I was wondering why this was on my dash for long lol
Anything useful learned went into:
edeloya/ffmpeg-fast-2-pass


Using I32Constant with negative value spins forever when emitting binary

Describe the bug
The body of the function below simply loads a single negative value constant on the stack and returns it. The emit_binary call will spin forever.
To Reproduce
#[test]
fn negative_one() {
    let mut builder = ModuleBuilder::new();
    let one_i32 = ResultType::from(vec![ValueType::I32]);
    let func_type = FunctionType::new(ResultType::empty(), one_i32);
    let func_type_index = builder.add_function_type(func_type).unwrap();
    let body: Expression = vec![
        NumericInstruction::I32Constant(-1).into(),  // any negative value will spin, any positive value will run
    ]
    .into();
    let main_func = Function::new(
        func_type_index,
        ResultType::empty(),
        body,
    );
    let main_func_index = builder.add_function(main_func).unwrap();

    let name = "spins_forever";
    let export = Export::function(name.into(), main_func_index);
    builder.add_export(export);
    let module = builder.build();

    let mut buffer = Vec::new();

    // This line spins forever if a negative value for the I32Constant is used
    emit_binary(&module, &mut buffer).unwrap();
}

Expected behavior
The I32Constant takes a rust i32 (signed 32bit integer). The constant should either take a u32 or work with negative values for i32
Toolchain
stable-x86_64-unknown-linux-gnu

The issue is in https://github.com/misalcedo/wasm-ast/blob/d47841b3f76e0ca3deaab1613beb7ea5db000801/src/leb128/mod.rs#L150. This test demonstrates why that function loops forever:
#[test]
fn test_i128_shift() {
    // Set a signed i128 to only the high bit, making a negative value
    let high_bit_only: i128 = unsafe { std::mem::transmute(1u128 << 127) };
    assert!(high_bit_only < 0);

    // Shift that value to the right by seven bits
    let mut value = high_bit_only;
    value >>= 7;

    // The high bit is still set after the shift (the shift is signed-aware)
    assert!(high_bit_only & value == high_bit_only);
}

Because the shift operation is signed-aware, the value will never become zero, which is the exit condition for the loop


AutoGraph could not transform when fine-tuning HuggingFace Pretrained Model

System information
Macbook OS 11.6
numpy==1.19.5
pathlib2==2.3.5
python==3.8.8
tensorflow==2.7.0
transformers==4.2.0

Describe the current behavior
During .fit(), receiving warnings:
WARNING:tensorflow:AutoGraph could not transform <bound method Socket.send of <zmq.Socket(zmq.PUSH) at XXX >> and will run it as-is.
Please report this to the TensorFlow team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output.
Cause: module, class, method, function, traceback, frame, or code object was expected, got cython_function_or_method
To silence this warning, decorate the function with @tf.autograph.experimental.do_not_convert

and
The parameters `output_attentions`, `output_hidden_states` and `use_cache` cannot be updated when calling a model.They have to be set to True/False in the config object (i.e.: `config=XConfig.from_pretrained('name', output_attentions=True)`).
The parameter `return_dict` cannot be set in graph mode and will always be set to `True`.

Would not have submitted except for the "please report" phrase in first warning. Happy to close quickly if this is resolved/trivial.
Describe the expected behavior
Neither of these warnings to appear prior to training.
Standalone code to reproduce the issue
# train_texts is a list of strings
# train_labels is a list of integers (0,1)

import tensorflow as tf
from transformers import AutoTokenizer, TFAutoModelForSequenceClassification
from sklearn.model_selection import train_test_split

train_texts, val_texts, train_labels, val_labels = train_test_split(train_texts, train_labels, test_size=.2)
checkpoint = "cardiffnlp/twitter-xlm-roberta-base-sentiment"
tokenizer = AutoTokenizer.from_pretrained(checkpoint)

train_encodings = tokenizer(train_texts, truncation=True, padding=True, max_length=512, return_tensors='tf')['input_ids']
val_encodings = tokenizer(val_texts, truncation=True, padding=True, max_length=512, return_tensors='tf')['input_ids']
test_encodings = tokenizer(test_texts, truncation=True, padding=True, max_length=512, return_tensors='tf')['input_ids']

train_dataset = tf.data.Dataset.from_tensor_slices((
    train_encodings,
    train_labels
))
val_dataset = tf.data.Dataset.from_tensor_slices((
    val_encodings,
    val_labels
))
test_dataset = tf.data.Dataset.from_tensor_slices((
    test_encodings,
    test_labels
))

model = TFAutoModelForSequenceClassification.from_pretrained(checkpoint)

optimizer = tf.keras.optimizers.Adam(learning_rate=5e-5)
model.compile(optimizer=optimizer, loss=model.compute_loss)
## Warnings occur here:
model.fit(train_dataset.shuffle(1000).batch(16), epochs=3, batch_size=16)

Other info / logs
Verbose==10 logs leading up to warning:
tf_verbose_log.txt

@adam1brownell,
You can suppress all debugging logs using below code snippet. Try setting log level before importing tf
import os
os.environ["TF_CPP_MIN_LOG_LEVEL"] = "3"
import tensorflow as tf

OR
import logging
logging.getLogger('tensorflow').disabled = True


pico_unique_id header needs some updates

From reading the comments in unique_id.h (which also appear here ) you might think that pico_get_unique_board_id always returns the ID of the flash chip. However looking at the implementation it looks like that on RP2350 it actually gives you the SYS_INFO_CHIP_INFO (which I think is described in section <IP_ADDRESS>. of https://datasheets.raspberrypi.com/rp2350/rp2350-datasheet.pdf ?).
And I guess this also means that you won't get a unique_id of all-0xEE on PICO_NO_FLASH builds for RP2350? :wink:

Yes, it, it uses a value from OTP on rp2350

merged into devleop


PubID 1.0: "ADHOC" cannot be "report number" according to the standard

<report-num> = ( <sequence-num> |
               ( <subseries-num> [<subseries-id>]′′-′′<sequence-num>) )
     <sequence-num> =
<subseries-num> =
<subseries-id> = ′′GB′′ ; GB used for SP 1190 GuideBriefs

For identifier NBS RPT ADHOC "ADHOC" cannot be "report number" according to the standard

Now we are parsing ADHOC as report number.


IOS Not full animation to the pressed tab when keyboard is opened

Current behavior
Animation between tabs not scrolls to the end.  The onIndexChange  not fires as a result. Animation ends if click on content
https://user-images.githubusercontent.com/45219732/182527044-70fa1bcb-52dd-46fb-9c66-c23b91732553.mp4
Expected behavior
Animation ends, onIndexChange fires
Reproduction

Platform

[ ] Android
[X] iOS
[ ] Web
[ ] Windows
[ ] MacOS

Environment

package
version

react-native-tab-view
3.1.1

react-native-pager-view
5.4.25

react-native
0.64.2

expo
no

node
18.7.0

npm or yarn
npm 8.15.0

I'm experiencing the same issue with version 3.1.1 and the current RN version (0.69.1) when using a textinput with autofocus enabled. A downgrade to version 2.16.0 fixes the issue.

Hey @Kruglyanski can you add a snack reproducing this?


UF-244: (Work-around) Default DEV environment to Wildfly 10.0.0(CR4)

See https://issues.jboss.org/browse/UF-244
This PR provides a workaround to the issue (of Async EJBs not running on Wildfly 8.1 - which is our Hosted Mode environment). Support for System Property org.uberfire.async.executor.safemode to force use of Executors.newCachedThreadPool has been added.
This PR sets the said System Property to "true" to ensure Hosted Mode (which uses Wildfly 8.1) works without further ado with mvn gwt:run or from your favourite IDE.

+1
master: 0419787f4ea23a5e7dbe2c7b10d0f7e5b525faca


Support other flight APIs

Obviously beggars can't be choosers when using a free API but OpenSky's response time & uptime have been rough recently. It would probably be worthwhile to explore supporting other APIs to drop in as replacement options in the event that the current downtime continues.
From a quick search we have a few options:

(Free) ADSB.lol: https://api.adsb.lol/docs
(Free-ish) FlightAware : https://www.flightaware.com/commercial/aeroapi
(Not Free) ADS-B Exchange: https://www.adsbexchange.com
(Not Free) Flightradar: https://www.flightradar24.com/commercial-services/data-services

ADSB.lol looks great but I'm not sure if it will be feasible to integrate on-device unless I can make some heroic memory savings elsewhere. With the size of the raw JSON response from ADSB.lol we currently have space in memory for around ~23 aircraft. This isn't nearly enough if the map includes major airports, e.g. KBOS currently has over 100 aircraft in the area.
Alternatively, we could put a proxy server in between the API(s) and the Skyportal but I was hoping to have everything be able to sit on a single device.

Merging in 935ec1c45e2abd9cd0c1367def79ed2ae29c25db I think takes care of the immediate need here. ADSB.lol integration is technically functional but will choke in areas of high congestion. I believe this is a drop-in match for ADS-B Exchange as well but I've left out official support since I can't test it.
Since OpenSky remains inoperable I decided to go ahead with the proxy server approach personally & created a hopefully reproducible example using AWS. For this use case I think we'll stay well within the limits of the free tier.


[UI] Support disabling of Dex

See https://github.com/epinio/helm-charts/issues/325
The UI assumes Dex will always be enabled. Need to ensure the helm chart value makes it's way to the ui-backend and disables the auth provider

@richard-cox I was unsure how to test this so just wanted to share what I tried and results.
1- I tried to disable dex from /chart/epinio/values.yaml:
https://github.com/epinio/helm-charts/blob/main/chart/epinio/values.yaml#L167-L168
This will not allow epinio to be deployed and will end up with the pod epinio-ui in status CreateContainerConfigError

Can you confirm if this is an error? When I tested here before the UI integration I was able to deploy Epinio.
2 - I attempted to disable solely from helm-charts/chart/epinio-ui/values.yaml (leaving the one on  /chart/epinio/values.yaml as true):
https://github.com/epinio/helm-charts/blob/6451a4764cf11c3cd51f2b86260f9d93a8b843ca/chart/epinio-ui/values.yaml#L27-28
This does not seemed to have effect and DEX is being displayed.

Can you please let me know if any of the tests above is valid / how to check this?
Thanks

Just checked what Manuel did and it seems the problem is that epinio-ui pod is unable to start due to missing dex-config.
Epinio deployed with --set global.dex.enabled=false. This is valid option from values.yaml and it should work.
$ kubectl describe pod epinio-ui-7c74cb88dd-7xnwz -n epinio
...
  Normal   Pulled     4s (x5 over 32s)  kubelet            Container image "ghcr.io/epinio/epinio-ui:v1.7.0-0.0.2" already present on machine
  Warning  Failed     4s (x5 over 32s)  kubelet            Error: secret "dex-config" not found

FTR: this item seems not working at the moment. Opened momentarily https://github.com/epinio/epinio/issues/2094 for fixing it. Once determined if the nature of the fix is backend or ui it can be decided if transfer the issue here.

This issue seems fixed in Fixed epinio-ui deployment with disabled dex epinio/helm-charts#378
Test steps and fix proof there: https://github.com/epinio/helm-charts/pull/378#issuecomment-1439956709


Support creation of pull request reviews

I found that issue about adding read-access to pull request reviews.
Would you mind if I add a PR with support of creation pull request reviews?

Nope, go for it :+1:


DELVEWHEEL file makes reproducibility difficult

The DELVEWHEEL file in dist-info contains the arguments passed to the program at repair time. Various build strategies will use temporary directories which then leak into this file, causing it to not be reproducible across runs.
It might be possible to setup a build environment and pass only relative paths for the input wheel, output directory, and lib paths. But with symlinking being tricky (impossible?) on Windows, that also becomes a difficult task.
It looks like only the Version entry in the file is used at a later time. The Arguments entry is stored but doesn't appear to be ever read again. Would you be open to omitting it, either outright or with some CLI option?

The Arguments entry has been useful in diagnosing issues, so I'd like to keep it. But to support your use case, I added the --no-diagnostic flag.

Can this please be reopened so SOURCE_DATE_EPOCH may be supported? It appears that other patchers support this:

https://github.com/pypa/auditwheel/pull/348
https://github.com/matthew-brett/delocate/pull/187

If you want support for SOURCE_DATE_EPOCH, then please open a separate issue.

https://github.com/adang1345/delvewheel/issues/41


EthCustodian: add ReentrancyGuard, withdraw method improvements

EthCustodian: withdraw() method - use call() instead of  transfer().
EthCustodian: upgrade OpenZeppelin to 4.5

It's required to change it for the future as transfer() gas provided might change. Reentrancy is being handled because the proof is consumed at the very beginning of the method.

Gents, the comments are addressed and the PR description is updated. Please make a final review.

Gents, the comments are addressed and the PR description is updated. Please make a final review.


Improve the Identity Verification Email

Bug Description
When a user gets the identity verification email in the hosted demo environment the email sender name, and the design of the email should be updated so that it appears nicely branded with some Fides or Ethyca branding.
Steps to Reproduce

Do this...
Then This...

Expected behavior
A description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

None of the Fides emails are "branded" right now - this should probably be a feature request for all emails, including the ability for customers to add their own branding.

@NevilleS one concern I have is putting the template creation responsibility on our customers. How do you envision that looking, from a setup perspective? As far as I know, when a customer configures a domain sending key with Mailgun, that only allows us to send messages via the API, not create full templates.

In general, we'd want users to maintain their own email/SMS providers. This gives them way more control over how their emails would look, so it's win/win. This is especially true for pure OSS usage where we can share anything from our own infra.
In some cases we might help a customer use our own Mailgun, but that'd be more of a special case

Created #1865 as a feature enhancement instead of trying to rewrite this one 😄


Feature request: settings.json - resource group filter to support regex

Describe the solution you'd like
In settings.json we have a few filters for:

subscriptions
resource groups
resource types

with some good examples in the FAQ :-)
I would like to see the resource groups filter to support wildcards just like the subscriptions filter - and hope to issue a PR for this soon.
Is this a good idea? Thoughts?

Subscription filter used at https://github.com/Azure/AzOps/blob/4eff6cb788892a41cf57c1166d754777d99cb1cc/src/internal/functions/Get-AzOpsResourceDefinition.ps1#L279
Resource group filter at
https://github.com/Azure/AzOps/blob/4eff6cb788892a41cf57c1166d754777d99cb1cc/src/internal/functions/Get-AzOpsResourceDefinition.ps1#L364
Tests would need to be updated as well.

Hey @jsandquist - sounds reasonable to align the filtering supported at different scopes. Are you willing and able to take a stab at this yourself?
Thanks,
Johan

Wow - a bit rusty apparently but eventually a PR will end up here in the proper repo 😆


Building without --feature tui fails

...
   Compiling dav-server v0.7.0
   Compiling rustic_core v0.3.0
   Compiling rustic_backend v0.2.0
   Compiling rustic-rs v0.8.0 (/build/rustic/src/rustic-0.8.0)
error[E0432]: unresolved import `super::tui`
  --> src/commands/snapshots.rs:20:5
   |
20 | use super::tui;
   |     ^^^^^^^^^^ no `tui` in `commands`
   |
note: found an item that was configured out
  --> src/commands.rs:27:16
   |
27 | pub(crate) mod tui;
   |                ^^^
   = note: the item is gated behind the `tui` feature

If something is gated behind a feature, other bits of code shouldn't depend on it. The cfg feature attribute probably needs to be added more places.

Thanks for reporting @alerque I had already on my list to fix this, so the fix will be included in the next patch release.


sfidaActionLog - Illegal wire type

When calling sfidaActionLog:
Unhandled rejection Error: Illegal wire type for field Message.Field .POGOProtos.Data.Logs.CatchPokemonLogEntry.pokemon_data_id: 1 (0 expected)

Problem with POGOProtos itself?

Possibly affected by the app updates today?

Im using 0.31.0 in a spoofed network.

That would be an issue with POGOProtos, yes. I don't see an open issue or any recent commits related to this on their repo yet though.

Similar problem, left unfixed: https://github.com/tejado/pgoapi/issues/207
I will open an issue.


Add regression test

Thank you for the great repository!
I would like to add regression tests to verify that this repo outputs the same images as the official repo.
For testing, I generated the image (v1_4_astronaut_rides_horse_plms_step50_seed42.png) using CompVis 7b8c883 (without watermark).
Test 1
bash .dev_scripts/test_regression_txt2img_v1_4.sh
comparing the following two images
IMAGE1: .dev_scripts/images/v1_4_astronaut_rides_horse_plms_step50_seed42.png
IMAGE2: outputs/txt2img-samples/test_regression_txt2img_v1_4/samples/00004.png
0.0

scripts/orig_scripts/txt2img.py outputs exactly the same image.
Test 2
bash .dev_scripts/test_regression_txt2img_dream_v1_4.sh
comparing the following two images
IMAGE1: .dev_scripts/images/v1_4_astronaut_rides_horse_plms_step50_seed42.png
IMAGE2: outputs/img-samples/test_regression_txt2img_v1_4/000004.42.png
0.7744293212890625

scripts/dream.py outputs nearly the same image.

Just ran your tests and I get the following results:
test_regression_txt2img_v1_4.sh: 0.5042826334635416
test_regression_txt2img_dream_v1_4.sh: 1.084851582845052
Dont know why but I think you should at least add the --full_precision flag when calling the dream.sh

Thank you for the PR. I will be integrating the latest round of requests over this weekend.


Always the same errors after several installations of plugins !

Hi !
After several installations of swh-plugins, I've got always these errors :
At test2.liq, line 17, char 32-34:
def multiband_band(radio, from, to, attack, release, ratio, threshold, gain)

Error 2: Parse error

At test2.liq, line 14, char 10-48:
limiter = ladspa.tap_limiter(limit_level = -0.5)

Error 15: Missing arguments in function application: source(audio=pcm('B), 'A).

`At test2.liq, line 13, char 13-39:
compressor = ladspa.sc4(rms_peak = 0.5)

Error 15: Missing arguments in function application: source(audio=pcm('B), 'A).

`
At test2.liq, line 41, char 2-17:
  multiband_band(radio, 0., 200., 3.5, 30., 3., -10., 2.),

Error 4: Undefined variable multiband_band

At test2.liq, line 42, char 2-17:
  multiband_band(radio, 0., 200., 10., 30., 2., -4., 0.),

Error 4: Undefined variable multiband_band

Here is my script :
test2_for_issue.txt
Thanks a lot ! I hope U can answer me and maybe in french ;-) I'm just a french newbie in Liquidsoap but I will want to learn.
@ plus !
Sebastien

Resolved with this : https://gist.github.com/BusterNeece/43a06ee6624975273fdc903ba4a39998


🚀 [Feature Request] - New UI for Mentor login page

Is your feature request related to a problem ? Please describe. ✍
I would like like to create a new UI for the mentors login page.
I have added the screenshot of the new UI.
Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Step 1
2. Step 2
3. Step 3

Additional context or screenshots
New UI will look like this:

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

You can remove confirm password


Update index.html MIME type from 'text/javascript' to 'application/javascript'

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Linux

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.15
node: 6.2.2
os: linux x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

This is a basic default application, generated and built with the angular-cli. Following the defaults, the resulting build is stored in dist/.
ng new myproject
ng build

The log given by the failure. Normally this include a stack trace and some
more information.

N/A

Mention any other details that might be useful.

The generated dist/index.html file contains the following line:
<script type="text/javascript" src="inline.js"></script><script type="text/javascript" src="styles.bundle.js"></script><script type="text/javascript" src="main.bundle.js"></script></body>

RFC 4329 Secion 7.1 says that the MIME type "text/javascript" is considered obsolete, in favor of "application/javascript".

That code is autogenerated by Webpack when building the project. This issue is better suited on that repo instead: https://github.com/webpack/webpack


Testing your Flash Eraser

@kentaylor does the Serial Monitor details below look ok for the output from a WeMos D1 Mini (4M)? The device wasn't bricked before running your sketch, I just wanted to test your sketch and all seems ok.
Starting...
SDK version:1.5.2(7eee54f4)
64
j = 0
addressSucceed: 0 - 0x0
j = 1
addressSucceed: 4096 - 0x1000
j = 2
addressSucceed: 8192 - 0x2000
j = 3
addressSucceed: 12288 - 0x3000
j = 4
addressSucceed: 16384 - 0x4000
j = 5
addressSucceed: 20480 - 0x5000
j = 6
addressSucceed: 24576 - 0x6000
j = 7
addressSucceed: 28672 - 0x7000
j = 8
addressSucceed: 32768 - 0x8000
j = 9
addressSucceed: 36864 - 0x9000
j = 10
addressSucceed: 40960 - 0xa000
j = 11
addressSucceed: 45056 - 0xb000
j = 12
addressSucceed: 49152 - 0xc000
j = 13
addressSucceed: 53248 - 0xd000
j = 14
addressSucceed: 57344 - 0xe000
j = 15
addressSucceed: 61440 - 0xf000
j = 16
addressSucceed: 65536 - 0x10000
j = 17
addressSucceed: 69632 - 0x11000
j = 18
addressSucceed: 73728 - 0x12000
j = 19
addressSucceed: 77824 - 0x13000
j = 20
addressSucceed: 81920 - 0x14000
j = 21
addressSucceed: 86016 - 0x15000
j = 22
addressSucceed: 90112 - 0x16000
j = 23
addressSucceed: 94208 - 0x17000
j = 24
addressSucceed: 98304 - 0x18000
j = 25
addressSucceed: 102400 - 0x19000
j = 26
addressSucceed: 106496 - 0x1a000
j = 27
addressSucceed: 110592 - 0x1b000
j = 28
addressSucceed: 114688 - 0x1c000
j = 29
addressSucceed: 118784 - 0x1d000
j = 30
addressSucceed: 122880 - 0x1e000
j = 31
addressSucceed: 126976 - 0x1f000
j = 32
addressSucceed: 131072 - 0x20000
j = 33
addressSucceed: 135168 - 0x21000
j = 34
addressSucceed: 139264 - 0x22000
j = 35
addressSucceed: 143360 - 0x23000
j = 36
addressSucceed: 147456 - 0x24000
j = 37
addressSucceed: 151552 - 0x25000
j = 38
addressSucceed: 155648 - 0x26000
j = 39
addressSucceed: 159744 - 0x27000
j = 40
addressSucceed: 163840 - 0x28000
j = 41
addressSucceed: 167936 - 0x29000
j = 42
addressSucceed: 172032 - 0x2a000
j = 43
addressSucceed: 176128 - 0x2b000
j = 44
addressSucceed: 180224 - 0x2c000
j = 45
addressSucceed: 184320 - 0x2d000
j = 46
addressSucceed: 188416 - 0x2e000
j = 47
addressSucceed: 192512 - 0x2f000
j = 48
addressSucceed: 196608 - 0x30000
j = 49
addressSucceed: 200704 - 0x31000
j = 50
addressSucceed: 204800 - 0x32000
j = 51
addressSucceed: 208896 - 0x33000
j = 52
addressSucceed: 212992 - 0x34000
j = 53
addressSucceed: 217088 - 0x35000
j = 54
addressSucceed: 221184 - 0x36000
j = 55
addressSucceed: 225280 - 0x37000
j = 56
addressSucceed: 229376 - 0x38000
j = 57
addressSucceed: 233472 - 0x39000
j = 58
addressSucceed: 237568 - 0x3a000
j = 59
addressSucceed: 241664 - 0x3b000
j = 60
addressSucceed: 245760 - 0x3c000
j = 61
addressSucceed: 249856 - 0x3d000
j = 62
addressSucceed: 253952 - 0x3e000
j = 63
addressSucceed: 258048 - 0x3f000

Exception (0):
epc1=0x40210704 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

ctx: sys
sp: 3ffffca0 end: 3fffffb0 offset: 01a0

>>>stack>>>
3ffffe40:  ffffffff 04080000 001c110c 01010000
3ffffe50:  ffffffff 00000003 ffffff00 ffffffff
3ffffe60:  ffffffff ffffffff ffffffff ffffffff
3ffffe70:  4020b035 ffffffff ffffffff ffff0064
3ffffe80:  00000000 3ffe939c ffffffd6 3ffe93ac
3ffffe90:  3ffec550 00000036 00000001 4020f5b8
3ffffea0:  00000001 3ffefdbc 3ffe939c 00000000
3ffffeb0:  00000000 ffffffff ffffffff ffffffff
3ffffec0:  ffffffff ffffffff ffffffff ffffffff
3ffffed0:  00000000 00310101 00640100 00000000
3ffffee0:  3ffe93c0 00000094 00000000 3ffe93b4
3ffffef0:  00000000 3ffe93c0 3ffe93d0 3ffe93e0
3fffff00:  00000000 00000000 3ffe93e6 3ffe943a
3fffff10:  3ffe93fc 3ffe9418 00000000 00000000
3fffff20:  00000000 00000000 00000036 00000000
3fffff30:  3fff053c 4020f083 3ffec550 3ffefdbc
3fffff40:  00000000 00000000 3ffec550 3ffe939c
3fffff50:  00000000 000000bc 00000000 00000036
3fffff60:  00000000 ffffffff 40204493 3ffec550
3fffff70:  3ffe9390 3fffdcc0 3ffe8b10 3ffe8b10
3fffff80:  00000050 3ffec550 3fffdab0 00000000
3fffff90:  40203dbb 3fffdab0 00000000 40202537
3fffffa0:  3ffe8b10 40000f49 3fffdab0 40000f49
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(1,6)

 ets Jan  8 2013,rst cause:4, boot mode:(1,6)

wdt reset

Yes that is the output you should see. You know it worked because a WeMos D1 Mini has 64 segments to make up 4M.
The crash at the end occurs after the setup() function completes and occurs because the loop() function is blank. It looks a bit disconcerting so maybe I should add something to the loop function.

why do you know this is Flash Erased ?
I think this is detroy bootloader
and I don't understand why j= 63
can you show me document ,my chip is ESP8266 node mcu

It is erased, but you would have to read the flash chip directly, rather than using a sketch in the ESP8266 to see it.
The boot loader is indeed lost but installing a new sketch using the Arduino IDE is hardware controlled and does not use software stored in flash. Most of the flash, including the boot loader, is overwritten every time it is programmed through the Arduino IDE so anything lost is restored next time you upload a sketch.

I understand this, how to read flash before and after erase ?

@kentaylor
Hi,
I don't show anything in serial monitor...
I attached ESP to USB and I opened serial monitor with 9600 baud rate, but I don't see anything... any help?


Add token config file

Added an example config file for the token, as well as example of how the file should look in README.md, since it wasn't specified anywhere.

Looks good, thanks for your contribution


Alti+Server complains about the "list" of admins not being an array when it's only one

Alti+Server threw an error when I started it with only a single entry in the admin list (set via server_configurator). It seems to assume it always gets an array of entries, which isn't the case if it's only one.
What I didn't test was if there is also an error when starting with zero entries, since that technically also shouldn't be an array.

Can you look in our stdout.txt file and send me the exact output, with a few lines of context before and after the message?  It will help me narrow down where this issue resides.
Thanks.

Starting alti+server with a single uuid in the admins list causes the server to stop shortly after being started without getting a chance to see much in the terminal because it immediately overwrites the text making only a "9" visible. Curses being funny i guess.
By doing ./alti+server > LOGFILE I was able to find out that the reason it stopped was "Not an ARRAY reference at ./alti+server line 2909. (which is the list of admins)
This error is not logged in stdout; that only shows:

Using /usr/bin/geoiplookup (good)
Using /bin/ping (good)
using JSON::XS (good)
Using /usr/bin/lzma (good)
Using/sbin/ip (good)
Using /usr/bin/curl (good)
Using /usr/bin/curl (good)
Using /usr/bin/curl (good)
Using /usr/bin/curl (good)
using DBD::SQLite (ok)

Yes sometimes the "u/U" in using is small and sometimes big ;)
Not sure why it confirms curl 4 times.
Either way looking at the LOGFILE output, the stdout.txt log perfectly aligns because the error happens right afterwards.
Adding a second entry in the admins list fixes the issue.
When the list has zero entries the alti+server apparently has no issue with it not being an array. Not even any mention of it in the log~

Got it, thanks.  I was looking in the wrong place.  I can do something about that.

Updated the using's to always use a capital U in 050d9be7e0d9a27422dab27debdebbac98d89c11
Fixed the alti+server code to handle both cases, when adminsByVaporID has 1 (non-array) and many (array) data structure configurations in 050d9be7e0d9a27422dab27debdebbac98d89c11


on https://skateshop.sadmn.com/, I got an error creating my first store, see screenshot

Have you tried opening other stores with different names?


move intercom and comscore to their own repo

make intercom and comscore supported libraries
update readme
fix misleading compile error when use the supported destinations

Codecov Report

Merging #90 (2114e66) into main (9b9774b) will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main      #90      +/-   ##
============================================
+ Coverage     77.71%   77.75%   +0.03%
- Complexity      440      441       +1
============================================
  Files            64       64
  Lines          5488     5488
  Branches        692      692
============================================
+ Hits           4265     4267       +2
+ Misses          679      678       -1
+ Partials        544      543       -1

Impacted Files
Coverage Δ

...alytics/kotlin/core/utilities/EventsFileManager.kt
95.94% <0.00%> (+2.70%)
: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 9b9774b...2114e66. Read the comment docs.


Zap Emoji should be replaced to be consistent in design

Zap Emoji should be replaced to be consistent in design. Currently, ⚡ will not be rendered as emoji but instead as Unicode- icon?
https://github.com/ydataai/ydata-profiling/blob/cb66a7e9e89545df7edd2b6c0830b520761a7ea9/README.md?plain=1#L87

It might be worth to also choose an icon for ## Key features because it's the only header without ...

suggestions could be:
## 🔑 Key features
## 🔑🌟 Key features
## 📌 Key features
## 📍 Key features
## 💡 Key features
## 🌈 Key features

https://github.com/ydataai/ydata-profiling/blob/cb66a7e9e89545df7edd2b6c0830b520761a7ea9/README.md?plain=1#L63
optional for points below:

🚀 for fast and efficient analysis
📊 for informative visualizations
📝 for detailed descriptive statistics
🔄 for flexible output formats
📈 for multivariate analysis and correlations
📅 for time-series analysis
📜 for text analysis
📷 for file and image analysis
🤝 for easy dataset comparison

It might be worth to also choose an icon for ## Key features because it's the only header without ...

suggestions could be:
## 🔑 Key features
## 🔑🌟 Key features
## 📌 Key features
## 📍 Key features
## 💡 Key features
## 🌈 Key features

https://github.com/ydataai/ydata-profiling/blob/cb66a7e9e89545df7edd2b6c0830b520761a7ea9/README.md?plain=1#L63
optional for points below:

🚀 for fast and efficient analysis
📊 for informative visualizations
📝 for detailed descriptive statistics
🔄 for flexible output formats
📈 for multivariate analysis and correlations
📅 for time-series analysis
📜 for text analysis
📷 for file and image analysis
🤝 for easy dataset comparison

@fabclmnt what about the missing icon for ## Key features? Important or not?


Default highlight for nil/true/false is not bright colour scheme friendly

By default, the plugin uses Bright Cyan to highlight nil/true/false identifiers. This might work for dark colour schemes, e.g. Darcula, but it doesn't for bright one. While it's not a hard job to tune the colours, I strongly believe that it's worth having good defaults.
I propose to use Identifiers → Constant (Language Defaults) colour, the same one that is used in some other languages.

fixed!


Don't show STUB workflows

For #1773

Coverage decreased (-8.2%) to 68.396% when pulling ed054dd6d140731ef472e14d1e9b50debb7c2098 on feature/1773/publishListNoSTUB into 15fe35ebb3437f058c1e120abedb6650857137db on develop.


Add terse output mode

In contrast to the --quiet output mode, the --terse mode
periodically prints status information if none have been printed
during a certain time frame (right now 15 seconds).
Additionally the status is printed before any command output so
that the source of the output could be determined more easily.

This PR sits on top of #1818 to avoid merge conflicts.

Sample output with timestamps:
NINJA_STATUS='[%e %f/%t] ' ~/src/ninja/cmake-build-debug/ninja --terse
[1.955 1/1694] Building CXX object modules/a.cpp.o
[17.944 114/1694] Generating bar.h
[33.023 168/1694] Generating foo.h
[37.162 207/1694] Linking CXX static library lib/baz.a
warning: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: archive library: lib/baz.a the table of contents is empty (no object file members in the library define global symbols)
[52.396 334/1694] Generating misc.cpp

As you could see the status lines for lines which do not produce output are more than 15s apart and skip many in-between-target outputs. The warning is printed with a status header and afterwards 15s elapse again, before printing another status.

I'm unsure about the use_console() condition and its use case. But as far as I understand it gets used if the process needs exclusive access to the console because it will perform I/O. In that case always printing the status line seems to be the correct way.


Final changes for RC2 based on sig-net review feedback

What type of PR is this?
/kind cleanup
/kind api-change
What this PR does / why we need it:
There are three changes here, all based on feedback from @thockin in #861:

The "Prefix" path match type has been renamed "PathPrefix" to leave room for a future "StringPrefix" match.
The "ClassName" field in PolicyTargetReference has been removed as it is not clearly necessary at this point.
A new optional "Name" field has been added to ReferencePolicyTo, enabling more fine grained control over which resource(s) may be referenced.

More thoughts on all of the above:

I think it could be useful to add StringPrefix matching in the future. Currently Envoy based implementations of this API need to use RegEx matching to support our PathPrefix matching. Although this is fine as a starting point, I can imagine at least some users of the API would prefer to have access to the StringPrefix matching they're familiar with for the implementations that support it. This doesn't commit us to providing StringPrefix as a match type, but does make that simpler if we want to.
I was the one who originally added "ClassName", but after looking through the docs, GEP, and asking around, it does not seem like this field was clearly needed. It may be helpful in certain use cases, but I don't think it's necessary at this point.
The idea of adding to.name in ReferencePolicy has come up many times already, and even reappeared when I presented this concept to sig-auth. Although it's true that we could add this at a later point, it would be messier. Users would need to know whether the implementation they were using was new enough to support that particular field of ReferencePolicy, and if it wasn't you may be unknowingly allowing more references than intended. Although I've generally pushed to keep ReferencePolicy as simple as possible to start, this feels like an inevitable addition and it is significantly simpler to add this up front.

Does this PR introduce a user-facing change?:
* The "Prefix" path match type has been renamed "PathPrefix".
* The "ClassName" field in PolicyTargetReference has been removed.
* A new optional "Name" field has been added to ReferencePolicyTo.

/hold for consensus
/cc @bowei @hbagdi @jpeach @youngnick

I agree with all three of these changes, I think that the call on ReferencePolicy name is particularly good.
/lgtm
/hold
in case anyone else wants to go.
I'll update the changelog again once this merges.

/lgtm


What does it take to install this on Windows?

At Code for SF Hack Night, we went through a test run of installing this on windows. You can see the steps below. We didn't quite finish the process.
We are working with Windows 7.
Steps:

Using git bash, clone the repository
Install the latest Python 3 from the main Python downloads site (takes a while)
The path to python is crazy in Git Bash: /c/Users/Username/AppData/Local/Programs/Python/Python35-32/python.exe
python3 is not on the path, so we made a python3 alias in ~/.bashrc
on windows the virtualenv activate script path is Scripts/activate.bat (run without source inside of cmd and cannot be run in git bash
make does not exist on cmd, so we ran pip install requirements\dev.txt directly. Installs were successful!!
the pdftk windows installer installs to this location, and adds the folder to PATH C:\Program Files (x86)\PDFtk Server. pdftk now works

Added vagrant for easy windows installs via vm https://github.com/brennv/pdfhook/tree/add-vagrant
https://www.vagrantup.com/


Add Tests to ensure Python 3.11, 3.12 support

Description
This PR ensures that taskipy runs on all latest python versions.
DoD:

CI passes given all latest python versions
All dev deps are compatible with latest python versions

Changes

Updated pylint so that it would use version 3+ for python >= 3.11
Added python 3.11, 3.12 to the CI matrix
Since the 3.6 CI is outdated and uses an old version of poetry, I added a step that only runs on 3.6 CI that removes the lockfile, since it is not compatible with the old poetry version
Disabled the "must use yield from" rule since we still support python 3.6, which does not support yield from

Merged because this is a blocker for people who want to work on taskipy but use a more recent python version


Generics vs Concrete Types

After consideration and pondering how to enable interoperability between crates for RNG usage, it becomes clear that there might be difficulty in achieving the necessary tools for querying resources/components in a robust manner.
Generic Types
The problem here is not needing to introduce more dependencies, doing things like trait queries. However, the ability to define a custom RNG algorithm might be important for particular use-cases where higher quality/secure entropy must be used, limited within app code or non-interoperable plugin code. In these cases, cross-plugin determinism is likely not going to be the priority, instead only being local determinism (for testing purposes).
Concrete Types
In most cases, devs are likely not going to care about the algorithms, just that either the RNG is fast or secure. Concrete types remove the need for trait queries and simplify the process for a plugin to determine whether a global resource or a component is available. It becomes much easier to write code to make use of a global source or fallback to a non-deterministic default.
Both types could live in the crate, but their use-cases will be separate. Documentation should provide the cases for each and what bevy plugin authors should rely on for interoperability.

Due to https://github.com/bevyengine/bevy/pull/7184, the resolution of this question is basically to force bevy_rand towards more concrete types instead of generics. TypePath requirements would basically require folks to manually newtype and implement TypePath on said newtype in order to get it to plug in to the generic component successfully, whereas a concrete type will avoid that pain altogether.
As such, I'm considering this question resolved.


feat(metrics): adding metrics in Veneer client implementation

This change introduces the porting of bigtable-core-client metrics with veneer(useGCJ) client.
The final list of supported metrics would be:

grpc.method.$METHOD.operation.latency
grpc.method.$METHOD.failure
table.put.latency
table.get.latency
grpc.method.ReadRows.firstResponse.latency
scanner.results.latency
scanner.results
bulk-mutator.mutations.added
sessions.active
grpc.rpc.active
grpc.rpc.performed
grpc.errors.$CODE
grpc.method.$METHOD.rpc.latency

These metrics are not migrated onto GCJ:

batch.latency
bulk-mutator.batch.meter
grpc.channel.active
channels.channel.$ID.rpc.latency
grpc.method.$METHOD.retries.performed
grpc.method.$METHOD.retries.exhausted.

This PR is ready for fresh rounds of review, PTAL!

@igorbernstein2 When you get a chance then please take a look.

I think we should take a different approach to this. I'm going to add an abstraction layer to veneer's metrics which should allow us to plug hbase metrics in


Shader variable hints and defaults don't work together

Godot version:
Godot Engine v3.0.2.stable.official
OS/device including version:
Windows 10 Home v1709 (Fall Creator's Update); Nvidia GTX 660
Issue description:
I am unable to mix variable hints and defaults within shaders. If I attempt to, Godot tells me there's an error with my syntax.
Here's what I tried to make it work, with neither working.
uniform vec4 color : hint_color = vec4(0.8, 0.0, 0.0, 1.0);
// SCRIPT ERROR: (null): Expected ';'
// ...despite the ';' at the end?

uniform vec4 color = vec4(0.8, 0.0, 0.0, 1.0) : hint_color;
// SCRIPT ERROR: (null): Expected expression, found: CURSOR

Either my syntax is somehow wrong, or the two just don't work together (and the docs say nothing about this situation, so...).
Steps to reproduce:
Attempt to mix variable hints and defaults as shown above.
Minimal reproduction project:
N/A

This has already been fixed with #17533 and should be available in the next release.

Oh, alright! I must of missed that issue during my search before submitting this.


There will be problems with atom coordination

When I run atom, atom will report an error!!
Atom
Editor is not responding
The editor is not responding. Would you like to force close it or just keep waiting?
[Force Close] [Keep Waiting]

It's the same every time.


Use alternate macro to enable/disable benchmarking.

Fixes #13.

Great @mikeantonelli, thank you very much for your contribution!


Replace the selected element

When I do something like
.pipe(hyperstream({
    '#id': fs.createReadStream(file)
}).pipe(process.stdout);

the content of file is inserted into the element that has the id 'id' and I end up with a excessive div which is only there so that I cant insert my other content. Can I somehow replace the selected element instead?

hyperstream uses trumpet under the hood, in the code there is no way of passing options to trumpet. In this case we'd want to define {outer: true} when creating streams. Would be neat if we could specify this. See - https://github.com/substack/node-trumpet#elemcreatestreamopts


Improve code coverage for firestore::FieldPath.

Also some cosmetic cleanups.

LGTM, sorry for not noticing.


Install netbase and ca-certs through apt-get instead of WORKSPACE.

Ref #79
This gets the diff between this image and our existing one much smaller.

@dlorenc  why is the diff smaller this way? The contents should be the same or not?

Sort of - the bazel rules for installing debs only unpack the deb. They don't run and pre/post configuration hooks, or today dpkg_status. This is functionally equivalent most of the time, but leads to a larger diff between an image with the same debs installed via dpkg.

@dlorenc  thx, do you have a diff around?, i like to understand this further

Sorry - a diff of what exactly? By diff I was referring to the output of another tool we've been working on: github.com/GoogleCloudPlatform/container-diff

@dlorenc  the difference between a image where the pkgs are installed with bazel, and one with apt.
Seen the container-diff thing earlier, i think i need to take a closer look.


Incorrect AUC ROC score and log loss.

The probability classification report gives wrong values for the above mentioned metrics. Also when I looked into this code - prob_class_ref_quality_metrics_widget.py.
the lines where auc and log_loss were calculated are mentioned in comments as problem

Hi @vikrant-sahu!
You got it right from the comments! We are aware of it and will fix it really soon :)
Could you share your use case when you got a wrong result? We will add it to the testing now.

If you want the data. Then sorry I can't share it as it a confidential dataset and can't be shared outside our network.

Hi @vikrant-sahu
Could share something of the below:

the number of classes in the dataset
the rough number of observations (are we talking thousands, or tens of thousands, or more)
whether the metric was incorrect or did not compute at all.

That would help!
We understand it can be sensitive - appreciate the response in any case.

Cool..

the number of classes in the dataset - 2 classes
the rough number of observations (are we talking thousands, or tens of thousands, or more) -  thousands, within 10K
whether the metric was incorrect or did not compute at all. It was incorrect.  I used sklearn and it gave different metric. Even AUC curve was incorrect. Also please check other curves too.

Hi @vikrant-sahu,
Apologies for the late reply! (🦠)
Thanks for your answers! We are still struggling to reproduce the bug. Here are a couple ideas we have on why the calculation is wrong.

Could you please check if your target (positive) class is the first in the column-mapping ['prediction'] list?

In other tools including sklearn, in order to calculate the ROC AUC metric, you have to explicitly pass the probabilities for the target class. Evidently expects the class columns to follow the order. If it is reversed, the metrics will be calculated incorrectly.

Do you pass the target function as is (categorical label) or there is some post-processing (e.g. you pass the class label like "0" or "1")?

If you pass a categorical label to Evidently, it should automatically binarize it. However, the problem might have happened at this stage, and we'd look further!
Overall, we believe that if you:

pass a binarized target label to the Evidently (1 for target class and 0 for other); and
make sure that positive class is the first in the column-mapping ['prediction'] list
the calculation should be correct.

If it is not, please let us know!

Hi @vikrant-sahu!
We found a bug and fixed it in #122


Tiles API integration on Canvas

Waiting on Pradeep from SIRPI to give an update

Openlayers may need to be updated from 8.2.0 to 9.0.0 at least. This is a hard requirement. Requires a discussion with the SIRPI team to understand how feasible this is and what the timelines will be.

Tiles have been fixed and updated in production after regeneration with the right CRS. We're not using tippycanoe, and instead using ogr2ogr. Pradeep has been updated and he needs to finish the integration. One drawback of not using tippycanoe is that the defaults of tippycanoe are better and easier. Needs more exploration of ogr2ogr documentation for better integration.

Regarding the Export layer functionality for vector tiles, does it make sense to have it at all?


Please pull request

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.
[x] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

Link to Website

CLA Assistant Lite bot: 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. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

Way too many domains registered at once. Likely abuse. Closing PR.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 09:36:29 on 2023.07.13
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 0, errors out: 0
Original problem ID: 32592
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=32592

Problem has been resolved in 3m 0s at 09:39:29 on 2023.07.13
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 32592


Update promisify-node dependency

After upgrading glob to 6.0.1, I see many warnings like this one when installing npm packages:

npm WARN unmet dependency /usr/local/lib/node_modules/oghliner/node_modules/cli requires<EMAIL_ADDRESS>but will load
npm WARN unmet dependency /usr/local/lib/node_modules/oghliner/node_modules/glob,
npm WARN unmet dependency which is version 6.0.1

I wonder if aggressively updating promisify-node will have a similar effect. And also if it'll cause any regressions, given that promisify-node's docs say its stable version is 0.1.5, and its build badge shows an error.
What's the benefit to updating this dependency?

What's the benefit to updating this dependency?

It's mainly to tell that oghliner is compatible with promisify-node 0.3.0 and avoid issues when our users install oghliner alongside promisify-node 0.3.0.
I wish there was a way to tell npm which version we prefer, but avoid warnings when a user installs oghliner with a supported-but-not-preferred version of a package we depend on.


Allowing 3.11 python version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.879%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1647

Relevant Lines:
2088

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.879%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1647

Relevant Lines:
2088

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.879%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1647

Relevant Lines:
2088

💛  - Coveralls


chore!: remove param_witnesses and return_witnesses from ABI

Description
Problem*
Followup to #5142
Related to #5104
Summary*
This PR deletes the param_witnesses and return_witnesses fields from the ABI as the locations of all inputs/return values are defined implicitly by the types themselves.
I've left this as draft as there's some changes which need to be made to the JS code which will require some extra work (it needs to be made aware of the sizes of various types.)
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[x] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

cc @sirasistant as you were interested in this.


[Internal lib] Research and implement a reusable input component

Brief description:
We are going to be making an internal library for form elements. Research how you can do that based on the documentation of shadcn and React-hook-form. The general idea is for these components to be fully reusable and to accept props for everything. So that we can not only use them in the HackAUBG page but in the admin panel in the future. You would also have to write tests with all the edge cases to verify that the inputs are working correctly. If you have any questions don't hesitate to ask @Aleks1908

I suggest creating a separate repo for internal libraries and pushing them to an artifactory, just to make our lives easier and not introduce complexity.

I think for such library it wont be needed to separate it. This library is going to tied to the project, its not going to be reused in other projects. And if we separate it in a different repo it will introduce additional overhead. Keeping the internal lib inside the repo will make it much easier for us to develop it and test it. If the library expands to something bigger in the future we can still separate it but for the moment I don't think it will be needed.

I think for such library it wont be needed to separate it. This library is going to tied to the project, its not going to be reused in other projects. And if we separate it in a different repo it will introduce additional overhead. Keeping the internal lib inside the repo will make it much easier for us to develop it and test it. If the library expands to something bigger in the future we can still separate it but for the moment I don't think it will be needed.

More overhead and more complexity = better Developer Experience and Staff engineering

Thank you for your opinion but we are going to stick with having them inside the repo for now.


Towards offline collaboration

I've been thinking about how to generalise document persistence and realtime collaboration so it supports the offline use-case:

create documents while there is no internet connection
continue editing docs while offline
resolve concurrent edits

Our current CollabSession implementation is very much tied to a server endpoint. Here's a proposal how we could realise a persistent editor session that uses a local DocumentEngine(=storage of changes + snapshots). In order to receive external changes (from a collab server) we use a generic replication mechanism, which can be triggered whenever there is an internet connection. After a 'sync' the remote and local stores must have the same or equivalent data.
Possible usage:
// Local storage setup (e.g. file-based or in-memory stores)
// NOTE: This could also be remote stores, they just need to follow
// the same interface
let documentEngine = new DocumentEngine({
  changeStore: localChangeStore,
  snapshotStore: localSnapshotStore
})

/*
  Helper to open a doc for persistent editing

  NOTE: dispose must be called on editorSession before releasing the reference
*/
function openDocument(documentId, cb) {
  documentEngine.getDocument(documentId, function(err, jsonDoc, version) {
    if (err) return cb(err)
    let doc = configurator.createArticle()
    jsonConverter.importDocument(doc, jsonDoc)
    let editorSession = new PersistentEditorSession(doc, {
      documentEngine: documentEngine,
      configurator: configurator,
      version: version
    })
    cb(null, editorSession)
  })
}

openDocument('doc-1', function(err, editorSession) {
  // yields a persistent (replicated) editorSession
})

This would already allow single-user offline editing. In order to support multi-user collaborative editing we can replicate with a hub like so:
let replicator = new Replicator(documentEngine, remoteEngine)
replicator.start() // start auto-replicating or alternatively call replicator.sync() manually.

In the most trivial implementation replicator syncs everything, meaning multiple docs, so remote and local stores have the exact same data after a successful sync. We may want to allow partial syncs in the future or keep certain documents 'private' until we share them.
Implementing replication could get tricky as we need to deal with situations where the remote endpoint received new data while we were active locally.
Here's a partial implementation of the PersistentEditorSession
/*
  Changes to the document are stored. External changes (e.g. coming in through
  replication) are applied to the current session (realtime collab)
*/
class PersistentEditorSession extends EditorSession {
  constructor(doc, config) {
    super(doc, config)
    config = config || {}
    this.config = config
    this.documentEngine = config.documentEngine
    this.documentId = config.documentId
    this.version = config.version
    // when a change happens externally (e.g. by a collaborator)
    this.documentEngine.on('change', this._onExternalChange, this)
    this.onUpdate('document', this.afterDocumentChange, this)
  }

  dispose() {
    this.documentEngine.off(this)
  }

  /*
    Make change persistent
  */
  _afterDocumentChange(change, documentId) {
    if (documentId === this.documentId) {
      this.documentEngine.addChange(documentId, change, 'silent', (err, newVersion) => {
        this.version = newVersion
      })
    }
  }

  /*
    Apply external change
  */
  _onExternalChange(change, documentId, version) {
    if (documentId === this.documentId) {
      if (change.ops.length > 0) {
        this._transaction._apply(change)
        this.getDocument()._apply(change)
        this._setDirty('document')
        // Only undo+redo history is updated according to the new change
        this._transformLocalChangeHistory(change)
        this._setSelection(this._transformSelection(change))
        this._change = change
        this._info = { remote: true }
        this.startFlow()
      }
    }
  }
}

@oliver---- what are your thoughts? If you like this architecture I could start with implementing a trivial fast-forward-only replicator and then we further optimize and write test cases for different replication scenarios.

In order to get the same change history after replication we could apply the following strategy:

remote store has predecence
rewrite change history in local store

For example consider this situation:
Local:  c1,c4,c5
Remote: c1,c2,c3

Step1: Reset local store to shared version c1 so we have
Local: c1
Remote: c1,c2,c3

Step2: Add remote changes
Local: c1,c2,c3
Remote: c1,c2,c3

Step3: Re-add local changes but rebased to c3
Local: c1,c2,c3,c4',c5'
Remote: c1,c2,c3,c4',c5'

If we have a editor session connected to the document being synced we need to apply the inverse of the removed changes first, then apply the remaining changes as represented in the store:
apply changes [c4^-1, c5^-1, c2, c3, c4', c5']


Upgrade ApplicationPattern and BasicService npm package to version 1.0.1

Fixes #169

Basic service, OAM services, Individual services are tested with the following new versions,
• onf-core-model-ap+1.0.1
• onf-core-model-ap-bs+1.0.1


Improve the support of Java related files.

Fixes #470
Changes proposed:

[x] Add
[ ] Prepare
[ ] Delete
[x] Fix

Things I've done:

[x] I've pulled the latest master branch.
[x] I've run npm install to install all the dependencies.
[x] I've run ESLint.
[x] My pull request fixes an issue, I referenced the issue.
[x] I've run npm run build to build the extension.

Superb job! @JimiC


Add example for animated height with max-height

In follow to #144

Sorry, I didn't see your proposal. Why don't I add new demo? Think it's good point to compare two cases.

For simplicity.
We can add a fourth slide with a width going behond the max height.

@ashl1 I have added an example. Thanks for your help 👍 .

I agree with you about simplicity, but think that is hard to find out this sokution from the demos, especially with no description said about this. It will be better to add "this slide with max-height" at the start of last slide.

It will be better to add "this slide with max-height" at the start of last slide.

Good idea 😄

Could you add this to not open small PR?

@ashl1 Alright, I'm on it.


W/System.err: remove failed: ENOENT (No such file or directory)

W/System.err: remove failed: ENOENT (No such file or directory) : /data/user/0/com.abc.xyz/cache/picasso-cache/c1d640c64d6dfaba7ef9a9702c2e5ada.0
This issue doesn't allow to cache image using Picasso with OkHttp3Downloader so Picasso failed to load image using .networkPolicy(NetworkPolicy.OFFLINE) but load in normal online mode. What's the solution?
This is what @JakeWharton said ref

Despite Picasso's name being included in the path, Picasso has nothing to do with this. These are coming from the underlying HTTP client which is managing the disk cache and Picasso has no control over it. It looks like the cache dir might have been cleared out from underneath the HTTP client which won't hurt anything.

Could you provide sample code of the client setup and any code relevant to the cache instance or cache directory?
Ideally an example app that reproduces the problem.
Is there any chance you are modifying the files in the cache via some other mechanism? e.g. deleting manually?

@swankjesse @JakeWharton is this normal anyway, https://developer.android.com/guide/topics/data/data-storage.html seems to suggest that Android will cleanup these cache files if it needs space.

Simply doesn't cache some image at first try. I prefetch 50 images, two at a time to make user experience better. It works on second try. Don't know why, I didn't found it in emulator cache.
Application.onCreate
Picasso picasso = new Picasso.Builder(context)
                .downloader(new OkHttp3Downloader(context,Integer.MAX_VALUE))
                .build();
        Picasso.setSingletonInstance(picasso);

Gradle
```
compile 'com.squareup.picasso:picasso:2.5.2'
compile 'com.squareup.okhttp3:okhttp:3.9.0'
compile 'com.jakewharton.picasso:picasso2-okhttp3-downloader:1.1.0'

code
Picasso.with(context).load(imageUrl)
                    .memoryPolicy(MemoryPolicy.NO_CACHE).fetch(new Callback() {}

They can be cleaned up from outside your app, yes. I'm not sure as to
whether they can be removed while the app is running or not.
On Wed, Oct 11, 2017 at 9:07 AM Qamar Abbas<EMAIL_ADDRESS>wrote:

Simply doesn't cache some image at first try. I prefetch 50 images, two at
a time to make user experience better. It works on second try. Don't know
why, I didn't found it in emulator cache.
Application.onCreate
Picasso picasso = new Picasso.Builder(context)
.downloader(new OkHttp3Downloader(context,Integer.MAX_VALUE))
.build();
Picasso.setSingletonInstance(picasso);
Gradle
compile 'com.squareup.picasso:picasso:2.5.2'
compile 'com.squareup.okhttp3:okhttp:3.9.0'
compile 'com.jakewharton.picasso:picasso2-okhttp3-downloader:1.1.0'

code
Picasso.with(context).load(imageUrl)
                    .memoryPolicy(MemoryPolicy.NO_CACHE).fetch(new Callback() {}

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/square/okhttp/issues/3645#issuecomment-335803330>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEEERKBZ60DEtJshwor_dEkz2ThYTnIks5srL2IgaJpZM4Pzi8P>
.

@JakeWharton System shouldn't be cleaning if there are a lot of storage free space available.
User can clear cache, system and some apps can clean this cache.
So this mean, cache folder is not reliable place for long term usage.
Is Context.getFilesDir() more reliable for caching images (downloading) once use forever per install.

@JakeWharton I might dig into this.  This could be as simple as checking the file exists before attempting to delete.  But also confirming that our cache behaves nicely when the cache is deleted underneath us.
https://android.googlesource.com/platform/libcore/+/jb-mr2-release/luni/src/main/native/libcore_io_Posix.cpp#1075
Seems like it comes from there.

Any progress on this? We're having the same issue.

I tried to reproduce the problem, but I couldn't get it to show broken behaviour with a OkHttp test client.  n.b. I wasn't including picasso in my test.  The OkHttp Cache behaved correctly and repaired itself as documented even if I trashed the cache files in the background.  But obviously my testing can't be exhaustive.

11-10 16:32:22.092 9684-9710/com.xxx.bbb D/Picasso: Dispatcher  enqueued     [R16]+2ms
11-10 16:32:22.093 9684-9939/com.xxx.bbb D/Picasso: Hunter      executing    [R16]+3ms
11-10 16:32:22.105 9684-9710/com.xxx.bbb D/Picasso: Dispatcher  batched      [R16]+15ms for error
11-10 16:32:22.308 9684-9684/com.xxx.bbb D/Picasso: Main        errored      [R16]+218ms
11-10 16:32:22.308 9684-9710/com.xxx.bbb D/Picasso: Dispatcher  delivered    [R16]+218ms
11-10 16:32:22.378 9684-9710/com.xxx.bbb D/Picasso: Dispatcher  batched      [R15]+523ms for error (will replay)
11-10 16:32:22.582 9684-9710/com.xxx.bbb D/Picasso: Dispatcher  delivered    [R15]+729ms
11-10 16:32:22.582 9684-9684/com.xxx.bbb D/Picasso: Main        errored      [R15]+729ms
R21]+15ms for error https:://s3.abc.amazonaws.com//1487229634.6965.KDou3U.png ```

Unclear what action to take here.


Add @returns tag

Hi! Please, consider adding @returns tag alongside with current @return tag. It seems that @returns is used by the community more widely. For example, WebStorm when generates jsDoc for functions uses @returns. Of course I can create issue in theirs tracker and ask them to change their mind, but from the other hand if we look into actual ESDoc manual we will see that almost all verbs use form with "s": @extends, @implements, @emits, @listens, @throws, so @returns in this line will look very consistent.

Isn't this already added? I'm raising an issue with this and I don't think it should be added (assuming it's not already): https://github.com/esdoc/esdoc/issues/550

Or following your point here, for argument purposes, @return should be removed if @returns is added`, because ambiguity causes inconsistency


Start preparing things for Django4.0

According to https://docs.djangoproject.com/en/dev/releases/4.0/#features-removed-in-4-0 there are some deprecated modules that will be removed

Hey, I was wondering if there is something else that needs to be done on this PR, or if it can be merged?


we need a 3d path planning alg

https://www.ri.cmu.edu/pub_files/pub3/stentz_anthony__tony__1994_2/stentz_anthony__tony__1994_2.pdf


SHT30 I2C Temperature & Humidity Sensor Library

The SHT30 is a common and inexpensive temperature and humidity sensor chip. This commit adds support for this library.
The code is modeled on the existing SDK BME680 library.

Dear @teledatics,
Thank you for your contribution.
Could you send me sample app to use this library?
We'd like to verify this with your sample app.
Best regards,
Newracom

Hi,
We developed this as part of our Teledatics GUI standalone firmware.
https://github.com/teledatics/nrc7292_sdk/tree/teledatics_gui
It is used with our Air Quality Sensor add-on board found at
https://www.teledatics.com.
Git steps:
git clone https://github.com/teledatics/nrc7292_sdk
git checkout teledatics_gui
Then build the teledatics_gui standalone firmware following the Newracom
SDK documentation.
Best,
James Ewing, CEO
--
Teledatics Inc
9 Cornerstone Sq 400-113
Westford, MA 01886
(978) 254-7945
On 10/12/22 22:35, newracom wrote:

Dear @teledatics https://github.com/teledatics,
Thank you for your contribution.
Could you send me sample app to use this library?
We'd like to verify this with your sample app.
Best regards,
Newracom
—
Reply to this email directly, view it on GitHub
https://github.com/newracom/nrc7292_sdk/pull/5#issuecomment-1276801890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWCMLOTAC5H2LWWPJQBMHQTWC44K5ANCNFSM6AAAAAAQX5P7QA.
You are receiving this because you were mentioned.Message ID:
@.***>


Function overloads for function expressions

TypeScript Version:  2.9.2

Search Terms:
Code function overload expression
Related https://github.com/Microsoft/TypeScript/issues/16731
I have this TypeScript code which uses overloads on a function declaration. This code works as expected.
    function identity(x: string): string;
    function identity(x: number): number;
    function identity(x: string | number): string | number {
        return x;
    }

    const a = identity('foo') // string
    const b = identity(1) // number
    const c = identity({}) // type error (expected)

I am trying to achieve the equivalent of the above using function expressions instead of function declarations, however I get a type error:
    /* Type '(x: string | number) => string | number' is not assignable to type '{ (x: string): string; (x: number): number; }'.
        Type 'string | number' is not assignable to type 'string'.
            Type 'number' is not assignable to type 'string' */
    const identity: {
        (x: string): string;
        (x: number): number;
    } = (x: string | number): string | number => x;

How I can achieve the same effect of overloading the function but with function expressions?
Usage of function declarations vs expressions is a matter of preference. Ideally we would be able to achieve the same behaviour using either techniques.

Is this possible?
Is the above behaviour a bug?

Is this possible?

no.

Is the above behavior a bug?

No. this is behaving as intended. there is a stronger relationship between overloads and an implementation signature that allows us to relax some of the rules.

Interesting, so it's not possible to achieve the same behaviour we see with the function declaration but using the function expression syntax? That's a shame. I guess we'll have to stick to function declarations for functions which require overloads.


GDS Reader & Writer in ODB

GDS Reader & Writer
This Project adds GDS input and output features to OpenRoad. It would replace the current GDS manipulation scheme, which is through Klayout, and further OpenRoad's capability to provide a tightly integrated RTL-to-GDSII flow.
This PR is created as part of the GSoC '24 project with CHIPS Alliance, mentored by Mehdi Saligane.
Features

Full set of data structures in OpenDB for storing GDS information
GDS file parsing, supporting all of the commonly used record fields in modern GDSII.
Layout manipulation through GDS data structures
GDS file outputs from layout stored in OpenDB
Parsing primitive layer information from .lyp files in Klayout

Future Works

Add GDS operations to the OpenRoad GUI
Integrate GDS data structures together with existing OpenDB structures
Conversion between LEF/DEF and GDS

How To Use
The entry point to the gds manipulation functionalities are at src/odb/include/odb/gdsUtil.h, src/odb/include/odb/gdsin.h, and src/odb/include/odb/gdsout.h. Documentation for the detailed classes and functions are in the file.
A more detailed specification of the Writer/Reader for future developers is available here.
Example Usage
For an example on how to use the GDS reader & Writer, check out src/odb/test/cpp/TestGDSIn.cpp

@oharboe note that the gds today is generated by klayout so this would help only for future work.

@oharboe note that the gds today is generated by klayout so this would help only for future work.

For my part reproducible .gds and .spef files is into the future anyway, so waiting for .gds writing directly from .odb is OK as it reduces the totalt engineering effort.
Is klayout only used to write .gds files and will klayout be dropped after .odb to .gds writes is activated in ORFS?

In some PDKs klayout could be used for DRC checking.  It will likely be a while until OR can generate GDS as this is just a first step.

@fangzhonglyu do you plan to handle aref?

Yes, AREF is already built into the reader/writer and shares the same class as SREF

@fangzhonglyu please ping when you have addressed all the feedback and this is ready for re-review.

@maliberty I believe everything is fixed?


Create my own image regression dataset for DIGITS

Hi, I am training a network that takes a color image as input and gives 2 float numbers as output. I have all training images collected and saved in a directory. The correspondent float numbers output are saved to a file. I am not sure how I can make a DIGITS dataset from them. My application is similar to the "Training an image regression model using DIGITS" tutorial. But in the tutorial, they used a python script to generate the simulated images and make the dataset at the same time. They did not show how to make dataset from existing images. Could anyone help?

Take a look at this tutorial @ArtlyStyles


Add uglifyjs and css clean plugins

for compression

https://github.com/abhijithvijayan/gulp-sass-boilerplate/commit/2e00b510b2a691356b739d34b62811f67b587b34

https://github.com/abhijithvijayan/gulp-sass-boilerplate/commit/53e3c81e0bc87362f8fefd8d6341b85e5e2d5596

[Done] Closing.


[IR] Improve ttg.memdesc

Add an allocShape field to denote the shape a memory descriptor when it's allocated. The value will be propagated to all its descendants created through subview ops.
Make encoding and memorySpace fields required instead of optional.
Implement the getAlias function for #ttg.shared_memory to shorten its length in .mlir files

@ThomasRaoux ready for another round of review


When the game is almost won, powerups automatically go into the loser's side.

When the board is like 99% captured and a powerup spawns, it immediately goes into the losing players' goal as soon as it spawns, which is lame. Some solutions...

Don't spawn things at the terrain line at extreme values
Maybe just spawn them randomly on the board somewhere

I think I addressed this already, there is a minimum and maximum x value now for powerup spawns.


Support consumer delivery timeout for brokers

Overview
At present, consumers consuming from a queue that do not acknowledge messages can cause messages to be held up in the broker until the consumer detaches. For some use cases, it could be desirable to timing out the consumer sent so that it can be sent to a different consumer.
This would require a change in Artemis in order to be implemented.

I assume you are thinking the use of Modified delivery state to implement timed acquision.  This would need client work too.

@k-wall I was mainly looking for a pure server side solution to this problem because we can't control all the clients.

@lulf the protocol allows you to know the delivery states your partner supports.  I think it would be feasible for a broker enhancement to use the delivery state if available (which ultimately helps prevents dups).  If the partner didn't support it then the broker could have a mode where it removes the acquision without the notification to the consumer.


python312Packages.cohere: 5.11.1 -> 5.11.2

Things done
Changelog: https://github.com/cohere-ai/cohere-python/releases/tag/5.11.2
cc @natsukium

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352053

x86_64-linux

:white_check_mark: 8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

aarch64-linux

:white_check_mark: 8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

x86_64-darwin

:white_check_mark: 8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist

aarch64-darwin

:white_check_mark: 8 packages built:

python311Packages.cohere
python311Packages.cohere.dist
python311Packages.llmx
python311Packages.llmx.dist
python312Packages.cohere
python312Packages.cohere.dist
python312Packages.llmx
python312Packages.llmx.dist


Add missing requirements that make py.test work.

I was testing a change and noticed that I could not run py.test in a fresh virtualenv.

Ah, i see. I will have to follow up on this tomorrow.

I think this PR can be closed now.


⚠ ClamAV has degraded performance

In 838f6df, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 464 ms

Resolved: ClamAV performance has improved in 7863b05.


MM-40056: fixes scrolling to selected thread

Summary
Currently when you select a thread and then load more items via infinite
loading (scrolling to the bottom) it will scroll to the selected item
when threads are fetched.
This commit fixes that by removing the thread ids (ids) from the
useEffect dependencies array.
Ticket Link
https://mattermost.atlassian.net/browse/MM-40056
Release Note
NONE

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/105020

@koox00 I'm getting a server error when trying to post a reply. Asked SRE support to take a look at the issue.
This is happening on multiple PR test servers for me, not just this PR.

/update-branch


Full Speed Machines & minutes

Hi,
Using the setting A1 B1 or C1, with the time unit minutes leads to a miscalculation.
1 A Assembler makes 0,25 Red Science per second
should be: 0,25*60sec/min=15 Red Science per minute
instead the Planners output is: 0.25/min (Assembling Machine 2 × 0.028 or Assembling Machine 3 × 0.017)
Example:
http://doomeer.com/factorio/index.html#s1132bbbbbbbbbbbbbbrgrgrrrrgrrrgrgrrrrrrrrrrrrrrrA1rrrrrrrrrgrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
http://doomeer.com/factorio/index.html#m1132bbbbbbbbbbbbbbrgrgrrrrgrrrgrgrrrrrrrrrrrrrrrA1rrrrrrrrrgrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr

Indeed! Thanks for the notice, I'll get this fixed.

Done!


docs:Support Thingsboard authentication with Casdoor

PR Checklist

[ ] No broken links found using link-checker.

Linkchecker
Use the following command to check the broken links.
docker run --rm -it ghcr.io/linkchecker/linkchecker --check-extern http://<IP_ADDRESS>:4000

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@ashvayka @stitenko plz review

@ashvayka @stitenko hi, any update on this?

ping @ashvayka @stitenko


Making findRepositoryRoot more robust

Fixes https://jira.duraspace.org/browse/FCREPO-2477

Please resolve merge conflict.


feat: eml format instead of json

Change FileTransport to save into .eml format
fixes #499.

Thanks for the PR! I'll test this in the following days.

Thanks for working on this!


clarify default consensus=noops in yaml file

Update validator.consensus description to indicate default .
Log consensus type in when creating noops plugin
All unit tests run.
One behave test fails due to #739

Signed-off-by: Tuan Dang<EMAIL_ADDRESS>


32bits support

Fixes #9 .
Tested on a i386 debian Docker with dmd 2.076.0.
TODO:

[ ] Test with ldc
[ ] Add travis CI through a 32 bits Docker image

Add travis CI through a 32 bits Docker image

FYI: Adding -m32 is enough and a lot faster than bootstrapping a Docker image.
(The official Linux zip/tar archive contains a 32-bit Phobos release, s.t. it will just work out of the box if the linker supports 32-bit too)
-> Have a look at this travis.yml file: https://github.com/libmir/mir-algorithm/blob/master/.travis.yml

Thanks @wilzbach ! Wasn't aware of this, added it to the travis config.
Now all the tests pass:

using --arch x86 with both dmd and ldc 64 bits
using x86 dmd in a 32 bits debian docker
on a 32 bits windows as reported by @p0nce
on a RaspberryPi 3 (32bits raspbian jessie) with ldc 1.4

Merging.