example/gpt2 benchmark cannot achieve 2ms

I just run gpt benchmark as below on 3090, but I cannot reproduce the 2ms speed in bounties sheet.
JIT=1 python3 examples/gpt2.py --timing

...
ran model in   5.90 ms

ran model in   5.91 ms

ran model in   5.92 ms

ran model in   5.93 ms

ran model in   5.93 ms
...

Is anything wrong for my testing?

You need to use half + beam. Beam might take some time to optimize. You can use DEBUG=2 to follow the progress of beam, but remove DEBUG=2 to get the full performance on the next run.
CUDA=1 JIT=1 HALF=1 BEAM=2 CACHELEVEL=0 JIT_BATCH_SIZE=4 python3 examples/gpt2.py --count 10 --temperature 0 --timing

oh I see, beam not beam search in LLM but beam in tinygrad

for achieving 2ms -> 1ms, please shed some light on it, maybe using speculative sampling as kernel and graph are all optimized and some inference mechanism may come to help?


[Feature Request]: Support extensionAlias field

What problem does this feature solve?
As mentionned in the following discussion and issue, to use Wepack (now rspack) with an ESM + TypeScript setup, the bundlers should support file extensions aliases to enable the following syntax:
// Importing from button.tsx but using the ".js" file extension to satisfy TypeScript.

import type { ButtonProps } from "./button.js"

As ESM is getting quite popular it would be great to have support for extensionAlias sooner than later 🙏🏻
TypeScript 5.0 comes with a "bundler mode" module resolution which should fix the issue but it would still be useful for organization which cannot move to TS 5.0.
Thank you
What does the proposed API of configuration look like?
Same as Webpack https://webpack.js.org/configuration/resolve/#resolveextensionalias

@patricklafrance I just found this issue while trying to migrate from Webpack. Has it been really implemented and released? My configuration gets rejected with the following:
 configuration.resolve has an unknown property 'extensionAlias'

@jraoult it has not been implementend. I closed the issue because it’s not necessary anymore with TS 5 offering the allowImportingTsExtensions configuration field.

@patricklafrance thx for your reply. In my case, allowImportingTsExtensions  doesn't provide the same benefits as extensionAlias. I'm sharing modules between Node and the browser. It's essential to be able to write import {...} from "./myModule.js" so it can be resolved once transpiled for the Node side (cf. https://www.typescriptlang.org/docs/handbook/esm-node.html). Neither import {...} from "./myModule.ts" nor import {...} from "./myModule" would work when using ESM resolution. So my solution was always to write the full import path with the .js extension and then get Webpack to try the .ts and .tsx when the .js doesn't resolve to an existing file.
Would you reconsider the decision not to implement it?

Hey @jraoult
I initally created an issue but I thought it was required to support ESM+TS+Webpack but I am not a maintainer nor contributor of rspack, there I have no say in that :)
Since this one is close and your use case is different, I would recommend creating a new issue.

@patricklafrance, my bad. Somehow I assumed you were one of the maintainers 😀. I'll create a new request then.


after updating, entities dissapear

