Stat bug (At least on Rogue)

Ambush makes Physical Power Bonus Stat change and go back to normal.
Feature?
https://user-images.githubusercontent.com/132175066/235328821-1e4edf9d-52b6-4a9d-a48f-43b22792c20b.mp4

@Phodecus read what the bonus says. 50% additional weapon damage from ambush, and what do we see in the "Physical Power Bonus" tab? From bonuses: 50%, so yes, this is a feature.
@Snaacky, i think it's safe to close the issue


Spinner shows after first slide on lazy load no matter what

If lazy loading is enabled, the spinner will show for a split second after the first slide change even if the image is immediately loaded.
I haven't figured out how to prevent this from happening without blocking the page from completing loading first.

this seems to have stopped happening


Support code completion of Flutter asset filenames in Image.asset() constructor (etc)

Originally raised in https://github.com/Dart-Code/Dart-Code/issues/3433 by @bdlukaa.
It would be nice if code completion understood when arguments are paths to Flutter assets and could provide completion for them (similar to how imports have filename completion):

Some possible ideas:

An annotation on the String parameter to mark this argument as a ~path~ URI
Code-gen to produce constants that would naturally show up in the completion list (this may work better if the type wasn't just String, although I suspect there would be less friction using Strings)

The annotation would be a better solution because it would be available to all API authors. Would we need variations to control which platform the path was for?

Based on https://github.com/flutter/flutter/issues/32039, I believe these should always use forward slashes (although it doesn't seem to be explicitly documented).

Yes, I believe that Flutter uses POSIX-style paths for all of its APIs. But to make it generally useful for other package authors we might need more flexibility. Of course, one could argue that file paths that need to be platform-specific should be constructed using the path package's join function, but maybe there's an opportunity for a lint if we know that it's suppose to be a platform-specific path.

Bumping the priority slightly as this is a quite frequently used API in Flutter so providing quality completions would have a significant impact.

Do we really need generality here?
This query shows 73k+ files that use Image.asset() with a string literal.
For comparison, using an identifier is less often, about 55k. Not zero, but I suspect that most of these do not originate from static literals that would benefit from a hypothetical @assertUriString.
So, I propose implementing support only for Image.assert().

Generality isn't an absolute requirement, but it is a very strong goal. We should always look for ways to make the support we're adding be something that has value for all of the package authors in the ecosystem rather than just for one or two hardcoded methods in the SDK libraries or Flutter packages. When package authors can express their intention for how an API is to be used, and we can use that information to provide a better dev experience, then we multiply the impact of our efforts.

I opened https://github.com/flutter/flutter/issues/144937 with a proposal for Flutter to consider.

It looks that Flutter folks are positive about these marker annotations.
So, I expect that they will accept the PR when we sent it.
But I wonder if I should first implement the corresponding DAS functionality, and see if it works well.
And add new API (annotations) to Flutter only then.
WDYT?

I'm fine with whatever you're comfortable with.
Implementing the completion side (possibly by special casing on use case) would tell us whether the annotations are correctly defined. It shouldn't be too hard to update them if we need to, as long as they haven't shipped yet, but having some confidence in the design might be nice.


Create Pi-In-The-Sky.md

Think I've completed this correctly

General process is right but build bot is saying that you mispelled PyconUK, it should be PyCon UK.

The build is failing because the structure of the YAML metadata in Pi-In-The-Sky.md is wrong -- unfortunately it's not obvious that this is the problem from the error messages that wok gives us.
In the interests of getting a move on with this, I've created #145 with the YAML fixed.


Remove obsolete ticker mixin from AnimatedSize docs

Fixes https://github.com/flutter/flutter/issues/83606

Duplicate of https://github.com/flutter/flutter/pull/83661 - closing


Leverage browser cache when response ETag is set

Feature Request
When Naja is dispatching AJAX requests, ETag is ignored and response is generated all the time. If Naja would send If-None-Match header with ETag from previous request as value, whole app could leverage one more cache level.

Hi, Naja builds on top of Fetch API and allows you to configure its parameters, including the cache mode. Beyond that, caching and sending the right headers are the responsibility of the browser, so if it does not work, it might be misconfigured


Gibberish appended to .conf file

Current behavior
Odd numbers currently appended to the supervisor log .conf files

@tira-io/tira-dev Can someone tell me what process writes these files?

To me, it looks like it is this one: https://github.com/tira-io/tira/blob/abff435501394fd265bcc8133a443b8a4eee9d8f/tira-web/src-java/de/webis/tira/client/web/CommandLineExecutor.java#L93

Thank you! Closing as the old frontend will soon be retired.


PR: Priority use of new APIs than removed or deprecated APIs

Hi,
This PR makes new APIs priority use than removed or deprecated APIs
to solves the following DeprecationWarnings of qtabrowser with QT_API=pyside2 or QT_API=pyside6.
QT_API=pyside2
qtawesome/icon_browser.py:125: DeprecationWarning: QDesktopWidget.screenNumber(const QPoint & arg__1) const is deprecated
  screen = desktop.screenNumber(desktop.cursor().pos())
qtawesome/qtawesome/icon_browser.py:126: DeprecationWarning: QDesktopWidget.screenGeometry(int screen) const is deprecated
  centerPoint = desktop.screenGeometry(screen).center()

QT_API=pyside6
qtawesome/icon_browser.py:273: DeprecationWarning: 'exec_' will be removed in the future. Use 'exec' instead.
  sys.exit(app.exec_())

exec_ function is handled as discussed in https://github.com/spyder-ide/qtpy/issues/286
Additionally, new set Filter Regular Expression is priority used than removed setFilterRegExp considering the possibility that PySide2/PyQt5 will report DeprecationWarning in the future.

I tested that this PR with the current master branch of QtPy (https://github.com/spyder-ide/qtpy/commit/53ce7b00f6cd90eb45e2b78bed953671841d4899) reports no DeprecationWarning on the following environments.
PySide2                    5.15.2
PySide6                    6.2.1

PyQt5                      5.15.6
PyQt5-Qt5                  5.15.2
PyQt5-sip                  12.9.0
PyQt5-stubs                <IP_ADDRESS>

PyQt6                      6.2.0
PyQt6-Qt6                  6.2.0
PyQt6-sip                  13.1.0

pyqt                      5.9.2            py36h05f1152_2
qt                        5.9.7                h5867ecd_1
sip                       4.19.8           py36hf484d3e_0

I rebased onto master.

Thank @dalthviz for review. I updated the commit.

keep sys.exit(app_exec())
change commit message to PR title


Add script for Dockerfile auto-builds

This pull request, in combination with the docker hub autobuild system allows us to create two docker images for each git tag that is pushed (e.g. KevinMenden/scaden:v0.9.4-cpu and KevinMenden/scaden:v0.9.4-gpu) as well as two docker images that will track the dev branch.
You will need to setup the autobuilds in the docker hub repository following the image below:

I already tried this on  https://hub.docker.com/r/zeehio/scaden/tags for testing and it works great.

Will have a look later today

Merged it, adjusted the automated build. Let's see if everything builds nicely.
Cool idea!


unable to create a python function in function app

I was successfully able to create an "HTTP triggered function in Azure" using the instructions here:
https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-python
I verified running the app using both local environment and the Azure portal. (Deploy the function app project to Azure)
I could not find any instructions on how to deploy the app when I make an update so I again tried:
func azure functionapp publish <APP_NAME>
I got the message the app was successfully deployed but when I go to Azure portal HttpTrigger is disappeared in the portal. Functions is empty.
Is this a known issue?

figured out the issue. I needed to run the function from local Function project level and I was running it from the directory that had the function code. Once I ran from local function project level everything is working.


Unable to integrating DataTables Extensions as per documentation

Hello,
I have followed the instructions as mentioned in the Read Me regarding use of extensions with the tabular table. link. However, doing so does not get me the extra set of buttons on my table. I was wondering if I was doing something wrong. If someone could guide me with this issue, it would be most helpful!
index.js
import dataTablesBootstrap from "datatables.net-bs4/js/dataTables.bootstrap4.js";
import "datatables.net-bs4/css/dataTables.bootstrap4.css";
dataTablesBootstrap(window, $);

// BUTTONS DATATABLES

import dataTableButtons from "datatables.net-buttons-bs4";
// Import whichever buttons you are using
import columnVisibilityButton from "datatables.net-buttons/js/buttons.colVis.js";
import html5ExportButtons from "datatables.net-buttons/js/buttons.html5.js";
import flashExportButtons from "datatables.net-buttons/js/buttons.flash.js";
import printButton from "datatables.net-buttons/js/buttons.print.js";

// Then initialize everything you imported
dataTableButtons(window, $);
columnVisibilityButton(window, $);
html5ExportButtons(window, $);
flashExportButtons(window, $);
printButton(window, $);

table.js

import Tabular from "meteor/aldeed:tabular";
// import { Template } from 'meteor/templating';

new Tabular.Table({
    name: "listUsersTable",
    collection: Meteor.users,
    autoWidth: false,
    order: [
        [0, "asc"],
        // [1, "desc"],
    ],

    // results dropdown
    lengthMenu: [
        [10, 25, 50, 100], // value
        [10, 25, 50, 100], // label
    ],
    // other properties...
    buttonContainer: ".col-sm-6:eq(0)",
    buttons: ["copy", "excel", "csv", "colvis"],
    throttleRefresh: 5000, // throttle the reactivity
    search: {
        caseInsensitive: true,
        smart: true,
        onEnterOnly: true,
    },
    responsive: true,

    columns: [
        {
            data: "username",
            title: "Username",
            width: "20%",
            autoWidth: false,
        },

        {
            title: "Profile",
            bSortable: false,
            width: "40%",
            tmpl: Meteor.isClient && Template.edit_user_links,
            tmplContext(rowData) {
                return {
                    item: rowData,
                    column: "profile",
                };
            },
        },
// other columns
]
});

I am unable to view the "copy", "excel", "csv", "colvis" buttons anywhere around my table. In addition to this, I would like to know the role of "buttonContainer: ".col-sm-6:eq(0)", Am I supposed to declare a div with that class?
Thanks!

Any updates on this? I'm able to see my buttons and the copy,csv ones work. However, pressing colvis doesn't do anything

same for me


ADBDEV-4936-19: Add assertions to return from dynamic_cast.

Add assertions to return from dynamic_cast.
dynamic_cast may return NULL, so I added assertions.

https://github.com/arenadata/gpdb/pull/807


Scalable Function support

What would you like to be added?
Utilizing of Scalable Functions (SFs) as resources exposed to the cluster.
What is the use case for this feature / enhancement?
SFs are relatively new type of functions which can be created in switchdev mode. Detailed information can be found at this wiki page. Arm host of the Bluefild DPU is capable to act as node in the cluster. Due to limitations VFs are created on x86 parent host, meaning only SFs can be created on arm host itself.
From plugin point of view SFs are unusual devices. Because SFs doesn't have own dedicated PCI device, it is not possible to implement new DeviceType in addition to NetDeviceType and AcceleratorType. However SFs are created on parent PF PCI device.
This pull request implements support for SFs as auxiliary devices, by extending configuration with additional field. If this field is provided resource pool of requested auxiliary devices created instead of parent PCI devices.
Perhaps handling SFs (and auxiliary network devices) with sriovdp is not correct since SFs unrelated to SRIOV at all and it is better to create brand new plugin. What do You think?

Greetings @DmytroLinkin !
I have raised this issue in today's community meeting. As its a new technology and not a trivial change in device plugin i think
it would be best to have a design doc (usually we use google doc) which will serve as common ground for discussions.
This design doc should include:

general overview of SFs (with additional links for folks who want abit more of a deepdive)
supported kernel / userspace (e.g devlink) versions
currently supported NICs (that you are aware of ofc)
use-cases
proposed external facing API changes (if any)
proposed coded changes

diagrams to ease understanding of code changes if needed

proposed testing coverage (e.g feature will be covered by unit-tests, integration tests, e2e tests)

Some notes on the implementation approach of PR#435:
I think we should strive to split into a separate device type (e.g AuxDeviceType) with its own set of selectors as:

different selectors may be used for aux/sf devices which will not be applicable for a pci network device and via versa
an aux/sf device is a device on the Kernel Auxiliary bus and not on PCI bus
an aux/sf device does not have PCI attributes. it does have a parent which is a PCI network device

to achieve this some refactoring may be needed but i think we would end up with a cleaner API and internal model.
Looking forward to seeing the design doc !

Design document - https://docs.google.com/document/d/10EtkmOerG6apCaRffN891y1jwmngqIqeu70O3PEgEDE/edit?usp=sharing

PR bringing refactoring of plugin layout along with additional unit tests coverage - https://github.com/k8snetworkplumbingwg/sriov-network-device-plugin/pull/441

PR Aux. network devices support - #442

Support was added in PR#442 cosing this one.
Thx for working on it @DmytroLinkin !


Why does Laravel not allow access to get parameters with a post request?

Laravel Version: 5.3
PHP Version: 7.0

I have been checking out the Laravel source code a bit and I found this bit of code:
return $this->getRealMethod() == 'GET' ? $this->query : $this->request;

From:
https://github.com/illuminate/http/blob/master/Request.php#L668
This basically specifies that if the request method for a request is a 'GET' that the input method returns the query string parameters and otherwise gives you access to the POST variables.
This means that whenever I would make a post request I can not do the following to get a query string parameter named "date" for example:
$request->input('date')

I know it is useful to not merge POST and GET data since you get the possibility of overriding them but what is the exact motivation behind not allowing a user access to the query parameters when you make a POST request?
The way I see it, the input could have been split up into postInput(or simply post) and getInput(or simply get) for example to allow access to both without merging them. Of course you lose the ability that a generic input method gives you, but you gain a lot of flexibility.
Any thoughts on this? (I am still wondering if it's alright to ask questions like this via an issue. Let me know if this is incorrect behavior. Somebody from stackoverflow directed me over here to ask my question.)

You can use get() instead of input().

Just a quick reminder; we've been told not to use get().
https://github.com/laravel/internals/issues/114
https://github.com/laravel/framework/issues/13138
https://github.com/laravel/docs/pull/2269

Yes it's not recommended, same as the case mentioned. But it gets the job done :)

we've been told not to use get()

Told not to use vs not recommended is totally different. Request::get() came from Symfony, not Laravel. While you can use it as you can use many of Symfony available method for Request is not advertise and documented, but doesn't mean you are told not to use it when it's exactly what you need.

I have access to my query string params on POST requests via the input method; did I miss something?


Cleanup not working properly

For example, running on the tests-#128 branch:
pytest parsl/tests --config parsl/tests/configs/local_ipp.py
========================================== 50 passed, 100 skipped in 425.61 seconds ==========================================
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/Users/awoodard/ci/parsl/parsl/dataflow/dflow.py", line 575, in cleanup
    executor.scale_in(len(job_ids))
  File "/Users/awoodard/ci/parsl/parsl/executors/ipp.py", line 243, in scale_in
    r = self.execution_provider.cancel(to_kill, *args, **kwargs)
  File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/site-packages/libsubmit-0.3.2-py3.6.egg/libsubmit/providers/local/local.py", line 240, in cancel
ProcessLookupError: [Errno 3] No such process

Note that when this is solved, we should be able to re-enable testing the IPP config on Travis (if #272 is merged).

If this is coming from a duplicate shutdown (which it might be?) then #287 might be relevant.

To clarify this, the ProcessLookupError may be a red herring. The main issue here that needs to be resolved is that running with IPP often leaves orphan processes.

Closing since this is an IP


Change the default font from DroidSans to Roboto

Besides the well-known advantages of Roboto, it also has better char coverage, we already use it for the italic files because DroidSans does not have italic versions.
Glyph counts:
# Current default fonts
898  DroidSans.ttf
898  DroidSans-Bold.ttf
949  DroidSans-Italic.ttf (old version of Roboto-Italic)
946  DroidSans-BoldItalic.ttf (old version of Roboto-BoldItalic)

# Latest version of Roboto
1072  Roboto-Regular.ttf
1072  Roboto-Bold.ttf
1073  Roboto-Italic.ttf
1073  Roboto-BoldItalic.ttf

Roboto files taken from http://www.google.com/design/spec/style/typography.html.

@tito what do you think?

What about the size? But +1 anyway.

@tito, there are slight size differences (first line is Roboto), but i don't see it as a problem.

What happens with the droid files, do we keep them in the repo? How about DejaVuSans.ttf?

Maybe we could also change our default text_size from 15sp to 14sp.
14sp is recommended by Google for button and body text.

My bad, i was talking about size on the disk, as it supports more char, it might be increased a little bit. But i'm unsure.
By the way, i wonder if we could use the default android font instead of packing it into the apk... Might be an optimization to do one day :)

@tito the 4 droid files are 547 kB, while the 4 new roboto files are 520 kB combined.
If this added space is a concern, we can either remove the droid files, or delete DejaVuSans.ttf, which is 581 kB. DejaVuSans was replaced as a default font years ago, we shouldn't ship it.

For using default android fonts,  we already have a fund in core.text get_system_fonts_dir https://github.com/kivy/kivy/blob/master/kivy/core/text/init.py#L160, we theoretically should just need to set "font_file_name"  and if it exists we would be able to use it.

@tito @dessant  just tested a apk with  font_name: 'ComingSoon' on android using kivy==master. It just works for us. No need for including a default font! \o/ :dancer:

the VKeyboard still reference the DejaVuSans. Ensure it works with Roboto (ie that all the glyph used in the default keyboard works)

meh, it looks like dejavu stays


Paper for FourCastNet v2?

Hi,
I noticed that you have a FourCastNet v2 running. A web search did not uncover any related publications.
Are there further resources, such as papers or original GitHub code or pretrained pytorch weigths?
I am curious to see what the differences are between the original V1 and this V2 version.
Thanks!

A few items I've come across that may help:
https://catalog.ngc.nvidia.com/orgs/nvidia/teams/modulus/models/modulus_fcn
https://catalog.ngc.nvidia.com/orgs/nvidia/teams/modulus/models/modulus_fcnv2_sm
https://arxiv.org/abs/2202.11214
https://arxiv.org/abs/2306.03838


Re-represent SMILES strings as SMILES fingerprint

We are going to try to represent the SMILES data using the notation found here. We will need to familiarize ourselves with RDKit, a tool that allows you to extract information from SMILES strings.

We shouldn't just directly copy and paste from the code in the paper-- we should try to spend some time observing how they extracted information from the SMILES strings, and write our own-- adding in documentation, as theirs is pretty scanty.


[WIP] UART owned pins

This PR makes the UartPeripheral take ownership of the pins that it needs.
const XOSC_CRYSTAL_FREQ: u32 = 12_000_000; // Typically found in BSP crates

let mut peripherals = pac::Peripherals::take().unwrap();
let sio = Sio::new(peripherals.SIO);
let pins = Pins::new(peripherals.IO_BANK0, peripherals.PADS_BANK0, sio.gpio_bank0, &mut peripherals.RESETS);
let mut watchdog = Watchdog::new(peripherals.WATCHDOG);
let mut clocks = init_clocks_and_plls(XOSC_CRYSTAL_FREQ, peripherals.XOSC, peripherals.CLOCKS, peripherals.PLL_SYS, peripherals.PLL_USB, &mut peripherals.RESETS, &mut watchdog).ok().unwrap();

// This is new:
// Set up UART on GP0 and GP1 (Pico pins 1 and 2)
let pins = (
    pins.gpio0.into_mode::<FunctionUart>(),
    pins.gpio1.into_mode::<FunctionUart>(),
);
// Need to perform clock init before using UART or it will freeze.
let uart = UartPeripheral::enable(
        peripherals.UART0,
        pins, // This is also new
        &mut peripherals.RESETS,
        uart::common_configs::_9600_8_N_1,
        clocks.peripheral_clock.into(),
    ).unwrap();

uart.write_full_blocking(b"Hello World!\r\n");

UartPeripheral takes any type that implements trait ValidUartPinout<UART: UartDevice>. This is implemented for:

tuple (TX, RX)
tuple (TX, RX, CTS, RTS)
the new Pins struct, in which developers can hand-pick the pins they want to use.

There are 4 traits that constrain the pins to the 4 functions they can have: Tx<UART>, Rx<UART>, Cts<UART> and Rts<UART>.
These traits are also implemented for (), so each one of the fields is optional. This is desired because some boards/devices have a single-wire UART connection that can only transfer or receive, so developers can use e.g. (Gpio1, ())

TODO (self): split the UART into a reader/writer struct

I don't have time to work on this for a while and I'm starting a new job in January, so I'm going to open this PR without being able to test if the CTS/RTS actually works.

Rebased onto the latest main

Sorry it took me so long to review this one, needed to find a block of time to properly investigate + test it.
I have tested with UART0 in a loopback scenario with:

GPIO 0 and 1 connected, GPIO 2 and 3 connected
GPIO 12 and 13 connected, GPIO 14 and 15 connected
GPIO 28 and 1 connected, GPIO 14 and 15 connected

I also tested with UART1 in a loopback scenario with

GPIO 4 and 5 connected, GPIO 6 and 7 connected

And I checked with it configured for 0,1,2,3 when 12,13,14,15 were connected (just to verify that it wasn't im
TX + RX are working just fine.
Split works as expected, very minimal changes to get a TX and RX pair (very nice!)
CTS / RTS work, but we aren't handling them well (elsewhere).
Further notes while I'm here:
Disconnecting CTS stops transmission as expected, reconnecting it resumes transmission as expected.
Disconnecting TX from RX and TX keeps working, but first character after reconnecting RX results in RTS being asserted.
I did try to clear errors but no joy. Test code is here:
https://gist.github.com/9names/0a670e374097f36bff704733d25afc83

Rebased onto the latest main


Create index.html

@Rick-Anderson,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Remove unecessary files

Since this is a reusable app, I don't think you should bundle the manage.py, urls.py, settings.py etc

Fixed.


Support scale property on java component

Support --min/max-replicas on az containerapp env java-component xxx create/update cmds
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

/azp run

About the CI failed:
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_addon_binding_e2e
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_dev_add_on_binding_customized_keys_e2e
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_dev_add_on_binding_customized_keys_yaml_e2e
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_dev_add_on_binding_e2e
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_dev_add_on_binding_none_client_type
FAILED src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py::ContainerappServiceBindingTests::test_containerapp_managed_service_binding_e2e
They are relative to java component: javaComponentClient，the api-version changed, please rerun with --live.
The other cases I will update with PR

/azp run

please resolve CI issues

Hi

please resolve CI issues

Hi @yanzhudd
I update the recording files yesterday due to network update their api-version, but they revert their change and break our CI:
https://github.com/Azure/azure-cli/commit/90f7650d87004adc97526416ee7879e24f46334e
What should we do? Thanks

After this PR:https://github.com/Azure/azure-cli-extensions/pull/7919 merged, sync main branch the CI will fix.

After this PR:#7919 merged, sync main branch the CI will fix.

This PR has been merged.


Apache reverse proxy configuration

Type: feature
The following has been addressed in the PR:

documentation update

Coverage remained the same at 74.338% when pulling bf8c018fc5a84ef84731df35365facf4a095feaf on mysiar:apache-reverse-proxy into 1bdb651636de20991aa3a7424c8830c27b93ac3b on verdaccio:master.

Coverage remained the same at 74.338% when pulling a514e254a251ab2feb9edce7c2b2f6c74e2e0a80 on mysiar:apache-reverse-proxy into 1bdb651636de20991aa3a7424c8830c27b93ac3b on verdaccio:master.

Coverage remained the same at 74.338% when pulling a514e254a251ab2feb9edce7c2b2f6c74e2e0a80 on mysiar:apache-reverse-proxy into 1bdb651636de20991aa3a7424c8830c27b93ac3b on verdaccio:master.

Coverage remained the same at 74.338% when pulling a514e254a251ab2feb9edce7c2b2f6c74e2e0a80 on mysiar:apache-reverse-proxy into 1bdb651636de20991aa3a7424c8830c27b93ac3b on verdaccio:master.

thanks @mysiar . Sorry the verbose :) I was testing some integrations.


Convert Annotation and Link to use AutoValue.

Codecov Report

Merging #264 into master will decrease coverage by 0.05%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #264      +/-   ##
============================================
- Coverage     94.88%   94.83%   -0.06%
+ Complexity      467      448      -19
============================================
  Files            70       70
  Lines          1702     1665      -37
  Branches        103       96       -7
============================================
- Hits           1615     1579      -36
  Misses           61       61
+ Partials         26       25       -1

Impacted Files
Coverage Δ
Complexity Δ

...a/com/google/instrumentation/trace/Annotation.java
100% <100%> (ø)
4 <4> (-9)
:arrow_down:

...in/java/com/google/instrumentation/trace/Link.java
100% <100%> (+3.84%)
2 <2> (-10)
:arrow_down:

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 97c5737...a1de321. Read the comment docs.


Setting Chroma persist_directory says "Using embedded DuckDB without persistence"

Trying to use persist_directory to have Chroma persist to disk:
index = VectorstoreIndexCreator(vectorstore_kwargs={"persist_directory": "db"})

and it displays this warning message that implies it won't be persisted:
Using embedded DuckDB without persistence: data will be transient

However, it does create files to the db directory. The warning appears to originate from https://github.com/chroma-core/chroma/pull/204#issuecomment-1458243316.    Do I have the setting correct?

Trying to use persist_directory to have Chroma persist to disk:
index = VectorstoreIndexCreator(vectorstore_kwargs={"persist_directory": "db"})

and it displays this warning message that implies it won't be persisted:
Using embedded DuckDB without persistence: data will be transient

However, it does create files to the db directory. The warning appears to originate from chroma-core/chroma#204 (comment). Do I have the setting correct?

I have the same issue

Same when using:
db = Chroma.from_documents(documents=docs, embedding=embeddings, persist_directory="db/")

returns:
Using embedded DuckDB without persistence: data will be transient

langchain==0.0.123
chromadb==0.3.13

Not sure if this is relevant in your cases, but I was experiencing this issue when setting chroma client_settings directly, eg, Chroma(client_settings=Settings(anonymized_telemetry=False)).
I think this is coming from the init method of Chroma, where will set client_settings if you set persist_directory.
See here
https://github.com/hwchase17/langchain/blob/master/langchain/vectorstores/chroma.py#L70
def __init__(
    self,
    collection_name: str = _LANGCHAIN_DEFAULT_COLLECTION_NAME,
    embedding_function: Optional[Embeddings] = None,
    persist_directory: Optional[str] = None,
    client_settings: Optional[chromadb.config.Settings] = None,
) -> None:
    """Initialize with Chroma client."""
    try:
        import chromadb
        import chromadb.config
    except ImportError:
        raise ValueError(
            "Could not import chromadb python package. "
            "Please install it with `pip install chromadb`."
        )

    if client_settings:
        self._client_settings = client_settings
    else:
        self._client_settings = chromadb.config.Settings()
        **if persist_directory is not None:
            self._client_settings = chromadb.config.Settings(
                chroma_db_impl="duckdb+parquet", persist_directory=persist_directory
            )**
    self._client = chromadb.Client(self._client_settings)
    self._embedding_function = embedding_function
    self._persist_directory = persist_directory
    self._collection = self._client.get_or_create_collection(
        name=collection_name,
        embedding_function=self._embedding_function.embed_documents
        if self._embedding_function is not None
        else None,
    )

Hi everyone, really sorry about this.
This is now fixed in chromadb 0.3.14
Here is the PR https://github.com/chroma-core/chroma/pull/243

Verified with 0.3.14, thanks!
❯ python app.py
Using embedded DuckDB with persistence: data will be stored in: db

thanks for solving this, but how do i load the persistent index once saved?

I am facing the same issue as @SimonB97,
persist_directory = 'chroma_db_store/index/' or 'chroma_db_store'
docsearch = Chroma(persist_directory=persist_directory, embedding_function=embeddings)
NoIndexException: Index not found, please create an instance before querying
Folder structure
chroma_db_store:
- chroma-collections.parquet
- chroma-embeddings.parquet
- index/

+1 same problem as @nishanthc-nd  and @SimonB97

+1 same problem as @nishanthc-nd and @SimonB97

This issue is resolved. Please create a new one.

This issue is resolved. Please create a new one if you need additional support.
Sure please track it here
https://github.com/hwchase17/langchain/issues/2491

Same when using:
db = Chroma.from_documents(documents=docs, embedding=embeddings, persist_directory="db/")

returns:
Using embedded DuckDB without persistence: data will be transient

langchain==0.0.123 chromadb==0.3.13

I am facing the same issue. Has you issue resolved?

Same when using:
db = Chroma.from_documents(documents=docs, embedding=embeddings, persist_directory="db/")

returns:
Using embedded DuckDB without persistence: data will be transient

langchain==0.0.123 chromadb==0.3.13

I am facing the same issue. Has you issue resolved?

Nope. Currently using pinecone instead, also because of slightly better retrieval results with hybrid search retriever.

@SimonB97 can you update chroma to 0.3.21?

same issue with me
    vectordb = Chroma(PRESISTENT_PATH, embedding_function=OpenAIEmbeddings())
I am using the same path to persist. can see files written in the folder. But it does not load index:
chromadb.errors.NoIndexException: Index not found, please create an instance before querying

@sidsarasvati hey - if you can share a minimal example with me at<EMAIL_ADDRESS>i will try to get to the bottom of this
we are also changing how persist works that will fix all of these issues once and for all

I believe this thread has moved to https://github.com/hwchase17/langchain/issues/2491

I am still getting this error for chromadb==0.3.21

This issue got solved . basically i have to use vectordb.persist()  after creation reading document. also specify name of persist_directory.
vectordb = Chroma.from_documents(texts, embeddings,persist_directory=persist_directory)
vectordb.persist()


class loss in ssl method

Hi vturrisi,
First thanks for your effort for this amazing repo of ssl.
In some of methods, such as barlowtwins, byol, I find two loss during pretrain stage:
https://github.com/vturrisi/solo-learn/blob/3ee84db28d8760a6eb2bba922cad8de35ee1d2b6/solo/methods/barlow_twins.py#L129
In this line, it shows two losses are returned for updating the pretrained model (I am not sure both loss are used). If the model is pretrained with class_loss, does it mean the model is not fully SSL? Because in the line:
https://github.com/vturrisi/solo-learn/blob/3ee84db28d8760a6eb2bba922cad8de35ee1d2b6/solo/methods/base.py#L471
The model has one classifier to do classification task with label.
If the model is optmized with barlowtwins and class_loss bothly, Does it introduce more information in pretraining?

class_loss is only computed for data for which there is a known target class. It is used for online evaluation. It is not backpropagated to the backbone because the classifier head is detached from the graph:
logits = self.classifier(feats.detach()).
All data that is strictly for SSL have a class index of -1 which is ignored in the class_loss.

Many thanks for your reply!
In the online evaluation, is it the 'train acc' on wandb? Does it use cifar100 test set or still train set? Because I also find the 'val_acc' on wandb, their results seems similar, but I am not sure they use same dataset for evaluation.
Another question: In the pretrain, is the linear classifier is random initilized in every evaluation stage or updated every step(isolated with backbone)?

1/ pretty sure train_acc is computed on training data, and val_acc is computed on validation data, as their names suggests.
2/ from what I remember, the linear classifier is learned during the whole training procedure.
But I will let @vturrisi confirm/correct me if needed.

@gcanat exactly. Both the backbone and linear classifier are trained together during training, with the classification loss not updating the backbone.


Use cURL for faster restores to development

We had reports of slow restores from backups larger than 500MB in #94.
This change uses curl rather than heroku pg:pull to perform a
database restore. We download the remote backup to tmp, re-initialize
the development database, perform a restore with pg_restore and then
delete the tempfile.

Nice! Have you done any tests to see speed differences? Want me to try some large datasets and report back?

@croaky you can't install the executables via Rubygems any longer, so the easiest way to test is to install the development build via Homebrew:
https://github.com/thoughtbot/parity/releases/tag/development. Be sure to verify that you don't have an rbenv shim intercepting your attempts to run production, staging, or `development.

👍

@croaky I'm going to wait for your report against the DBs that caused you trouble before merging.

@geoffharcourt I can confirm that even for pretty small databases, using curl approach is way faster than heroku pg:pull. That is probably true because retrieving the dump file and running pg_restore from a local source is much faster than retrieving the data from the remote source as it gets restored. Hope that helps!

@fagiani thank you for the info! I am going to try to merge this soon.

I'm encountering some issues in testing where the database role in Heroku are named in such a way that they cause permission errors when the restore step happens. I'm looking in to what we can do about that.

time development restore staging with v0.10.0 for a 650 MB database:
 557.00 real         5.22 user         6.27 sys

time development restore staging with #100 for a 650 MB database:
 47.16 real         2.21 user         1.59 sys

@croaky can you test on a database today with the development release? https://github.com/thoughtbot/parity/releases/tag/development

hey @geoffharcourt, how long it usually takes to get a release on brew formulae after the PR is merged? Thanks again!

Hi @fagiani at the moment it's driven by my available time! If you want to install the development build on Homebrew (using the --devel switch it's at this commit). I'd appreciate the testing feedback to confirm that everything is working as expected.

@geoffharcourt maybe I am missing something but tried those commands without success:
$ brew tap thoughtbot/formulae
$ brew install --devel parity
Warning: thoughtbot/formulae/parity-0.10.0 already installed
$ brew install --devel parity-0.10.1
Error: No available formula with the name "thoughtbot/formulae/parity-0.10.1"

Any clues?

@fagiani try uninstalling parity, then execute brew install --devel parity with no argument? You may have to delete your Homebrew cache.

@geoffharcourt Thanks for the direction. It worked!
Tested both restoring from staging and from production on a couple of heroku apps. Results are incomparable!
I'd guess using cURL will get all data compressed at once then process it as batch locally while the former approach will end up doing several requests to the remote endpoint for the various restore steps and as you can see most of it is network activity that can get even worse with latency.
Here is a sample of a pretty small database (~35MB):
0.10.0: development restore-from production  1.15s user 0.70s system 0% cpu 4:34.71 total
0.10.1: development restore-from production  0.85s user 0.31s system 8% cpu 13.521 total

Keep Rocking!


Support for pushing notifications to the Ubuntu ISO Tracker

Sending this out for an initial review. The goal of this PR is to send out notifications to the Ubuntu ISO Tracker about any new WSL builds that are completed, notifying the respective per-series products. This way we'd have Ubuntu WSL images appearing on the tracker automatically. It also plays in nicely with another feature of this related to the ability to re-trigger builds via the tracker.
http://iso.qa.ubuntu.com/
This is the first time I deal with github actions, so that part is mostly written blindly by just looking at other sections and reading documentation. There's also some open questions here.
Open questions:

Version of the resulting WSL build. Right now I went with the simple route of just using build_id, but from what I see it's like a small number right now. Ideas I had was things like DATESTAMP.build_id or something, or does build_id suffice?
Not sure if the ISO Tracker API will work over HTTPS (which we need as it's outside of Canonical network)
I have no idea how github actions are triggered and how long the environment survives, but in the code I used /tmp/all-releases.csv in case that it might 'stick around' from previous job runs. I can switch to just doing it via LP directly, but if it's persistent for long enough I thought it might save a few LP API calls.

Other than that I think it's good enough. I only tested it in dry-run mode on my local machine. I'm open to suggestions!

Pushed a new version, ready for review.
In this version, as per discussion, I have switched to the approach of generating the ISOTracker config on the fly dynamically without actually creating a configuration file (pushed support for that to lp:ubuntu-archive-tools). I reorganized some of the github actions to have a better order too.
I tried a bit to move the notification logic to update-build-artifacts as you suggested and even had an idea how to do it (calling git-tree for HEAD to get the list of changed files to determine which projects got updated), but in the end decided to go with how it was before as I am not as confident in github actions logic. Since this then requires having the WSL repository available, and from the looks of it the update-build-artifacts job was working in the wiki repository directory. And I was like, eh, I don't feel comfortable enough to twiddle with things like these without having any way of testing this.
So yeah, I'd say we can switch to the other approach, but it feels like more invasive then?

Thanks for the changes here and not relying on the hardcoded ISO tracker configuration anymore. It looks good to me :) However, it seems you didn’t remove the hardcoded version from your branch.
On the other big comment, I’m still convinced that the best approach is to do in update-build-artifacts workflow:

there are some use cases for manual builds, without uploading to the store. In that case, the iso tracker should not be notified.
this whole logic of notifying the iso tracker is the same than "should we update our version database"? So, it means that if this job is running and we have a diff here, we had the corresponding desired upload done to the store for that version already. This way, we are sure our logics are aligned.
I think this can be easily done by calling git status in a job just after "Copy modified artifacts to base wiki", determining which file in which folder have been changed, and using this to know what to notify. If you need any additional metadata, I’m happy to give some hands here :)
"

Could you take a look if this is something that would work? Thanks!

Almost there!
I suppose one final thing to think about (poked JB a while ago about that as well) is actually how we should identify new builds in the ISO Tracker. Right now it's the buildid, but the ISOTracker would have to somehow construct a nice way of offering something to download using that ID.

Agreed, do you want that we resolve this next week before merging?

hm, okay, I feel that I'd need help getting a better understanding here. So from what JB told me a while ago, one way of 'accessing' WSL downloads is via pointing to the sideload download urls from build jobs, e.g.:
https://github.com/ubuntu/WSL/actions/runs/1852204709
The ISO Tracker url creations is rather simple and 'stupid'. It basically needs to construct the url using simple substitution only via the build_id, project, arch etc. Nothing complex can be done, just substituting variables in the url. In this case, it feels to me we'd have to send the WSL action run ID to the ISOTracker, then we could at least link to the action url for people to fetch the sideload archives.
Is it possible to get the run ID somehow? Or do we need to move this to some different stage then?

Should now be again good for review. As per our earlier discussion, switched to using the GITHUB_RUN_ID. Hope this is correct! Thank you @didrocks for helping out on all the stages of this PR!

Naming transitions are now completed. Let’s merge that. Thanks for working on it!


Console not accurately tracking userid

Bug Report
System Information

Linux: Debian 11
AMP version <IP_ADDRESS>
Which AMP release stream Mainline

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms

What are you trying to do? Track users logging into the game server and leaving the game server properly
What are you expecting to happen? When user leaves the game server, they are accurately removed from the console
What is actually happening? When a user leaves the game, it is randomly picking someone to say they logged out and leaving the person who really logged out as in game when they are not.

Reproduction
Add Greelan's Path of Titans Template to the ADS
Install the game server ( Path of Titans )
Start the game server and have multiple people connect to the server in game
Have one or more people leave the game while still having some players on the server.
check the console versus the in game social menu or use the console command listplayers
Greelan and I have looked through this extensively and have come to the conclusion that the regex is correct for the leave section.

Adding to this:
The user join regex in the template matches on username and userid. However, the user leave regex is only able to match on userid. Query whether the absence of username in the leave regex is causing tracking issues for AMP?
Relevant regex:
Console.UserJoinRegex=^(?:\[[\d\.]+-[\d\.:]+\]\[[\d ]+\])?TitansNetwork: AIGameMode::InitNewPlayer\(\?EncryptionToken=(?:.+?)==\?Name=(?<username>.+?)\?\?PID=(?<userid>.+?)\?PT=\d+\?OS=\d+\?SplitscreenCount=\d+\)$
Console.UserLeaveRegex=^(?:\[[\d\.]+-[\d\.:]+\]\[[\d ]+\])?AlderonLog: IAlderonCommon:UnregisterPlayer\(\) Request: {"player_id":(?<userid>.+?),"platform":"(?:.+?)"(?:.*?)}$

Yes, also having this issue. Caused major headaches when trying to schedule backups when no users are online. Happens on multiple instances and templates, 7 days to die and core keeper I can confirm off hand.


Component Docs Are Practically Unusable On Mobile And Smaller Screens

This issue is to report a significant usability concern I have with your Components Documentation. I find this documentation to be practically unusable on mobile devices and smaller screens. The main two symptoms I am running into are:

The DOM of the page is HUGE, which can cause very high load times for devices with lower memory (a mobile-specific concern)
The device preview pane will overlap the documentation text as the screen size gets smaller. Since the text does not wrap around the device preview, the left sidebar cannot be resized, and the device preview cannot be hidden, the documentation becomes completely unreadable. Definitely a concern on mobile, but it's even a problem on my 13 inch Macbook Air.

I am now forced to be at my home or office workstation with an external monitor connected in order to read Native-Base documentation. That is of course unreasonable, as there are many other places I wish to consume this documentation on a smaller screen (ex: while commuting to work, at the coffee shop, or even just on my laptop).
Without being able to easily consume documentation for a framework, it becomes hard to continue using the framework. I think it would be wise for this issue to be given careful consideration. Even just something as simple as adding a show/hide toggle to the device preview may be enough to appease most of this issue's concerns.

@SupriyaKalghatgi @suvenduchhatoi I am requesting attention on this issue please.

@ecbrodie We have considered this. @SupriyaKalghatgi will get back to you.

@ecbrodie I will look into this and get back to you
Will take some time though

@ecbrodie The latest docs is live with 2.12.0 and usable on smaller devices

@SupriyaKalghatgi I have tried out the updated docs on my mobile device and here's my feedback:

The webpage on mobile has gone from completely unusable to barely usable
I am now able to read the text of the desired component I'm looking up about 50% of the time. Half the time, the webpage crashes due to the DOM still being extremely large and thus eating up all my device's memory. The other half of the time, I still experience severely degraded performance (ex, large page load times, reading about a second component will cause the page to crash)
I still see the Device Preview Widget load on the mobile page, but then disappear a few seconds later. I think that this approach still causes issues. The device preview may still be loaded into the page, just not visible. This could be eating up into the DOM size and thus hurting performance.
Why not split this one giant HTML page into multiple smaller pages? Or, just load each component' section lazily as requested?

Overall, while my issue may be minimally fixed, I don't think it's enough to consider Native Base's documentation to be sufficient for mobile devices.


[Solved] TensorList shape mismatch:  Shapes -1 and 3 must match

After exporting the model and testing that it works properly, I've converted it to Tensorflowjs following your steps.
I've loaded it to the browser and I can't find the way to let it predict an image,
Here's the code:

const process_input = (image ) => {
const tfimg = tf.browser.fromPixels(video_frame).toInt();
const expandedimg = tfimg.transpose([0, 1, 2]).expandDims();
return expandedimg;
};
const image = document.getElementById('image');
const preImage = process_input (image);
tf.engine().startScope();
model.executeAsync(testImg).then(predictions => {
console.log(predictions);
tf.engine().endScope();
});

Right after that, I got an error saying:

Unhandled Rejection (Error): TensorList shape mismatch:  Shapes -1 and 3 must match

I have the same issue

I have the same problem

The problem was with TensorFlowJS 3.0.0
after upgrading to 3.1.0 I can confirm all work well, just when converting the model - do not use the converter wizard as it adds the argument --control_flow_v2=True which causes a different problem.

Well noticed, @nirchetrit! Thanks for your contribution

The problem was with TensorFlowJS 3.0.0
after upgrading to 3.1.0 I can confirm all work well, just when converting the model - do not use the converter wizard as it adds the argument --control_flow_v2=True which causes a different problem.

please share a saved_model.pb file with me, thanks

Hey,
please make sure you are running:
"@tensorflow/tfjs": "^3.1.0",
"@tensorflow/tfjs-converter": "^3.1.0",
As well tfjs-converter 3.1.0 in your python environment..
For the converter use the following command:
tensorflowjs_converter \
    --input_format=tf_saved_model \
    --output_format=tfjs_graph_model \
    --signature_name=serving_default \
    --saved_model_tags=serve \
    saved_model \
    web_model

Anyway, this is the issue post

Hey,
please make sure you are running:
"@tensorflow/tfjs": "^3.1.0",
"@tensorflow/tfjs-converter": "^3.1.0",
As well tfjs-converter 3.1.0 in your python environment..
For the converter use the following command:
tensorflowjs_converter \
    --input_format=tf_saved_model \
    --output_format=tfjs_graph_model \
    --signature_name=serving_default \
    --saved_model_tags=serve \
    saved_model \
    web_model

Anyway, this is the issue post

i just want a saved_model.pb    thanks<EMAIL_ADDRESS>

Hi @nirchetrit , I have encountered the same issue so I followed your solution. In more details:

I have created the virtualenv with tensorflowjs-converter 3.1.0
I have cloned the app from @hugozanini repository.
Instead of executing "npm install "I have manually installed tfjs, tfjs-converter, tfjs-node, tfjs-core : all in 3.1.0 version
I also installed tfjs-data and tfjs-layers as they were listed as necessary when I execute " npm list --depth=0" command

Unfortunately I still can't get it working now with different error: " Unhandled Rejection (TypeError): undefined is not a function (near '...scores[0].forEach...') " .
I am training exact same model on the same data as @hugozanini. My version of model is here: https://raw.githubusercontent.com/TrybusRafalJan/TWM_projekt/main/web_model/model.json
I would much appreciate your help.

Hi @nirchetrit , I have encountered the same issue so I followed your solution. To be more specific:

I have created the virtualenv with tensorflowjs-converter 3.1.0
I have cloned the app from @hugozanini repository.
Instead of executing "npm install "I have manually installed tfjs, tfjs-converter, tfjs-node, tfjs-core : all in 3.1.0 version
I also installed tfjs-data and tfjs-layers as they were listed as necessary when I execute " npm list --depth=0" command

Unfortunately I still can't get it working now with different error: " Unhandled Rejection (TypeError): undefined is not a function (near '...scores[0].forEach...') " .
I am training exact same model on the same data as @hugozanini. My version of model is here: https://raw.githubusercontent.com/TrybusRafalJan/TWM_projekt/main/web_model/model.json
I would much appreciate your help.

You have you change de index in the boxes, scores and classes variables


Add quadlet and GH actions for whisper app

whisper images should be added to GH workflow and need to create quadlet files

this can wait for a bit as we are still getting this image into a state where it can be used as a model server with an exposed api.

closing this with merge of #83


Issue with loadYamlContent function

Discussed in https://github.com/Azure/bicep/discussions/12205

Originally posted by kpanugan October 19, 2023
I am seeing the following issue when using loadYamlContent function in bicep file
var bicepObject = loadYamlContent('testVal.yaml')
output helloWorld object = bicepObject
where input is something simple
TopValues:
 labels:
   -keyName: "null"

The outputs i was expecting was
{
   "TopValues":{
     "labels":[{
        "keyName":"null"
     }]
    }
}

but i am getting it as
{
   "TopValues":{
     "labels":[{
        "keyName": null
     }]
    }
}

why is the value for "keyName" getting converted to a null instead of string which has null

@dciborow - can you take a look at this one?

@kpanugan , can you try and add a space between '-' and 'keyName'?
I'm curious if that is causing an issue... I will try and get a test case for this. My first take is that if there is an issue it might be in the yaml library we are using (we aren't going any of the nested parsing ourselves...)

