Windows Installer - missing api-ms-win-crt-runtime-l1-1-0.dll

When using the installer the service cannot start (so the install cannot complete) due to missing
api-ms-win-crt-runtime-l1-1-0.dll - so if KB2999226 not previously installed the install cannot finish.
The readme file states

Everything that is needed is included in the MSI installer.

os - windows 7 home edition - not updated for more than year ago.

Thank you for the report. So the prerequisites for the application are:
For Windows 8.1 and earlier versions, or Windows Server 2012 R2 and earlier versions:
Make sure that your Windows installation is up-to-date and includes KB2999226, which can be installed through Windows Update. If you don't have this update installed, you'll see an error like the following when you launch a .NET Core application: The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.
For Windows 7 or Windows Server 2008 R2:
In addition to KB2999226, make sure you also have KB2533623 installed. If you don't have this update installed, you'll see an error similar to the following when you launch a .NET Core application: The library hostfxr.dll was found, but loading it from C:<path_to_app>\hostfxr.dll failed.

Documentation updated.
Prerequisites are mentioned on README.md.


Multistep ahead forecast feature

Feedback from forecasting people that multi-step-ahead forecasting is pretty important. So I am thinking about building it in here. Probably with a method called model.forecast(). What it does is like:

If it makes sense, fits the theme and something good to have, I will start working on it for the next couple of weeks.

@RLstat I am assuming you are implementing this right?

@ethem-kinginthenorth , Yes, I am working on it.

@RLstat awesome. could you please give me an estimate when you can deliver this? I would like to plan the next release.

@ethem-kinginthenorth Probably by the end of this month.

@RLstat thanks. I am waiting you to finish before doing another release. please keep me updated. thanks

@ethem-kinginthenorth update: likely to have a merge request regarding this feature by the end of next week.

closing this as the new feature has been merged.


Store back the CR only if it has changed

Fixes #231 by comparing the original CR with the post-reconcile state, issuing an update only in case the CR has changed.
Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

This change is


fix bug and add function

1 changed file
1、fix in bad network condition the ping checker return fail but network status possible set to reachable while not post status change notification to users; so if user call - (ReachabilityStatus)currentReachabilityStatus function return status is not match with the app UI current show state. eg: the app shows current time is in no network condition while can send out network request.
2、add when in bad network condition ping fail two times, changed reachable status to not reachable; later network become better, if ping two times return success, we consider the network is connected and change network status to reachable and post change notification to users .

1、fix in bad network condition the ping checker return fail but network status possible set to reachable while not post status change notification to users; so if user call - (ReachabilityStatus)currentReachabilityStatus function return status is not match with the app UI current show state. eg: the app shows current time is in no network condition while can send out network request.
2、add when in bad network condition ping fail two times, changed reachable status to not reachable; later network become better, if ping two times return success, we consider the network is connected and change network status to reachable and post change notification to users .

which user case you want to handle? does it really exists or you meet with it? @iMickChen
I am thinking about it

I got your point. Thanks a lot! But I think ping success once we will mark "connection ok", double check not needed. I will commit the codes.

I think when ping two times result change network status to unreachable, latter network become better the first time ping success we  mark "connection ok" is not convenient, I thinks if next ping is still success we can mark the networking is connected. double check can avoid network fluctuation cause frequently post notification.
en about first problem is my company Test Engineer find and submit bugs for me, I have actually repeat that problem in my app and the RealReachablity demo

Ping check maybe too strict for status report, so I introduce the double check to reduce this situation. From this sight of view, I will not force the double check when first ping success.

Double  ping success check  is only affect current status is unReachable and localConnection is connected. if not force double check, return status is only check one time.  the first ping success like localConnection local connected call back. the next ping like to make sure your reachability is "Real"


[Deepbook] Modify the cancel all orders to emit an event vector at end of function call

Description
Instead of emitting a single event per cancel, we emit one big CancelOrders event at the end of the order matching loop, and at the end of cancel_all_orders.
This change is motivated by the fact that we can have MoveAborts that occur because there is an emitted event limit on transaction execution. An example error is https://suiexplorer.com/txblock/Ck3g7SJMCVDEgHXHP9jMAU4EDzHQGXkstxqwPiQ2CxgR?network=testnet
MovePrimitiveRuntimeError(MoveLocationOpt(Some(MoveLocation { module: ModuleId { address:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000002, name: Identifier("event") }, function: 0, instruction: 0, function_name: Some("emit") }))) in command 0

Test Plan
How did you test the new or updated feature?
Sui move build, sui move test

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[x] protocol change
[x] user-visible impact
[ ] breaking change for a client SDKs
[x] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[x] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@oxade: is there a limit on the size of a single event?

@oxade: is there a limit on the size of a single event?

Yes, 250k.


My traffic generating host does not reach the OpenVino application in a Network Edge deployment