PLEASE DO NOT DELETE AND FILL IN!
Describe the bug
After uptating to latest version, entities dissapeared and only 4 are present, none of which provide current readings (this is used on an account with Octopus Mini
To Reproduce
Update to altest version of integration
Expected behavior
Being able to read meter values as well as current demand
Home Assistant Version
Home Assistant 2023.6.3
Supervisor 2023.06.4
Operating System 10.3
Frontend 20230608.0 - latest
Integration Version
v7.4.4
Fresh Install?
update
Home Assistant Logs

Enabled debug logging, and attempted to reconfigure integration.
home-assistant_octopus_energy_2023-07-03T10-53-24.572Z.log

Thanks for the logs. I'll have a look when I get a chance. I suggest you revert back to the last known good version as it might take me a couple of days to get a fix out.

sorry for the dumb question. how can i revert to previous version or install the previous one?

Thanks, I've reverted to 7.4.3 and entities are back.

Hello. This should be fixed as part of v7.4.5


Glob pattern for windows directory wildcard

I am trying to find files from multiple directories with one glob pattern. For example There are 2 directories with names of L:/05XX14/ and L:/05XX15/. If I use the first 2  patters below I get the files from the individual locations. If I try the last pattern I get nothing. Any Ideas?
works           L:/05XX14/*.dwg
works           L:/05XX15/*.dwg

not working       L:/05**/*.dwg

You probably should be using:
L:/05*/.dwg
not:
L:/05**/.dwg
A "globstar" () should be used alone in a path Like: yyyy//*.dwg

@jvoccia Right, but L:/05**/*.dwg ought to match the same things as L:/05*/*.dwg.  I gather that's the bug.

@jmorrisIII What's the L: drive in this case?  Network share or something?  Does it work in C:?

@isaacs the L: drive is a network drive. I also tried the 'L:/05**/.dwg' pattern on my C: drive with the following pattern 'C:/globtest/05/*.dwg' and it does work locally.

FWIW, I'm seeing what I think is similar behavior -- or at least cross-drive issues with globbing.
> glob.sync('E:/B56F007A.BIN')
[ 'E:/B56F007A.BIN' ]
> glob.sync('E:/B56F007*.BIN')
[]

E: is an attached mass-storage device.

I have also noticed the same behavior.
I would expect to get matches from "pre_*.xls", but reverted to matching "*.xls" and transforming the returned array instead.

I had a similar issue matching files on an SD card. Setting the cwd option to the drive mount-point/letter fixed it for me.

This is no longer an issue on v9, as drive letter paths are handled properly.


Fix many Kt warnings so as to see the forest for the trees.

/gcbrun

Should we make it so that new Kt warnings break the build?

@jblebrun I am going to land this as the conflicts were just a few lines, and I think will merge cleanly.


Need support in installing framework

Description
I am trying to install the framework but I am not able to install it properly as getting different type of errors. If anyone has complete guide how to install a project that will be helpful.
Your environment
Detox version:
React Native version:
Node version:
Device model:
OS:
Test-runner (select one): jest / other

Hi @ppj7887, we have a very comprehensive guide for setting Detox on your project: https://wix.github.io/Detox/docs/next/introduction/getting-started
Did you try to follow it? If so, can you please be more specific, what errors do you get?

Getting error for test binary apk not found. I am not sure what should I do?


Rewrite to async

This is a behind the scenes rewrite to change to async functions. The existing Docker and Command-line settings didn't change so all previous setups will continue to work.
Changes

Change JuiceboxTelnet from telnetlib to telnetlib3 (Fixes #25)

This started the cascade of needing to update every other class to async as well

Update JuiceboxUDPCUpdater, JuiceboxMQTTHandler (fka. JuiceboxMessageHandler) to async and moved to separate files.

In JuiceboxMQTTHandler, built out framework that should better support sending commands from JPP to the JuiceBox as well as storing the latest value sent to HA. Hopefully this, along with the Experimental option below, will facilitate further development of controlling the JuiceBox from JPP/HA.

Updating PyProxy required essentially a full rewrite so renamed to JuiceboxMITM. Incorporated asyncio-dgram
Add EXPERIMENTAL option for users to opt in to the in development functions. Currently this exposes:

Data from JuiceBox and Data from EnelX sensors to HA
A MVP Text field to send "commands" to the JuiceBox

Improved logging including logging to both stderr and a file. Implement log rotation to keep 14 days of file logs.
Implemented aiorun and tini for better garbage management, thread cleanup, and graceful shutdowns
Attempted to incorporate better handling when connections or updates fail. This includes restarting connections, implementing timeouts to prevent freezing, as well as fully exiting the program when too many errors have occurred to allow a docker restart of the app.
Incorporate several items from #55

Add ignore remote option, now called IGNORE_ENELX option to prevent commands from EnelX to going to the JuiceBox and data from the JuiceBox from going to EnelX

Any commands from EnelX will still be captured by JPP

Add Current Rating sensor
Add the parsed fields from the JuiceBox status messages as attributes in the Local Data experimental sensor

Moving away from SRC and DST in both the settings and the code as it was not clear what they should contain.

Deprecated the SRC option and replaced it with LOCAL_IP
Deprecated the DST option and replaced it with ENELX_IP
Current setups using SRC and DST will continue to work for now but should eventually be updated to the new terms.

Add LOCAL_PORT option (Fixes #60)

ToDo

DNSPython asyncresolver not working
Improve error handling in MQTT Handler
Lots more regression testing

At this point, I believe this is ready for review and testing. I released it with the async_beta docker tag for testing as well.
services:
  juicepassproxy:
    image: ghcr.io/snicker/juicepassproxy:async_beta

   [...]

I'll likely end up making some more small tweaks and will remove some extraneous logging and commented out code.
@snicker
@ivanfmartinez
@FalconFour

At this point, I believe this is ready for review and testing. I released it with the async_beta docker tag for testing as well.
services:
  juicepassproxy:
    image: ghcr.io/snicker/juicepassproxy:async_beta

   [...]

I'll likely end up making some more small tweaks and will remove some extraneous logging and commented out code. @snicker @ivanfmartinez @FalconFour

I will try to test on this weekend.
Thanks

@Snuffy2 I think that when using ignore_enel_x, the telnet to juicebox step can be skipped
juicepassproxy_tst    | 2024-05-15 09:04:33  INFO      [entrypoint.sh] IGNORE_ENELX: true
juicepassproxy_tst    | 2024-05-15 09:04:33  INFO      [entrypoint.sh] EXPERIMENTAL: true
juicepassproxy_tst    | 2024-05-15 09:04:33  WARNING   [main] Starting JuicePass Proxy v0.2.2 (Log Level: INFO)
juicepassproxy_tst    | 2024-05-15 09:04:33  INFO      [main] log_loc: /log/juicepassproxy.log
juicepassproxy_tst    | 2024-05-15 09:04:33  INFO      [main] config_loc: /config/juicepassproxy.yaml
juicepassproxy_tst    | 2024-05-15 09:04:33  INFO      [main] telnet timeout: 30
juicepassproxy_tst    | 2024-05-15 09:05:03  WARNING   [main] Error in getting EnelX Server and Port via Telnet. (TimeoutError: Telnet Connection Failed)
juicepassproxy_tst    | 2024-05-15 09:05:03  INFO      [main] enelx_server: jbv1.emotorwerks.com
juicepassproxy_tst    | 2024-05-15 09:05:03  INFO      [main] enelx_port: 8042
juicepassproxy_tst    | 2024-05-15 09:05:03  INFO      [main] local_addr: <IP_ADDRESS>:8042
juicepassproxy_tst    | 2024-05-15 09:05:03  INFO      [main] enelx_addr: <IP_ADDRESS>:8042

When I stopped charging the car, the current value did not change to 0, the proxy just stopped sending updates.
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Voltage to 133.0 using hmd/sensor/JuiceBox/Voltage/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Energy (Lifetime) to 4117615.0 using hmd/sensor/JuiceBox/Energy--Lifetime-/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Status to Charging using hmd/sensor/JuiceBox/Status/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Temperature to 69.8 using hmd/sensor/JuiceBox/Temperature/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Current Rating to 32.0 using hmd/sensor/JuiceBox/Current-Rating/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Frequency to 60.07 using hmd/sensor/JuiceBox/Frequency/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Energy (Session) to 1379.0 using hmd/sensor/JuiceBox/Energy--Session-/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Current to 12.0 using hmd/sensor/JuiceBox/Current/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Power to 1596.0 using hmd/sensor/JuiceBox/Power/state
juicepassproxy_tst    | 2024-05-15 09:42:10  INFO      [ha_mqtt_discoverable.sensors] Setting Data from JuiceBox to X:v09u,s001,F31,u00064112,V1330,L00004117615,S02,T21,M0024,C0024,m0032,t09,i45,e-0001,f6007,r99,b000,B0000000,P0,E0001379,A00120,p0995!ZHS: using hmd/sensor/JuiceBox/Data-from-JuiceBox/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Voltage to 133.4 using hmd/sensor/JuiceBox/Voltage/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Energy (Lifetime) to 4117618.0 using hmd/sensor/JuiceBox/Energy--Lifetime-/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Status to Plugged In using hmd/sensor/JuiceBox/Status/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Temperature to 69.8 using hmd/sensor/JuiceBox/Temperature/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Current Rating to 32.0 using hmd/sensor/JuiceBox/Current-Rating/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Frequency to 60.09 using hmd/sensor/JuiceBox/Frequency/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Power to 0.0 using hmd/sensor/JuiceBox/Power/state
juicepassproxy_tst    | 2024-05-15 09:42:16  INFO      [ha_mqtt_discoverable.sensors] Setting Data from JuiceBox to X:v09u,s001,F30,u00064118,V1334,L00004117618,S01,T21,M0024,C0024,m0032,t09,i46,e-0001,f6009,r99,b000,B0000000!YM7: using hmd/sensor/JuiceBox/Data-from-JuiceBox/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Voltage to 205.7 using hmd/sensor/JuiceBox/Voltage/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Energy (Lifetime) to 4117618.0 using hmd/sensor/JuiceBox/Energy--Lifetime-/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Status to Unplugged using hmd/sensor/JuiceBox/Status/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Temperature to 69.8 using hmd/sensor/JuiceBox/Temperature/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Current Rating to 32.0 using hmd/sensor/JuiceBox/Current-Rating/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Frequency to 60.09 using hmd/sensor/JuiceBox/Frequency/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Power to 0.0 using hmd/sensor/JuiceBox/Power/state
juicepassproxy_tst    | 2024-05-15 09:42:17  INFO      [ha_mqtt_discoverable.sensors] Setting Data from JuiceBox to X:v09u,s001,F10,u00064119,V2057,L00004117618,S00,T21,M0024,C0024,m0032,t09,i47,e-0001,f6009,r99,b000,B0000000!Z79: using hmd/sensor/JuiceBox/Data-from-JuiceBox/state

Will merge this PR into master.
It can be tested from the edge Docker tag until packaged into a release
For those previously testing with the async_beta Docker tag, please switch to edge

amazing work @Snuffy2, about to set up 0.3.0 locally!


Uploading mods

As Soldat 2 has composable mods that are packaged as json files, it would be useful to distribute them too on TMS2.
Currently one could upload a mod as a map, but I don't know if you or the community would approve of that.
Introducing a new category for mods might be useful.
Thanks for building & hosting tms <3

Hey, thanks for reaching out :)
Would it be appropriate for mods to always be uploaded with a screenshot?

I created a new gametype called MOD to be used for mods rather than maps for the time being.
It'd be more elegant to have a new part of the site dedicated to creating+browsing+downloading mods but this will need to come later.


As soon as i add the await decodeNotificationPayload(signedPayload) call in to my code, firebase functions wont deploy

its giving me the error Error: Functions codebase could not be analyzed successfully. It may have a syntax or runtime error as soon as i add this function to my codebase, any reasons why?

This sounds like an issue with Firebase functions. Can you specify which version of Node.js to use? Note that version 15.6.0 or later is required.

your probably right, im using v16, tried using 18 buts also failing

hey, @nicoladaniello  i have that line comented out for now, will check after lunch and tell you asap what i got


Module not Found

Following the README instructions but using my installed Renode on Ubuntu WSL, I am receiving the following error message:
ModuleNotFoundError: No module named 'Antmicro'
How to have this module?

Closing issue. I was using Portable Binary of Renode which is not supported.


Blazor layout update

Provide a blazor layout separation defending on authorisation.

I will implement the layout segregation for the authorized and the nonauthorized component of the service.

In the PR I will provide the mongo pagination for the students service: GET /students.

It an enscaled duplicate of #57.


Create an activity from code

This package seems to lack api for creation an activity from the code.
However, activity seems to be nice to display some automated logs.
Will you accept pull request with implementation of this or should a separate package be created?

Hi @derlaft
Yes, this is a nice to have feature (I thought I have added that, but seems I am wrong ;) )
So sure, we are open to accept pull request to add this feature.
(going to close this issue, just open a pull request when it is done)
Thank you.

Hi, @derlaft
from your implementation, how to pass the first parameter (*admin.Context) to CreateActivity
eg. How to create an activity when order state updated by code?


An overloaded function cannot call identical overloaded function with its parameters

Bug Report
🔎 Search Terms
no overload matches call  implementation succeed
🕗 Version & Regression Information
At least in 4.9 and it does occur in the current nightly
This is the behavior in every version I tried, and I reviewed the FAQ for entries.
⏯ Playground Link
Playground link with relevant code
💻 Code
function innerGet(): Record<string, string>;
function innerGet(id: string): string | null;
function innerGet(ids: string[]): Record<string, string | null>;
function innerGet(idOrIds?: string | string[]): Record<string, string | null> {

}

function outerGet(): Record<string, string>;
function outerGet(id: string): string | null;
function outerGet(ids: string[]): Record<string, string | null>;
function outerGet(idOrIds?: string | string[]): Record<string, string | null> {
  return innerGet(idOrIds);
  // No overload matches this call.
  // The call would have succeeded against this implementation, but implementation signatures of overloads are not externally visible.
}

🙁 Actual behavior
Trying to call a function with the same overloaded  parameters will result in a "no overload matches this call" error.
🙂 Expected behavior
There should be no error. It's pretty clear that the types are compatible.

Duplicate of https://github.com/microsoft/TypeScript/issues/39885 / https://github.com/microsoft/TypeScript/issues/1805.

Ok, thanks.  I never came across this in 3 years of using TS and I have been using plenty overloads. It's good to know that, better late then never but I wished the docs mentioned it. This is an issue that will not come up immediately, so there may be plenty of code using overloads that will need to be refactored upon realization that there is a major bug that has been marked as wontfix. I only found: "Always prefer parameters with union types instead of overloads when possible"  but I don't think it sufficiently warns against it. I would interpret it as "use union types if you don't need to narrow the return type based on the input arg".
And when I try to implement the same with the extends keyword, I find myself between the rock and a hard place. I run into a bug I encountered earlier #52051 . As a matter of fact, my workaround to that bug was using overloads :)
function get<Arg extends string | string[] | undefined>(
  idOrIds: Arg
) : Arg extends string ? string | null
  : Arg extends string[] ? Record<string, string | null>
  : Record<string, string> {
  if (typeof idOrIds === 'string') {
    return ''; // Not assignable
  }

}

function get2<Arg extends string | string[] | undefined>(
  idOrIds: Arg
) : Arg extends string ? string | null
  : Arg extends string[] ? Record<string, string | null>
  : Record<string, string> {
  if (typeof idOrIds === 'string') {
    return '' as ReturnType<typeof get2>; // Not going to pass either
  }

}

Playground
I guess I will use @ts-ignore, unless there's some way to override it with casting.


Sanitycheck should not write results into scripts/sanity_chk

Describe the bug
Not a bug really, has been this way since day 1. We need to stop writing into scripts/ and have all output in 1 place. Sanitycheck might be invoked on tests out of the tree and results should be written where the script is called, preferably in sanity-out
To Reproduce
Run sanitycheck and example scripts/sanity_chk
Expected behavior
Write results along side all other output
Impact
zephyr tree should be kept clean, test results should all be in 1 place.

Already addressed in recent sanitycheck overhall.


Synchronizing VLP16 without GPS

Hi there,
wasn't sure where to ask this question as it relates to the hardware side of things. We all know accurate time stamping is important but how do you go about time synching when you don't have a GPS (indoor operation) to provide the VLP16 with? Did anyone end up using the linux pps API to timestamp the lidar?
Thanks!

I haven't personally needed that level of precision, although in my case I was recording data and processing it offline - so the machine was operating at very low CPU load.
You're mainly going to see an issue if the timestamps of multiple sensors are very inconsistent or have high jitter.  This GENERALLY becomes less of a problem if you set up the velodyne node to deliver one point cloud message per packet (default is one per revolution or half revolution depending on if you enabled dual returns mode), and have Cartographer accumulate the scans.
At least in my experience, two VLP-16 units and a Microstrain IMU, with the velodyne node configured for npackets=1, gave great results when recorded on a ThinkPad E470 that wasn't doing anything else.
However, if using a SICK LMS100 with the default driver and the num_subdivisions_per_laser_scan option caused issues, because if there is enough timing jitter that the delta between two scan timestamps is ever less than (real scan period)*(num_subdivisions_per_laser_scan-1)/(num_subdivisions_per_laser_scan), you will get an immediate fatal error.


check blank credentials

I usually set the credentials from environment variables, that are blank strings when not set.

@elmendalerenda Thanks!


feat(datepicker): expose the validators that the datepicker uses internally as a public API

Reproduction
https://stackblitz.com/edit/angular-inex9i?file=app%2Fdatepicker-formats-example.ts
Steps to reproduce

Add a MatDatePicker to a component and bind it to a Reactive form control
Ensure you are reporting the built-in parse error (matDatepickerParse) using mat-error
Type in a bad date and see the parse error.
Call setValidators() on your reactive form control. It doesn't matter what is sent to setValidators
Enter invalid data and you will no longer see matDatepickerParse reported

Expected Behavior
Parsing errors after calling setValidators() should continue to report parsing errors
Actual Behavior
Parsing errors are no longer reported.
Additional Information
The provided DateAdapter (custom or not) is still used. However, since datepicker-input will provide a null value if the provided DateAdapter says the inputted date is invalid, you cannot workaround this issue with a custom validator.
Many complex forms may have conditional validation so using setValidators is completely expected.
Environment

Angular: 8.0.0
CDK/Material: 8.0.1
Browser(s): Google Chrome 73.0.3683.75 (Official Build) (64-bit)
Operating System Windows 10 64-bit

This is because the call to setValidators is overwriting the default validators that come with the mat-datepicker. You can avoid it by preserving the existing validator like this: https://stackblitz.com/edit/angular-inex9i-kwp4rc?file=app/datepicker-formats-example.ts
That said, it might be nice to also expose the validators that come with the mat-datepicker as a public API so that users can add them explicitly. (e.g. ctrl.setValidators(new DateInputParseValidator())). I'll leave this open as a feature request for adding them to the API

@mmalerba
Thank you for the quick response.
Unfortunately, the downside to using the existing validator function is that it may have conflicting validators within its composition. If a control is initially required but later becomes optional (the converse is also a common case), your validator function will include the required validator. Also, control.clearValidators() will cause it to become null. The only safe way to use this method is to ensure you don't set any validators on initialization, save the validator function for later retrieval and then apply initial validation requirements.
As of now, I can use the private API to get the parse validator of MatDatepickerInput using @ViewChild(ren). But now I am having to perform a view query just to set validators reliably. As long as MatDatepickerInput is coercing invalid values to null, I'm afraid it will be difficult to get this internal validator without a view query. This seems to be a natural consequence of implementing ControlValueAccessor and Validator together.
Ultimately, our team is leaning towards another route.
Thank you!

@mmalerba  @workcomped is there any way we can set DatePicker min,max validations on ts file. Currently, in case the component which has dates and implments controlValueAccessor and when we patch if from parent, the validation becomes valid even it is invalid, which is because the validations are coming from html which causes the delay.


Presenter updates

Whew!  This implements the new updates to Presenters:
class SolarSystem extends Presenter {

  setup () {
    // runs before `this.getModel` has executed. Useful for setting up a repo fork
  }

  ready () {
    // runs after setup, and the first model calculation
    console.log(this.model) // [{ id: "mercury" }, { id : "venus" } ...]
  }

  getModel () {
    return {
      planets: state => state.planets
    }
  }

  render () {
    const { planets } = this.model
    return <PlanetsView planets={planets} />
  }
}

Presenters that do not implement a model do not listen to repo changes.
view always calls React.createElement
render works as an other React component
Presenters have access to the current calculated model via this.model
The update hook has access to the latest model
Added ready, a hook that fires after setup that has access to the most recent model.
getModel can no longer return a function

Hopefully this makes Presenters feel a bit less magical, and more idiomatic to React.

Presenters that do not implement a model do not listen to repo changes.

I think this is important to call out in the documentation. It could also be clearer in the overview of Presenters that one of their primary purposes IS to listen to repo changes and re-render, and that implementing a getModel method is necessary to do this.
I'm sure there is one, but what's a use case for a Presenter without a getModel method?

@greypants To perform general prep work and to catch intents to perform general, UI related actions. For example, on RA we have a presenter that acts as a container for multiple views that display charts:
class StrategiesPresenter extends Presenter {

  setup (repo, { location }) {
    repo.push(getStrategies).onDone(() => {
      this.fetch(repo, location.query)
    })
  }

  update (repo, { location }) {
    if (location.query.selected !== this.props.location.query.selected ||
        location.query.region !== this.props.location.query.region) {
      this.fetch(repo, location.query)
    }
  }

  fetch (repo, { selected }) {
    const request = repo.prepare(getStrategySeries)
    const {strategies} = repo.state

    let picked = strategies.filter(s => s.Region === repo.state.ui.region.value)
                           .filter(s => within(selected, s.Key))

    picked.forEach(s => request(s.ID))
  }

}

@greypants We removed blanket passing of state from model because it's a dangerous default. It leads to a bunch of recursive re-renders across your UI because the Presenter wants to know everything.

Re-wording the overview could be something along the lines of:

The Presenter add-on makes it easier to keep application logic high within a component tree. It subscribes to state changes via a getModel method, designed specifically to extract and compute properties coming from a Microcosm instance. When state changes, model keys are efficiently sent down as props to child “passive view” React components.

@greypants I like that rewording a lot. FWIW, that presenter I shared is the specific reason I want to add getModel and the ready callback. It could be so much cleaner if had access to the model in update, which we'll have soon:
class StrategiesPresenter extends Presenter {

  getModel (props) {
    let selected = props.location.query.selected

    return {
      missing:  state => strategies.filter(s => s.Region === state.ui.region.value)
                                   .filter(s => within(selected, s.Key))
                                   .filter(s => !s.loading || s.dataPoints)
                                   .map(s => s.id)
    }
  }

  ready (repo) {
    repo.push(getStrategies)
    this.fetchMissingData()
  }

  update () {
    this.fetchMissingData()
  }

  fetchMissingData () {
    let fetch = this.repo.prepare(getDataPoints)
    this.model.missing.forEach(fetch)
  }

}

Once we land on an API for queries, that could eventually become:
class StrategiesPresenter extends Presenter {

  getModel (props, state, select) {
    let selected = props.location.query.selected

    let isSelected = select('strategies').join('region', 'ui.region.value').within('id', selected)
    let isMissing = isSelected.where({ loading: false, dataPoints: null }).pluck('id')

    return {
      missing: isMissing
    }
  }

  ready (repo) {
    repo.push(getStrategies)
    this.fetchMissingData()
  }

  update () {
    this.fetchMissingData()
  }

  fetchMissingData () {
    let fetch = this.repo.prepare(getDataPoints)
    this.model.missing.forEach(fetch)
  }

}


environment name auto-completion

If I have an environment called DJANGO_ZIPLINE and try to use the auto-completion with pew workon DJAN[tab], pew auto-completes properly. But if I do pew in DJAN[tab], no auto-completion happens. Just saying.

I guess this might affect multiple  shells... But just in case: are you
seeing this on bash, zsh, fish?
Sent from mobile. Please excuse my brevity.
On 16 Feb 2017 6:30 am, "Shadi Akiki"<EMAIL_ADDRESS>wrote:

If I have an environment called DJANGO_ZIPLINE and try to use the
auto-completion with pew workon DJAN[tab], pew auto-completes properly.
But if I do pew in DJAN[tab], no auto-completion happens. Just saying.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/berdario/pew/issues/136, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAt8w_6JHAVUtnaE19wkuE7VgdEPlSNNks5rc-0NgaJpZM4MCoq8
.

Bash


New package: POMDPTools v0.1.0

Registering package: POMDPTools
Repository: https://github.com/JuliaPOMDP/POMDPs.jl
Created by: @zsunberg
Version: v0.1.0
Commit: d259ab9cc4445e186f546bea601b30730b2f40bd
Reviewed by: @zsunberg
Reference: https://github.com/JuliaPOMDP/POMDPs.jl/commit/d259ab9cc4445e186f546bea601b30730b2f40bd#commitcomment-79096691
Description: MDPs and POMDPs in Julia - An interface for defining, solving, and simulating fully and partially observable Markov decision processes on discrete and continuous spaces.

[noblock] This combines several POMDP-related packages: https://github.com/JuliaPOMDP/POMDPs.jl/issues/290 fixing a long-running pain point for using POMDPs.jl
I need it to be merged by Sunday (preferably earlier) to get ready for a hackathon (https://sites.google.com/view/pomdps-hackathon) where we will fix some downstream issues.


JAWS virtualization shows UI elements instead of terminal content

Windows Terminal version
1.16.2642
Windows build number
No response
Other Software
JAWS
Steps to reproduce

Open terminal
press JAWS+ALT+W (note: JAWS = Caps lock key)

Expected Behavior
works in 1.15.2713
A window should pop up with the text from the terminal
Actual Behavior
The window shows all of the ui elements and no terminal content

Looked at this today. Tested out a few versions and found a lot of broken versions:

main (b7e537e5e) - broken
1.15.1862.0 - broken
1.15.2713.0 - broken
1.14.1432.0 - broken

I'll follow up with Alex Benoit (the one who reported these to me).

Alex said he is no longer experiencing this issue in...

stable Version: 1.15.3466.0
preview Version: 1.17.2852.0

Alex is also using JAWS Version 2023.2212.23 ILM

https://support.freedomscientific.com/Downloads/JAWS/JAWSWhatsNew?version=2022
2022.2110.60 literally didn't support the Terminal


Documentation should be more clear about how to create a server

Summary
I would like to see better documentation around how to use this package.
I would write the docs if you tell me how this works.
Motivation
It's not quite clear what kind of net.Conn you should pass into the Server function. Since this should be SCTP-over-UDP I expect it's the result of a net.ListenUDP. However, that conn will receive packets from all kinds of hosts, and I haven't found a way to isolate a single connection from that.
If you tell me how it works I'll add an explanation to the readme.

Hey @keks
Server unfortunately only does a single connection. You will need to multiplex yourself, I usually use the 5-Tuple. This could be a really great example also! I don't think we should add the de-multixplexing code to this package itself though. We might already have it in github.com/pion/transport
It would also be good to make examples/ping-pong just a simple go run... the complexity from the Makefile obscures this a bit.

Thanks for the quick response! Hm, I understand. Unfortunately I couldn't find anything in the transport repo.
I was hoping not having to write this myself, and would rather not commit to too much, since I need this for a recreational coding project :sweat_smile:. I'll give it a shot though. If anything comes out of this, I'd be happy to have it live in the pion code base, e.g. the transport repo. But let's not get ahead of ourselves :wink:

@keks awesome! If that is a big blocker I am sure I could code it up quickly. I would rather see you using Pion, then we get feedback/bug reports etc..

Sure, if that is quick to do for you, please go ahead! I undestand you'd rather maintain your own code :)

I hear you @keks. Current pion/sctp does not provide you with listen/connect semantics. I would like get #74 resolved some time soon.


Improve 'Setup' documentation

The documentation to begin working through the Swift exercises could use some clarification. It's a multi-step process to integrate the test file with a new project, solve the exercise, and submit correctly.

Create a new project with Xcode, in the same folder as the Exercism test file:

Drag the Exercism test file into the <project_name>Tests group, and add the line @testable import <project_name>  on the second line of the Exercism test file:

Create the working file/class, and save in the same folder as the Exercism test file: [see first image]

When you are ready to submit, do so from the folder that contains the working file and the Exercism test file

Nice suggestions!
Do you mind summiting an update PR to this doc ? https://github.com/exercism/xswift/blob/master/docs/TESTS.md

@masters3d All set! https://github.com/exercism/xswift/pull/120

Looks good! thanks


use the materialstore-0.16.6 where the JobNameNotFoundException was added

Use it
https://github.com/kazurayam/materialstore/releases/tag/0.16.6

done at v0.9.6-SNAPSHOT


Czech translation

Hey, I've translated the game to Czech language. Some of the translations have been slightly altered in Czech so that they accound for language-specific semantics and make more sense.

Country code updated ;)


NIO just updated their package manifest to 5.6 and it started erroring when building the tests

Description
@tomerd made the change in apple/swift-nio#2235 and that now causes an error on linux and Android when compiling LinuxMain.swift. Workarounds are to revert that pull or add --enable-test-discovery, which avoids compiling LinuxMain.swift.
Expected behavior
The NIO tests to build and run.
Actual behavior
This compilation error:
/home/butta/swift-nio/Tests/LinuxMain.swift:146:1: error: expressions are not allowed at the top level
(LinuxMainRunnerImpl() as LinuxMainRunner).run()

Steps to reproduce

Check out swift-nio.
Build the tests with swift test.

Swift Package Manager version/commit hash
5.6.2 and latest 5.7 and trunk snapshots
Swift & OS version (output of swift --version && uname -a)
Swift 5.6.2/5.7/5.8 running on Ubuntu 20.04 x86_64 or Android 12 AArch64

That's expected since we were assuming that any non-main.swift file is always using @main when using a 5.6+ tools-versions -- https://github.com/apple/swift-package-manager/pull/5688 improves this behavior already, so I don't think there is more to do for SwiftPM here.

https://github.com/apple/swift-package-manager/pull/5688 should fix it on 5.7 and main

Alright, so people using 5.6 who set swift-tools-version to 5.6 are expected to patch that NIO manifest like this?
diff --git a/Tests/LinuxMain.swift b/Tests/LinuxMain.swift
index eacd4b02..a6a92e48 100644
--- a/Tests/LinuxMain.swift
+++ b/Tests/LinuxMain.swift
@@ -40,10 +40,9 @@ import XCTest
 // without the compiler noticing that we're calling a deprecated function.
 // This hack exists so we can deprecate individual tests which test deprecated functionality without
 // getting a compiler warning...
-protocol LinuxMainRunner { func run() }
-class LinuxMainRunnerImpl: LinuxMainRunner {
+@main class LinuxMainRunnerImpl {
    @available(*, deprecated, message: "not actually deprecated. Just deprecated to allow deprecated tests (which test deprecated functionality) without warnings")
-   func run() {
+   static func main() {
        XCTMain([
              testCase(AcceptBackoffHandlerTest.allTests),
              testCase(AdaptiveRecvByteBufferAllocatorTest.allTests),
@@ -144,5 +143,4 @@ class LinuxMainRunnerImpl: LinuxMainRunner {
         ])
     }
 }
-(LinuxMainRunnerImpl() as LinuxMainRunner).run()
 #endif

That patch works with both 5.6.2 and the latest Aug. 9 trunk snapshot build for linux, but I think you should probably get #5687 into a 5.6 patch release, or this @main requirement is going to break many CIs that test older Swift versions such as 5.6.
As I just noted on that NIO pull, #5687 does fix this issue, but 5.6 is currently not patched with it.

this problem was introduced in 5.5 actually, and 5.6 also suffers from it. SwiftNIO adopting 5.6 brings to to bear because it also using LinuxMain.swift, which is less common at this point. I think the workaround for folks that run swift-nio tests  is to pass --enable-test-discovery not change LinuxMain.swift

this problem was introduced in 5.5 actually, and 5.6 also suffers from it.

You're right, I just tried it with Swift 5.5.3 and it errors the same.

SwiftNIO still supports 5.4 and that does not have @main

I think it does, but don't know if this patch would work with it.
5.5 having this issue too definitely makes fixing 5.6 less important, but would be nice to get #5687 into a 5.6 patch release. If that's too late because of the impending 5.7, I understand.

Hmm, the fix was already reverted on 5.7.0, #5684, hope it makes it into 5.7.1.


Auto Refresh PowerBI

Feature Request
"You will need to refresh the Power BI dashboard every time to see the new results" - Is there any way that this can be automated?
Additional information
I need to activate the refresh button to see the new information from the .json file but currently it is done manually.  I was thinking of even closing PowerBI and starting it up again but I still have to manually refresh
Thanks

Unfortunately not - Power Bi Desktop is a designer - you would have to publish the report to a PowerBi Server or to the cloud to get auto or scheduled refreshes


feat(popup/Home): new UI for home screen

Context

Part of https://github.com/interledger/web-monetization-extension/issues/569
Part of https://github.com/interledger/web-monetization-extension/issues/568

Changes proposed in this pull request

Looks good. One minor detail the send button doesn't appear to be disabled when amount is not entered or not valid ( let's make sure value is more than 0). This would be consistent with the validation we're doing for the connect button on the setup screen as well


MAINT: Removed specfun_lib and updated specfun_wrappers

This is the next PR in the chain for moving specfun into a C++ header library. This specifically removes the previous specfun C functions, and the static library (specfun_lib) those were compiled into. It also turns specfun_wrappers.c into specfun_wrappers.cpp, using our new header library directly.
From what I can see, it appears the functions in specfun_wrappers.h are the functions that are being turned into ufuncs. These functions also add additional behaviour and error checking, for instance setting the right NaN values where appropriate. So I think these functions also need to go into the special header library.
A few of them appear to be using PyMem_Malloc. This doesn't appear to be for any reason other than to allocate temporary space, so I intend to replace that with malloc. Then later we'll sort out the dynamic memory allocation all in go. Someone should shout if there is a fundamental reason PyMem_Malloc is being used here.
cc @steppi this is ready for review

The ones in specfun_wrappers.h are the ones that are indeed ufuncs and the ones on cython wrappers are the public python api ones. this happens in that cryptic generate_pyx.py file. However I think now you are exporting all symbols currently, but the ones that were in specfun.c  should go into detail namespace.
Also we have to keep the license parts of the deleted files in the new cpp files with filenames changed.

@izaid, I fixed the windows failures due to missing math constants in my open hyp2f1 PR by moving where they are conditionally defined in config.h. See here: https://github.com/scipy/scipy/pull/20089/commits/23ad2a0523d0e5fcd82b87a11c8e1afa25477d10.

@steppi Done.

Ah I see, but the problem is math constants not being defined in specfun_wrappers.cpp and special/config.h isn't included there. Let's just put what's now in specfun_wrappers.h into the header only library like you suggested. Then the math constants can defined by including config.h. I agree with @ilayn that what was once in specfun.c should go in the detail namespace.

I think the way to structure it would be
specfun/specfun.h has the wrappers that actually be come ufuncs
specfun/detail/_specfun.h has what used to be in specfun.c.

@steppi Ok, cool. Should I do this as part of this PR?

Alright, so I've moved all the wrappers into specfun now. It should be fine, but I do see there is an error we've seen before: "dereferencing type-punned pointer will break strict-aliasing rules". This particularly happens when we use reinterpret_cast to and from a npy_cdouble and a std::complex<double>.
I remember talking about this before with @steppi and @lucascolley. Why are we preventing this? I appreciate that if we are only passing in a single value, it's not a big deal to copy-by-value. But if we have a whole array of npy_cdouble that we want to operate on as an array of std::complex<double>, reinterpret_cast is the way to do it. I would normally change the compiler flags to stop the error and allow this behaviour. Is there really no way to make this work in a way consistent with SciPy?

Why are we preventing this?

IIRC, what we want is std::bit_cast, but that arrived in C++20, and we currently support C++17.

Thanks @lucascolley! I think bit_cast would work, but for a single value only. Not for an array of N objects at a memory address.
Perhaps the real question is why aren't we compiling with -fno-strict-aliasing?

Ok, I pushed some maybe fixes for this. Let's see if converting the values, but casting the pointers, is enough.

Do you need to use C++ constructs here? I think the previous wrapper behavior was good enough with simple flat memory. If I remember correctly reinterpret_cast only works between void pointers.
I would prefer turning on all errors and warnings so that we don't use something opinionated in case this goes into another code with conflicting flags which is my personal experience with all C++ code I've used so far.

@ilayn In end, I didn't need it actually. I'm still not a fan of not being able to reinterpret_cast, but I accept it.
@steppi Think we're good now and ready for the review.

Have just pushed all the changes @steppi  requested.

Ah no, please go ahead with your judgement, I don't have nearly enough experience with the C++ casting rules.
But I do know that it is a major criticism to the standard when and how the casting/aliasing is made strict or not. For example for reinterpret_cast also works for integral types of some sort, (sometimes work sometimes does not) but in this case type T and type S has to be similar (another unnecessarily complicated presentation).
Just wanted to point out that in C++ these seemingly innocent steps are exceptionally rich with footguns and hence we should be very defensive of letting things pass with flags in my opinion.
Otherwise no objections from my side.

Thanks @izaid, looks good.

Just wanted to point out that in C++ these seemingly innocent steps are exceptionally rich with footguns and hence we should be very defensive of letting things pass with flags in my opinion.

Yeah, I agree @ilayn. It's good things are working now without any warnings.


Enable drag_dest_set()

Need to add DestDefaults, TargetEntry, and gdk::DragAction to the Gir generation script. I couldn't figure out why adding DragAction to gdks Gir.toml didn't generate anything, so I'm posting this issue instead of a general PR.

With DragAction is no problem, next diff will generate it.
Problem with TargetEntry:

It almost only one class that used with const* in sys, and your ToGlibPrt implementation for Boxed<ffi::GtkTargetEntry> defined for mut*, so many build error appears.
It don't have usable function or get/setters and gir currently don't support direct access to record fields.
(May be this record really don't need those and new is enough to use)

--- a/Gir.toml
+++ b/Gir.toml
@@ -9,6 +9,7 @@ generate_safety_asserts = true

 generate = [
     "Gdk.CursorType",
+    "Gdk.DragAction",
     "Gdk.GLError",
     "Gdk.Gravity",
     "Gdk.ModifierIntent",

So it sounds like there needs to be a manual implementation of GtkTargetEntry for this functionality to be exposed? Anyone interested in tackling that?

Why not doing it? Might be nice for you to discover a bit how it works under the hood. :p

As of gtk-rs/gdk#144 only a manual implementation of TargetEntry is necessary to get drag_source and drag_dest functions working.

IMHO as with GdkRGBA better almost ignore free and copy functions and declare normal rust struct with ToGlibPtr ..


[BUG] - Support for non-latin characters does not work

UE Version:
E.g. UE 5.2
Frontend Version:
E.g. UE5.4-0.0.4
Problem component
FrontEnd
E.g. Signalling Server, Frontend, Pixel Streaming C++ plugin
Description
I created a EditableText in UE5.2. When I input Chinese from pixelstreaming, it dose not fire a CompositionStart event.
I found a fix at here: https://github.com/EpicGames/PixelStreamingInfrastructure/pull/452.
But it still dose not work.
Steps to Reproduce:

create a EditableText in UE
open pixelstreaming
try to input some Chinese from frontEnd to the EditableText
ascii code is send directly to ue, not Chinese

Expected behavior

Chinese input can fire CompositionStart | Update | End.

Screenshots
If applicable, add screenshots to help explain your problem.
I added this code to player.html, then it act like this:
work
1 i select EditableText in UE
2 active the input.example bellow
3 then it works fine. The Chinese shown on both EditableText and input.example bellow

not work
4 when i click on the other place except input.example
5 then the actived EditableText does not fire Composition Event any more.

          First select textbox, then to open IME:

on macOS type option + `

on Windows type windows + .

        <input type="text" id="example" name="example" />

        Event log:
        <textarea
          readonly
          class="event-log-contents"
          rows="8"
          cols="25"
          id="eventLog"></textarea>
        <button class="clear-log">Clear</button>

Platform (please complete the following information):

OS: macOS
Browser + version:  chrome 123.0.6312.59
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Any more information?

CC @DenisTensorWorks We will need an internal ticket for this one.
CC @Belchy06 @mcottontensor

No... bad bot, we do want this to stay open.

Sounds related: https://github.com/EpicGamesExt/PixelStreamingInfrastructure/issues/120

Sounds related: #120

Agreed.


juliaboxpkgdist:v0.3.12 to match current juliabox.com

Could juliaboxpkgdist:v0.3.12 be updated to match what's currently available on juliabox.com?
Probably irrelevant info, but it's currently
0.3.12
0.4.6
0.5.0-dev
on juliabox.com its
0.3.12
0.4.7
0.5.0
0.6.0-dev

The Dockerfile is already same as what is live on JuliaBox. It is tagged latest now (will likely move to a date based tag next) to indicate that it has the latest patch versions.
A ready image with this tag is not available on dockerhub though and you may have to build it locally, see https://groups.google.com/d/msg/julia-box/a7vmohiSdX4/0AxJoMpDAwAJ

Done and tagged
https://hub.docker.com/r/ianshmean/juliaboxpkgdist/


Bring under the dev-tools umbrella

Hey, we discussed making semverver a tool under the dev-tools team. I hope you think this is still a good idea! I can't remember exactly what we discussed as the next steps to do that. Here are a few things I can think of:

[ ] get feedback from @killercup and @oli-obk (did you two get a chance to try this out?)
[ ] move to rust-lang-nursery
[ ] add a description and links to https://github.com/nrc/dev-tools-team/blob/master/overview.md

I tried it out on a bunch of crates of different sizes. While it has some kinks to be worked out, I think it is already useful as an initial decision helper for the version bump.

Yes, I still believe this to be a good idea - to (hopefully) get more visible, which would speed up bug discovery and fixes a bit. When we decide to do this, I'll open a PR against the docs.
Other than that, I think the next reasonable step would be to discuss some of the bug-issues filed here, since I wasn't able to determine the exact cause for all of them yet.

I think it's safe to close this now. Further feedback should get it's own issue. :)


uers/v-jandrew/extension-docs-revision-writers-pass

date

Learn Build status updates of commit 21acf99:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit d2c943e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit cc75b39:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit a99394b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 38e6441:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 6c979f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/released-features.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/roadmap.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit b816f49:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:warning:Warning
View
Details

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/released-features.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/roadmap.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md

Line 8, Column 10: [Warning: ms-date-invalid - See documentation] Invalid date format for 'ms.date': '11/207/2022'. Must be a date in format M/D/YYYY, no more than 30 days from today.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 39659c2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/released-features.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/roadmap.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 714c268:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/developer-policies.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/released-features.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/roadmap.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit f47b733:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/developer-policies.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/released-features.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/whats-new/roadmap.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Command for getting initial rancher password doesn't work

Seen on rancher/rancher:master-head 94bca99
Related to https://github.com/rancher/dashboard/issues/3574
The command for getting initial rancher password from Welcome to Rancher page doesn't work:
> kubectl get secret --namespace cattle-system bootstrap-secret -o go-template={{.data.bootstrapPassword|base64decode}}{{"\n"}}
If 'base64decode}}{{
}}' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf base64decode}}{{
}}
Error from server (NotFound): secrets "bootstrap-secret" not found

I identified two problems so far:

kubectl command triggered from bash complains that base64decode}}{{ }} command doesn't exist - reason is that pipe | is not escaped:
secret bootstrap-secret in cattle-system ns doesn't exist (rancher deployed over helm)

The go-template should be single-quoted, it got lost somewhere.
That's the namespace & name in the helm notes and what's in the chart..  You'd need to be using the new version of the chart from master, not 'rancher-latest' or similar.
If the notes don't look like this (helm get notes -n cattle-system rancher) you don't have the updated chart which generates a secret.

How can I get the new version of the chart from master? I'm afraid we have to wait for 2.6 RC, or?

Waiting for an RC from master

This is fixed in rancher/rancher:2.6.0-rc1 deployed by helm. The secret exists and the offered kubectl command returns a valid rancher password. Also the command is escaped correctly now.

Close.


Add serialization test of address space schema

Add resource limits and resource usage by plans to output
Add available authentication services to output
Remove undocumented schema endpoint
Rewrite systemtest to check official schema endpoint

Fixes #2461

@enmasse-ci run tests testcase=ApiServerTest


ARROW-12851: [Go][Parquet] Add Golang Parquet encoding package

Adding the implementation of encoding types of data for Parquet including Plain, RLE, Dictionary, Delta Byte Array, Delta Packing types. It also includes hashing implementation for more efficient hash tables than using go's std map implementation as shown in the benchmarks included in the test files which do benchmark comparisons between a go-map based implementation and the hash table implementation that I ported from the C++
In addition, while adding some test cases I discovered that apparently the -force-vector-width=32 argument on the asm generation was causing segfaults on the encoding tests, so let's let LLVM make it's own choice about the vector width and interleaving.

@emkornfield @sbinet @nickpoorman And here we go with the next chunk! time for the implementation of the encoding types, we're in the home stretch now, i think i've only got about 2 or 3 more of these: metadata, file reading/writing, and integration with arrow

@zeroshade apologies this is likely going to be another rough week in terms of availability to review.  If you don't hear anything by next tuesday please ping again.

@emkornfield Pinging for tuesday update :smiley:

Starting to take a look.

@zeroshade still working my way through but at least I've started, will try to continue to review over the next few days.

bump @emkornfield @fsaintjacques
thanks!

@zeroshade still making my way through.  I was wondering if you would be open to limiting this PR to the interfaces and the encoders already reviewed and we can have follow-up PRs for the remaining decoders?

@emkornfield I'll see if i can easily remove the files for the remaining decoders, should i consider as "reviewed" any of the encoders/decoders you've commented on? Or were there any you reviewed but didn't leave comments on?

@emkornfield so because of the way things are developed and interdependent, the most i'm able to remove while still being compileable in this PR is the unit tests, the level encoder, the memo table code and the hashing stuff for those memo tables.
All in all 13 files

@emkornfield so because of the way things are developed and interdependent, the most i'm able to remove while still being compileable in this PR is the unit tests, the level encoder, the memo table code and the hashing stuff for those memo tables. All in all 13 files

if you don't mind that would be great, thats ~1/3 of the PR

@emkornfield Done! Hope that helps

@emkornfield bump

Just bumping this again in the hopes for more reviews so i can get this merged
@emkornfield @sbinet @fsaintjacques @nickpoorman

Sorry will try to finish it off this week.  Please ping me again if you don't hear back anything by Wednesday morning.

@emkornfield Pinging as requested since I didn't hear anything by wednesday :)

Thanks for the ping, sorry this week went a  bit haywire, going to review some more now.

@emkornfield Just giving another poke here for any other feedback, thanks!

I'll double check but I think this is ok to merge, will try to do so this evening.

@emkornfield  just poking for update to get this merged so i can put the other half up

Sorry, for the delay merging now.


Array DataType Should be Saved as an Array

Expected behavior
Array datatype should be saved as an array
Actual behavior
Array datatype saved as an object
Steps to reproduce the behavior
Just make a array datatype and import then export it again.

Firebase and Firestore actually store arrays as objects with integers as key names (see https://firebase.googleblog.com/2014/04/best-practices-arrays-in-firebase.html). So when they get exported, they show up as an object, but they should show up as an array after getting imported again.

Actually, I'm having second thoughts on this. I'm going to do some more investigating for Firestore specifically

@jefrydco Thanks for pointing this out. I had incorrectly assumed that Firstore worked the same way as Firebase since my code ended up treating arrays as numeric-key-based objects. Check out v.0.8.1 for the fix. You'll need to export with that version to get the arrays in the output, then import again.

@jloosli You're welcome, thanks for fixing this issue. Ok, fortunately my database isn't big so I've done it manually. :smile:


Chore/config codecov

Codecov Report

Merging #41 (85dcee2) into main (1f17d9b) will increase coverage by 3.27%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   74.10%   77.38%   +3.27%
==========================================
  Files           3        3
  Lines         336      336
==========================================
+ Hits          249      260      +11
+ Misses         75       62      -13
- Partials       12       14       +2

see 1 file with indirect coverage changes


Add skill chain to embed skills

Have a way to show a skill chain embed within the tooltip. For example, auto-attacks tend to have a chain and it would be nice if you could display them one below another starting with 1st skill. Maybe a "gw2armory-skill-chain" with a list of ids?

@valento92 this is more for just auto attack skills right?
for example when you keep using the skill it changes to another?

Not only autoattacks, Temporal Curtain is a mesmer focus skill which has a sequence. So sequence skills join the team.


Add files via upload

https://www.hewlett-woodmere.net/Domain/497

@dciobanu2007 Pull request merged. Thank you!


genpass: 0.5.1 -> 0.5.14

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.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.

Heya, genpass author here :)
Glad you're using my pet project !

upstream has indeed moved as part of my journey to selfhost all of my services, haven't got to updating nixos package yet
there's no new features or bugfixes in the new versions, it's mostly dependency updates and such plus some experiments that I don't feel constitute a stable release (hence it's still not 1.0)
I did not update nixos version of genpass, as I wanted to finish making some changes, like

stabilise the CI to make sure all versions in nixos build and work as expected
there were some changes to the cli flags and I am debating if I like them or not

So kinda torn here, on one hand don't want to discourage contributions, on the other hand don't want to push half-baked software into nixos :)

So kinda torn here, on one hand don't want to discourage contributions, on the other hand don't want to push half-baked software into nixos :)

I will mark this PR as draft so people can see your comment. Looking forward to the next available version.


aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://<IP_ADDRESS>:8020;

Hi
I am running two Aries agents using docker. I am working on the Bedrock network established by the bedrock consortium. I trying to establish a connection between these two agents. I am getting the error in the subject when I try to get the connection_id from the event output on the terminal. My agents are being started using the following two commands
sudo PORTS="8030:8030 8031:8031" scripts/run_docker start -l test.agent --inbound-transport http <IP_ADDRESS> 8030 --outbound-transport http --endpoint http://<IP_ADDRESS>:8030 --wallet-type indy --wallet-name test_wallet --wallet-key test_wallet123 --ledger-pool-name bbutestnet --genesis-url https://raw.githubusercontent.com/fwbehemoth/behemoth-lair/main/pool_transactions_genesis --admin <IP_ADDRESS> 8031 --admin-insecure-mode --auto-provision --auto-accept-invites --auto-accept-requests --auto-ping-connection --auto-respond-credential-proposal --auto-respond-credential-offer --auto-respond-credential-request --auto-store-credential
and
sudo PORTS="8020:8020 8021:8021" scripts/run_docker start -l udacity.agent --inbound-transport http <IP_ADDRESS> 8020 --outbound-transport http --endpoint http://<IP_ADDRESS>:8020 --wallet-type indy --wallet-name test_wallet1 --wallet-key test_wallet1 --ledger-pool-name bbutestnet --genesis-url https://raw.githubusercontent.com/fwbehemoth/behemoth-lair/main/pool_transactions_genesis --admin <IP_ADDRESS> 8021 --admin-insecure-mode --auto-provision --auto-accept-invites --auto-accept-requests --auto-ping-connection --auto-respond-credential-proposal --auto-respond-credential-offer --auto-respond-credential-request --auto-store-credential
I am able to open the swagger-ui at localhost:8021 and localhost:8031. I created a connection invitation from "udacity.agent" and then received it on "test.agent".
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 798, in create_connection
raise exceptions[0]
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 785, in create_connection
yield from self.sock_connect(sock, address)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 439, in sock_connect
return (yield from fut)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 327, in iter
yield self  # This tells Task to wait for completion.
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 469, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 8020)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 182, in _step
result = coro.throw(exc)
File "/home/indy/aries_cloudagent/transport/outbound/http.py", line 82, in handle_message
endpoint, data=payload, headers=headers
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 536, in _request
req, traces=traces, timeout=real_timeout
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1187, in _create_direct_connection
client_error=client_error,
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:8020 ssl:default [Connect call failed ('<IP_ADDRESS>', 8020)]
2022-05-23 22:16:48,645 aries_cloudagent.transport.outbound.manager ERROR Outbound message could not be delivered to http://<IP_ADDRESS>:8020
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 798, in create_connection
raise exceptions[0]
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 785, in create_connection
yield from self.sock_connect(sock, address)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 439, in sock_connect
return (yield from fut)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 327, in iter
yield self  # This tells Task to wait for completion.
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 469, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 8020)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 182, in _step
result = coro.throw(exc)
File "/home/indy/aries_cloudagent/transport/outbound/http.py", line 82, in handle_message
endpoint, data=payload, headers=headers
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 536, in _request
req, traces=traces, timeout=real_timeout
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1187, in _create_direct_connection
client_error=client_error,
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:8020 ssl:default [Connect call failed ('<IP_ADDRESS>', 8020)]
2022-05-23 22:16:51,262 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://<IP_ADDRESS>:8020; Error: (<class 'aiohttp.client_exceptions.ClientConnectorError'>, ClientConnectorError(ConnectionKey(host='<IP_ADDRESS>', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('<IP_ADDRESS>', 8020)")), <traceback object at 0x7fc9c9ea0a88>); Re-queue failed message ...
2022-05-23 22:17:01,266 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://<IP_ADDRESS>:8020; Error: (<class 'aiohttp.client_exceptions.ClientConnectorError'>, ClientConnectorError(ConnectionKey(host='<IP_ADDRESS>', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('<IP_ADDRESS>', 8020)")), <traceback object at 0x7fc9c9eaa0c8>); Re-queue failed message ...
2022-05-23 22:17:11,276 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://<IP_ADDRESS>:8020; Error: (<class 'aiohttp.client_exceptions.ClientConnectorError'>, ClientConnectorError(ConnectionKey(host='<IP_ADDRESS>', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('<IP_ADDRESS>', 8020)")), <traceback object at 0x7fc9c9eaa748>); Re-queue failed message ...
2022-05-23 22:17:21,294 aries_cloudagent.transport.outbound.manager ERROR >>> Outbound message failed to deliver, NOT Re-queued.
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 798, in create_connection
raise exceptions[0]
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 785, in create_connection
yield from self.sock_connect(sock, address)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 439, in sock_connect
return (yield from fut)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 327, in iter
yield self  # This tells Task to wait for completion.
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 469, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 8020)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 182, in _step
result = coro.throw(exc)
File "/home/indy/aries_cloudagent/transport/outbound/http.py", line 82, in handle_message
endpoint, data=payload, headers=headers
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 536, in _request
req, traces=traces, timeout=real_timeout
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1187, in _create_direct_connection
client_error=client_error,
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:8020 ssl:default [Connect call failed ('<IP_ADDRESS>', 8020)]
2022-05-23 22:17:21,294 aries_cloudagent.transport.outbound.manager ERROR Outbound message could not be delivered to http://<IP_ADDRESS>:8020
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 986, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 798, in create_connection
raise exceptions[0]
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/base_events.py", line 785, in create_connection
yield from self.sock_connect(sock, address)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 439, in sock_connect
return (yield from fut)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 327, in iter
yield self  # This tells Task to wait for completion.
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 250, in _wakeup
future.result()
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/futures.py", line 243, in result
raise self._exception
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/selector_events.py", line 469, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 8020)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/asyncio/tasks.py", line 182, in _step
result = coro.throw(exc)
File "/home/indy/aries_cloudagent/transport/outbound/http.py", line 82, in handle_message
endpoint, data=payload, headers=headers
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 1138, in aenter
self._resp = await self._coro
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/client.py", line 536, in _request
req, traces=traces, timeout=real_timeout
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 542, in connect
proto = await self._create_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 907, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
raise last_exc
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 1187, in _create_direct_connection
client_error=client_error,
File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aiohttp/connector.py", line 992, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:8020 ssl:default [Connect call failed ('<IP_ADDRESS>', 8020)]
Any help on this is much appreciated.

Your endpoints are incorrect - --endpoint http://<IP_ADDRESS>:8030
The IP (or host name) in this endpoint needs to be something accessible from the other agent(s), since you are running the agents in docker containers you need to use the internal docker IP, or (one some machines) host.docker.internal
Also since you have all the auto flags set, you don't need to manually accept the invite, it will happen automatically

I changed the --endpoint "http://host.docker.internal:8020" and --endpoint "http://host.docker.internal:8030" for the two agents respectively. Now I am getting the following error on the udacity.agent

Do you still have the --auto flags in your aca-py startup?  If so then your agents will automatically respond to invitations and connection requests and you will get errors when you try to call the endpoints
You can check the connections with the GET /connections endpoint to check the connection status.  In the above error, it is looking for a connection with state invitation but if you have the --auto flags enabled it will likely be in state active or connected

I removed all the --auto flags, here are the latest commands I used:
sudo PORTS="8020:8020 8021:8021" scripts/run_docker start -l udacity.agent --inbound-transport http <IP_ADDRESS> 8020 --outbound-transport http --endpoint "http://host.docker.internal:8020" --wallet-type indy --wallet-name "test_wallet1" --wallet-key "test_wallet1" --ledger-pool-name bbutestnet --genesis-url https://raw.githubusercontent.com/fwbehemoth/behemoth-lair/main/pool_transactions_genesis --admin <IP_ADDRESS> 8021 --admin-insecure-mode --auto-provision --auto-ping-connection
and
sudo PORTS="8030:8030 8031:8031" scripts/run_docker start -l test.agent --inbound-transport http <IP_ADDRESS> 8030 --outbound-transport http --endpoint "http://host.docker.internal:8030" --wallet-type indy --wallet-name "test_wallet" --wallet-key "test_wallet123" --ledger-pool-name bbutestnet --genesis-url https://raw.githubusercontent.com/fwbehemoth/behemoth-lair/main/pool_transactions_genesis --admin <IP_ADDRESS> 8031 --admin-insecure-mode --auto-provision --auto-ping-connection
Next, I created an invitation on the udacity.agent as shown below

I received this on test.agent using the "invitation" object from above on the test.agent "post - connections/receive-invitation". The response for this as shown below

Then, I accepted this invitation using the "post connections/{conn_id}/accept-invitation on test.agent. I get the below response for this. The connection_id = 4720aa24-abb5-464e-924b-bb2dcb692eb0:

After the above step, I was hoping to see an event on the udacity.agent terminal with a new connection_id. But nothing shows up on this terminal as shown below. I was hoping to use a connection_id from the terminal to accept the invitation on udacity.agent swagger.

I am stuck at this step. How do I make the udacity.agent now accept the invitation from test.agent?
On the udacity.agent under the "Get Connections", I only see the original invitation sent to test.agent as shown below.

Please review and let me know what am I missing here?

Are you running on Linux?  You may need to use something other than host.docker.internal
See:  https://stackoverflow.com/questions/48546124/what-is-linux-equivalent-of-host-docker-internal
Otherwise can you post the log from the test.agent window?

I am using WSL 2 to use ubuntu on my windows machine. I have docker desktop installed. My ubuntu version is 20.04.2 LTS. I will read the link you sent and see if I need to change host.docker.internal to something else.
In the mean time here is the image of the test.agent terminal. Nothing gets logged on this terminal so far.

Also what parameter should I use with my command to show "events" on my agent terminals? In the Hyperledger Aries open API lab with the demo "faber" and "alice", the --events flag was used. But that does not appear to be a parameter with aca-py.

if you run aca-py directly it doesn't support the same params as the alice/faber demo
You can get more log info using the --log-level info parameter (or --log-level debug)

I used the docker IP of <IP_ADDRESS> instead of host.docker.internal. I also used the --log-level ingo parameter with both the agents. At the last step when I accept the invitation on test.agent, I get the warning shown below on the udacity.agent. It says "No correspoding DID found.....". Is the problem with the DID of the test.agent?

That just means the connection is using private DIDs (I think), which is the default.  Not sure why those messages are tagged as warnings

@ianco, I finally figured out how to send messages across various agents. I am running Docker Desktop on windows with WSL 2 and Ubuntu. The following three endpoints are ok to use in my case for the --endpoint parameter
http://host.docker.internal OR
IP address of my ubuntu terminal obtained by running command - hostname -I  OR
IP address of my Docker Desktop, found it in the docker settings.
The command I ended up using was
sudo PORTS="8040:8040 8041:8041" scripts/run_docker start -l test2.agent --inbound-transport http <IP_ADDRESS> 8040 --outbound-transport http --endpoint "http://host.docker.internal:8040" --wallet-type indy --wallet-name "test_wallet2" --wallet-key "test_wallet2" --ledger-pool-name bbutestnet --genesis-url https://raw.githubusercontent.com/fwbehemoth/behemoth-lair/main/pool_transactions_genesis --admin <IP_ADDRESS> 8041 --admin-insecure-mode --auto-provision --auto-ping-connection --log-level info
The main error I was making before was that once an agent creates a new connection, and the invitation is received and accepted by another agent. The original agent can complete this connection by using the "POST /connections/{conn_id}/accept-request" instead of using the "POST /connections/{conn_id}/accept-invitation". I was using the /accept-invitation endpoint before and that was the issue.

@grajnikanth  good news thanks for the update!

In case someone has this problem with docker in Linux, instead of using --endpoint "http://host.docker.internal:8040", try
--endpoint "http://<IP_ADDRESS>:8040"

This is the default gateway if your container uses a bridge network. This solved my problem.


s390x images?

Hi,
This is to query for the support for s390x architecture.
s390x is left out from the grafana Makefile (https://github.com/kubernetes/heapster/blob/master/grafana/Makefile#L30). Why is that? Is this related to the already merged https://github.com/kubernetes/autoscaler/pull/182 on Mutiarch addon-resizer image. If so, should we re-enable s390x pushes?
Thanks

As @luxas suggested, @ixdy and @mkumatag might be able to help. Thanks￼￼


Could you please provide video retrieval evaluation code?

Hi! Thanks for your excellent work and open source your code!
Could you please provide video retrieval evaluation code?

Sure, I have uploaded the retrieval code at main_retrieve.py whereas it may exist some ad-hoc bugs. Please check it over before running it.

Thasnks!


A problem

The task list statements can not be resolved!
The example codes:

[ ] It is an unfinished task
[x] It is a finished task

However, the OmniMarkupPreview can not show that!

The task list you are asking about is a Github Flavored Markdown feature. I don't think this project has any explicit support for this markdown version.

I was able to add this feature to OmniMarkupPreviewer myself. You have to add the markdown-checklist extension for MarkdownRenderer. Unfortunately the original author, @tobiashochguertel, removed the repo from GitHub.
I don't remember how I installed the extension exactly but it involved copying over these files:
Sublime Text\Data\Packages\OmniMarkupPreviewer\OmniMarkupLib\Renderers\libs\markdown\extensions\checklists.py
Sublime Text\OmniMarkupPreviewer\public\checklists.js
Sublime Text\OmniMarkupPreviewer\public\checklists.css
Sublime Text\OmniMarkupPreviewer\templates\checklists.tpl
Sublime Text\OmniMarkupPreviewer\templates\checklists-export.tpl

and adding "checklists" to the MarkdownRenderer extensions list in OmniMarkupPreviewer.sublime-settings
{
  "renderer_options-MarkdownRenderer": {
    "extensions": ["extra", "codehilite", "toc", "nl2br", "strikeout", "superscript", "smarty", "checklists"]
  }
}

For posterity, there is a clone of the markdown-checklists repo here: https://github.com/SCP-028/markdown-checklists


Returning the Date and Time

How to return the date and selected time?

Check the docs here: https://react-schedule-meeting.netlify.app/docs/usage
You'll see there is a prop called onStartTimeSelect which emits the selected time and date with this: https://react-schedule-meeting.netlify.app/docs/usage#starttimeeventemit object type


Router links sometimes lead to wrong pages or don't work

Version
3.0.1
Reproduction link
http://daggy1c.watchduck.net/nodes/9
Steps to reproduce
Start on page 9, click parent 2, click parent 1. Link does not work.
Start on page 10, click parent 1, click child 2. Link leads to 13 instead of 2.
What is expected?
That the links go to the correct pages.
What is actually happening?
Sometimes these links go to the wrong page or don't work.

A detailed description is on Stackoverflow: https://stackoverflow.com/questions/51332783
Full version with console logging: http://daggy1.watchduck.net/nodes/9
Code on GitHub: https://github.com/watchduck/daggy/tree/static-data/front/src
Works without tag="li":
http://daggy1a.watchduck.net/nodes/9
https://github.com/watchduck/daggy/tree/simple-router-links/front/src
This is a duplicate of https://github.com/vuejs/vue-router/issues/2305, which was closed when a team member asked for a smaller reproduction, but not reopened when it was provided. Sorry for the noise, but there seems to be no other way.
https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github
Original reporter should be able to reopen a closed issue: https://github.com/isaacs/github/issues/583

Please don't do this again. The other issue is already in my todo list j just do not have the time to check it yet.
This creates unnecessary noise for me and other people watching the repository

Hopefully GitHub will introduce a more meaningful status than "closed" for situations like this. A yellow tag saying something like "in progress" would be great.


PD-7487 Tag copied amis in remote accounts

This change will tag amis that have been copied between regions in all
remote accounts.

👍


Start the Window App?

I'm feeling quite foolish about this, being a long-time VS/.NET dev, but I haven't figured out how to launch the Windows version of the app.  What am I missing?  I've set "WeatherTwentyOne.WinUI" as my startup project, and when I attempt to run the project I get "Unable to start debugging.  The startup project cannot be launched. ..."
Admittedly I'm very new to Maui (this is my first attempt even to look at a Maui app), but....

It was hard back then, now with rc1/preview8, you can run the app from PR https://github.com/davidortinau/WeatherTwentyOne/pull/37 on Windows as follows:

https://github.com/dotnet/maui/issues/2493#issue-997086299, and
https://github.com/dotnet/maui/issues/2493#issuecomment-920128239

It was hard back then, now with rc1/preview8, you can run the app from PR #37 on Windows

I assume we're getting closer, but I can't even build that branch. I get "Unable to find package PInvoke.User32. No packages exist with this id in source(s): C:\Program Files\dotnet\library-packs, dotnet6, public, xamarin".