@kpanugan , per SharpYaml, to make it null, you can wrap it in double quotes ""null"".
https://github.com/xoofx/SharpYaml/issues/106
https://github.com/xoofx/SharpYaml/pull/112


Request for multiple documents stopped working

Hi, I was successfully using this script during a couple of months, but 1 or 2 days ago it stopped working without a reason. I have two servers - local Windows 7 and public AWS, surprisingly the script stopped working on local Windows server only.
Environment: Windows 7 x64, XAMPP with PHP 7.1.7 x86 ThreadSafe with relevant GRPC DLL.
require './vendor/autoload.php';

use Google\Cloud\Firestore\FirestoreClient;

$store = new FirestoreClient([
    'projectId' => 'some-super-demo'  // project is publicly available without any permissions
]);

$collections = $store->collections();              // works
$collection = $store->collection('demo');          // works
$document = $store->document('demo/monday');       // works

// the line below does NOT work, it hangs for a minute, then returns random error, usually about permissions

$documents = $collection->documents();

Error.

Fatal error: Uncaught Google\Cloud\Core\Exception\ServiceException: {
"message": "Missing or insufficient permissions.",
"code": 7,
"status": "PERMISSION_DENIED",
"details": []
} in C:\Users\MyUser\Desktop\Programs\Php\htdocs\localhost.store.com\vendor\google\cloud-core\GrpcRequestWrapper.php on line 254
1 | 0.2130 | 352424 | {main}(  ) | ...\index.php:0
2 | 0.2870 | 2876984 | Google\Cloud\Firestore\CollectionReference->documents(  ) | ...\index.php:42
3 | 0.2880 | 2886752 | Google\Cloud\Core\ExponentialBackoff->execute(  ) | ...\Query.php:202