Hello, I have been studying and testing the OpenNESS Network Edge architecture for a couple of months but I encounter the following problems and doubts when trying to deploy the OpenVino application following this documentation: [https://github.com/open-ness/specs/blob /master/doc/applications-onboard/network-edge-applications-onboarding.md#onboarding-openvino-application]
In my case, OpenNESS for Network Edge is fully installed and set up in a VPN with two nodes: <IP_ADDRESS> for the Controller and <IP_ADDRESS> for the Edge Node (node01). And the traffic generating host is at <IP_ADDRESS>.
The specs say "From the Edge Controller, set up the interface service to connect the Edge Node's physical interface used for the communication between Edge Node and traffic generating host to OVS" Does this mean I cannot use node01 interface <IP_ADDRESS> and that I need a second physical interface on said node? In any case, I have a second physical interface on node01 to receive the streaming of the traffic generating host, and it is <IP_ADDRESS>. But after the "kubectl interfaceservice attach ..." process I no longer have access to the machine through that interface, is this normal?
Another question: the specs say "The subnet <IP_ADDRESS>/24 is allocated by Ansible playbook to the physical interface which is attached to the first edge node", "node jfsdm001 is bridged to subnet <IP_ADDRESS>/24", "Ingress traffic originating from <IP_ADDRESS>/24 can only reach the pods deployed on jfsdm001 ", so: as I said, my host is on ip <IP_ADDRESS>, how can I add a new subnet or modify subnet <IP_ADDRESS>/24 to that the traffic of my host is accepted?
Any answer or documentation that you can provide me to resolve these doubts will be welcome, thank you very much.

This ticket is open for a while now. Given that we have multiple releases since can you please check if this on the latest and open a ticket if it's still an issue.


[CLI] Different results between CLI and Web

I used the CLI to output a jpg using --mozjpeg and --webp, but using the same options given on the tool based on the web, the output given to me is different.
Output on the web:
mozjpeg -> 92.4kb
webp -> 51.6kb
Output using the CLI:
mozjpeg -> 84.9kb
webp -> 13.2kb
Also, CLI affects the space color of the image and gives a bad compression, resulting in a worst processed image, comparing with the tool based on the web. I used the same .jpg source for this test, and the same options (I copied the same code that offers the web, the npx command).
I used on the CLI:
webp version
squoosh-cli --webp '{"quality":75,"target_size":0,"target_PSNR":0,"method":0,"sns_strength":50,"filter_strength":60,"filter_sharpness":0,"filter_type":1,"partitions":0,"segments":4,"pass":1,"show_compressed":0,"preprocessing":0,"autofilter":0,"partition_limit":0,"alpha_compression":1,"alpha_filtering":1,"alpha_quality":100,"lossless":0,"exact":0,"image_hint":0,"emulate_jpeg_size":0,"thread_level":0,"low_memory":0,"near_lossless":100,"use_delta_palette":0,"use_sharp_yuv":0}' -d out 30.jpg

mozjpeg version
squoosh-cli --mozjpeg '{"quality":75,"baseline":false,"arithmetic":false,"progressive":true,"optimize_coding":true,"smoothing":0,"color_space":3,"quant_table":3,"trellis_multipass":false,"trellis_opt_zero":false,"trellis_opt_table":false,"trellis_loops":1,"auto_subsample":true,"chroma_subsample":2,"separate_chroma_quality":false,"chroma_quality":75}' -d out 30.jpg

Oh interesting! YOu are right that has probably to do with colorspaces. On the web we rely on canvas to convert to sRGB, on the CLI I just take what the decoder gives me.

@surma Probably is something with the decoder, the results are different and distinguishable between each version (web and CLI).

I get particularly bad results trying to compress an image to webp using the CLI. Online the result is fine, but offline it does not seem the encoder options are being respected. I get potato quality regardless of the options I pass to the CLI. Tried copy/pasting the CLI from the webapp too, to no avail.

Yup, can confirm and reproduce. Looking into this.

Yup, can confirm and reproduce. Looking into this.

@surma Thanks for look into this. What about the color space with both formats?

@surma Thanks for look into this. What about the color space with both formats?

@rodsotdia From what I can tell, the MozJPEG decoder does indeed decode to sRGB. Do you see color issues?

@rodsotdia From what I can tell, the MozJPEG decoder does indeed decode to sRGB. Do you see color issues?

I'm having the same quality issues on v0.6.1 (possible duplicate of https://github.com/GoogleChromeLabs/squoosh/issues/898). Output size is the same (and very aggressively compressed) regardless of the chosen value of --optimizer-butteraugli-target.

I'm having the same quality issues on v0.6.1 (possible duplicate of https://github.com/GoogleChromeLabs/squoosh/issues/898). Output size is the same (and very aggressively compressed) regardless of the chosen value of --optimizer-butteraugli-target.

@surma Yes, I think the color space is different:

Left: Original
Center: Processed through app.
Right: Processed through cli.

@surma Yes, I think the color space is different:

Left: Original
Center: Processed through app.
Right: Processed through cli.

I am also experiencing problems where WebP images are dismissed as invalid in the CLI, but are decoded correctly in the browser. It sounds pretty reasonable to me that it is because the CLI relies in a different parser, so I haven't spend much more time on it. Let me know if you want a complete bug report with sample images.

Got same problem with oxipng, from web I got this command :
npx @squoosh/cli --quant '{"enabled":true,"zx":0,"maxNumColors":16,"dither":1}' --oxipng '{"level":3,"interlace":false}'
The working command:
npx @squoosh/cli  --quant '{"enabled":true,"zx":0,"numColors":16,"dither":1}' --oxipng '{"level":"3","interlace":false}'
We need to use numColors with cli, not maxNumColors. And we can use level: 6 with the cli.


Error when making container

Step 6/7 : RUN pip3 install -r requirements.txt
---> Running in 24fc7b4bd1f7
Collecting discord.py[voice]~=0.16.0 (from -r requirements.txt (line 1))
Downloading discord.py-0.16.12.tar.gz (414kB)
Requirement already satisfied (use --upgrade to upgrade): pip in /usr/lib/python3.5/site-packages (from -r requirements.txt (line 2))
Collecting youtube-dl (from -r requirements.txt (line 3))
Downloading youtube_dl-2017.11.26-py2.py3-none-any.whl (1.7MB)
Collecting colorlog (from -r requirements.txt (line 4))
Downloading colorlog-3.1.0-py2.py3-none-any.whl
Collecting cffi (from -r requirements.txt (line 5))
Downloading cffi-1.11.2.tar.gz (435kB)
Complete output from command python setup.py egg_info:
gcc: error trying to exec '/usr/lib/gcc/x86_64-alpine-linux-musl/5.3.0/../../../../x86_64-alpine-linux-musl/bin/as': execv: Exec format error
gcc: error trying to exec '/usr/lib/gcc/x86_64-alpine-linux-musl/5.3.0/../../../../x86_64-alpine-linux-musl/bin/as': execv: Exec format error
    No working compiler found, or bogus compiler options passed to
    the compiler from Python's standard "distutils" module.  See
    the error messages above.  Likely, the problem is not related
    to CFFI but generic to the setup.py of any Python package that
    tries to compile C code.  (Hints: on OS/X 10.8, for errors about
    -mno-fused-madd see http://stackoverflow.com/questions/22313407/
    Otherwise, see https://wiki.python.org/moin/CompLangPython or
    the IRC channel #python on irc.freenode.net.)

----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-zj35idpo/cffi/
You are using pip version 8.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
The command '/bin/sh -c pip3 install -r requirements.txt' returned a non-zero code: 1

Just want to add that pip is already at it's latest. I also installed pip3 as well.

Anyone have any ideas? Resorted to just installing onto Ubuntu but would really like to use the container on this host.

May be fixed with https://github.com/Just-Some-Bots/MusicBot/commit/b19f5070ab5e692c89b9545db69be74b829b5941. Will be in the next release.


Standalone acceptance tests

Motivation and Context
Some Acceptance tests rely on data state set by previous tests which, not only prevents them from running independently but just changing the feature file name, can cause them to fail.
The goal was to establish a pattern whereby each Scenario runs in isolation.
A "@standlone" tag differentiates between standalone/non-standalone Scenarios. Non-standalone (or sequential) tests should run exactly as before but "@standlone" now indicates a Scenario can run in parallel and optionally, create its own data using a<EMAIL_ADDRESS>tag.
About 18% of Scenarios have been converted so far -
add_a_survey.feature (6 scenarios)
breadcrumb_navigation.feature  (3 scenarios)
display_unused_enrolment_code.feature (1 scenario)
generate_new_enrolment_code.feature (1 scenario)
sign_in_internal.feature (7 scenarios)
sign_out_internal.feature (1 scenario)
social_change_case_status.feature (3 scenarios)
social_disable_uac.feature (1 scenario)
social_find_case_by_postcode.feature (2 scenarios)
social_sign_in_internal.feature (7 scenarios)
social_sign_out_internal.feature (1 scenario)
social_view_case_details.feature (1 scenario)
survey_enrolment.feature (2 scenarios)
view_collection_exercise_created_state.feature (2 scenarios)

Scenarios that use the @fixture tag, use data from their Feature/Scenario to improve traceability -
Survey Data
=========
Survey name = 'BUSINESS' OR 'SOCIAL' + "-" + feature name + UTC creation timestamp (may be compacted)
Short name = RU Reference (unique per Scenario)
Survey Ref  = a randomly generated number above 90000 (keeps standlone tests together on "View list of business surveys" page)

Collection Exercise Data
==================
User Description = 'BUSINESS' OR 'SOCIAL' + "-" + scenario name (may be compacted)
A Respondent login (if required) =  generated from RU Reference e.g<EMAIL_ADDRESS>
    A typical @fixture tag test takes around 30 seconds to run, in parallel, this reduces to about 8 seconds

Negatives
Time to convert the remaining 170+ Scenarios
New acceptance tests being added using the old way
On Going
Scenario's that require more than one sample
Scenario's with multiple Collection Exercises
Graceful exit after test/system failures/exceptions
How to handle Scenario Outlines
Logging
Debugging multi-threaded app in Pycharm
What has changed
New environment variables
IGNORE_SEQUENTIAL_DATA_SETUP = skips the 4 standard non-standalone collection exercises + respondent '49900000001' registration - defaults to 'False'
New tags
@business - currently does nothing but may be useful in future to separate business/social test runs
@standalone - enables a Scenario to run in parallel and can be used with the "@fixture" tag
@fixture.xxxxx - allows Scenario specific data setup
New files
run_tags.py  - run tests by tag(s) - a temp solution (hopefully) to help debugging tests during development.
run_in_parallel - run standalone Scenarios concurrently
How to test?
Everything
from a terminal in the rasrm-acceptance-tests directory, run - "make acceptance_tests" as usual, all 211 should pass and 21 Surveys (name prefixed with "BUSINESS" or "SOCIAL") are on the "View list of business surveys" page
Just Sequential (non-standalone) tests
from a terminal in the rasrm-acceptance-tests directory, run - "make acceptance_sequential_tests", all 173 tests should pass
Just Parallel tests (no need to run "make setup" anymore :-) )
from a terminal in the rasrm-acceptance-tests directory, run - "make acceptance_parallel_tests", 38 tests should pass with 21 new surveys showing on the "View list of business surveys" pagepage
Links
Test in conjunction with

 Make acceptance tests more independent

 T005: Method to run standalone acceptance tests in parallel

thanks @NickGrantONS , doesn't look possible to check exit code as Makefile rule is executed in a separate shell so, how about something like @AdamHawtin suggested earlier, treat them as separate Concourse jobs? so, make "acceptance_tests" run sequential, "acceptance_parallel_tests" parallel and ditch "acceptance_sequential_tests" -  thoughts?

we'll need to do the concourse work as a matter of urgency, because erroneous things could end up flowing through our pipleline, but yes that'd be an OK workaround

@NickGrantONS found a few posts that "claim" to do it, my attempts have failed so far so will go with "plan a"


ISPN-7135

ClusterListenerReplTest.testPrimaryOwnerGoesDownBeforeBackupRaisesEvent
random failures

Change test to allow for 2 retries

https://issues.jboss.org/browse/ISPN-7135

Fixed

integrated! thanks @wburns


Gallery ToC shows both tags and individual examples

📚 Documentation
After merging PR #4975 we now have both tags and the original example list shown on the left-hand side

Since we can already browse all examples with image tiles, removing the text list and only keeping the tags could make the navigation cleaner.

Awesome this actually makes it simpler since that is the default for sphinx-gallery. Will update soon!


feature: use custom errors

Context
Starting from Solidity v0.8.4, there is a convenient and gas-efficient way to explain to users why an operation failed through the use of custom errors. This way is less expensive, especially when it comes to deploying cost than passing a string to require or assert.
Gas comparison
Before

After

Result
As you can observe, the deployment cost is highly reduced for the mocked contracts (almost 20%).
Tradeoff
This improvement requires a bump to 0.8.4.  I am personally convinced this is worth it and the accessibility issue caused by the bump is acceptable due to the fact the bump is minor.

my biggest concern is that we want to match open zeppelin's accessibility, and they still have their library at ^0.8.0

It's not the biggest deal in the world, I'll talk to the rest of the team and see what they think.

Alright, let's do this. Thanks for making this change

Thanks for this PR, Wouldn't it better that we use NatSpec to further explain the reasons behind the error for convenient error-reporting?
If it does, I can create another PR with additional changes.


Configure commitlint

Proposed Changes

Configure commitlint to check if commit messages adhere to a standard that let us implement automated versioning and publishing.

Related to #4947
TODO: Configure this as a required check
Readiness Checklist
Author/Contributor

[x] I included all the needed documentation for this change.
[x] I provided the necessary tests.

Reviewing Maintainer

[x] Label as breaking if this is a large, fundamental change.
[x] Label as either: automation, bug, documentation, enhancement, infrastructure.

@zkoppert If I got the commitlint configuration right, this PR should fail the required checks when it will be added to the merge queue because this repository is configured to use the default message when merging with a squash commit: the PR title and the list of commits. If this is the case, we can also validate the fact that a squashed commit has to adhere to the convention as well.


Upgrade the Go version of the demo app

The app in /demo/greeter uses an outdated version of Go, and it is being reported by Trivy as having several High and Medium-risk dependencies vulnerabilities . We need to upgrade the Go version (maybe matching the same version Galadriel uses) along with these dependencies.

I think that this was solved here:  https://github.com/HewlettPackard/galadriel/pull/92

You're right! thanks Victor ❤


Graph refresh of configuration_scripts and configuration_workflows in one InventoryCollection

Depends on https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/117

The build is broken due to the PR dependency


Is possible to read and write 64bit register

Hi!
thanks for this tool!
Is possibile to read/write 64bit register.
I need to access to eneergy meter data stored in INT64 type
Do you think is possible?

Hello.
There is no 64-bit integer support now. But it is possible to implement feature in future release. Do you need this feature?

Thanks for the immediate reply....
I needed for reset the partial energy readings of this energy gateway https://www.se.com/it/it/product/PAS600/ecostruxure-panel-server-universal-concentratore-wireless-e-gateway-modbus-110277-vac-dc/
You can download the modbus address list in the file DOCA0241EN-08.zip
Thanks

Implemented at version 1.7.0


WinPayloads Starting error

Python is giving an unknown error.Every software is working fine except Winpayloads.Kindly check the entry.
Regards,

Info?


Move gzclose() to gzlib.c.

Modern linkers should be smart enough to link it in only if it is used. I checked the size of minigzip.exe with and without NO_GZCOMPRESS and whether or not gzclose was in gzclose.c or gzlib.c and there was no difference in MSVC. Perhaps this was done for some ancient linkers?

Rebased


Next Upcoming Berlin event in March 2018 organized by Wiredcraft

RSVP: https://www.meetup.com/de-DE/Berlin-Hacker-News-Meetup/events/248018512/

Thanks, added manually because of conflicts.


Rust code changes to not get compiled

Changing DesignCompose Rust code and then building/running an application does not trigger a rebuild of the Rust code. Example:

Open the designcompose root project in Android Studio
Build and run validation from Android Studio on an emulator
Add a log line to layout.rs in the layout crate, in add_style(), such as info!("add_style!")
Build and run validation from Android Studio again
-> It runs immediately without rebuilding, and no log lines are seen.

I've reproduced it, looking into it.


refactor: drop dependency on pify

Now that we dropped support for node.js 6, we can just use util.promisify.

The ci/kokoro: docs failure is unrelated to this change.
@jkwlui -- any ideas? It looks like it might be a test that's set up internally with Kokoro, but the build config isn't yet in this repo, since it failed with:
 Failed to get build config
com.google.devtools.kokoro.config.ConfigException: Couldn't find build configuration under /tmp/workspace/workspace/cloud-devrel/client-libraries/nodejs/presubmit/googleapis/cloud-profiler-nodejs/node10/docs/src/github/cloud-profiler-nodejs/.kokoro/presubmit/node10


Add hexdocs link + number of calls arg

This PR adds a link to the hexdocs, as finding the docs for Mimic can be a little tricky. Searching elixir mimic comes up with a bunch of stuff that isn't this, presumably because this page hasn't been spidered yet.
It also adds the arg for number of calls in the example of that, as it was missing before.

Thank you so much! 🎉


These Examples are really not working

These refrences are just not working maybe these needs to be updated with latest code please have alook as for FIX there is not sch a good help is available
Thanks

Update:
After doing research the issue been solved some of the code used from this repo
Thanks


CLOUD-48047 Individual flow for instance termination

@bbihari plz review

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2304/

LGTM


InterfaceRedirectResolver - an IUriResolver that treats interface implementations as implied redirects

The InterfaceRedirectResolver is a simple IUriResolver implementation that redirects from a registered interface URI to the first registered implementation for that interface.
This PR also fixes a bug in https://github.com/polywrap/toolchain/pull/1518 where the build() method in the IClientConfigBuilder interface did not accept the new options as an argument.
Closes https://github.com/polywrap/toolchain/issues/1501

I wonder if we need a separate uri resolver for this, Can't we just use a normal redirect resolver? I agree that it may help save a few line of code for users but they can create something similar themselves. This is also not very configurable. It just redirects interface to first implementation which wouldn't be a behavior that everyone wants

Fair enough! It's also true that when using embedded packages (plugins or wrappers) it is often possible to use the interface URI as the implementation URI:
// in interfaces config
[defaultInterfaces.concurrent]: new Set([defaultInterfaces.concurrent]),

// in packages config
[defaultInterfaces.concurrent]: concurrentPromisePlugin({}),

But if you're using non-embedded Wasm wrappers for implementations, or if the interface URI can't readily be assigned to a specific embedded package (e.g. the uri resolver interface), then this new resolver is useful.
This resolver is syntax sugar that lets you do something like this without adding a redirect:
// in interfaces config
[defaultInterfaces.concurrent]: new Set(["wrap://package/concurrent"]),

// in packages config
["wrap://package/concurrent"]: concurrentPromisePlugin({}),

I now know we can remove all of the global redirects without this resolver. I didn't realize that would be possible at the time Jordan and I talked about the issue. We were just thinking about ways to remove global redirects. (In retrospect, I think Jordan was alluding to the idea of using the interface URI as the implementation URI, but it went over my head.)
So I'm not sure whether this resolver is immediately useful to us.

IIRC, we decided this was not needed


OpenBSD as a supportet platform?

Electron version: 1.6.2
Operating system: OpenBSD

I was trying to get https://github.com/cryptocat/cryptocat running on an OpenBSD system.
After cloning the repository i ran "npm run setup", but this fails while installing<EMAIL_ADDRESS>with the following error message:
><EMAIL_ADDRESS>postinstall /store/cryptocat/cryptocat/node_modules/electron
> node install.js

/store/cryptocat/cryptocat/node_modules/electron/install.js:61
      throw new Error('Electron builds are not available on platform: ' + platform)
      ^

Error: Electron builds are not available on platform: openbsd
    at getPlatformPath (/store/cryptocat/cryptocat/node_modules/electron/install.js:61:13)
    at Object.<anonymous> (/store/cryptocat/cryptocat/node_modules/electron/install.js:19:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:393:7)
    at startup (bootstrap_node.js:150:9)
npm ERR! OpenBSD 6.1
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.10.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

What would be needed to add support for OpenBSD as a platform?
Is this something realistically possible?

See https://github.com/electron/electron/issues/3797 free BSD support, not sure about difference between freebsd and openbsd but I assume it's a similar issue 👍

See electron/electron#3797 free BSD support, not sure about difference between freebsd and openbsd but I assume it's a similar issue +1

It probably is not. Both are completely different OS and not like Linux distros.


Need consistent way to validate a model-provider is properly configured

Right now, to verify a model-provider was properly configured,  the model provider modal calls an api for listing available models, which directly calls the model provider. This does not work for all our model providers. I forget which ones @thedadams said it does work for.
Id like a consistent way to verify a model-provider is properly configured. Maybe model-provider needs to have a /validate endpoint?

Tangentially related to https://github.com/otto8-ai/otto8/issues/819. That one makes me think the backend needs to call a validate endpoint and mark the provider as being in an error state.

Based on a conversation about this issue, I say we do the following:

Implement the validation as we discussed: use the Error field to indicate if there were any issues getting the available models in the controller. We definitely want this change no matter what in case a user configures the model provider incorrectly.
After that is done, then we can add the /validate endpoint discussed here. I currently don't have an idea of how this would work. If you have one great. Otherwise we can discuss it.


High priority: No delete function like sort($event) provided in table.stories.ts

Detailed description

cannot get index of table.

A general issue?

ibm-table, table.stories.ts

Provide a function to return index of table or delete function for specific rows in table

What browser are you working in?

What version of the Carbon Design System are you using?
"@carbon/icons-angular": "^10.4.0",
"carbon-components": "^10.4.1",
"carbon-components-angular": "^3.13.4",
"carbon-icons": "^7.0.7",
What offering/product do you work on? Any pressing ship or release dates we should be aware of?

Steps to reproduce the issue
create a table with , when I create several custom rows in table, I cannot delete them or delete the specific row.

.html
<ibm-table #tableContent
style="display: block; width: 100%;"
[model]="model"
[size]="size"
[showSelectionColumn]="showSelectionColumn"
[striped]="striped"
[isDataGrid]="isDataGrid"
(sort)="customSort($event)"
>

.ts
customSort(index: number) {
this.sort(this.model, index);
}

sort(model, index: number) {
if (model.header[index].sorted) {
// if already sorted flip sorting direction
model.header[index].ascending = model.header[index].descending;
}
model.sort(index);
}
delete(model, index: number){
console.log("enter delete, model="+model+", index="+index);
model.delete(index);
}
3. no customDelete for me to call delete(model, index: number) like what customSort do.
Additional information

Screenshots or code
Notes

model provide rowsSelected function to return all selected status.

I found that model provide rowsSelected function to return all selected status.


1.14 Release Review

During 1.14 we had a few issues that were spotted too late to be fixed for 1.14 itself leading to 1.14.1 to be needed quickly.
We want to post-mortem the issue(s) seen and decide on what we should do to improve the scenario.
We had some good ideas in the standup today, so created this issue to get all these recorded for further discussions.
/cc @wallrj @inteon @ThatsMrTalbot @SgtCoDFish @maelvls @erikgb @SpectralHiss  - Please add your thoughts to the issue.
I will attempt to link all the issues in this message later.

My suggestion from the standup:
In the release thread for 1.14.0 @wallrj shared a snippet to generate a diff between the old chart and the new, which pretty much immediately made it obvious what there was another bug (a Service that was deleted when it shouldn't have been).
It'd be helpful to have that diff for any change to the chart, and it could be automatically generated. The current diff is noisy because it includes version number changes, but those could be filtered out before we diff to make the actual changes obvious!

Another possible improvement: we should specify as part of the release process when and who should validate a beta release.

While releasing the OperatorHub package, I've setup local automated testing and I've updated the Release Process:

https://github.com/cert-manager/cert-manager-olm/pull/104


Further improve PWA

[ ] In PWA mode, when you tap to focus in the composer input the keyboard slides up. However, it slides the WHOLE page rather than just the composer. It’s not immediately obvious this is a problem, although you can't tap any of the navigation items at the top of the screen. And then it's really a problem as the reply streams in because you stay focused in the input (which is correct) but you can’t read the reply because it's at the top of the screen. The fix is for this to behave like the ChatGPT mobile app (or iMessage) where the keyboard slides up and pushes up the composer but keeps the top of the page visible.

[ ] Install instructions: On a mobile phone, when you first navigate to the app in a browser we just render the app normally in this mobile browser. However, it's not a good experience. I think we should detect you're viewing the app in a mobile browser, intercept and redirect you to installation instructions. I'd probably create home_controller and '/install' can be the first route on it. Ideally the instructions should detect if you're on iOS or Android and customize the instructions it presents. (I think speakeasy.app might be an example of this)

[ ] In PWA mode you can still two-finger zoom in on the whole app. We should disable this.

[ ] In dark mode the iOS menu bar is white. Maybe we can’t fix this and have to pick a single color, but it might be a simple setting to make the menu/status bar transparent?

[ ] DEFER — The conversations and assistants in the left nav are a little bit small to tap with your finger. Comparing it to ChatGPT mobile, I think we should both increase the font size and add some padding above and below. Likewise with your name/profile bar in the bottom left. Comparison:
*

[x] DEFER — All the tappable elements in the top bar while viewing a conversation, those feel a bit too small as well.

[x] Hover states don't work properly on mobile so we should eliminate those. Specifically, when you tap on the conversation title in the left nav it does not activate that conversation, instead it activates the hover state of that conversation. You have to tap a second time to actually select that conversation. As a first step, we can disable all hover states on mobile. This used to be difficult but it looks like Tailwind now supports this easily (https://github.com/tailwindlabs/tailwindcss/discussions/1739#discussioncomment-3630717). Separately we can figure ou thow to

[x] Login & signup pages are too tall so they can be scrolled. Repro: add the app to phone home screen, open the app and make sure you're logged out, try scrolling up & down on the login page. We must have some big whitespace beneath the form.

[x] If you long tap on a conversation (or assistant) in the nav bar it does not have useful behavior. Can we disable long-tap for mobile web? Not sure if PWA supports that somehow, maybe in PWA config or as a modifier on each link or a tailwind thing?

[x] On iPad PWA, the whole page can scroll up and down a bit rather than being fixed (or rather, just having the conversation scroll). This is most evident on a brand new conversation. Try scrolling the main area. But even on a long conversation if you put your finger near the composer area then you can scroll the full page up and down separately from just scrolling the conversation messages.

[x] The logo needs a little more whitespace around it, it's a bit too close to the edge. Here you can see it as compared with a few other logos
*

[x] Our logo is stretched on the iPad splash screen (it looks fine on mobile) — this is a known iOS bug: https://github.com/elegantapp/pwa-asset-generator/issues/93
*

[x] We should disable all hover tooltips on mobile. With the touch screen, the tooltip doesn't appear until you tap and then it's left sitting on screen. So, for example, when you send a chat message you still see "send message" tooltip above the submit button after you've tapped it. Tooltips aren't appropriate on mobile.

[x] When you open the nav bar on mobile there is a weird black line at the top, we should hide this:

[x] We need to make room at the bottom of the page for the iOS grab handle. The tricky thing is, some iOS devices need that extra space and others don't. React Native (and I believe Swift) solve this by the concept of safe area (react native can wrap the view in SafeAreaProvider and it just does the right thing). Does an equivalent exist in PWA apps?

[x] When you try to scroll outside of the scroll box (because you reach the top and the bottom) it moves the header and footer. Here I'm pulling down. There is some fix for this with CSS but I forget what it is

@jasonpaulso I had accidentally marked this PWA issue as complete but there are still some improvements. I just cleaned this up to it's up to date. If you feel so inclined :) the top two items on this list would be particularly impactful. Some of the others might be easy too.

Absolutely @krschacht I can work on the remaining items

@krschacht just letting you know that I'm still working on this. I think I've sorted a few points and a few others I'm noodling on.

Thanks @jasonpaulso , you're awesome. And in case you didn't notice yet, a couple days ago, I slipped a new one to the very top of the list. As I've been using the mobile experience more, this might be the single biggest usability issue.

@jasonpaulso I just noticed a couple new small visual issues that seemed to crop up. I don’t know if these were part of the latest PR but I don’t think we had these a couple months ago.
First, here is a screenshot:

In the top left corner, as the assistants scroll beneath the sticky assistant there is a little gap where they are visible. We used to have a spacer element in this slot that existed solely to fill it so we don’t see these peeking through.
At the bottom of the screen, the left sidebar has a dark gray background which no longer extends to the very bottom of the screen and, actually, I guess the main right column has a light gray background which also doesn’t extend. I know we added that extra space for the iOS menu handle but I was pretty sure that this extra space only pushed up the contents of the main column whereas now it’s actually pushing up the whole page.

These are small visual things, but I thought I’d mention while things are fresh b/c maybe you might immediately know what caused these.

I’d say it’s likely related to something I’ve done. I can sort it out on Monday!

On Jun 12, 2024, at 7:03 PM, Keith Schacht @.***> wrote:
@jasonpaulso https://github.com/jasonpaulso I just noticed a couple new small visual issues that seemed to crop up. I don’t know if these were part of the latest PR but I don’t think we had these a couple months ago.
First, here is a screenshot:
image.png (view on web) https://github.com/AllYourBot/hostedgpt/assets/35061/6b6a58fd-2eea-466a-b2d8-6340fd0a4b52
In the top left corner, as the assistants scroll beneath the sticky assistant there is a little gap where they are visible. We used to have a spacer element in this slot that existed solely to fill it so we don’t see these peeking through.
At the bottom of the screen, the left sidebar has a dark gray background which no longer extends to the very bottom of the screen and, actually, I guess the main right column has a light gray background which also doesn’t extend. I know we added that extra space for the iOS menu handle but I was pretty sure that this extra space only pushed up the contents of the main column whereas now it’s actually pushing up the whole page.
These are small visual things, but I thought I’d mention while things are fresh b/c maybe you might immediately know what caused these.
—
Reply to this email directly, view it on GitHub https://github.com/AllYourBot/hostedgpt/issues/298#issuecomment-2164035145, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACT5ZUSBP4XRC43YDPVFFHDZHDHVXAVCNFSM6AAAAABGVZWECCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGAZTKMJUGU.
You are receiving this because you were mentioned.


Create a test runner that lets you control which tests to run

This issue was originally filed by<EMAIL_ADDRESS>
Per (https://groups.google.com/a/dartlang.org/forum/#!searchin/misc/"[misc]$20Test$20Suites?"/misc/RLS89WZKdJE/zSk84lMbhsYJ):
It'd be really great to have a test runner that could automatically (based on invocation):
 * Run all the tests in a directory (recursively)
 * Run all the tests in a file
 * Run specific tests in a file with nested tests
Right now, you have to do stuff like:
// suite1.dart
main() {
  group('suite 1', () {
    test('a', () { ... });
    test('b', () { ... });
    test('c', () { ... });
  });
}
// suite2.dart
main() {
  group('suite 2', () {
    test('a', () { ... });
    test('b', () { ... });
    test('c', () { ... });
  });
}
// everything.dart
#import('suite1.dart', prefix: 'suite1');
#import('suite2.dart', prefix: 'suite2');
main() {
  suite1.main();
  suite2.main();
}
which is a bit more tedious.
Bob Nystrom said we're going to have to wait for reflection in order to implement this.

This issue has been moved to dart-lang/test#146.


Create built-in tool for Brave Search API

Add a new built-in tool called sys.search.brave that utilizes the Brave Search API.

Closing this issue because we are tracking the work over in gptscript-ai/search.


User databases shouldn't share a global namespace

If two users each request a database named 'foo', it'd be silly for them to share it. Unless you really wanted that, which seems unlikely to me.
The default should probably be that user databases are separated by socket.id so that they can't be shared. I.e. one-db-per-user is the default.
Of course there's also db-per-role to consider, and maybe some devs will want their users to share a global database and do some fancy filtered replication. So the API should be flexible enough to handle all cases.

Is this already handled by the server because pouchCreator is called per socket and saved against '$' + socket.id?
https://github.com/nolanlawson/socket-pouch/blob/master/lib/server/index.js#L195

No, because the default PouchCreator will still use the same name for both, meaning they will use the same database under the hood. OTOH users can easily override this, so I'm going to close this issue as unimportant.


Fixing redirection loop bug

The proxyGrantingTicket can be null if the cache is expired. When the
proxyGrantingTicket is null and calling InsertProxyGrantingTicketMapping
will throw exception and causing redirection loop.

:+1:


[Release] Update DeepRec release version to 1.15.5+deeprec2201.

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


After installing please does not work, wrong file edited (.-bashrc).

zkitzo@Hetzner:~$ please
-bash: please: command not found
zkitzo@Hetzner:~$ source .bashrc
zkitzo@Hetzner:~$ please
-bash: please: command not found
zkitzo@Hetzner:~$ nano .bashrc
zkitzo@Hetzner:~$ echo `echo $0`
-bash
zkitzo@Hetzner:~$ ls -lAh
-rw-rw-r--  1 zkitzo zkitzo  209 May 31 19:49 .bash_aliases
-rw-------  1 zkitzo zkitzo 205K Jun 13 17:11 .bash_history
-rw-r--r--  1 zkitzo zkitzo  220 Jan  7 22:16 .bash_logout
-rw-rw-r--  1 zkitzo zkitzo    7 Jun 13 17:10 .-bashrc
-rw-r--r--  1 zkitzo zkitzo 4.1K May 22 21:08 .bashrc

Also /home/zkitzo/.local/bin is not in my $PATH. Easy to add but I think you should fix it!

Also /home/zkitzo/.local/bin is not in my $PATH. Easy to add but I think you should fix it!

Yes, that must be the problem. Unfortunately, it's not something I can fix since it's distro and python dependent. The solution for 'command not found' is to add ~/.local/bin to your PATH. I can add a warning for this in the readme, thanks for reporting!

Don't forget that $0 === -bash on my Ubuntu system.

Don't forget that $0 === -bash on my Ubuntu system.

I'll update the instructions to include manual editing :)


Release 0.8.0.RC1

Resolved via https://github.com/r2dbc/r2dbc-h2/commit/9af351101513bc983ed69491866344f71aa1c7d5.


soft-serve: 0.3.3 -> 0.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/charmbracelet/soft-serve/releases.
meta.description for soft-serve is: "A tasty, self-hosted Git server for the command line"
meta.homepage for soft-serve is: "https://github.com/charmbracelet/soft-serve"
meta.changelog for soft-serve is: "https://github.com/charmbracelet/soft-serve/releases/tag/v0.4.0"
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.0 with grep in /nix/store/h5ad14fngjqhpwsz8vcyf1k9fhcjk7dw-soft-serve-0.4.0
found 0.4.0 in filename of file in /nix/store/h5ad14fngjqhpwsz8vcyf1k9fhcjk7dw-soft-serve-0.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
soft-serve

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h5ad14fngjqhpwsz8vcyf1k9fhcjk7dw-soft-serve-0.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A soft-serve https://github.com/r-ryantm/nixpkgs/archive/bbdaab12e6ca7a9f3bd20323252c67b747beb041.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h5ad14fngjqhpwsz8vcyf1k9fhcjk7dw-soft-serve-0.4.0
ls -la /nix/store/h5ad14fngjqhpwsz8vcyf1k9fhcjk7dw-soft-serve-0.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

soft-serve

Maintainer pings
cc @penguwin for testing.

Result of nixpkgs-review pr 186014 run on x86_64-linux 1

1 package built:

soft-serve


vdexExtractor cannot use in Android 10，can you help me？

Hello, thank you very much for developing such a great tool, vdexExtractor.
However, I recently discovered that , I am using "adb pull /system/framework/*.dex", and then using vdexExtractor can't get the dex file on Android 10. The boot-framework.vdex are small on Android 10, but the boot-framework.oat and boot-framework.art files are big, it is strange.
In addition, I cannot use jadx to open the /system/framework/framework.jar file directly.
The framework.jar contains 4 dex files. Decompressing the framework.jar to export the dex, I also cannot use jadx to view the dex source code.it makes me upset.
can you help me solve this problem?

the rom http://bigota.d.miui.com/V<IP_ADDRESS>.QFACNXM/miui_CEPHEUS_V<IP_ADDRESS>.QFACNXM_035a571448_10.0.zip

May be there's no dex file in vdex file ?
Android 9 introduced uncompressed dex,  and for Android 10, most of the boot dex files are not compressed in the jar files.
For such kind of jars, dex2oat will not re-write dex file to vdex files.

in my case, the same problem.
android 8, the vdex_extractor operates well.
but Android 9~10 this vdex_extracotr is not doing well!
always this log print
ERROR] Unsupported Vdex version
[WARNING] Invalid Vdex header - skipping './Pixel/framework/arm64/boot-ims-common.oat'

i also can't run it on Android 10,
can you help?

me too


I couldn't run fastlane init

New Issue Checklist

[Done] Updated fastlane to the latest version
[Done] I read the Contribution Guidelines
[Done] I read docs.fastlane.tools
[Done ] I searched for existing GitHub issues

Issue Description
I got this error when I ran fastlane init command.
[16:45:38]: the tool automatically for you. Have fun!
[16:45:38]: $ xcodebuild -showBuildSettings -project ./.xcodeproj
[16:45:48]: Command timed out after 10 seconds on try 1 of 4, trying again...
[16:45:58]: Command timed out after 10 seconds on try 2 of 4, trying again...
[16:46:08]: Command timed out after 10 seconds on try 3 of 4, trying again...
[16:46:18]: Command timed out after 10 seconds on try 4 of 4
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

[INSERT OUTPUT HERE]
Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.6

Ruby
2.2.4

Bundler?
false

Git
git version 2.13.3 (Apple Git-91)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.12.6 (16G29)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode-beta.app/Contents/Developer/

Xcode Version
9.0

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.53.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
1.11.1

xcpretty
0.2.6

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

excon
0.55.0

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.0.3

uber
0.0.15

declarative
0.0.9

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.12.0

json
1.8.1

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

generated on: 2017-08-21

Please run `fastlane env` and copy the output below. This will help us help you :+1:
If you used `--capture_output` option please remove this block - as it is already included there.
[INSERT OUTPUT HERE]

Thanks for contacting us about this! This is a known issue with Xcode 9.0 beta 5 and earlier.  You can learn more about the issue here:
https://github.com/fastlane/fastlane/issues/9983#issuecomment-323542197
The good news, however, is that we are fairly certain that Xcode beta 6 (released today) has fixed this issue! Give it a try and let us know if it helps. 🚀

It works. Thanks a lot.

Great news - so glad to hear it is working for you!
I'm going to close this issue now - please let us know if you have any other questions about fastlane!  🚀


Initial configuration for Rails cache

Use Redis for caching in production and staging, with an appropriate
connection pool size
Use null_store in test to ensure nothing gets cached
Use Redis for caching in development if caching is enabled (for
parity with production)

Review app deployed to https://teaching-vacancies-review-pr-2758.london.cloudapps.digital


Migrate locality lookup from Mapzen to the Fortis Feature Service

This is implemented in Fortis-Spark via the FeatureServiceClient.


Enhance compatibility of emscripten built codecs with Cloudflare Workers

Currently using the packages for avif, jpeg and webp would require workarounds at build time to work in Cloudflare Workers. This was shown in the Cloudflare Worker Example.
It required:

Polyfilling the ImageData class into the global scope
At build time replacing import.meta.url and self.location.href values.

This added the burden onto consumers of these packages and was highlighted in issues #20 and possibly #18
This PR:

Adds a pre script that polyfills these values in the Emscripten Module glue code at runtime – only when run in a Cloudflare Worker
Updates the examples to work with the latest module versions

When decoding or encoding using the png module, the object globalThis.ImageData will need to be polyfilled too. I don’t see the script pre.js being included in the module, I suppose this needs to be included in the source and also in Makefile?
Tested this on my machine by polyfilling it manually in my project, not sure how cpp works so I have no idea how to make a PR.

Thanks for bringing that to my attentioin @sengho66, the png module is Rust based and so doesn't follow the usual emscripten approach.
I've created an issue (#25) and will follow up when I get a chance.

@sengho66 I've released v2.1.0 of @jsquash/png, let me know if that works for you 🙇

@sengho66 I've released v2.1.0 of @jsquash/png, let me know if that works for you 🙇

Thank you, will have a look when I have the chance.
Also I am quite new to the open source scene, not sure if it’s alright to ask non-related question in a specific topic.
When importing the compiled binary of the webp’s wasm module directly, Typescript will warn you that module is not found because webp_enc_simd.wasm.d.ts doesn’t exist. I have written a script in Rust to emit the declaration by reading into the binary and then parse them and create a d.ts for it. However the names are mangled because of some of the clang flags tell the compiler to minify the emscripten’s code so the emitted declaration’s name will be weird. Do you happen to know how to have clang or emcc not to mangle and preserve the function name? Again, I do not know anything about cpp or emcc.
Thanks!

When importing the compiled binary of the webp’s wasm module directly, Typescript will warn you that module is not found because webp_enc_simd.wasm.d.ts doesn’t exist.

You must be using some kind of bundler with your Frontend application, as normally you can't import wasm binaries directly. The easiest way to type it would be to cast it to WebAssembly.Module.

I have written a script in Rust to emit the declaration by reading into the binary and then parse them and create a d.ts for it.

This sounds very complicated 😅 . Would a simpler solution work? As you're likely using it with the generated glue code they're already typed as part of this library. See packages/webp/codec/enc/webp_enc.d.ts


Runewords should be Sortable

Sort by

Level
Name

Runewords are sortable using the following functions

sortWords(words, 'level')
sortWords(words, 'name')


GeoStream is not assignable to parameter of type 'GeoRawProjection' in d3 API version 4

In d3.geo API 3, it has the function to project the geo location coordinates onto the map like leaflet.
for example the code in version 3 is like
var transform = d3.geo.transform({point: self.projectPoint});
self._path = d3.geo.path().projection(transform);
projectPoint: function(x, y) {
var point = MELBPARKING.Map.map.latLngToLayerPoint(new L.LatLng(y, x));
this.stream.point(point.x, point.y);
}
Now I use the angular2 framework to build the leaflet map to project the coordinates in D3.js, the D3.js 's API is built upon the version 4. I looked into the D3.js 's library, the geoTransform and geoProjection are exported
export {default as geoTransform} from "./src/transform";
export {default as geoProjection, projectionMutator as geoProjectionMutator} from "./src/projection/index";
In my angular2 project, I used d3.js and leaflet.js to build a leaflet map component, shown as below
import * as L from 'leaflet';
import * as d3 from 'd3';
import {geoTransform,geoProjection} from "d3-geo";
export class MapsComponent implements OnInit {
map;
_path ;
ngOnInit(){
console.log('init map');
      his.map = L.map('mapid', {
      center: L.latLng(38, 15),
      zoom: 5,
      });
this.map.setView(L.latLng(-37.81108500,<PHONE_NUMBER>0), 18);
var self = this;
var transform = geoTransform({point: self.projectPoint})
console.log(transform);
self._path = geoProjection(transform);
}

projectPoint(x, y) {
     var point = this.map.latLngToLayerPoint(new L.LatLng(y,x));
     this.map.stream.point(point.x, point.y);
}

}
However the project met an error as below
ERROR in /maps.component.ts (87,32): Argument of type '{ stream(s: GeoStream): { point: (x: any, y: any) => void; } & GeoStream; }' is not assignable to parameter of type 'GeoRawProjection'.
Type '{ stream(s: GeoStream): { point: (x: any, y: any) => void; } & GeoStream; }' provides no match for the signature '(lambda: number, phi: number): [number, number]'.
what is the wrong

please close this issue, a duplicate of https://github.com/d3/d3-geo/issues/111


automated tests

we need automated testing for the theme.  example use cases:
unit scenario
when tile.j2 macro is used to create a UI component but the required tile attributes are not included, no UI component is rendered
integration scenario
when palette: dark is set in mkdocs.yml, then dark.css should be loaded
i don't have a lot of experience doing automated testing for frontend projects so any help here would be extremely appreciated.  even just a pointer in the direction of a simple example project would be helpful.

https://stackoverflow.com/questions/42090084/how-can-i-unit-test-the-jinja2-template-logic

https://alexharv074.github.io/2020/01/18/a-method-of-unit-testing-jinja2-templates.html
and
https://github.com/alexharv074/jinja2-unit-testing

ansible? https://stackoverflow.com/questions/35407822/how-can-i-test-jinja2-templates-in-ansible

https://github.com/pallets/jinja/blob/main/tests/test_tests.py

set up initial test suite (see #58)

major improvements in https://github.com/ntno/mkdocs-terminal/pull/72

refactored partials to allow for better unit testing
added unit tests for theme features (navigation hiding, palettes, search button)

see examples for mocking singleton, mocking object attributes in #88

seems in pretty good shape at this point
TODO: update text in contributor guide to reflect this


Make Error::inner_message universal

Closes #162

I fixed a red test, can you please have a look @kornelski?


New designated initializer.

I did changes to my pull request.
First of all, I rebased it, so now it contains only one commit.
Second, I did the following changes, as we discussed with BamX and Kevin.

dataPath is now readonly public.
designated initializer changed to - (id)initWithLanguage:(NSString *)language configDictionary:(NSDictionary *)configDictionary configFileNames:(NSArray *)configFileNames dataPath:(NSString *)dataPath engineMode:(G8OCREngineMode)engineMode NS_DESIGNATED_INITIALIZER;
where configDictionary is a dictioanry of the config variables and configFileNames is an array of file names containing key-value config pairs. All the config variables can be init only and debug time both. Furthermore they could be specified at the same time, in such case tesseract will get variables from every file and dictionary all together.
To avoid ambiguity with Apple Naming Conventions the following functions were renamed:

setUpTesseractToSearchTrainedDataInTrainedDataFolderOfTheApplicatinBundle (only setters should start with set)
initEngine (only initializer should start with init. in such case the function should return id)
copyDataToDocumentsDirectory (if function starts from copy, the special rules are implemented by ARC to the function)

if the dataPath is specified, the whole content of the tessdata from the application bundle is copied to the Documents/dataPath/tessdata and tesseract is initialized with that path.
_dataPath is replaced with self.dataPath everywhere besides init method.

Finally, I'm not familiar with the Kiwi, so I'm not able to write down unit-tests righ now.
Therefore, I would appreciate, if you'll do some unit tests for these changes, while I do study the Kiwi.
That will help me to check my on Kiwi code and increase my unit-tests developing in the future for the project.
Thanks and looking forward for any more comments about the feature.

ok. That's the final commit.
Now it contains all the test @kevincon mention in the beginning.
It also closes a lot of tasks.
So, @kevincon, could you please close related issues and change the wiki to show the latest changes?

Well done! Let me know what you think about the comments I left about some of the code, but other than taking care of those items, or if @BamX has any other thoughts, I think it's ready to merge.
By the way, I'm not sure if any of the code in this pull request changes the example code in the Using Tesseract Wiki page: https://github.com/gali8/Tesseract-OCR-iOS/wiki/Using-Tesseract-OCR-iOS Was there something in particular you wanted me to change?
Once we merge I'll take care of closing the related issues.

@kevincon, I think it's good idea to mention our new functionality in the wiki page.

New initializer with an ability to start tesseract from the Caches folder. Where the lang files could be downloaded by the user in runtime. And where they are symlinked from the app bundle, if exists in app bundle.
An ability to specify init only tess variables from the dictionary, one or more config files or even both.
An ability to get variables already set for tess.

Okay I agree, I'll work on those Wiki items when I get home (on the train right now).

Okay here's the new Wiki page: https://github.com/gali8/Tesseract-OCR-iOS/wiki/Advanced-Tesseract-Configuration
Let me know if you think it looks okay, and then I'll go ahead and close related issues and merge.

Seems very good. Just one note. Could you explain, that all the config files specified for the tess should be located in the 'tessconfigs' or 'configs' subfolders of the 'tessdata' folder?

Ah right, I thought it wasn't required, but from the man page I see that it is. I've updated the Wiki page to reflect that now.

Thanks a lot!

Okay, merging and closing. Thanks @ws233 and @BamX!

yahooo! :)
thx you too!


Ambassador Doesn't Fire when Wait For Headshot is on.

As title says, ambassador waits infinitely and never shoots, when the option is turned off the ambassador works fine.

Fixed in https://github.com/tf2cheater2013/Fedoraware/commit/071b757141ac7f1abf4d70f0c07ea663cd24e3df


V2.2.1

Upstream 2.2.1, and bump boost dep.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


I qts copy test

Trello card
Context
Changes proposed in this pull request
Guidance to review

@peteryates if you have time to show me how to create an accordion that would be fab. For example 'Help with qualifications' could go into one

PS @peteryates @gemmadallmandfe this page isn't for publication yet but for user testing on Monday :)
Thank you

@laurahermionetennant92 This hasn't deployed properly to the Review app - you need to change any internal links to remove the domain eg
FROM https://getintoteaching.education.gov.uk/steps-to-become-a-teacher
TO /steps-to-become-a-teacher

Thanks @gemmadallmandfe I think I've done that!

Changed to draft - this is for user testing only and should not be merged into production

@laurahermionetennant92 Couple of things that jump out from having a quick look:

you've got multiple h1s (#) on the page - they all need changing to h2s (##) and subsequent headings need moving down a level too
I think the reason that the heading styling is different from your other international page (eg blue h2s) is that there is an article class of longform in the frontmatter
the link on the email at the end doesn't work - it opens Gmail. You don't need to add a link manually here - it will automatically be recognised as an email address

@EllieNodder I have made some updates and taken in your suggestions (thank you) – can we hop on a call today/tomorrow to look at the design (mainly thinking of how we can compress the sections as per this page https://getintoteaching.education.gov.uk/international-returners)
Thank you :)

@EllieNodder I have made some updates and taken in your suggestions (thank you) – can we hop on a call today/tomorrow to look at the design (mainly thinking of how we can compress the sections as per this page https://getintoteaching.education.gov.uk/international-returners) Thank you :)

Will loop @Tomcowan1 into this call as he'll have a better idea about this than me! Will book some time into our calendars :)

Hi @EllieNodder thanks for your help earlier – I've fixed those typos and the jump link. It would be great if you could look at the design and create a sidebar with our contact email. Look forward to speaking next week :)

Hi @peteryates, thanks for all your work on this.
Would it be possible to make the jump link from eligibility criteria open up the relevant accordion?

Jump link from participating providers needs to open up the accordion labelled Choose your iQTS teacher training provider.

When I click on these external links and then back again, the accordion has closed up, making it hard to find where I was – can this be fixed?

Hi @laurahermionetennant92 I've confirmed with @peteryates that the accordions would need dev work to work in the ways you suggest - so they are what they are for the time being, I'm afraid!
At some point we will review accordion design and usage more widely across the site
In the meantime, let me know when you are ready for the page to be published
As mentioned, we have amended the URL slightly; if you have referred to the previous URL in any marketing materials, just let us know and we'll set up a redirect

@peteryates please could you look at my latest commit, it's not displaying on the review page...thank you!


Question: is there a way to parameterize the queue for an action notification of a policy?

I have been experimenting with email notifications with policies, and the process is working well.  However, I'd like to not have to explicitly imbed the queue name in every policy definition, as we'll be deploying the same set of policies in several accounts, and each has its own queue.  The queue is the same as what is associated with the Custodian Mailer Lambda function that is running in each account.
We'd ideally like to keep the accounts completely separate (not share a queue across accounts).  Is there a way to parameterize this, use an environment variable, etc. so that I don't hard code it into each policy?  Or - if it can be fetched from the value set for the Custodian Mailer function, that would be ideal as well.  Any advice would be greatly appreciated.

while i've been resistant to variable interpolation in config files, this is probably an appropriate use case to enable better policy reuse. env vars are a little implicit and have implications on the various runtime modes we support. i think we can probably extend run cli with --vars and take a vars file with some simple value interpolation, no loops or conditionals though, probably doing interpolation pre yaml load. when we bake policy for lambda execution we'll bake in a post interpolated version.
alternatively generating your config with the interpolation out of band. also while not the same worth looking into advanced yaml syntax for avoiding repetition of common blocks (anchors and aliases).

Ultimately what I'm doing is providing templates for account owners to run if they'd like to - and my plan will be to give them scripts to create a role and queue ahead of time.  So in the end, for every account there is a cloud-custodian-role and a cloud-custodian-queue but since the full arn is required each time (which includes the account number) that is where I need the parameterization.  Since I can pass in the arn for the role, I'm OK, but I can't do that for the queue.  If there was a way for the arn to be generated based upon the account, that would also fully solve it for me.  By the way, I think this is a really terrific, powerful tool.  I'm really enjoying working with it thus far!

filed as separate issue (#938) for variable interpolation.

fwiw account queue arn does now support account id variable interpolation.

Kapil,
Can you please direct me to the doc for this, or provide a sample?  I'd love to use this.
Thanks,
Carrie


⚠ Bofrost.lu has degraded performance

In be72021, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1255 ms

Resolved: Bofrost.lu performance has improved in d05414c after 6 minutes.


Transifex push action is failing

Tx push action is failing, see https://github.com/qgis/QGIS-Website/actions/runs/2977249556
Any idea?
Originally posted by @rduivenvoorde in https://github.com/qgis/QGIS-Website/issues/1048#issuecomment-1235155988

@rduivenvoorde not sure how the missing file documentation.pot is supposed to be created?

source/site/forusers/documentation.rst was removed in 8c9bdb0252d262a70998764b4353d960f084190a.  363a7a615a5f42ef532a2d9fec3114f0c7c34dd0 removes all files from .tx/config so create_transifex_resources.sh can re-detect them on the fly.


Add Separator to MenuSections

Closes
This is more of a discussion PR.
I want to be able to create Sections in menus which already have a Separator inside of it. I'd also like for the last Section, if trailed by nothing else, not to display the separator.
I contemplated adding renderProps to Sections in order to handle the isLast. I ran into some issues with that, it wouldn't render the entire menu, but no warnings or errors. Instead, I've opted for the moment to force the issue and render nothing in place of the separator if the Section is the last thing in the Menu.
I could add them in an implementation by doing something like
    <>
      <AriaSection>
          {props.children}
      </AriaSection>
      <Divider />
    </>

and then make use of the :last-child psuedo selector
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

I contemplated adding renderProps to Sections in order to handle the isLast. I ran into some issues with that, it wouldn't render the entire menu, but no warnings or errors. Instead, I've opted for the moment to force the issue and render nothing in place of the separator if the Section is the last thing in the Menu.
I could add them in an implementation by doing something like

Maybe a silly point but should we be automatically getting rid of the separator for the last item or could we instead rely on user determine whether or not to include said separator in their render? I can't really think of a reason someone would want a separator following their last section but might be good to allow for that if someone did want to render one.
I'm surprised adding renderProps to the Section broke stuff, not sure why that would be. Did it still have all the proper items in the collection?

@LFDanLu yeah, that's most of the reason I brought up this PR was to attempt to automatically remove the separator for a section if it's the last thing.
In this PR I do not render it.

Shouldn't the separators be between sections not inside them?

Shouldn't the separators be between sections not inside them?

Possibly, I didn't find anything that said you couldn't have separators inside a group though. Only this little blurb, which implies it, but doesn't explicitly say it.

Menu items can be grouped in elements with the group role, and separated by elements with role separator. Neither group nor separator receive focus or are interactive.

And group inherits from section which inherits from structure https://w3c.github.io/aria/#structure which allows for separators

ok but for spectrum the separators are between sections I think. v3 doesn't expose standalone separators.

That's fine, if you try to include it in RAC though, it blows up with an unsupported child node in Section, and that seems wrong


Limit requests sent when opening the connection, by sending initial …

…payload, when first request is being made.

LGTM. Please try to add unit test.

closed and reopened to rerun Travis.

Looks great to me. Can you please rebase and rerun Travis to validate it builds? We upgraded the build tool set 2 days ago.
Thanks for you contributions!


Refactory for client implementation.

Split each interface to steps: validata(opt), pre, rpc, wait_for_status(opt), post(opt)

Signed-off-by: Ji Bin<EMAIL_ADDRESS>

/cc @yhmo

/lgtm


Required laneId during on AddCardLink

In a few cases, laneId is being required on adding a custom AddCardLink component.

@harshaktg hank you for PR!
I think it is enough to change only 201 line in src/controllers/Lane.js to merge this PR

I think we do need the changes in AddCardLink.js file as well @dapi . I've written down a comment for that. Can you check and merge the same?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Call api.visitComponentTree in Vue2's backend api

Referred in #1518
In Vue 2.x projects, backendApi api.visitComponentTree is not called in component tree 's  capture method
If it was not intended to drop this function call by design, then it was a mistake since it never triggers hook.on.visitComponentTree when traversing through the component tree,  leading the userland plugin failed to perform component parsing.
It's deeply needed in our team because we are developing a custom plugin strongly relied to it.
Please consider if it's possible to fix this feature in the app-backend-vue2 package, thanks a lot!

@Akryum Please consider if the bugfix is possible, thanks!


Dockerfile not build

$ git clone https://github.com/APIs-guru/graphql-faker.git
$ cd graphql-faker
$ docker build -t graphql-faker  .

Sending build context to Docker daemon  4.304MB
Step 1/6 : FROM node:8.8.1-alpine
8.8.1-alpine: Pulling from library/node
b56ae66c2937: Pull complete
16e68ed80c6a: Pull complete
4818769bd05b: Pull complete
Digest: sha256:ab9161b1be7ed90f1bcf8d483ef72f138010054732bb12a3288ec679a41f2226
Status: Downloaded newer image for node:8.8.1-alpine
 ---> 04a3ba95f191
Step 2/6 : MAINTAINER James Kyburz<EMAIL_ADDRESS> ---> Running in 5d8869c5a605
 ---> 8c406551f0af
Removing intermediate container 5d8869c5a605
Step 3/6 : RUN apk --no-cache add --virtual native-deps   git &&   npm install graphql-faker -g &&  npm cache clean --force &&  apk del native-deps
 ---> Running in 264c7cee5faa
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.6/main/x86_64/APKINDEX.tar.gz: could not connect to server (check repositories file)
fetch http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.6/community/x86_64/APKINDEX.tar.gz: could not connect to server (check repositories file)
ERROR: unsatisfiable constraints:
  native-deps-0:
    masked in: cache
    satisfies: world[native-deps]
  git (missing):
    required by:
The command '/bin/sh -c apk --no-cache add --virtual native-deps   git &&   npm install graphql-faker -g &&  npm cache clean --force &&  apk del native-deps' returned a non-zero code: 2

Related https://github.com/nodejs/docker-node/pull/367

@arquio I don't use Docker myself and Dockerfile was in community PR I merged.
Can you please explain in more details what's wrong with Dockerfile?
If you know how to fix it PR would be highly welcome ❤

@IvanGoncharov I'll try when be solved the problem with the simple image "alpine".
At the moment, I did a very simple Dockerfile for us labX in https://github.com/travelgateX/labX-graphql-benchmarks/tree/master/team-resources/task2-server
Thanks for all!

This should be resolved through #44. Also, you do not have to build the image yourself, there is an automated build at https://hub.docker.com/r/apisguru/graphql-faker/

Thanks @spawnia
@arquio I will close this issue but feel free to reopen if you still have this problem.


Add a check-only mode or action

In some workflows, there are jobs whose only purpose is to ensure that proper cache state exists for other jobs to pick up. If such a job hits an already stored state, downloading that state for this job only wastes time and network bandwidth because the job does not need to do anything. Here's an example.
It would be nice to add a mode that only checks existence of the key and sets the cache-hit output.

Have similar case.
We have workflow with unit tests parallelized using the matrix.
In order to run bundle install just once (and not in each of the parallel jobs), we have first job that builds the cache (ie installs the ruby bundle).
If the cache is already hit, we don't need to download it, because the second step in the job have if: steps.bundle-cache.outputs.cache-hit != 'true'
As @mzabaluev mentioned, having option to only "check" the cache hit / skip the download if cache is hit, would save bandwidth and time

I assume you would want the cache to still save. I can not think of any reason to want a check-only mode, where it doesn't save either unless you're going to define two cache steps in your job and you're going to make the second depend on the first's check result but that seems more cumbersome and slower than just a save-only-if-changed mode.
A save-only-if-changed mode also seems kind of confusing, because what if for some other reason you still don't do your build and now it saved under the key? You now have a broken cache. You can't put the saving under the if-cache hit-condition as that's a post run and uncontrollable.
I'm thinking for advanced usages perhaps it would be better to split the cache action into 3 parts where you have to manually add a save step whereas the standard cache action does that automatically. The 3 parts would be cache-check, that only peeks and does nothing else, cache-restore that only restores for a read-only mode, and a cache-save for storing changes. Then you can do a job with the steps:

cache-check
build (if !cache-check.cache-hit)
save  (if !cache-check.cache-hit)

That seems easier to follow and maintain when you want to optimize for performance beyond what the standard cache action (restore+saving) does.
(it's also quicker in case the post-if is useless as just parsing and executing a JS post run that does nothing can take 10 seconds)

I have a save-only flag implemented here: https://github.com/MartijnHols/cache/tree/feature/save-only, just waiting for #474 to be merged before making a PR since that branch includes those changes.

My project has to compile PHP (~5min) and then run tests using the built PHP binary (<1min), and a failure of the tests results in the PHP build cache not being stored. This is a problem when the failing build wanted to create a new cache because it adds 5 minutes to each failing build for no reason.
My solution for this problem is the same as OP's: have a leading build job whose only job is to prime the cache if it doesn't exist.
This would benefit from being able to just check if a cache exists without downloading it.

Still needed.

I'm thinking for advanced usage perhaps it would be better to split the cache action into 3 parts where you have to manually add a save step which the standard cache action already does automatically but in a less transparent way. The 3 parts would be cache-check, that only peeks and does nothing else, cache-restore that only restores for a read-only mode, and a cache-save for storing changes. Then you can do a job with the steps:

cache-check[build]
build (if !cache-check.cache-hit)
cache-save[build] (if !cache-check.cache-hit)

That seems easier to follow and maintain when you want to optimize for performance beyond what the standard cache action (restore+saving) does.
(it's also quicker in case the post-if is useless as just parsing and executing a JS post run that does nothing can take 10 seconds)
If your test suite uses the build you'd do:

cache-restore[build]
test

(now you wouldn't want to save, especially if your job (here "test") runs the risk of mutating your build)
And if you want to always restore and save you could do either:

@actions/cache[node_modules]
yarn install

or

cache-restore[node_modules]
yarn install
cache-save[node_modules]

For the same effect.

I made this and use it daily: https://github.com/MartijnHols/actions-cache#readme

@MartijnHols Any reason why you haven't turned your fork into a PR on @actions/cache with simply more inputs keys?

All my previous PRs were ignored

Could really benefit from this in my team's current setup.  We have a setup workflow which primes the cache when needed for subsequent workflows, but setup itself doesn't need to spend time downloading the cache.
This setup workflow itself should ideally only do two things:

cache hit - skip cache download and complete workflow so subsequent jobs can run
cache miss, so regenerate cache

Right now there's no way to skip the cache download in step 1.  If we could skip it would shave off ~20 seconds of unneeded download time in the setup job itself.

For anyone looking, this is now available with the lookup-only option


Pipelines restart slowly

Currently if you have a pipeline that has completed N jobs, and you restart pachd, it will take O(N) time before the pipeline can pick up from where it left off and start spawning new jobs.
This is because the pipeline essentially needs to "reprocess" all jobs, except that the jobs that have been completed are not actually run again.  But still, it can take a while if N is large.  In a deployment I'm looking at, it took more than an hour for five pipelines that collectively have about 4k jobs to restart.

Should be fixed by 1.7 / commit invariance

I'm still having this problem in pachyderm 1.10


Add The Knests Stack under Project Starters

Github repo: https://github.com/tudorconstantin/knests/
Introductory blog post: https://programming.tudorconstantin.com/2020/05/the-knests-stack.html

added. Thank you @tudorconstantin


Fixed the typo issue with example query

@sapinderpalsingh : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thank you, @sapinderpalsingh! #sign-off


Use prefixMessages in ChatOpenAI

Fixes #2913

Why not just pass a ChatPromptTemplate?

Thanks for the PR! Why not just pass a ChatPromptTemplate?

Sorry, still very new to langchainjs... could you elaborate a bit more? I'm just trying to add what OpenAIChat had and is missing here. prefixMessages param is current unused.

Check out: https://js.langchain.com/docs/modules/model_io/prompts/prompt_templates/#chat-prompt-template

Thanks for the link. I understand chat prompt template, but I'm not sure what you are suggesting that I do with it.
I'm trying to use the plan and execute agent with the ChatOpenAI model. I found two ways to get a system message to the agent.

chat model instantiation with prefix messages (while ChatOpenAI accepts the param, but it doesn't use it like OpenAIChat)
create my own planner instead of using the default one so I can supply my own prompt to the llm chain

Ah gotcha - option 2 is a better choice for this actually.
We'll be looking into improving our agent docs in general (CC @bracesproul). Going to close this for now.


webpack2: is not a loader (must have normal or pitch function)

I have got the following error with  webpack2 and json-loader
(node:38655) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 31): Error: Module '/node_modules/json-loader/index.js' is not a loader (must have normal or pitch function)

What does it mean?

What versions of webpack and json loader are you using.

<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>All dependencies
```js
{
	"dependencies": {
		"camelcase": "^3.0.0",
		"normalize.css": "^4.2.0",
		"debug": "^2.2.0",
		"decko": "^1.1.3",
		"fuse.js": "2.5.0",
		"react": "^15.3.2",
		"react-dom": "^15.2.1",
		"react-redux": "^4.4.5",
		"react-iframe": "^0.0.4",
		"react-addons-css-transition-group": "^15.3.2",
		"react-bem-helper": "^1.1.0",
		"redux": "^3.0.5"
	},
"devDependencies": {
	"chrome-stub": "1.5.0",

	"autoprefixer": "^6.5.1",
	"precss": "^1.4.0",
	"enzyme": "^1.1.3",

	"istanbul-instrumenter-loader": "^0.1.3",
	"babel-preset-airbnb": "^1.0.1",
	"babelify": "^7.2.0",
	"browserify": "^13.0.0",
	"babel-runtime": "^6.3.19",
	"babel-plugin-espower": "2.3.1",
	"karma": "^1.3.0",
	"karma-mocha": "^1.2.0",
	"karma-coverage": "^1.1.1",
	"karma-webpack": "^1.8.0",
	"karma-spec-reporter": "0.0.26",
	"karma-sourcemap-loader": "0.3.7",
	"karma-phantomjs-launcher": "1.0.2",
	"karma-babel-preprocessor": "6.0.1",
	"karma-browserify-preprocessor": "0.2.0",
	"mocha": "^3.1.2",
	"phantomjs-prebuilt": "2.1.13",

	"babel-core": "^6.17.0",
	"babel-loader": "^6.2.5",
	"babel-eslint": "7.0.0",
	"babel-preset-es2015": "^6.16.0",
	"babel-preset-es2016": "^6.16.0",
	"babel-preset-es2017": "^6.16.0",
	"babel-preset-react": "^6.16.0",
	"babel-preset-react-hmre": "1.1.1",
	"babel-plugin-transform-object-rest-spread": "6.8.0",
	"babel-plugin-transform-decorators-legacy": "1.3.4",
	"babel-plugin-transform-react-remove-prop-types": "0.2.10",

	"isparta": "^4.0.0",
	"express": "^4.13.3",

	"eslint": "^3.8.1",
	"eslint-loader": "^1.6.0",
	"eslint-config-pobedit": "^0.0.5",
	"eslint-friendly-formatter": "^2.0.6",
	"eslint-plugin-react": "^6.4.1",
	"eslint-plugin-babel": "^3.3.0",

	"react-addons-test-utils": "^15.3.2",

	"react-transform-hmr": "^1.0.4",
	"react-dev-utils": "^0.2.1",
	"redux-devtools": "^3.3.1",
	"redux-devtools-dock-monitor": "^1.1.1",
	"redux-devtools-log-monitor": "^1.0.11",
	"redux-devtools-inspector": "^0.8.0",
	"redux-logger": "^2.2.1",
	"redux-thunk": "^2.1.0",
	"redbox-react": "^1.2.10",
	"react-transform-catch-errors": "^1.0.2",

	"webpack": "^2.1.0-beta.25",
	"webpack-dev-middleware": "^1.2.0",
	"webpack-hot-middleware": "^2.2.0",
	"webpack-bundle-size-analyzer": "2.2.0",
	"webpack-visualizer-plugin": "0.1.5",
	"clean-webpack-plugin": "^0.1.13",
	"unused-files-webpack-plugin": "^3.0.0",
	"extract-text-webpack-plugin": "^2.0.0-beta.4",
	"optimize-css-assets-webpack-plugin": "^1.3.0",
	"imports-loader": "^0.6.5",
	"json-loader": "0.5.4",
	"find-cache-dir": "0.1.1",
	"stats-webpack-plugin": "0.4.2",
	"postcss-loader": "^0.9.1",
	"postcss-import": "^8.1.2",
	"base64-inline-loader": "^0.0.1",
	"css-loader": "^0.23.0",
	"style-loader" : "^0.13.0"
}

}
</details>

I have the same issue with custom loader which is just a simple function like:
function codeGenerationLoader(input) {
  const output = //create string output
  return output;
}

module.exports = codeGenerationLoader;
module.exports.default = codeGenerationLoader;

initial run for the loader works as expected but recompilation in the watch mode fails with the same with error message is not a loader (must have normal or pitch function). I'm also using webpack beta.25

I don't know what happened, but I suddenly started to get this error with regards to html-webpack-plugin/lib/loader. Can't build or anything. Any ideas?

OK, I found out the culprit of the problem, here's a PR: https://github.com/webpack/loader-runner/pull/7.
Why is the async System.import tried BEFORE a NodeJS require, anyway?

I am getting this error (trying to upgrade a project to latest webpack) but have no idea what it means or what to do about it... A link to any docs would be very welcome here as this issue is the top result in Google when searching for the error message.

The reason is likely that you forgot to explicitly add the -loader extension to the configuration of your loader.
See the migration guide.
A more helpful error message would be welcome though.

The reason is likely that you forgot to explicitly add the -loader extension to the configuration of your loader.

Yes! That turned out to be the culprit indeed!
Probably a change for the better.


Be/api fixes

clean up backend code and show coach info in severeal api endpoints
closes #191

@Zelzahn i have merged main into this branch, but since i had rewritten some code i had to delete some of your code from #166 (websockets), specifically in the async_to_sync functions in views.py.
what data needs to be sent in these functions?

The async_to_sync functions are used to send messages to the websockets, do I need to refactor some of this code or can it just be added back in?


Updates the README with links for Solaris/AIX.

/cc @coderanger

:fireworks: :fireworks: :fireworks:


zero Search results

Please provide us with the following information:
Following the thought process of my "Search results," I am getting good expected search results when using the localhost, but when using the public URL (.azurewebsites.net), I get [] empty search results.
I'm not sure what the issue is with it only letting me search and receive good results under localhost.

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

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Is this related to the other issue around global document access, or is it a different issue?


Only download button displayed

Hi, I use version 1.0.2 of pdf-viewer with Vaadin 14.8.4. I try to use it as follows, but only download button, which works, shows up:
PdfViewer pdfViewer = new PdfViewer();
pdfViewer.setSizeFull();
try {
    InputStream inputStream = new URL("https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf").openStream();
    StreamResource resource = new StreamResource("file.pdf", () -> inputStream);
    pdfViewer.setSrc(resource);

    getContent().add(pdfViewer);
} catch (IOException e) {
    e.printStackTrace();
}

I am adding it to VerticalLayout which has full width set.
Any ideas? Am I doing something wrong?
Thank you

Update: I switched to Vaadin 23.1.1 with pdf-viewer version 2.1.0. Issue still remains, only download button is displayed.

Hello @Wlad-K.  Is there any console error displaying?  I did a local test and everything seems to work okay. Here's my test project: v23-pdf-viewer-test.zip Can you tell me if there's something else I'm missing there so I can reproduce your issue?

Hello @paodb, your project is working.
I turned log level to DEBUG, but unfortunately there is no log. Neither on backend nor browser console any error/warning is shown. Any idea how to investigate it more?

Hi @Wlad-K, what about browser console? any error there? Can you reproduce the issue in a simple project and share it with me so I can take a look?

In the end what helped was to add pdf-viewer package in the @EnableVaadin() annotation in one of the modules we have.


[CH6750] search autocomplete support

Added methods to support the following search REST endpoints and autocomplete REST endpoints
getSearchResults => GET https://ac.cnstrc.com/search/[query]
getAutocompleteResults => GET https://ac.cnstrc.com/autocomplete/[query]
24 tests added covering search method and associated parameters listed above, executing in ~9 seconds.
16 tests added covering autocomplete method and associated parameters listed above, executing in ~7 seconds.
Functional changes:

c version parameter is now passed along with all requests with the exception of GET synonym group(s) and GET redirect rule(s) as they will not accept requests containing this parameter
Log error to the console if apiKey or apiToken is not provided
s and i parameters are required and validated on all requests against autocomplete and search
ui and us parameters are validated if provided on all requests against autocomplete and search
Track functions removed

@sblaurock if possible, don't use autocomplete_section and use section instead everywhere.


Fillna doesn't work when series object is an argument

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Modin version (modin.__version__):
Python version:
Code we can use to reproduce:

import modin.pandas as pd

df = pd.DataFrame({'a': ['a'], 'b': ['b'],}, index=['row1'])
df['c'] = pd.NA
df['c'] = df['c'].fillna(df['b'])   # df['c'].fillna('c') works fine
print(df)

Describe the problem

when fillna is called with series object as argument seems nothing happens while pandas does actual na replacement
Source code / logs

After this commit, _copartition function is called in binary_op also for columns, which still does reindexing, however, for some functions this action is superfluous, for example, in the case of fillna.
Should we make reindexing optional or make a second _copartition call optional? cc @prutskov

@anmyachev, according to our patterns of parallel execution partitioning of operands must be aligned by both axis for binary operator (https://modin.readthedocs.io/en/latest/flow/modin/core/dataframe/algebra.html#binary-operator).
The issue @Garra1980 mentioned is reproduced with Modin version before commit with adding cell-wise execution.
The root cause of issue is operation df['c'].fillna(df['b']) is performed on separated Series objects without full knowledge about the dataframe. The same flow we can reproduce using pandas:
import pandas as pd

df = pd.DataFrame({'a': ['a'], 'b': ['b'],}, index=['row1'])
df['c'] = pd.NA

ser_left = pd.Series([pd.NA], name="c")
ser_right = pd.Series(["b"], name="b")
df['c'] = ser_left.fillna(ser_right)
print(df)

So, probably we need to change the implementation of fillna for such case.

The issue @Garra1980 mentioned is reproduced with Modin version before commit with adding cell-wise execution.

Yes, there is another problem that I know how to fixed. The problem is that in our internal implementation we use single-column dataframes, which behave differently from the behavior of Series. Some example here:
import pandas as pd

df = pd.DataFrame({'a': ['a'], 'b': ['b'],}, index=['row1'])
df['c'] = pd.NA
print(df['c'].fillna(df['b'])) # works as `df['c']` is a Series in pandas implementation
# attempt to emulate Modin internal behavior
print(df[['c']].fillna(df[['b']])) # all objects here are one-column Dataframes and this's not work

Your example isn't working because you need to specify index for Series:
ser_left = pd.Series([pd.NA], name="c", index=["row1"])
ser_right = pd.Series(["b"], name="b", index=["row1"])

Apparently the only option left is to make reindexing optional.

Your example isn't working because you need to specify index for Series:
ser_left = pd.Series([pd.NA], name="c", index=["row1"])
ser_right = pd.Series(["b"], name="b", index=["row1"])

Thanks for catch!

Apparently the only option left is to make reindexing optional.

Could you please describe what "reindexing" do you mean?

Could you please describe what "reindexing" do you mean?

_copartition calls _join_index_objects, which finds the common index to cast the left and right operand to, but for fillna doesn't need to do this (this is True for column reindexing). You can see my changes in https://github.com/modin-project/modin/pull/4674.