Permissions in my FireStore.
service cloud.firestore {
  match /databases/{database}/documents {
    match /{document=**} {
      allow read, write;
    }
  }
}

I haven't seen this issue for a while, so probably it can be closed.

I have same problem now.
I'm use

Windows 8.1
Xampp
php 7.1
php_grpc.dll from php_grpc-1.19.0-7.1-ts-vc14-x86.zip

My vendors:

"google/apiclient": "^2.2
"google/cloud-firestore": "^1.4",
"google/protobuf": "^v3.3.0",


Unable to verify with custom Signature suites

https://www.w3.org/2018/credentials/v1
Signature suites are hardcoded in this context.
This causes "The property "created" in the input was not defined in the context.",... with custom suites.
This  was not detected in my initial test for: https://github.com/transmute-industries/lds-jws2020
because I was signing a did doc... which defines "created" outside of a specific signature suite context.
Interestingly... I'm not seeing this error here: https://github.com/transmute-industries/lds-jws2020/blob/master/src/tests/vc-edu.spec.js
So its possibly related to a version drift issue.

This was caused by not setting compactProof: false,
I find this default of "true" to be a little confusing... since it results in JSON which is likely to confuse / frustrate developers unfamiliar with JSON-LD.

This issue is not actionable, so I suggest closing after leaving any comments for future searchers.

Closing due to inactivity.


Removed 'if not null' documentation as it cannot be null in Particle Component

Fixes https://github.com/playcanvas/developer.playcanvas.com/issues/238
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

Wait, are you saying that if I add a particlesystem component to an entity and I set localVelocityGraph, and then query localVelocityGraph2, does it return localVelocityGraph or null...or something else? This is a bit confusing.

Here is the original thread: https://forum.playcanvas.com/t/change-local-velocity-of-particle-system/17961/
The current documentation implies that localVelocityGraph2 was optional but it isn't the case. Both localVelocityGraph and localVelocityGraph2 need to be set for a particle system to behave correctly.
In the Editor, if randomise is unticked for the graph, it will set both localVelocityGraph and localVelocityGraph2 to be the same graph.

I looked at engine example particles-snow, and when I comment out these two lines:
                velocityGraph2: velocityCurve2,
                rotationSpeedGraph2: rotCurve2,

the example still runs, but the randomisation is gone. That suggests that these parameters can be null.

Doesn't seem to work when velocityGraph2 is explicitly set to null after creation though: https://playcanvas.com/editor/scene/1093460
var ParticleVelocity = pc.createScript('particleVelocity');

ParticleVelocity.prototype.initialize = function() {
    var self = this;
    setTimeout(function() {
        console.log(self.entity.particlesystem.localVelocityGraph);
        self.entity.particlesystem.localVelocityGraph = new pc.CurveSet([

            [0, 0],

            [0, 0],

            [0, 0]

        ]);

        self.entity.particlesystem.localVelocityGraph2 = null;

        self.entity.particlesystem.reset();
        console.log(self.entity.particlesystem.localVelocityGraph);
    }, 1000);
};

We need to check if this is a bug or expected behaviour.


Test

Test issue
https://groups.google.com/forum/#!topic/cesium-dev/_T3vRx1D858

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/#!topic/cesium-dev/_T3vRx1D858
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium-concierge/issues/89 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

I am a bot who helps you make Cesium awesome! Thanks again.

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/forum/#!topic/cesium-dev/_T3vRx1D858
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium-concierge/issues/89 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:


ShadowDelta sample will not run with the new endpoint format

The endpoint you get from AWS IoT Console has been updated to a new format.
Old Format: (UUID).IoT.(AWS Region).amazonaws.com
New Format: (UUID)-ats.IoT.(AWS Region).amazonaws.com
When running the ShadowDelta sample with the new endpoint format I get the following output:
[INFO] Wed Oct 10 14:23:30 2018 :681 [OpenSSL Wrapper] [139705419639680] [ConnectTCPSocket:L234] : resolved <new format endpoint> to <valid ip>
[ERROR] Wed Oct 10 14:23:30 2018 :711 [OpenSSL Wrapper] [139705419639680] [PerformSSLConnect:L376] :  Server Certificate Verification failed.
If I remove the -ats from the new endpoint (which is the old endpoint format) the ShadowDelta sample successfully runs with the following output:
[INFO] Wed Oct 10 14:23:38 2018 :981 [OpenSSL Wrapper] [140195081255808] [ConnectTCPSocket:L234] : resolved <old format endpoint> to <valid ip>
[INFO] Wed Oct 10 14:23:39 2018 :137 [Network Read] [140195045361408] [HandleConnack:L228] : Network Connect Response. Success : SDK Code 0.
I have not tried other samples but I assume it will affect them too.

When you switch to the new -ats endpoint, you must ensure you are using the correct ATS root CA. See here for more details: https://docs.aws.amazon.com/iot/latest/developerguide/managing-device-certs.html

Glad to hear it! Happy coding 😃


Snapshot

Few functions to manipulation snapshots:

CreateSnapshotRepository
TakeSnapshot
RestoreSnapshot
GetSnapshots(and specific one by Name)

@stumpyfr Thanks for your work. I reviewed the code on github, I'm going to pull and run it soon.


AWS Curve ball

Drama! https://forums.aws.amazon.com/ann.jspa?annID=6776
AWS is going to enforce virtual host style syntax which ruins the assumption I made previously about defaulting to path style. This will need to be set as a config field.

Implemented: https://github.com/Jeffail/benthos/commit/de6799b0a430a9a46c0d4537f253b4e34da60f01


Missed sendgrid via RBL

Here email headers:
Return-Path<EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Return-Path<EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: from wfbtvdtn.outbound-mail.sendgrid.net (wfbtvdtn.outbound-mail.sendgrid.net [<IP_ADDRESS>])
	by mx1.catap.net (OpenSMTPD) with ESMTPS id f41c214b (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO)
	for<EMAIL_ADDRESS>	Mon, 9 Dec 2024 02:09:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clubnft.com;
	h=from:subject:list-unsubscribe:mime-version:content-type:reply-to:to:
	cc:content-type:from:subject:to;
	s=s1; bh=WsI/qb3w0DegSvsqU64IWwx3uA70ytNOsiP4nXybrIQ=;
	b=afeoZeKYtaD7Den7LauJ5ZJYCEFNsvGXC+RWq9yny9KEZ0+bnxRKrMMcqsqpJ7iIpSWE
	oc7YluPBrchkv89rRuFz4lxqlVfk41vMgkPqRSAbPk/V/AQ3YydkWusRZBvODOI7VCs7b1
	8NNxOovA3mvBs6BS8Fu4QYOdt3yFSoQlD6hrhNeaqM9z/bJ/LGEQkpBItNjsVeg19wbfPx
	rtf2D+Zbmm1tqiLfztSC+jS/gXgZ1min0MN/F5LDxPsydi9mxwY22HyhV+ByA2LMH8+rVP
	JXfCsadwE7A75Ll7cBt/07NB/XMIGAl/AELWtzH+QzAp8wfdeu1Mrh9oBMBiRRXQ==
Received: by recvd-578d769b87-kw9vv with SMTP id recvd-578d769b87-kw9vv-1-67564362-F
	2024-12-09 01:09:54.379410379 +0000 UTC m=+2087254.957309691
Received: from DESKTOP-FPGODED (unknown)
	by geopod-ismtpd-4 (SG) with ESMTP
	id OEs8chsITdi5HwvEgePPVg
	for<EMAIL_ADDRESS>	Mon, 09 Dec 2024 01:09:54.250 +0000 (UTC)
From: OpenSea<EMAIL_ADDRESS>Subject: New Offer Received!
Date: Mon, 09 Dec 2024 01:09:54 +0000 (UTC)
List-Unsubscribe: <mailto:matt@clubnft.com?subject=Unsubscribe>
X-Priority: 3
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="CC3084E4ADB74A889F6E798CB6E90834"
Message-ID: <OEs8chsITdi5HwvEgePPVg@geopod-ismtpd-4>
Reply-To<EMAIL_ADDRESS>X-SG-EID:
 =?us-ascii?Q?u001=2E2iNtUAqqmnCvkDaBFuQSIll0+YXpkoFy6dxUGmBmQO5gfu+jnmU6rvPBW?=
 =?us-ascii?Q?FOo4qHALQE2cXuTU+CY0A20Q0N+bDCvkf9eWOux?=
 =?us-ascii?Q?NVdwVNDoWjMocrxXTaOQRDN+92JlkqQCVmZpVqb?=
 =?us-ascii?Q?WmuWvJL7L5uZeo6L332QyaBqOn=2FsKDB6rNkrD0f?=
 =?us-ascii?Q?Uz4HYfG3LdvYo3R6Q4nEEkyUfUc2O37djOOokOP?=
 =?us-ascii?Q?C13DKDNjJZBD5dwpvg8R88=3D?=
To<EMAIL_ADDRESS>X-Entity-ID: u001.SRP8q+jZWSu7PZj/SVLH9g==

it is working as:
Dec  9 04:00:06.163 [72719] dbg: config: adjusting regex capture rule __ESP_SENDGRID_DOM priority to -10000
Dec  9 04:00:06.165 [72719] dbg: config: adjusting regex capture rule __ESP_SENDGRID_ID priority to -10000
Dec  9 04:00:06.167 [72719] dbg: config: adjusting regex capture rule __ESP_SENDGRID_IDA priority to -10000
Dec  9 04:00:08.079 [72719] dbg: rules: ran header rule __ESP_SENDGRID_ID ======> got hit: "bounces+25782035-"
Dec  9 04:00:08.079 [72719] dbg: rules: ran header rule __ESP_SENDGRID_DOM ======> got hit<EMAIL_ADDRESS>Dec  9 04:00:08.807 [72719] dbg: rules: ran header rule __ESP_SENDGRID_EID ======> got hit: "<YES>"
Dec  9 04:00:08.821 [72719] dbg: async: launching A/25782035.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL
Dec  9 04:00:08.821 [72719] dbg: async: starting: __ESP_SENDGRID_RBL, HASHBL, A/25782035.sendgrid.espbl.snb.it (timeout 15.0s, min 3.0s)
Dec  9 04:00:08.827 [72719] dbg: async: launching A/clubnft.com.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL_D
Dec  9 04:00:08.828 [72719] dbg: async: starting: __ESP_SENDGRID_RBL_D, HASHBL, A/clubnft.com.sendgrid.espbl.snb.it (timeout 15.0s, min 3.0s)
Dec  9 04:00:08.948 [72719] dbg: async: calling callback on key A/25782035.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL
Dec  9 04:00:08.949 [72719] dbg: async: calling callback on key A/clubnft.com.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL_D
Dec  9 04:00:08.949 [72719] dbg: async: completed in 0.121 s: HASHBL, A/clubnft.com.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL_D
Dec  9 04:00:08.949 [72719] dbg: async: completed in 0.126 s: HASHBL, A/25782035.sendgrid.espbl.snb.it, rules: __ESP_SENDGRID_RBL

Looks like a miss.

Thanks, listed.
to add more IDs to rbl just forward the email as attachment to<EMAIL_ADDRESS>


Need data in nested format but getting with the repetitive object like

:)

Hey @vipulpatel1994, can you provide an example and explain what you are trying to achieve in more detail?

Closing this due to inactivity.


Fix issue where insurance messages would appear as received if you only lost gear you were wearing

Insurance messages each need a unique "stash" ID, properly handle this as part of the processing side of insurance
Remove handling of parent IDs from the insurance storing side of insurance, as we don't need to do that processing twice
Add a new step to the profileFixer service that resolves any already broken trader messages with attached insurance items

This one is a bit annoying to test:

Equip and insure atleast one piece of gear
Load into raid and die
Close server, modify insurance return time to be in the past
Restart server and login, verify the message from the trader shows your lost item(s)
Validate profile JSON doesn't have the PMCs equipment ID in the insurance message stash property


The type name 'ServiceController' could not be found in the namespace 'System.ServiceProcess'.

I got an error message when using Cake.Services
The type name 'ServiceController' could not be found in the namespace 'System.ServiceProcess'. This type has been forwarded to assembly 'System.ServiceProcess, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' Consider adding a reference to that assembly. [release.cake]
This is how I add to the header file.
#addin "nuget:?package=Cake.Services&version=0.3.2"

I would assume that your referencing ServiceController in your script without including a reference to System.ServiceProcess.


WorkManager not working with Proguard and not debugable mode

Hello folks,
When changing the gradle configuration on the app like this:
debug {
            debuggable false
            minifyEnabled true
            shrinkResources true
            zipAlignEnabled true
        }

The Worker stops working. The problem is also showing in our company app. It I change the debugable to true, the problem goes away (which is really odd). I am not sure if this is the best place to post the problem since this is just an example library, but I believe there's a bug with the WorkManager library.
The problem can be easily reproduced by changing the configuration of this library like the example above. The app never gets to the point of saving the blurry image with the new configuration

Interesting. I confirm, that i can reproduce your issue.
But if you add proguard in your debug block, the work manager 2.0.1 works fine.
        debug {
            debuggable false
            minifyEnabled true
            shrinkResources true
            zipAlignEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }

I am not sure if you skip the proguardFiles so as to allow shrinking with R8.

Thanks for reporting this.
I'm closing this issue because I cannot reproduce it in this codelab using WorkManager v2.1.0.
If you think that this is a problem of the WorkManager library, please open a bug on the WorkManager public issue tracker: https://issuetracker.google.com/issues/new?component=409906&template=1094197
Please reopen if you still think this is an issue with the codelab.

Where is this issue on Github?


unpin binutils

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
binutils was pinned to version 2.30-22 in https://github.com/falcosecurity/falco/pull/397 because binutils-2.31 requires kernel > 4.16. Current based image (debian:buster) is on kernel 5.10. There's no need to pin to the lower version. This will keep it patched.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NO

NONE

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e6a8b41 unpin binutils

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: lichao127
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

docker/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @lichao127! It looks like this is your first PR to falcosecurity/falco 🎉

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e6a8b41 unpin binutils
fea9bfe follow tab indentation

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

62f7f63 unpin binutils

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

cc @FedeDP @Andreagit97

Hi! Thanks for this PR!

binutils was pinned to version 2.30-22 in https://github.com/falcosecurity/falco/pull/397 because binutils-2.31 requires kernel > 4.16

I don't think that's true; the issue is that drivers built using newer binutils are not going to work on older kernels; that's what the comment says after all:

debian:stable head contains binutils 2.31, which generates
binaries that are incompatible with kernels < 4.16. So manually
forcibly install binutils 2.30-22 instead.

Basically, we need to use old binutils version to have a wider compat matrix!

I don't think that's true; the issue is that drivers built using newer binutils are not going to work on older kernels; that's what the comment says after all:
Basically, we need to use old binutils version to have a wider compat matrix!

Pinning binutils to an old version means it will not be patched for CVEs like CVE-2018-10372, CVE-2018-10534 etc. It also blocks other packages from security patching as a lot of packages are has dependencies on it.
Also, the base image has changed from debian:stable to debian:buster in https://github.com/falcosecurity/falco/pull/1719.
The comments added in https://github.com/falcosecurity/falco/pull/397 should either be updated to reflect the reason to pin binutils, or they should be cleaned up.

Pinning binutils to an old version means it will not be patched for CVEs like https://github.com/advisories/GHSA-pw2g-xg7w-mccx, https://github.com/advisories/GHSA-672m-f2rr-8wvq etc. It also blocks other packages from security patching as a lot of packages have dependencies on it.

Yep that's an issue, for sure. Still, we need the widest possible compatibility unfortunately.

Also, the base image has changed from debian:stable to debian:buster in https://github.com/falcosecurity/falco/pull/1719.

Yes because debian:stable switched to bullseye  but we needed buster.
cc also @LucaGuerra

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

cc @LucaGuerra

Ehy, #2718 is updating the default Falco image to Debian 12 (keeping the current image as legacy). Do you think this would still be needed?

Moving to TBD until further user input.
/milestone TBD

To be honest I would close it since the issue should be solved by https://github.com/falcosecurity/falco/pull/2718... Of course, if this is not the case feel free to re-open it! :)


fix-1733: Social Sharing wrong session

Checklist

[x] I have read the Contribution & Best practices Guide.
[x] My branch is up-to-date with the Upstream development branch.
[ ] I have added necessary documentation (if appropriate)

Short description of what this resolves:

Social Sharing wrong session

Changes proposed in this pull request:

Social Sharing wrong session

Fixes #1733

Please resolve conflicts.