text:
[NeuralChat] add time tracer decorator

Type of Change
feature
Description
This is to mimic LangChain's LangSmith View Trace functionality.
That is, with one line simple decorator on one method, you can use this to

[x] print the time that method use
[x] print the caller and callee dependencies of all tracer nodes in a tree structure

To use it, simply decorate the method you want to trace with
@tracer.time_tracer
def your_func_here_xxx():
        .......

The benefit is that this will not involve a lot of redundant modification to the original code.
Expected Behavior & Potential Risk
Expected: for example, by adding @tracer to the following four functions, here we can track the time used by those four with a structure:
create_chat_completion: 50.53 seconds
|-----> get_generation_parameters: 0.0 seconds
|-----> generate_completion: 50.46 seconds
|----------> predict: 50.46 seconds

Risk:
called methods using asyncio or independent threads will interfere the inspected call stack so the dependencies tree structure cannot be captured correctly, but time printing should still work.
Concurrent access to the same tracer instance may not work
How has this PR been tested?
Current not added
Dependency Change?
None

Will try to leverage existing interface. Close this PR for now.

repo: intel/intel-extension-for-transformers


text:
FedCurv algorithm

Implements "Federated Curvature" algorithm from paper: Overcoming Forgetting in Federated Learning on
Non-IID Data.
Closes #66.

TensorBoard

Jenkins please retry a build

Experiments results:

Graphs show that FedCurv with lambda equal to 10 performs better than FedAvg in terms of accuracy, and some other lambda values (1000, 10000000).

Experiments results:  Graphs show that FedCurv with lambda equal to 10 performs better than FedAvg in terms of accuracy, and some other lambda values (1000, 10000000).
@itrushkin
Is histology_test_experiment the FedAvg setup?

Experiments results:  Graphs show that FedCurv with lambda equal to 10 performs better than FedAvg in terms of accuracy, and some other lambda values (1000, 10000000).
@itrushkin
Is histology_test_experiment the FedAvg setup?

@alexey-khorkin Yes, correct. Perhaps the difference could be much more visible with rounds increasing.

@igor-davidyuk Re-launched experiment and data is being split and loaded properly.

source: gharchive/pull-request

authors: alexey-khorkin itrushkin

repo: intel/openfl

license_type: permissive

license_source: github-api


text:
markup for warnings

It would be useful to highlight paragraphs as info or warning (as in https://github.com/github/markup/issues/887).
The proposal with embedded :bangbang: in a table was tried, but didn't work with Sphinx (:bangbang: as rendered literally, https://github.com/intel/pmem-csi/pull/715#discussion_r489332503):
### Metrics support

:bangbang: | Metric support is an alpha feature. What data is provided may change.
:---: | :---

=>
Metrics support

:bangbang:
Metric support is an alpha feature. What data is provided may change.

@intelkevinputnam : do you have an idea how to do this?

I don't know of a way to make special characters work for both GitHub and Sphinx. Rather than the emoji, though, you could use **WARNING** or **NOTE**, or **!!**:

!!
Metric support is an alpha feature. What data is provided may change.

restructuredText has "Admonitions" which can be warnings, notes, etc. Markdown doesn't have them out of the box, though. Myst flavored markdown implements reST admonitions with this syntax:
```{admonition} Warning
This is Beta software.
```

In GitHub they look like this:
This is Beta software.

I could probably implement something that works like this in a couple of days. They work OK in GitHub (the notes would appear in code blocks) and would be proper "Notes" and "Warnings" in Sphinx output.

I think **WARNING** and **NOTE** inside a table are good enough, no need to implement any custom syntax support in the publishing pipeline.
@avalluri : agreed?

@avalluri : agreed?

Yes.

This renders poorly in the docsite: https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/job/pmem-csi/job/PR-760/Doc_20Site/docs/install.html#metrics-support
Let's stick with the current approach (**WARNING:** or **NOTE:** at the beginning of a paragraph.

source: gharchive/issue

authors: avalluri intelkevinputnam pohly

repo: intel/pmem-csi


text:
Make a parallel build setup.py

Need to parallelize the build of c ++ code when called python setup.py

i want to work but im new to coding can you refer something so that i can learn about it and fix this issue!
it will great help for ME! Thankyou

hi id like to take this up

ScikitEX-Team1 is working on this.

authors: EstablishedShark GhimBoon PetrovKP ritiksoni00

repo: intel/scikit-learn-intelex


text:
Question regarding renaming core to _core

Hi!
In the https://github.com/numpy/numpy/pull/24634 PR, numpy.core is being renamed to numpy._core which affects .github/workflows/build-numpy.yml file here.
Would renaming core path to _core work here? Or do you need to run the CI against other numpy versions?

@mtsokol thanks for reaching out. I think renaming core to _core would work just fine. I can update our CI once your PR is merged.

Hi @r-devulap, https://github.com/numpy/numpy/pull/24634 has been merged!

thank you. I have updated our CI with that change. See #87

authors: mtsokol r-devulap


text:
Remove non-python requirements

Motivation:
The requirements.txt file is used by python tools (pip, in particular) to describe the python dependencies.
The file current contains non-Python dependencies, which confuses these Python tools.
Modification:
Remove non-Python dependencies from the requirements.txt file.
Result:
The pip install . command now functions correctly.

Summary

Related issue :

Robot Results

:white_check_mark: Passed
:x: Failed
:next_track_button: Skipped
Total
Pass %
:stopwatch: Duration

32
0
0
32
100
19.973304s

Passed Tests

Name
:stopwatch: Duration
Suite

GET USER1
9.549 s
Teapot-Tests

GET USER2
8.475 s
Teapot-Tests

GET NO TOKEN
0.011 s
Teapot-Tests

GET INVALID TOKEN
1.026 s
Teapot-Tests

PUT REQUEST INVALID TOKEN
0.010 s
Teapot-Tests

PUT REQUEST NO TOKEN
0.010 s
Teapot-Tests

PUT REQUEST USER1
0.141 s
Teapot-Tests

PUT REQUEST USER2
0.086 s
Teapot-Tests

GET FILE USER1
0.070 s
Teapot-Tests

GET FILE USER2
0.061 s
Teapot-Tests

GET FILE NO TOKEN
0.010 s
Teapot-Tests

GET FILE INVALID TOKEN
0.010 s
Teapot-Tests

DELETE REQUEST USER1
0.039 s
Teapot-Tests

DELETE REQUEST USER2
0.040 s
Teapot-Tests

DELETE REQUEST INVALID TOKEN
0.010 s
Teapot-Tests

DELETE REQUEST NO TOKEN
0.009 s
Teapot-Tests

GET USER1 EXTRA_AREA
0.038 s
Teapot-Tests

GET USER2 EXTRA_AREA
0.043 s
Teapot-Tests

GET NO TOKEN EXTRA_AREA
0.014 s
Teapot-Tests

GET INVALID TOKEN EXTRA_AREA
0.010 s
Teapot-Tests

PUT REQUEST INVALID TOKEN EXTRA_AREA
0.009 s
Teapot-Tests

PUT REQUEST NO TOKEN EXTRA_AREA
0.009 s
Teapot-Tests

PUT REQUEST USER1 EXTRA_AREA
0.037 s
Teapot-Tests

PUT REQUEST USER2 EXTRA_AREA
0.037 s
Teapot-Tests

GET FILE USER1 EXTRA_AREA
0.060 s
Teapot-Tests

GET FILE USER2 EXTRA_AREA
0.054 s
Teapot-Tests

GET FILE NO TOKEN EXTRA_AREA
0.010 s
Teapot-Tests

GET FILE INVALID TOKEN EXTRA_AREA
0.009 s
Teapot-Tests

DELETE REQUEST USER1 EXTRA_AREA
0.035 s
Teapot-Tests

DELETE REQUEST USER2 EXTRA_AREA
0.035 s
Teapot-Tests

DELETE REQUEST INVALID TOKEN EXTRA_AREA
0.009 s
Teapot-Tests

DELETE REQUEST NO TOKEN EXTRA_AREA
0.009 s
Teapot-Tests

authors: paulmillar vrbanecd

repo: interTwin-eu/teapot


text:
Generating Go code for the API server

schematic works nicely when creating a client.
I think it might be cool to consider generating code for the server too.
The bare minimum would be generating the response structs to serialize responses.
A more ambitious goal would be to generate the main boilerplate to serve the HTTP API: http handlers, helpers to parse requests and render responses, etc.
Maybe even doing something like this:
package main

import (
  "http"
  "github.com/whatever/api/server"
)

func main() {
  // NewHandler takes an object that implements server.Handler and returns an http.Handler
  // server.Handler is generated by schematic and it has one method for each link in the Schema
  h := server.NewHandler(backend{})
  s := &http.Server{Addr: ":8080", Handler: h}
  s.ListenAndServe()
}

+1
It would be great to split this package in two parts. First, a generic JSON Schema  implementation, then the client code generator. That would allow people to easily reuse the first part to generate server implementations.

FYI, there's a new project called goa that generates JSON Hyper Schema from Go code and also generates all the scaffolding to serve the API so you can focus on the business logic.
http://goa.design/index.html

@ernesto-jimenez As far as I can see, though, goa is monolithic, in the sense that it's not possible to generate only the server scaffolding, based only on the hyperschema: the only possible input is goa's own DSL.

@KellerFuchs goa allowed you to generate de JSON Hyper Schema from their DSL, and then you could ideally other tools to generate the client. I believe since my comment back in December goa favoured Swagger more instead, but have not checked it recently :)

@ernesto-jimenez Yes, but this doesn't cover at all implementing an existing Hyper-Schema, or simply wanting to model the API directly during the design phase.
Anyhow, I will likely have a stab at implementing this.

authors: KellerFuchs ant0ine ernesto-jimenez

repo: interagent/schematic

license: mit

license_source: bigquery


text:
Version checker does not check dokku version in a proper way

When you have a dokku 0.7.1 server, we still say that your dokku is out of date.

Duplicate of #194

repo: intercity/intercity-next

license: MIT


text:
The Dashboard URL breaks after updating the page

Can reproduce in pie-server:

Open KPI and Plugins
Refresh page (F5)
Click on folder breadcrumbs KPI & Plugins
Open SQL KPI - the URL gets broken like this: https://pie-chart-bug.demo.community.intersystems.com/dsw/index.html#/IRISAPP/KPIs%2520&%2520Plugins/SQL Based KPI.dashboard

Here is the video: https://www.loom.com/share/5f715cabf9f045858bf622d4fa4a6da2

Works! Fixed in 3.1.68

repo: intersystems-community/DeepSeeWeb


text:
fix: update version of swift-markdown-ui and TCA to fix compile error  of swift 6

Compile error in the latest version's Xcode 16.

Thank you!

repo: intitni/CopilotForXcode


text:
Problem with Twitter permissions (DM)

Hello all!
I got a PHP application which I am trying to switch to Ruby on Rails using this gem.
When I authorize it with my old PHP account it grants the authenticating user permission to read and write direct messages, but when I try to authenticate that same user on the same application, it won't give me those permissions.
I am thinking its an error with this gem because with PHP it worked fine.
Anyone having same issues or have any ideas how to fix this?

Twitter's permissions are handled 100% in the application registration. OmniAuth can't and won't have anything to do with direct message permissions being granted or not for your application. Best of luck figuring it out, though!

authors: garzaa mbleigh

repo: intridea/omniauth


text:
Add Command Line Tool

Adds a basic command-line tool redfinger that just prints out links with some popular rels. It was going to have hCard support until I discovered the blocking issue https://github.com/intridea/redfinger/issues/10

bump?

repo: intridea/redfinger


text:
Update many badges to be accurate colors

Description:

Colors of some badges are not accurate.
Expected:

For the badges to be accurate
Actual Outcome:

Some of the colors are off.
Additional Context:

None

this was started in commit https://github.com/inttter/md-badges/commit/b626a1e6d8697c7e83b1251582a7ee064aa6cf4b.
it was fully completed in commit https://github.com/inttter/md-badges/commit/10f88491d8e911bf6063d63ad394906f9946497a.

repo: inttter/md-badges


text:
Add more values

I work in the automotive industry, and we sometimes have swdp sizes in the added ranges below.

@rajohns08 thanks for your contribution! I will review it and I hope to merge and release it soon. Sorry for the long delay.

@rajohns08 did you use SDPFactory to create the new values? If not, it is better to use it and update the max value from 800 to 1000.

@rajohns08 I had some time to work on it, so I'll do it for both sdp and ssp.

@rajohns08 I'm happy to let you know that now you can see the changes in version 1.1.0, thanks for your contribution!

repo: intuit/sdp


text:
Corrected empty bucket get assignment bug and removed extra method fr…

Empty bucket reassignment bug and removed unused interface method in Assignments.

Looks good, and the unit and integration tests worked locally - it's the EventLog test which fails once again...

Alright, looks good - a few minor nits, but other than that :shipit:.

Changes Unknown when pulling 6d891e500284b1ca14d5af7a7d629772546a1881 on feature/empty-bucket-get-assignment-bug into ** on develop**.

:shipit: !

authors: coveralls mans4singh shoeffner

repo: intuit/wasabi


text:
utils: remove future import

:heart: Thank you for your contribution!
Description
Please describe briefly your pull request.
Checklist
:rotating_light: Please review the guidelines for contributing to Invenio.

[ ] Did you create different commits for logically separate things? Check the format of the commit(s) message(s).
[ ] [InvenioRDM specific] Did you follow the style guide?  Check the documentation.
[ ] [InvenioRDM specific] Did you add translations (i18n) for new labels, backend and frontend? Check the documentation.
[ ] [InvenioRDM specific] Did you add accessibility (a11y) tags? Check the documentation.
[ ] Did you add documentation? We all love well-documented frameworks, right?
[ ] Did you include third-party code (a library, package, etc.)? If yes:

[ ] Make sure that its open source license is compatible with Invenio (note: GPL and AGPL licensed code is not accepted)
[ ] Did you respect the license conditions (normally you need to keep the copyright and license header)?

Green light on all GitHub Actions status checks is required in order to merge your PR. Check your code additions will fail neither code linting checks nor tests and will not decrease test coverage.

External contributors
Copyright

[ ] Identify who is the copyright holder (a legal entity - i.e. person or organization - normally this is your employer) for the produced code.
[ ] Make sure that you have updated the copyright headers for touched files (non-trivial contributions >15 lines).

See copyright and license policy for details.
Reminder
By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

You license your contribution under the same terms as the current repository’s license.
You agree that you have the right to license your contribution under the current repository’s license.

If you ticked all the boxes above, you're good to go! :rocket:

FYI: It's already removed from master

repo: inveniosoftware/invenio-accounts


text:
upgrade: script record upgrade from v4 to v5

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/926

Discussed IRL:
1- Flag check: Do you have subjects or affiliations with more than "name/subject". i.e. will they cause troubles?
2- If yes, give a recipe to fix them
3- If not (or after fix) run the script and assume:
3.1 - id is present: is a vocabulary (note that affiliations will contain id+name in the dumped data)
3.2 - name/subject is present: is s custom term

repo: inveniosoftware/invenio-app-rdm


text:
global: release v1.3.0

Depends on:

#109
#108
#124

Missing #109. Releasing 1.3.0a5

authors: lnielsen ppanero

repo: inveniosoftware/invenio-previewer


text:
global: upgrade to ES7

Possible breaking changes affecting the module

hits.total is now an object

Closed via #257

repo: inveniosoftware/invenio-records-rest


text:
global: fix alembic dependency version

FIX Fixes upgrader and database creation by limiting alembic
version to <0.7.

Signed-off-by: Nicolas Harraudeau nicolas.harraudeau@cern.ch
PS: I chose the same version limit as in invenio-upgrader.

This is connected with: inveniosoftware/invenio-upgrader#3

@nharraud Can you please amend the commit log message to something like:
installation: fix alembic dependency version

* FIX Fixes database creation and upgrading by limiting Alembic version
  to <0.7.

and repush?  (so that the news would appear in the "installation" section of the release notes, for clarity). Thanks.

@tiborsimko done

authors: kaplun nharraud tiborsimko

repo: inveniosoftware/invenio


text:
[FR] Add delivery date to shipment

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
I would like to keep track of when shipments are delivered, not only when they are shipped.
Suggested solution
Add a 'delivery date' field to shipments, similar to the shipment date.
This field does not have to have any logic attached to it, it should be:

shown in the shipment overview
possible to filter shipments in the API which are delivered/not delivered (just like shipped)

Describe alternatives you've considered
Placing the delivery date in metadata, but that doesn't allow easy filtering of the list of shipped/not-delivered.
Examples of other systems
No response
Do you want to develop this?

[X] I want to develop this.

Seems like a reasonable addition to me, even without any additional business logic

authors: SchrodingersGat miggland

repo: inventree/InvenTree


text:
[bug?] https via nginx does not work on baremetal inventree

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
hi once more,
as recommended by the documentation of gunicorn and also InvenTree itself I am currently working on putting my server behind an nginx instance. This worked for http access but as soon as I want to use https the connection goes into an weird read-only state. if you have a session running it is still possible to see all elements visible for this user but every time you try to change something a notification about insufficient user rights appears. if you try to log-out or log-in you get:
Authentication Failure
You have been logged out from InvenTree.

I am a beginner with nginx so I am aware that this could be an configuration issue however it feels weird for me that http works completely and https has this weird behavior.
I based my nginx config on the one from the docker example and with some modifications to my local ports and circumstances it worked at least for http. However I have a slight weird port configuration as my server is currently only accessible via port 8000 so I set the port inventree is listening on to 8080 and nginx to 8000.
Steps to Reproduce

have an barematel install mirroring the one from the inventree documentation
configure nginx with the docker template, (un-)comment the https specific lines (nginx.conf.zip)
set nginx listening port to 8000 and inventree/gunicorn to 8080 (or any other available port)
start inventree and nginx
try accessing the server

Expected behaviour
The server should be accessible via nginx https the same way it is via nginx http.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.12.0 dev
Django Version: 3.2.18
Database: postgresql
Debug-Mode: True
Deployed using Docker: False
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

have you verified it doe not work with port 443?

@matmair I just tested it and with port 443 it works, even with no other port open for http. After a bit of research I discovered that apparently nginx supports ssl only over 443 so if you need multiple https ports on the same server you need to get a bit creative.
So mostly an nginx problem the only suggestion I would have here is to add a note somewhere that points to this nginx behavior to help other starters to avoid this pitfall

I mean you can route to another port but it is a bit more work than changing out the target port and involves advanced config concepts.
We can mention it but the question is where. I would like to keep the main docs simple as it is very long as it is.

@matmair I wouldn't add it to the main docs either. I think a small comment in the nginx config examples should be enough as this anyway would be the starting point for most working with it.

@T0jan agree
Do you have a useful link that you would suggest for further info?

@matmair there is sadly no clear description (or at least I didn't found some) that states that only port 443 works. most just say one should use a reverse proxy in nginx if a different port is used but don't explain in detail why. maybe just point to the official documentation for at least examples? https://docs.nginx.com/nginx/admin-guide/security-controls/terminating-ssl-http/

@T0jan I'm playing catch up here - are you suggesting that our documentation needs an update?

Ok, happy to close this out then?

I mean there was no comment added yet or did I missed that?

Sorry, didn't link the PR - https://github.com/inventree/InvenTree/pull/5243 - LMK If you are happy with this

looks good to me 👍

authors: SchrodingersGat T0jan matmair


text:
bug: Page with TS codeblocks causes Internal Server Error

Starting a few days a go one of the react-native-google-mobile-ads pages started showing the following error message:

The page used to work flawlessly before, so I assume this has something to do with #359. Checking the browsers dev tools reveals that the GET request to https://docs.page/invertase/react-native-google-mobile-ads/impression-level-ad-revenue results in an internal server error (status 500).
I narrowed the problem down to the following two codeblocks in our docs:
https://github.com/invertase/react-native-google-mobile-ads/blob/b4443b473bba2322b8b7f0b80ed9cd7689af8f0a/docs/impression-level-ad-revenue.mdx?plain=1#L26-L39
Removing them OR(!) switching their language from ts to tsx resolved the problem, which can be verified by looking at the preview of the branch I used for debugging.

@DoctorJohn Thanks for reporting. This was because of the twoslash rendering which has now been removed. Unfortunately it can't handle external types without them being explicitly installed which won't work for docs.page.
The page is live again.

authors: DoctorJohn Ehesp


text:
feat: :lipstick: update lots of icons

What type of PR is this? (check all applicable)

[x] Refactor
[ ] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[x] Yes: continuation of an already merged ui update
[ ] No, because:

Have you updated all relevant documentation?

[ ] Yes
[x] No - Unneeded

Description
Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

Merge Plan

Added/updated tests?

[ ] Yes
[x] No : Unneeded

[optional] Are there any post deployment tasks we need to perform?

@psychedelicious I need to have a bot run linting because I will always forget 😬😆

repo: invoke-ai/InvokeAI


text:
🛑 Bitwage API (Sandbox) is down

In 836a971, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 81 ms

Resolved: Bitwage API (Sandbox) is back up in f231482 after 32 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In cba7ae0, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 148 ms

Resolved: Bitwage API (Sandbox) is back up in e0ec15a after 6 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In f468d9d, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 253 ms

Resolved: Bitwage API (Sandbox) is back up in 1aa70d1 after 33 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In b49ba39, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 268 ms

Resolved: Bitwage API (Sandbox) is back up in d25176a after 17 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 59f6a48, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 283 ms

Resolved: Bitwage API (Sandbox) is back up in 3bbc4b1 after 7 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In f503b58, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 307 ms

Resolved: Bitwage API (Sandbox) is back up in 85417a1 after 13 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In b850053, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 244 ms

Resolved: Bitwage API (Sandbox) is back up in 2fd9b4a after 22 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 48f80eb, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 283 ms

Resolved: Bitwage API (Sandbox) is back up in b256a46 after 10 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 03d8bdc, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 303 ms

Resolved: Bitwage API (Sandbox) is back up in b21dab6 after 45 minutes.


text:
Backslashes not converted to forward slashes in upload requests

See: https://github.com/io7m/brooklime/actions/runs/288019827

Done in https://github.com/io7m/brooklime/commit/9eda070b974daa905a05b9a595b6469b8c896b3e.

Done in https://github.com/io7m/brooklime/commit/9eda070b974daa905a05b9a595b6469b8c896b3e.

license: ISC


text:
Remove bokeh plots relying on bokeh matplotlib compat

As of https://github.com/bokeh/bokeh/pull/6008 mpl compatibility in bokeh is officially deprecated. We should remove the BokehMPLWrapper plot and the DistributionPlot, TimeseriesPlot and Bivariate plot that are hooked up. The examples of those plots in the Bokeh_Backend Tutorial.
I'll open a separate issue to remove the TimeSeries Element because it's data format is strange and functionality is subsumed by other Elements. We should also consider implementing our own implementations for Distribution and Bivariate, which represent 1D and 2D KDEs respectively and would fit in among our statistics Elements. At that point I'd consider dropping our seaborn interface entirely.

Sounds good to me! Hopefully the seaborn functionality will be supported by the new statistical element types.

Bokeh matplotlib compatibility has now been removed and its functionality will be replaced with statistical Element types in 2.0 (see https://github.com/ioam/holoviews/issues/1200).

authors: jlstevens philippjfr

repo: ioam/holoviews


text:
holoviews.notebook_extension() overrides %matplotlib inline

%matplotlib inline
import holoviews
import matplotlib.pyplot as plt
holoviews.notebook_extension()

Odd! Thanks for reporting this.
And everything is fine if you set %matplotlib inline after loading the extension?

It doesn't always work, I changed the order here, but the matplotlib plots are still missing here.
Not sure if the same behaviour is reproduced by my simple example...

What's changed here is that the plt.switch_backend('agg') is now no longer executed when importing holoviews matplotlib backend instead it's executed when running hv.notebook_extension(). I'd be very surprised if simply moving %matplotlib inline after the notebook extension didn't fix it. Indeed when I do this, it seems to work fine:
import holoviews as hv
import numpy as np

hv.notebook_extension('matplotlib')
points = [(0.1*i, np.sin(0.1*i)) for i in range(100)]
hv.Curve(points)

And in a second cell:
import numpy as np
import matplotlib.pyplot as plt
%matplotlib inline

x = np.linspace(0, 1, 500)
y = np.sin(4 * np.pi * x) * np.exp(-5 * x)

fig, ax = plt.subplots()

ax.fill(x, y, zorder=10)
ax.grid(True, zorder=5)

Is there anything different about your setup?

The problem is the following:

You see that the order matters. So if a holoviews object is plotted first, the matplotlib object isn't plotted anymore.

authors: basnijholt jlstevens philippjfr


text:
Minor fix to seaborn plots

Tiny fix for bug mentioned in https://github.com/ioam/holoviews/issues/1336

It's a trivial one line fix so I'll merge when the tests go green.


text:
Removed TreeOperation

Finishes off the last suggestion made in in issue #1419.
Featuremapper still has TreeOperations so ioam/featuremapper#14 should be merged first. I've already pushed a commit to Topographica to make sure it can use the featuremapper version when the HoloViews version disappears.

I think both this PR and the one on featuremapper are now ready to merge.


text:
Fixes for matplotlib colormapping

Several fixes for matplotlib colormapping:

Colormapping elements that support fill does not override edgecolor
Label the colorbar correctly
Fixed bug colormapping Contours/Polygons

The removal of the print shouldn't affect the tests (surely) so I'll go ahead and merge.


text:
viewing connection fields of sparce/gpu models

I now can train some sparse/gpu models and wanted to look at the results. What's the best way to view connection fields of sparce/gpu models? If nothing in place yet, any hints on how to get back the connection fields from the cusparse weight array?

I remember briefly looking into this but I don't recall much so I can only comment generally on how the sparse representation is stored. Basically all the weights in a projection are stored in a single large sparse matrix, where each column represents one CF. So to view a single CF you should slice into the large matrix and then reshape the column to the size of the source sheet. Let me know if you run into any issues.

Thanks. I will try this. BTW I am finding the interactivity of the GUI (can run and watch and interrupt at same time) and the way .ty files can be ingested in notebooks simply too difficult to replace with the notebook. So if the problem of viewing legacy models (non-sparse) in latest topographica on github is not solvable, I may try to transplant the sparse/gpu parts into a version where the GUI is still working.

Was the idea of copying the connection fields weights from GPU back to host at end of simulation (mentioned in @Tasignotas thesis) implemented? I can see there the fields in  GPUSparseCFProjection for (sparse) 'weights' and (cusparse.CSR) 'weights_gpu' and I am assuming the weights are still in weights_gpu after each run. So I am wondering whether a function for copying from weights_gpu to weights exists somewhether. Looked into gpu folder and could not find anything...

I don't think that they were ever copied out, but I could be mistaken.
Jim
On Tue, Oct 13, 2015 at 3:41 PM, M. Jabri notifications@github.com wrote:

Was the idea of copying the connection fields weights from GPU back to
host at end of simulation (mentioned in @Tasignotas
https://github.com/Tasignotas thesis) implemented? I can see there the
fields in GPUSparseCFProjection for (sparse) 'weights' and (cusparse.CSR)
'weights_gpu' and I am assuming the weights are still in weights_gpu after
each run. So I am wondering whether a function for copying from weights_gpu
to weights exists somewhether. Looked into gpu folder and could not find
anything...
—
Reply to this email directly or view it on GitHub
https://github.com/ioam/topographica/issues/635#issuecomment-147846376.

Ok, but how the receptive fields as produced on GPU would've been verified? I can see the activities with the gcal_sparse example with artificial patterns, but these response activities do not validate the learning is as expected.

If the activities match by the end of the simulation then that verifies the learning by proxy. The chance of getting the same activity with different weights just by chance might as well be zero.

This is good for validation.

So seems reasonable to add a function to copy weights_gpu to weights for GPUSparseCFProjection which would be used when need to view and save the weights.

ok, here is a function that copies weights from gpu to cfs. Tested this on my old fork of topographica where i have transplanted the sparce/gpu stuff and it seems to work. I am not sure whether this is the most efficient way though.
from math import sqrt
from nmutils import info
import numpy as np
def cfs2cpu(in_conns):
for c in in_conns:
try:
gw = c.weights_gpu
m = gw.todense(to_cpu=True)
if m is None:
info('Could not get the dense matrix for connection {0}. Ignoring...'.format(c.name))
continue
rows,cols = m.shape
except:
import sys
e = sys.exc_info()[0]
info("Exception: '{0}' while coppying GPU weights of connection {1}. Ignoring.".
format(e, c.name))
continue
info('Copying weights all {0} GPU weights of connection {1} to CF weights in flatcfs.'.format(rows,c.name))
for i in xrange(rows):
row = m[i]
(s,) = row.shape
s=sqrt(s)
cf = row.reshape((s,s))
r1,r2,c1,c2 = c.flatcfs[i].input_sheet_slice
# Note below will not work as __set_weights of SparseConnectionField.
# np.copyto(c.flatcfs[i].weights, cf[r1:r2,c1:c2])
c.flatcfs[i].weights = cf[r1:r2,c1:c2].copy()
del m

authors: jbednar mjabri philippjfr

repo: ioam/topographica


text:
moved terms of service button closer to menu dropdown button

Positioned terms of service closer to menu dropdown button

quarantest build successful. Demo link at
http://d7209c33.quarantest.iobio.io

Looks good to me


text:
Calling variants on same gene duplicates variants

Call variants (alignments only, no vcf files) on a gene. Then call again. Notice how the number of variants doubles.

This probable explains the issue that a user was having where they saw more variants when they changed the +/- region to a smaller region.

Yeah, this would make sense

authors: AlistairNWard tonydisera


text:
Unable to show the images

Hello everyone.
During this last three days I'm trying to show photos library in app, so I figured out many issues until I face one that sens to don't have any solution.
As I see, the cdvphotolibrary:// does not work in web view, so in the webview doc there is an explanation to use the full file path, so, i did that but ionic puts ioni://localhosts in front of the file path and It gets 404 error.
Bellow some prints and peace of code.
<ion-content no-padding>
  <ion-grid no-padding>
    <ion-row no-padding>
      <ion-col no-padding *ngFor="let libraryItem of library" col-3>
        <button>
          <img [src]="libraryItem.filePath">
        </button>
      </ion-col>
    </ion-row>
  </ion-grid>
</ion-content>

import { Component, ChangeDetectorRef } from '@angular/core';
import { IonicPage, NavController, NavParams, Platform, ModalController, ToastController } from 'ionic-angular';
import { ErrorDialog } from '../../dialog/errorDialog';
import { Config } from '../../config';
import { PhotoLibrary, LibraryItem } from '@ionic-native/photo-library';

@IonicPage()
@Component({
  selector: 'page-post',
  templateUrl: 'post.html',
})
export class PostPage {

  public config: any;
  public library: LibraryItem[];
  PermissionPage: any = 'PermissionPage';
  public cdvToken: any;

  constructor(
    public navCtrl: NavController,
    public navParams: NavParams,
    public dialog: ErrorDialog,
    public photoLibrary: PhotoLibrary,
    public platform: Platform,
    private cd: ChangeDetectorRef,
    public modalCtrl: ModalController,
    public toastCtrl: ToastController
  ) {
    this.config = Config.config();
    this.library = [];
  }

  ionViewDidEnter() {
    this.fetchPhotos();
  }

  fetchPhotos() {
    this.platform.ready()
      .then(() => {
        this.library = [];
        this.photoLibrary.getLibrary()
          .subscribe({
            next: (chunk) => {
              this.library = this.library.concat(chunk);
              console.log(this.library);
              this.cd.detectChanges();
            },
            error: async (error: String) => {
              if (error.toString().toLowerCase().startsWith('permission')) {
                const modal = await this.modalCtrl.create(this.PermissionPage);
                modal.onDidDismiss(() => {
                  this.fetchPhotos();
                });
                await modal.present();
              } else {
                const toast = await this.toastCtrl.create({
                  message: this.config.permissions.photoLibrary.getError,
                  duration: 6000
                });
                await toast.present();
              }
            },
            complete: () => {
              console.log('success fetching library items');
            }
          })
      });
  }
}

some emulator prints
1 - With full path
https://s3-sa-east-1.amazonaws.com/hunterappassets/ionic+localhost.png
https://s3-sa-east-1.amazonaws.com/hunterappassets/dom.png
https://s3-sa-east-1.amazonaws.com/hunterappassets/404.png
2 - with cdvphotolibrary://
<ion-content no-padding>
  <ion-grid no-padding>
    <ion-row no-padding>
      <ion-col no-padding *ngFor="let libraryItem of library" col-3>
        <button>
          <img [src]="libraryItem.thumbnailURL | cdvphotolibrary">
        </button>
      </ion-col>
    </ion-row>
  </ion-grid>
</ion-content>

import { Pipe, PipeTransform } from '@angular/core';
import { DomSanitizer } from '@angular/platform-browser';

@Pipe({name: 'cdvphotolibrary'})
export class CDVPhotoLibraryPipe implements PipeTransform {

  constructor(private sanitizer: DomSanitizer) {}

  transform(url: string) {
    return url.startsWith('cdvphotolibrary://') ? this.sanitizer.bypassSecurityTrustUrl(url) : url;
  }
}

https://s3-sa-east-1.amazonaws.com/hunterappassets/photolibrary3.png
https://s3-sa-east-1.amazonaws.com/hunterappassets/photolibrary2.png
https://s3-sa-east-1.amazonaws.com/hunterappassets/photolibrary1.png

I've tried your code without success, would be good if you could provide a sample app that I can just npm install and run.
Anyway, cdvphotolibrary is a CDVURLProtocol and that won't work in the WKWebView, so you should go with the file url.
File urls should be converted with window.Ionic.WebView.convertFileSrc() (regular javascript) or  if using ionic use @ionic-native/ionic-webview (see https://ionicframework.com/docs/native/ionic-webview)

So I tried to use window.Ionic.WebView.convertFileSrc() and It works like a charm!

authors: jcesarmobile vitorbarros

repo: ionic-team/cordova-plugin-ionic-webview


text:
fix(ios): make programmatically focus work on iOS 13

closes #435

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

authors: Ionitron jcesarmobile


text:
iPhone X status bar overlaps ion-toolbar

Bug Report
Ionic version:
[x] 4.7.4
Current behavior:
ion-toolbar component inside router-outlet overlaps with iphone X status bar
Expected behavior:
ion-toolbar does not overlap with status bar
Steps to reproduce:
Create an application with a page rendered in a router outlet and DOM elements adjacent the outlet and the ion toolbar from inside the outlet will overlap the status bar.
Related code:
<sidemenu content="menu-content"></sidemenu>
<ion-router-outlet id="content"></ion-router-outlet>

<ion-toolbar>
  <ion-menu-button slot="start"></ion-menu-button>
  <ion-title>Assets</ion-title>
</ion-toolbar>
<ion-content>
  <ion-list [inset]=true lines="none">
    <ion-item *ngFor="let token of tokens" [routerLink]="token.guid ? ['/wallet/assets', token.baseChainSymbol, token.guid] : ['/wallet/assets', token.baseChainSymbol]" routerDirection="forward" lines="none"
              class="asset-item">
      <ion-thumbnail slot="start">
        <ion-img *ngIf="token.logo" [src]="token.logo"></ion-img>
        <ion-img *ngIf="!token.logo" src='https://gravatar.com/avatar/{{ token.guid }}?d=wavatar&r=x'></ion-img>
      </ion-thumbnail>
      <ion-label class="asset-title">
        {{ token.symbol }}
      </ion-label>
      <ion-label class="asset-label">
        {{ token.balance }} {{ token.symbol }}
        <ion-card-subtitle *ngIf="token.baseValue > 0">
          {{ token.baseValue * token.balance }} {{ currentBaseCurrency }}
        </ion-card-subtitle>
      </ion-label>
    </ion-item>
  </ion-list>
</ion-content>

Other information:

Issue was due to ion-toolbar missing a wrapping ion-header tag 🤦♂

repo: ionic-team/ionic


text:
fix(slides): add effect plugins for swiper

Short description of what this resolves:
Missing Coverflow, Cube, Fade and Flip swiper effects for ion-slides
Changes proposed in this pull request:

Add needed plugins to swiper builder

Ionic Version: 4.0.0-beta.17
Fixes: #15857

Can you run npm run build and commit the changes as well? also make sure you run npm i before.

Status?

Sorry, is this waiting for something on my end?  I rebuilt and committed a few weeks ago. I can do it again if needed.

Short description of what this resolves:
Missing Coverflow, Cube, Fade and Flip swiper effects for ion-slides
Changes proposed in this pull request:

Add needed plugins to swiper builder

Ionic Version: 4.0.0-beta.17
Fixes: #15857

Fade effect still not working

hey @manucorporat
We're out of beta and it wasn't inserted, why? :(

@brandyscarney I noticed we already have swiper as a dependency on our package.json: https://github.com/ionic-team/ionic/blob/master/core/package.json#L58
Do we need this additional swiper.js file?

Interesting, there seems to be a load by the package and its bundle separates into folder. It makes no sense this double load.
Remember that you have a new version:
https://github.com/nolimits4web/swiper/blob/master/CHANGELOG.md#swiper-450---released-on-february-22-2019

Yeah that's interesting. I think it may be fine for now. What do you think @brandyscarney.
Re: the new swiper version-- I think this should be a separate PR, but worth looking into!

Hi there,
After some discussion with the team, we have decided to go a different route with the swiper animation plugins. Instead of adding the additional animations directly into the framework, we have decided to expose the event handlers that swiper provides. This has a few benefits:

Ionic users do not need to include the swiper animations in their bundle if they aren't using it.
Users can still incorporate the flip, fade, cube, and coverflow effects. We will provide instructions on how to do so in the Ionic Docs.
Users can also develop and integrate their own custom animations.

I have created a PR for this here: https://github.com/ionic-team/ionic/pull/17959 which will be merged instead of this PR. Any feedback on this PR would be greatly appreciated!
Thank you very much for your contributions here, we really appreciate it! You will be added as a co-contributor to #17959.
Thanks!

I'm going to close this, please refer to Liam's comment above as to why. If anyone has feedback please add it on the Pull Request he linked to, thank you!

authors: CFT-Chris Nazirovich brandyscarney kalicki liamdebeasi manucorporat


text:
feat(modal): add initial border radius

Pull request checklist
Please check if your PR fulfills the following requirements:

[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[X] Build (npm run build) was run locally and any changes were pushed
[X] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

On iPhone X and up there is the "wrong" border transition.
See this issue #20501
What is the new behavior?

Now checks if the bottom safe area isn't 0px which would mean there is a home-indicator and therefore it is an iPhone with edge to edge display and then adds the desired border-radius.
Does this introduce a breaking change?

[ ] Yes
[X] No

Other information

Thanks for the PR! What issue does this address? It seems to be different than the one linked in your PR description.

Sorry, maybe I gave a bit to lees information.
This is the current behavior:

This is what this PR fixes:

It just adds the right border radius and doesn't fix the statusbar color "bug"

Thanks for the PR! We appreciate all of the hard work you put into doing this. After discussing with the team, we have decided not to merge this PR.
While I agree that this PR brings the card modal closer to the native iOS modal spec, it brings tradeoffs that do not make the code easily maintainable.
The ratio value used here is hardcoded, but the ratio on new iPhones is subject to change at any time. Apple could release a new phone with a smaller notch and this could potentially break (Allegedly this may happen https://www.theverge.com/2020/4/13/21218806/apple-iphone-12-2020-redesign-notch-cameras-specs). I realize we could just update this array with whatever the new ratio is, but I do not think it is a good idea to add code that we will need to potentially race to update any time a new phone comes out.
I spent some time investigating other ways of accomplishing this border radius check, and I am not sure there is a good way of making this work currently. We try to make our components as close to the native spec as possible, so if this feature becomes easily doable in the future we will be happy to revisit this. Thank you!

authors: julian-baumann liamdebeasi


text:
Extension not loading the JS code logic - menu in BM not showing up

Hello @ionutvmi ,
Since April 16th, the extension has stopped loading and I confirmed with other colleagues that it's on their side too.
I tried locally and loaded the unpacked version and I found one issue in the manifest declaration that seems to be the cause of this.
In the manifest.json file, the URLs have a trailing slash at the end that seem to block the extension from working.
I don't have a lot of experience with Chrome extensions, but this change made it work for me - maybe you can test it on your side and see if that helps.
Thanks!

Indeed the new restricted permissions cased the issue.
I have modified them in 1.7.5
Unfortunately it might take a while until it reaches everybody due to the new web store review process.
Hopefully it will be published early next week, until then people can load the extension using the guidelines from: https://github.com/ionutvmi/bm-extender#install

Looks like the fix was published !
Please reopen this ticket if you still encounter issues.

authors: ClaudiuCudla ionutvmi

repo: ionutvmi/bm-extender


text:
Firefly Iota abheben

Task description
Ich kann meine iota von Firefly nicht abheben ich werde nach meinem password gefragt was ich dann eingeben und es geht nicht ? es ist doch mein firefly password oder ?
Requirements
.
Acceptance criteria
.
Creation checklist

[ ] I have assigned this task to the correct people
[ ] I have added the most appropriate labels
[ ] I have linked the correct milestone and/or project

Es gibt eine PIN und ein Passwort. Zum Versenden von Token benötigst du das Passwort.

kann ich das passwort noch änder ? oder ein neues machen ?

Du kannst dein Password in den Einstellungen ändern, allerdings brauchst du dafür das alte Passwort. Wenn das nicht funktioniert, kannst du mit deiner recovery phrase ein neues Profil anlegen und das alte danach löschen.

Vielen Dank :)

Gerne :)

wenn ich ein neues Profil mache und das alte lösche sind deann meine Iota weg ?

Nein, deine Iota hängen im übertragenen Sinne an deiner recovery phrase. Solange du die hast, kannst du deine Wallet jederzeit reproduzieren. Ich würde dir allerdings empfehlen erst das neue Profil anzulegen, bevor du das alte löschst. Wenn du nur ein Profil hast, geht es sowieso nicht anders.

okay vielen dank für deine wissen :)

repo: iotaledger/firefly


text:
[Bug report]: FAQ - Page Not Found

Platform
Desktop
Version
1.6.5
Description
FAQ page not found

Expected behaviour
There is information or guide in the FAQ
Actual behaviour
Page Not Found
We could not find what you were looking for.
Please contact the owner of the site that linked you to the original URL and let them know their link is broken.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
1 Go to Help
2 Click FAQ
Error Message Show - Page not found
Operating System
Windows
Diagnostics
No response
Developer Profile
Yes
Profile Type
Software (Stronghold)
Staking
No response
Crash Status
None of the above
Error Messages
Error Message Show - Page not found
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This issue was already solved with https://github.com/iotaledger/firefly/pull/4562 and will be included in the next version.


text:
admin interface - data load

Implement an interface to load memos and users from a json

Issue #54

repo: iotexpert/memosystem


text:
support solc v0.5.0

What type of PR is this?
feature
fixed: #1081

Closed in favor of #1124

repo: iotexproject/iotex-explorer


text:
🛑 备用KMS激活服务器 01 is down

In 2f9a92d, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in ea2fc72 after 10 minutes.

repo: iougemini/ikms-uptime


text:
🛑 备用KMS激活服务器 01 is down

In b016ba6, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 5d35aec after 9 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In cabb734, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in df23c2d after 18 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 97bd2d4, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in c12079c after 10 minutes.


text:
🛑 备用KMS激活服务器 11 is down

In 755e0e1, 备用KMS激活服务器 11 (s01.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 11 is back up in c6c1830 after 23 minutes.


text:
make sure we create map keys when we have all the typing information

Map keys were being created too soon, and some typing information (such
as StackType in the case of ustack and kstack calls) could be missing in
some cases. If we wait until the final pass of the analizer to create
the keys, we have all the typing information.
Fixes: https://github.com/iovisor/bpftrace/issues/475

thanks!

authors: brendangregg mmarchini

repo: iovisor/bpftrace


text:
Fails to build git =, rev= dep under a subdirectory

I had to switch to use git version of error-stack like this:
-error-stack = "0.1.1"
+error-stack = { version = "0.1.1", git = "https://github.com/hashintel/hash/", rev="5edddb5" }

cargo build works fine with it, but nix build .#foobar fails with:
> nix run .#res.starter
path '/home/dpc/lab/rustshop/services' does not contain a 'flake.nix', searching up
warning: Git tree '/home/dpc/lab/rustshop' is dirty
error: builder for '/nix/store/yj8a6ir4szhq4aa73xhnjwi5bwcxd2xf-services-workspace-deps-deps-0.0.1.drv' failed with exit code 101;
       last 10 log lines:
       >   Unable to update https://github.com/hashintel/hash/?rev=5edddb5#5edddb55
       >
       > Caused by:
       >   failed to update replaced source https://github.com/hashintel/hash/?rev=5edddb5#5edddb55
       >
       > Caused by:
       >   failed to parse manifest at `/nix/store/36f54ndv3y8yr2zhbxy1ss7mhs6jjj80-vendor-cargo-deps/8379b92581444212dd05e8733c6ac22ae88bba0f603ebf7660db6adbcf973197/orchestrator-0.0.0/Cargo.toml`
       >
       > Caused by:
       >   `artifact = …` requires `-Z bindeps` (hash_engine)
       For full logs, run 'nix log /nix/store/yj8a6ir4szhq4aa73xhnjwi5bwcxd2xf-services-workspace-deps-deps-0.0.1.drv'.
error: 1 dependencies of derivation '/nix/store/0bz9mki1h7fhk23i1qf1alpr4zc1bg2i-starter-res-gen-0.0.1.drv' failed to build

The problem might be that this crate lives in a subdirectory of larger project?

Thanks for the report @dpc, this looks like a legitimate bug! Here's what I think is happening:

The error-stack crate is part of a repository which has multiple crates
When we vendor the repository we extract all crates we can find in the repository
When we vendor the repository, cargo will try to parse all Cargo.toml files it finds in there, even if the crate isn't actually consumed by the dependency that is being built
In this particular case a crate name orchestrator is part of this repository and is vendored. That crate uses an artifact value in its Cargo.toml which chokes since it appears to be a nightly-only feature

It sounds a like a possible solution is to update step 2) above to only vendor crates in the Cargo.lock file we care about. This is what cargo vendor appears to be doing as it will only vendor the crates that are actually used

authors: dpc ipetkov

repo: ipetkov/crane


text:
feat: add header

Closes #153
Revisited the styles of the logo to match the footer and header designs
Added header height global variable to variables.css
Added the header.

lgtm 👍


text:
Publish gx 1.2.4

@whyrusleeping this is meant to fix the messy gx publish I did that included /src.

LGTM, thanks :)

authors: geoah whyrusleeping


text:
Move to ipfs-shipyard?

Now we have an org to incubate projects that not part of the core implementation of the protocol or discussion of the spec. That org is ipfs-shipyard created from https://github.com/ipfs/pm/issues/448
Short description:

IPFS Shipyard is a venue for the community to pursue and collaborate on research experiments, products, code libraries and more around the IPFS project. It is where innovation in userland happens and where we discover and form new primitives to push to the core of IPFS.

Anyone opposing?

Why? This is part of webui and as such shipped with every release of go-ipfs

@dignifiedquire we should still be able to ship this as part with webui, even if it's with ipfs-shipyard

Sure, but it is part of the core offering is what I am trying to say. So I don't see the reason to move it to the shipyard

It can stay here :)

repo: ipfs/ipfs-geoip


text:
在未发布视图线性布局下超过四列的图片后图片显示不全布局混乱

- (void)viewDidLoad {
    [super viewDidLoad];
    // 初始化
    [self setup];

    // 1. 常见一个发布图片时的photosView
    PYPhotosView *publishPhotosView = [PYPhotosView photosView];
    // 2. 添加本地图片
    NSMutableArray *imagesM = [NSMutableArray array];
    for (int i = 0; i < 6; i++) {
        [imagesM addObject:[UIImage imageNamed:[NSString stringWithFormat:@"%02d", i + 1]]];
    }
    publishPhotosView.py_x = PYMargin ;
    publishPhotosView.py_y = PYMargin * 2 + 64;
    // 2.1 设置本地图片
    publishPhotosView.images = imagesM;
    publishPhotosView.photoMargin = 0.0;
    // 3. 设置代理
    publishPhotosView.delegate = self;
    publishPhotosView.photosMaxCol = 4;
    publishPhotosView.imagesMaxCountWhenWillCompose = 6;

    // 4. 添加photosView
    [self.view addSubview:publishPhotosView];
    self.publishPhotosView = publishPhotosView;
}

该bug已经修复、请下载最新版本或者执行 pod update 测试！ 谢谢反馈


text:
Added CheckCrawler function to API.

I added an IsCrawler property to the IpResponse model to get rid of the dirty data.

Hey thanks for the contribution!
This is a cool feature idea but the implementation strategy isn't right. This is something we'd ideally get from the IPinfo API directly, from data sources that are proprietary and a lot more resilient, rather than essentially a few user-configurable checks on the hostname/ASN/etc, which are not the most reliable techniques for this.
This feature exists on the website but not the API currently - hoping it'll get added soon, then we could include it in all SDKs.

You're welcome. I use it this way in my own projects with around accuracy of around 90%. Since it works with real users instead of crawlers, it partially reduces my database traffic. But you're absolutely right about it not being as reliable as your actual data sources.
I hope so too, good job 👍

authors: UmanShahzad g-u-r-k-a-n

repo: ipinfo/csharp


text:
🛑 NowBoarding (tokyo) is down

In 5d628d9, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 403
Response time: 60 ms

Resolved: NowBoarding (tokyo) is back up in 07b60d4.

repo: iplanwebsites/up


text:
🛑 NowBoarding (tokyo) is down

In 4049cb9, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NowBoarding (tokyo) is back up in c02162e after 4 minutes.


text:
🛑 NowBoarding (tokyo) is down

In 08c9703, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 403
Response time: 85 ms

Resolved: NowBoarding (tokyo) is back up in 58b2423.


text:
Create package table

fixes #134
I wasn't sure about the headings; what would be a more logical/helpful way to group the dependencies?
I used the the table generator script in js-ipfs. Right now, that script has the dependencies and headings hard-coded. Might it make more sense to have a more generic table generator for all the projects in the js-ifps universe?

Thanks a lot! It took me a while to figure out what "Packages" actually means (also in the js-ipfs case). Am I correct that this is a list of dependencies that belong to the IPFS ecosystem?
Could you please add that information (or the corresponding one if I'm wrong)?
PS: For the CI failures I've created https://github.com/ipld/js-ipld/issues/139

Yep, I think you got it right (see also: https://github.com/ipfs/js-ipfs/issues/1050). I've added some brief clarification above the table.
I believe the real advantage of a table like this is that you can see coverage and build status at a glance without having to go through each repo individually. To that end, it might make more sense to only include IPFS repos that are closely related to js-ipld, i.e. not ipfs/is-ipfs. Of course, this table is another thing that must be kept up to date, so it's really up to you if you think it's worth adding. Ideally, this sort of information could be managed automatically through waffle.io or something.

authors: jonahweissman vmx

repo: ipld/js-ipld


text:
refactor: pass in IPLD Formats into the constructor

Instead of having IPLD using all currently available IPLD Format
implementations automatically, pass the Formats that should be
used into the constructor as options.
This will also decrease the bundle size as every user of IPLD can
decide which IPLD Formats should be used. By default
ipld-dag-cbor and ipld-dag-pb are used as those are the ones
also heavily used within the IPFS ecosystem.
BREAKING CHANGE: Not all IPLD Formats are included by default
By default only the ipld-dag-cbor and ipld-dag-pb IPLD Formats
are included. If you want to use other IPLD Formats you need
to pass them into the constructor.
The code to restore the old behaviour could look like this:
const ipldDagPb = require('ipld-dag-pb')
const ipldDagCbor = require('ipld-dag-cbor')
const ipldGit = require('ipld-git')
const ipldBitcoin = require('ipld-bitcoin')
const ipldEthAccountSnapshot = require('ipld-ethereum').ethAccountSnapshot
const ipldEthBlock = require('ipld-ethereum').ethBlock
const ipldEthBlockList = require('ipld-ethereum').ethBlockList
const ipldEthStateTrie = require('ipld-ethereum').ethStateTrie
const ipldEthStorageTrie = require('ipld-ethereum').ethStorageTrie
const ipldEthTx = require('ipld-ethereum').ethTx
const ipldEthtrie = require('ipld-ethereum').ethTxTrie
const ipldRaw = require('ipld-raw')
const ipldZcash = require('ipld-zcash')

…

const ipld = new Ipld({
  blockService: blockService,
  formats: [
    pldDagPb, ipldDagCbor, ipldGit, ipldBitcoin, ipldEthAccountSnapshot,
    ipldEthBlock, ipldEthBlockList, ipldEthStateTrie, ipldEthStorageTrie,
    ipldEthTx, ipldEthtrie, ipldRaw, ipldZcash
  ]
})

/cc @alanshaw @hugomrdias

It's not clear, but the parts of the CI that matter passed (and the failed part can't be retriggered).

@diasdavid I've done the js-ipfs change already locally. Once this change is merged and released. I will make PRs to those repos updating js-ipld with the corresponding changes. There's not point of keep too many PRs open for a long time.

@diasdavid Projects I've identified that need changes if this change is released:

js-ipfs: https://github.com/ipfs/js-ipfs/pull/1652
js-ipfs-unixfs-engine: https://github.com/ipfs/js-ipfs-unixfs-engine/pull/232
ipld-explorer: doesn't need changes, only ipld-explorer-components does
ipld-explorer-components:

Once https://github.com/ipfs-shipyard/ipld-explorer-components/issues/5 is fixed, I'll look into making it work with a release where this PR is merged

ipld-explorer-cli: wait for https://github.com/tableflip/ipld-explorer-cli/issues/10 to be fixed. Then I can check if my local changes really work.

There is already an example on how to add other formats in the README.


text:
Webpack issue involving fetch(), whatwg-fetch(), and polyfill loading

Have been having a strange problem over the last few days while trying to import and use any of the promise-based fetch() modules.  Here's the solution I found-- update the .structor/webpack.base.js file to reflect:
new webpack.NoEmitOnErrorsPlugin(), new webpack.ProvidePlugin({        // make fetch available       fetch: 'exports-loader?self.fetch!whatwg-fetch', }),
there are 2 changes, the first is that the -loader suffix was missing from exports, and second is the NoEmitOnErrorsPlugin needed updating after webpack was complaining about using a deprecated module.
Not sure if this is known or not, but I wanted to document it for anyone else that might be experiencing these issues.
Thanks again for your hard work!

My solution was to create a class.
import 'whatwg-fetch';

class ClientFetch {
  constructor(props) {
    this.fetch = this.fetch.bind(this);
    this.Headers = this.fetch.Headers;
    this.Request = this.fetch.Request;
    this.Response = this.fetch.Response;
  }
}

export default ClientFetch;

authors: squirmsound theanthonyplan

repo: ipselon/structor


text:
Suggestion: Add simple "headline" and "body" properties and call the arrays "altheadlines" and "altbodies"

Looking at the examples, they seem more complicated than we would like, so could we go back to having a separate "headline" property? To be discussed when Johan is back!

I'm ok with that, but will that lead to a simple description and a simple body too?

At the meeting Aug 23 we decided - NO

repo: iptc/newsinjson


text:
Documentation: Readme as Overview, Quick setup, and Table of Content

Documentation: Readme as Overview, Quick setup, and Table of Content
Description
Provides overview of project, introduction, quick setup and test.
Also provide links to API schema and Design docs

See README.md

repo: iqDF/benjerry-api


text:
Player meldet (unregelmäßig) eine falsche Session-ID

Steps:

Frische Testcenterinstallation (beinhaltet Beispielunits mit Simple-Player)
Login als Beispielnutzer (test)
Test laden
ggf. Test erneut laden (Klick auf IQB-Logo und dann "Test fortsetzen")

Verhalten:
Es erscheint ab und zu (nicht bei jedem Versuch, aber reproduzierbar) auf der Konsole eine Fehlermeldung. Siehe Screenshot anbei.
Hat keine sichtbar Auswirkung auf das Verhalten in der Anwendung. Aber Fehler auf der Konsole sind trotzdem zu vermeiden.

Sollte mit diesem Commit behoben sein:
https://github.com/iqb-berlin/verona-player-simple/commit/cd05aa9482b9fce73e80bcbe5486525b3b04d9bf

authors: paflov rhenck

repo: iqb-berlin/verona-player-simple


text:
🛑 iTa'LeEM Cloud is down

In 058dbf3, iTa'LeEM Cloud (https://italeemc.iium.edu.my) was down:

HTTP code: 503
Response time: 1070 ms

Resolved: iTa'LeEM Cloud is back up in 9e56f89 after 1 day, 23 hours, 59 minutes.

repo: iqfareez/iium-services-status


text:
[RFC] New versioning scheme for IREE Python packages

Summary
Our pre-compiled software is currently made publicly available using different versioning schemes. We're proposing a new versioning scheme to remedy this situation to which downstream packages depending on IREE can easily adopt.
This affects these packages:

https://pypi.org/project/iree-compiler/ (current version 20240828.999)
https://pypi.org/project/iree-runtime/ (current version 20240828.999)
https://pypi.org/project/iree-turbine/ (current version 2.4.1)
(maybe) https://pypi.org/project/iree-tools-tflite/ (current version 20240226.813)
(maybe) https://pypi.org/project/iree-tools-tf/ (current version 20240226.813)

Here are examples of the new versions we propose:

Type of build
Version format
Version example

Stable release (PyPI)
X.Y.Z
3.0.0

Nightly release (GitHub schedule)
X.Y.ZrcYYYYMMDD
3.0.1rc20241029

Dev release (GitHub pull_request)
X.Y.Z.devNN
3.0.1.dev50

Local build
X.Y.Z.dev
3.0.1.dev

Key

Identifier
Explanation

X
Major version

Y
Minor version

Z
Patch version

rc
release candidate (main branch)

dev
developer build (code on pull request branches)

YYYY
Year, e.g. 2024

MM
Month, e.g. 10

DD
Day, e.g. 29

NN
Build number (increasing ID from GitHub per workflow), e.g. 50

Background
Currently CalVer is used for releasing iree-compiler and iree-runtime whereas iree-turbine utilizes a version number in the format of X.Y.Z. Therefore, compatible versions cannot be derived from the version number. A common versioning scheme would be SemVer, but as the MAJOR version must be increased when incompatible API changes are introduced a cross-project version number (primarily a shared MAJOR version) cannot be guaranteed if APIs are not identical. Switching to a non-CalVer scheme requires a package rename as the first release segment would otherwise need to be set to a number larger than 20240928, e.g. 30000000, or to introduce an N! epoch segment which however is not a convenient solution, see Python version epochs are broken.
Detailed proposal
A shared version format is proposed for the packages

iree-base-compiler (formally named iree-compiler)
iree-base-runtime (formally named iree-runtime)
iree-turbine

Major or minor releases are published every 6 weeks for all packages uniformly. Based on logistics and/or practical engineering issues, releases may be delayed or deferred as needed. Patch versions for individual packages can be published outside of that cycle as needed.
A release number is in the format of X.Y.Z (MAJOR.MAJOR.PATCH).

X and Y are defined as shared version numbers between all packages.
The patch level Z MAY be incremented individually.
A PATCH release contains only bug fixes and the version Z (x.y.Z) MUST be incremented. A bug fix is an internal change that fixes incorrect behavior and MUST NOT introduce breaking changes.
A MINOR release (unlike SemVer) as well as a MAJOR release MAY contain backwards-incompatible, breaking changes, like API changes and removals and furthermore bug fixes and new features.

Development and nightly releases:

Development builds (e.g. from a regular CI) MUST be released with a version number defined as X.Y.Z.devN, where N is a build number.
Nightly releases MUST be released with a version number defined as X.Y.ZrcYYYYMMDD.
The intent is to promote a recent, high quality release candidate to a final version. Binary stamps and tools will continue to report the original release candidate version.

The following semantics apply:

If the version X (X.y.z) is increased for one package, the version number change MUST be adopted by all (other) packages. The same applies for the version Y (x.Y.Z).
If the version X or Y are changed, Z MUST be set 0.
After a release, either Y or Z MUST be increased to ensure precedence of nightly builds.
For example:

The latest stable release published on November 15th 2024 is versioned as version 3.0.0.
The next nightly builds are released as 3.0.1rc20241116 or 3.1.0rc20241116.
The next stable release is released as 3.0.1 or 3.1.0.

Additional version information
With switching from CalVer to the proposed versioning scheme, the build date is not encoded in the version number any longer. However, additional information is provided by --version, e.g. iree-compile --version gives:
IREE (https://iree.dev):
  IREE compiler version 20240730.970 @ d39c3c56682e006e842b32aa6f38c272f77c8f3c
  LLVM version 20.0.0git
  Optimized build

which can be extended by the build date.
Implementation plan
Each project will have a version_info.json file containing the latest X.Y.Z version. Local, pull request, and nightly builds will read from this file and append their own suffixes to it. When a new release is promoted to PyPI from a nightly release, a script will be used to edit the embedded version, removing any rcYYYYMMDD suffix and then we will upgrade the version in each version_info.json file so future builds will use new versions. The new releases will start at version 3.0.0, since iree-turbine is currently 2.4.1.
Timeline
We would like to begin implementation work soon and have this completed within ~2 weeks.

Highlighting an important detail that could be missed: with these version changes, existing workflows that use
python -m pip install iree-compiler iree-runtime

will need to be replaced with new packages
python -m pip install iree-base-compiler iree-base-runtime

Simply switching the version scheme on the existing packages would require starting with a version greater than the existing calver (20240828), or using Python version epochs, which are broken.
After rolling out the initial releases for each package, we can also explore ergonomics improvements like functional or meta packages that themselves depend on both "base" packages, so users can install a single project or the individual packages if they want precise control.
We can also publish tombstone package releases to the iree-compiler and iree-runtime projects that warn about the name change and maybe eventually (after years?) remove the old names/packages entirely.

One open question is where we'll publish nightly releases to.
We currently push a new release every night to https://github.com/iree-org/iree/releases and a release index to https://iree.dev/pip-release-links.html using this script: https://github.com/iree-org/iree/blob/main/build_tools/scripts/generate_release_index.py . We could switch to a single "dev-wheels" release like https://github.com/nod-ai/SHARK-Platform/releases/tag/dev-wheels with a release index generated for us by GitHub like https://github.com/nod-ai/SHARK-Platform/releases/expanded_assets/dev-wheels .
Even if we rename the packages to iree-base-runtime and iree-base-compiler, we should be able to continue using the current system. Maybe as a future refactoring we can switch to the single release style.
Eventually we could also push nightly / pre-release versions of packages to pypi so users can just pass --pre instead of -f, --find-links <url>.

Oh, I just found / re-remembered that iree-turbine versioning is intended to be based on PyTorch versions. I presume we're departing from that now, but using the existing 2.* versions as a starting point for our new 3.* versions across all packages?

The versioning scheme for iree-turbine is rooted on the then-current PyTorch released version, with optional date-based dev/pre-release suffixes (i.e. rcYYYYMMDD or devYYYYMMDD) or intra PyTorch releases (i.e. postVVVV).
This process is being trialed to correspond with the 2.3.0 release of PyTorch. In this scenario, the pinned nightly build of IREE is considered current and promoted as part of the Turbine release to PyPI (and the release is marked as not pre-release on the GitHub releases page).

I just pushed iree-turbine version 2.5.0 (https://github.com/iree-org/iree-turbine/releases/tag/v2.5.0), which I guess we could say coincides with PyTorch 2.5.0 (https://github.com/pytorch/pytorch/releases/tag/v2.5.0), but that's mostly a coincidence.
We could also have iree-turbine keep tracking PyTorch versions and instead start the iree-base-compiler/iree-base-runtime versions at 1.0.0. I do like taking this opportunity to use a common version scheme across all of our packages, diverging from external projects like PyTorch.

That quote is from https://github.com/iree-org/iree/blob/main/RELEASING.md , which also then has this section:

In the future, we would like to adopt a real versioning scheme (beyond the
nightly calver+build number scheme) and manage promotion and pinning of the
core IREE dep more explicitly and in alignment with how downstreams are using
it.

We are starting to roll out the new versions and package names now. Hoping to have nightly releases of iree-base-compiler and iree-base-runtime tonight, then packages on PyPI tonight or tomorrow.

This new version scheme has now been rolled out completely with https://github.com/iree-org/iree/releases/tag/iree-3.0.0 and documented at https://iree.dev/developers/general/versioning-scheme/.
Some follow-up tasks:

[ ] https://github.com/iree-org/iree/issues/19193
[ ] Mark the old iree-compiler and iree-runtime Python packages as deprecated somehow (push a new release of each using calver, log a warning on import?)

authors: ScottTodd marbre

repo: iree-org/iree


text:
[LLVMGPU] Set prefetching on translation info

This patch makes prefetch_shared_memory part of translation_info config dictionary, allowing us to control prefetching at dispatch level, instead of globally turning it on/off. Prefetching is still off by default, the flag makes KernelConfig add prefetch_shared_memory unit attribute to config dictionary.

@kuhar You would need to change your tuning script to explicitly put prefetching in tuning config after this patch

cc: @RattataKing ☝

FYI this improved the SDXL benchmarks we run in this repo (on mi250 using rocm):
E2E Benchmark Time: 1330.0 ms (golden time 1661.5 ms)
Scheduled Unet Benchmark Time: 340.0 ms (golden time 450.5 ms)
Prompt Encoder Benchmark Time: 16.8 ms (golden time 17.5 ms)
VAE Decode Benchmark Time: 288.0 ms (golden time 288.5 ms)

(we set --iree-llvmgpu-enable-prefetch=true in https://github.com/iree-org/iree/blob/main/build_tools/pkgci/external_test_suite/sdxl_vae_decode_gpu_rocm_gfx90a.json)

Results were visible on presubmit here: https://github.com/iree-org/iree/actions/runs/9681801742
"Golden" times can be updated at the bottom of this file to pin down the improvements: https://github.com/iree-org/iree/blob/main/.github/workflows/pkgci_regression_test.yml

FYI this improved the SDXL benchmarks we run in this repo (on mi250 using rocm):
E2E Benchmark Time: 1330.0 ms (golden time 1661.5 ms)
Scheduled Unet Benchmark Time: 340.0 ms (golden time 450.5 ms)
Prompt Encoder Benchmark Time: 16.8 ms (golden time 17.5 ms)
VAE Decode Benchmark Time: 288.0 ms (golden time 288.5 ms)

(we set --iree-llvmgpu-enable-prefetch=true in https://github.com/iree-org/iree/blob/main/build_tools/pkgci/external_test_suite/sdxl_vae_decode_gpu_rocm_gfx90a.json)

Results were visible on presubmit here: https://github.com/iree-org/iree/actions/runs/9681801742
"Golden" times can be updated at the bottom of this file to pin down the improvements: https://github.com/iree-org/iree/blob/main/.github/workflows/pkgci_regression_test.yml

This would mean that not using prefetching on the tuned configurations is actually better. Adding a parameter for prefetching to the tuning script might be a good idea @kuhar @RattataKing

authors: Groverkss ScottTodd kuhar


text:
Listen on multiple ports?

Is there a common pattern for listening on multiple ports (say 80 and 443), while preferably sharing the same threadpool?

Hm... Not to my knowledge at this moment. One possibility is just listening on 443 with a second Iron instance and proxying it to the 80.

When 0.7 is released you might be able to configure hyper to listen to multiple ports and then mount iron as service creator.

authors: Hoverbear nathanaeljones phlmn

repo: iron/iron


text:
check boot of vm with ssh connection

Proposed Changes
Fixes #217

i did over 300 runs and every run was successful. i couldn't simulate problem with getting private IP. It looks as env problem.

PR can be merge after PR https://github.com/ironcore-dev/libvirt-provider/pull/245. Some small changes for improve stability from this PR will be implemented there.

repo: ironcore-dev/libvirt-provider


text:
Apresentação - Módulo 3

Pessoal, como entregáveis do terceiro projeto, temos, dentre outros:

2 URLs do projeto (front e backend)
2 URLs do repositório (github)
URL dos Slides

Usem esta issue para compartilhar seus projetos.
@gbrein @marbmo  @pdiv55  @sanychernizon  @dioliveira84  @Wilkor  @sandrabosk  @gsicuto

https://bybeni-front.herokuapp.com/
https://bybeni-back.herokuapp.com/
https://github.com/sanychernizon/bybeni
https://github.com/sanychernizon/bybeni-server
https://slides.com/sanychernizon/bybeni/live

RACHEI by @marbmo e @pdiv55 :

https://app-rachei.herokuapp.com/

https://api-rachei.herokuapp.com/

https://github.com/pdiv55/rachei-front

https://github.com/pdiv55/rachei-back

https://slides.com/pdiv55/rachei

https://github.com/gbrein/Live-Xp-Front
https://github.com/gbrein/Live-Xp-Back
https://serene-peak-75978.herokuapp.com/
https://aqueous-plains-46792.herokuapp.com/
https://slides.com/gbrein/deck-1

https://github.com/Wilkor/front-react-bigbets/
https://ironpet-me.herokuapp.com/api/v1
https://bigbets.stackblitz.io/
https://docs.google.com/presentation/d/1zp_80w0k-YttElZUonyXsQ5NL_5wHb7pBd2zgTN-lfg/edit?usp=sharing


text:
SSL Error: CERT_UNTRUSTED on Linux and OS X 10.6.8

We've been getting this error since sometime mid-morning on Oct 18, before that worked fine. Same problem on Linux.
info it worked if it ends with ok
verbose cli [ 'node', '/usr/local/bin/npm', 'install', '.' ]
info using npm@1.0.99
info using node@v0.4.12
verbose /usr/local/bin/node node symlink
verbose config file /Users/rhutchis/.npmrc
verbose config file /usr/local/etc/npmrc
verbose config file /usr/local/lib/node_modules/npm/npmrc
silly testEngine { name: 'app',
silly testEngine   version: '0.0.1',
silly testEngine   dependencies: { 'http-proxy': 'http-proxy' },
silly testEngine   _id: 'app@0.0.1',
silly testEngine   devDependencies: {},
silly testEngine   engines: { node: '*' },
silly testEngine   _engineSupported: true,
silly testEngine   _npmVersion: '1.0.99',
silly testEngine   _nodeVersion: 'v0.4.12',
silly testEngine   _defaultsLoaded: true,
silly testEngine   scripts: {} }
verbose caching /private/tmp/npm-test/package.json
verbose loadDefaults app@0.0.1
verbose where, deps [ '/private/tmp/npm-test', [ 'http-proxy' ] ]
verbose from cache /private/tmp/npm-test/package.json
info preinstall app@0.0.1
verbose from cache /private/tmp/npm-test/package.json
verbose into /private/tmp/npm-test [ 'http-proxy@http-proxy' ]
verbose cache add http-proxy@http-proxy
verbose cache add [ 'http-proxy@http-proxy', null ]
silly cache add: name, spec, args [ undefined,
silly cache add: name, spec, args   'http-proxy@http-proxy',
silly cache add: name, spec, args   [ 'http-proxy@http-proxy', null ] ]
verbose parsed url { pathname: 'http-proxy@http-proxy',
verbose parsed url   href: 'http-proxy@http-proxy' }
silly cache add: name, spec, args [ 'http-proxy',
silly cache add: name, spec, args   'http-proxy',
silly cache add: name, spec, args   [ 'http-proxy', 'http-proxy' ] ]
verbose parsed url { pathname: 'http-proxy', href: 'http-proxy' }
info addNamed [ 'http-proxy', 'http-proxy' ]
verbose addNamed [ null, null ]
info addNameTag [ 'http-proxy', 'http-proxy' ]
verbose GET http-proxy
verbose raw, before any munging http-proxy
verbose url resolving [ 'https://registry.npmjs.org/', './http-proxy' ]
verbose url resolved https://registry.npmjs.org/http-proxy
verbose etag "AWGI6DQIJ0AFENBDJJCKI3R94"
ERR! Error: SSL Error: CERT_UNTRUSTED
ERR!     at ClientRequest. (/usr/local/lib/node_modules/npm/node_modules/request/main.js:241:28)
ERR!     at ClientRequest.g (events.js:143:14)
ERR!     at ClientRequest.emit (events.js:64:17)
ERR!     at HTTPParser.onIncoming (http.js:1357:9)
ERR!     at HTTPParser.onHeadersComplete (http.js:108:31)
ERR!     at CleartextStream.ondata (http.js:1231:22)
ERR!     at CleartextStream._push (tls.js:303:27)
ERR!     at SecurePair.cycle (tls.js:577:20)
ERR!     at EncryptedStream.write (tls.js:96:13)
ERR!     at Socket.ondata (stream.js:36:26)
ERR! Report this entire log at:
ERR!     http://github.com/isaacs/npm/issues
ERR! or email it to:
ERR!     npm-@googlegroups.com
ERR!
ERR! System Darwin 10.8.0
ERR! command "node" "/usr/local/bin/npm" "install" "."
ERR! cwd /private/tmp/npm-test
ERR! node -v v0.4.12
ERR! npm -v 1.0.99
verbose exit [ 1, true ]

I meant to add that if I go to https://registry.npmjs.org/http-proxy in a browser I'm getting an SSL error.

Yes, you should get an SSL error in your browser, if you don't add the CA cert to your browser's list of trusted certs.
What does this output?
npm config ls
npm config get ca

You can work around this in a few ways:

Put the npmCA certificate as the "ca" configuration (which should be the default.)
Set the strict-ssl configuration flag to false.  (default is true).
Set the registry config to a non-ssl registry url: http://registry.npmjs.org/

Btw, this is the npmCA certificate:
$ npm get ca
-----BEGIN CERTIFICATE-----
MIIChzCCAfACCQDauvz/KHp8ejANBgkqhkiG9w0BAQUFADCBhzELMAkGA1UEBhMC
VVMxCzAJBgNVBAgTAkNBMRAwDgYDVQQHEwdPYWtsYW5kMQwwCgYDVQQKEwNucG0x
IjAgBgNVBAsTGW5wbSBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxDjAMBgNVBAMTBW5w
bUNBMRcwFQYJKoZIhvcNAQkBFghpQGl6cy5tZTAeFw0xMTA5MDUwMTQ3MTdaFw0y
MTA5MDIwMTQ3MTdaMIGHMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExEDAOBgNV
BAcTB09ha2xhbmQxDDAKBgNVBAoTA25wbTEiMCAGA1UECxMZbnBtIENlcnRpZmlj
YXRlIEF1dGhvcml0eTEOMAwGA1UEAxMFbnBtQ0ExFzAVBgkqhkiG9w0BCQEWCGlA
aXpzLm1lMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLI4tIqPpRW+ACw9GE
OgBlJZwK5f8nnKCLK629Pv5yJpQKs3DENExAyOgDcyaF0HD0zk8zTp+ZsLaNdKOz
Gn2U181KGprGKAXP6DU6ByOJDWmTlY6+Ad1laYT0m64fERSpHw/hjD3D+iX4aMOl
y0HdbT5m1ZGh6SJz3ZqxavhHLQIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAC4ySDbC
l7W1WpLmtLGEQ/yuMLUf6Jy/vr+CRp4h+UzL+IQpCv8FfxsYE7dhf/bmWTEupBkv
yNL18lipt2jSvR3v6oAHAReotvdjqhxddpe5Holns6EQd1/xEZ7sB1YhQKJtvUrl
ZNufy1Jf1r0ldEGeA+0ISck7s+xSh9rQD2Op
-----END CERTIFICATE-----

which you can also find in the npm source code, in lib/utils/config-defs.js, for verification.  You can verify the cert in the source as being authentic by checking the last tagged commit, which is signed with my GPG private key.  The associated public key can be found by searching the MIT pgp key database for my email address: http://pgp.mit.edu:11371/pks/lookup?search=i%40izs.me&op=index

This appears to be caused by a configuration problem on a local network. We are looking into it. If we use a different network everything is working.
Sorry for the noise, and thanks for your help.

authors: hutch isaacs

repo: isaacs/npm


text:
[QUESTION] Is the example working?

Given example once runned does not show an overlay over the text as it's supposed to do (like in the gif image)

yeah, are you using the latest version?

Hi! Thanks for your super fast reply!
That's the version:
"@ismaelmoreiraa/vision-camera-ocr": "^3.0.1",

That's it, this version needs the vision library in version 4 or higher. In this version, vision has a different preview that cannot match with the screen preview above.
I didn't find a way of make it simple, but in the vision v4 you draw directly in the frame itself. :)
https://react-native-vision-camera.com/docs/guides/skia-frame-processors

authors: frabanca ismaelsousa

repo: ismaelsousa/vision-camera-ocr


text:
Option to not force glide when glide: ALLOW

The "glide: ALLOW" flag forces users to glide, even when on the ground. It prevents users from walking at all.
The use case where this becomes a problem is as follows:
Global region (standard global region): No gliding allowed. Glide flag is set to DENY
Inner region (no parent / no inheritance): Gliding allowed. I need to override the glide DENY on the global region.
When I use the glide: ALLOW flag in my inner region everybody ends up flat on the ground in "glide position". Walking is no longer possible. The flag forces glide rather than allowing it. To allow normal game play I had to remove this flag.
When I set my inner region (with no glide flags set) to a higher priority than the global region, glide still isn't allowed in the inner region. This is because even though the inner region has a higher priority, a glide flag actually needs to be set (allowed or denied - not "unset") in the higher priority region for it to take precedence.
Is this a bug in WGEP? Hoping you can take a look.
Thanks!

The original suggestion was to allow gliding without having elytra equipped, so the ALLOW flag was supposed to do that. Tbh most of the flags would benefit from having "DEFAULT" option

Hi. Thanks for finding time to take a look at this. I can see how it would be cool to allow glide without an Elytra, but even when equipped with an Elytra (for real) you can still walk. With the glide: ALLOW flag set you can't walk anymore! ;) That seems a bit buggy. Even without addressing my particular use case, maybe there is a way to allow a player to walk when glide: ALLOW is set?
However, In my case I really wouldn't want to allow people to glide without an elytra. I just want to deny it's use in a region.
Having a "DEFAULT" option would be nice, but I'm pretty sure you mean that WG itself needs to provide this option so that your plugin can use it. i.e. "DEFAULT" is different than "unset" - "DEFAULT" is a real value for the flag. The priority on the flag values from low to high could be 0-unset, 1-allow, 2-deny, 3-default. In my scenario, the global region would be set as priority 0 / glide: DENY. The inner region could be set to priority 0 / glide: DEFAULT. In this case glide would be allowed in the inner region without forcing it with glide: ALLOW. You could set a higher priority on the inner region but you wouldn't need to. I suppose you could also set the priorities as 0-unset, 1-allow, 2-default, 3-allow, and then use a higher priority on the region to override allow, etc... anyway, all of this can work in different ways if there was a real "DEFAULT" value for the flag.
Anyway, is that what you mean by having a "DEFAULT" option? and, If yes... I guess that means without a major update to WG, there isn't much you can do to fix things in WGEF. Is that correct?

I could resolve this in WGEF itself by changing it to custom state flag which has three options, ALLOW, DENY and DEFAULT/NONE/UNSET. I have seen this being suggested for other types of flags also to allow overriding the option in child regions.
Regarding the issue of not being able to walk depends a lot whatever the client sends is it on the ground, I have yet to test this. If thats not the case however it would most likely need another state flag just for the glide flag, FORCED. Meaning allow allows gliding on the area and FORCED, as the name suggest, forces you to glide like the current behavior does.

It would be great if you could handle it in WGEF with a custom state flag. I'm very happy to test / help any way I can if you are able to some find time to do the dev work.
As for the inability to walk with glide: ALLOW set, I have observed the "forced glide" at various elevations (if that's what you mean) - not on purpose. Just because I happened to be at different elevations when testing it. If there is something specific you want me to test here, I can do that too.
I appreciate you taking time to look at this. Thanks!

I could resolve this in WGEF itself by changing it to custom state flag which has three options, ALLOW, DENY and DEFAULT/NONE/UNSET. I have seen this being suggested for other types of flags also to allow overriding the option in child regions.

But wouldn't DEFAULT (or whatever) be the same as not setting the flag? Why does this need an custom state?

But wouldn't DEFAULT (or whatever) be the same as not setting the flag? Why does this need a custom state?

My understanding is that DEFAULT would actually be a flag value, so not the same as not setting it / "UNSET". The problem is that WG region priority handling only comes in to play if a region flag has an actual value (not "UNSET"). However, for WGEF to set a new flag value of "DEFAULT" it means that WG would need to accept/respect 3 flag values: ALLOW, DENY, DEFAULT and then UNSET / no value set at all.
I'm realizing how confusing what I just wrote is!! ;) Here is how I think it would work:
Global region: DENY Glide
Inner Region: ALLOW Glide + higher priority than global region
Result: Glide is denied in the global region but forced in the inner region because ALLOW == FORCE (and nobody can walk).
Global Region: DENY Glide
Inner Region: "UNSET"/no value for the Glide flag + higher priority than global region
Result: Glide is denied in the global region and Glide is still denied in the inner region. Why? - Even though the inner region has a higher priority, no actual Glide flag value is set (UNSET is not a value) and WG will only apply priority if a flag value is set. So, the inner region's higher priority "UNSET" is ignored by WG and the global region's DENY Glide flag still takes precedence over the inner region.
Global Region: DENY Glide
Inner Region: DEFAULT Glide + higher priority than global region
Expected Result: Glide is denied in the global region but allowed (without forcing) in the inner region. Why? - If we can set an actual value of "DEFAULT" for the glide flag in the inner region (a value that WG will accept/respect) then WG will consider the higher priority on this region for the Glide flag and override the global Glide DENY / returning the inner region to the "default" state without forcing Glide using ALLOW.
Of course, I may have no idea what I'm taking about (highly likely actually), so please correct me as needed!! ;)
Assuming this is what isokissa3 had in mind, it seems to me that WG would need to accept DEFAULT as a valid flag value, and I'm not sure if it does?

This is AWESOME! Thank-you! I've tested it in Paper MC v1.15.2  Build 87 with the latest version of WorldGuard (bukkit-7.0.2). It works great!
The only problem I have is that the flags don't persist through a server restart. I have Glide:DENY in the global region and Glide:ALLOW in my inner region. I've tried it several times. After a server restart the glide flags disappear.
Once in the server log I saw a WorldGuard error saying something like "cannot enumerate glide flag...". Although I can consistently reproduce the state after restart where the flags do not persist, I cant reproduce these errors/warnings in log. No idea why.
If you have time, could you help me to troubleshoot?
Thanks again for making this update. I think it will be really useful to others using the plugin too!
P.s. - Not sure if this is the right place to handle this. Let me know.

Ah yeah, this was small mistake on my part, fixed now

That's great. Glad it was something simple! Can I download the new plugin jar now from spigotmc or does it take time for it to update? Seems like it's the same jar (same file hashes).

No, I need to put it manually on spigot, you can grap the dev build which is always up to date with the Github's sources.

Ok, got it. Working great! Thanks again for taking time to do this. I really appreciate it. I had to disable elytra flight on the server, and now it's back (in designated regions). The kids are VERY happy. I showed them this thread so they know that a young guy like you is making great Minecraft plugins and helping everybody out. Very cool. Thank-you!


text:
🛑 bomberofloridablanca.isolucion.co is down

In a1490e2, bomberofloridablanca.isolucion.co (https://bomberofloridablanca.isolucion.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: bomberofloridablanca.isolucion.co is back up in 007255a after 8 minutes.

repo: isolucionco/EstadoIsolucionHosting


text:
Helm value mixer.enabled defunct and misleading

Describe the bug
values.yaml has a mixer.enabled flag. This is never used in the helm templates in favor of mixer.policy.enabled and mixer.telemetry.enabled. This is confusing, because users (or at least me), will set mixer.enabled=false and be confused that it is still running. This flag is even used in our documentation, making our minimal install docs broken: https://istio.io/docs/setup/kubernetes/minimal-install/. I have tested the docs - telemetry is installed.
Expected behavior
mixer.enabled should do something.
OR
mixer.enabled should be removed and docs updated.
Option two is likely simpler.

Forgot to check the new docs, https://preliminary.istio.io/docs/setup/kubernetes/additional-setup/config-profiles/ actually uses the values-minimal.yaml which is correct, so no need for docs to be updated.

Fixed by https://github.com/istio/istio/pull/13214

repo: istio/istio


text:
Environments Workgroup 1.2 Features and Code Muave Epic

These are features and code mauve wok planned in the Environments workgroup. Focusing on these items is our priority. Folks are free to submit work unrelated to these items. We can consider altering the Epic features over time.
(P0) Code Mauve:
stability testing for multi cluster and mesh expansion
Load balancing with locality (howardjohn)
More automated stability tests for whitebox - stability, performance, etc
Tests for environments WG related documentation
multicluster
mesh expansion: #13374
SRE-related documentation
metrics
alerts
selection of applications added to test cases
casandra
consul
kafka
nats
mysql
postgresql
redis
Will be added under modular installer, and be included by the test/stability.
MCP automated stability and install tests
Move the install/upgrade to KIND
Move bookinfo tests to KIND
Evaluate KIND for CNI tests.
Features:
(P?) Distroless images Issue #12122 (P?)
(P0) Decomposed Installation - repository: https://github.com/istio-ecosystem/istio-installer
(P1) Operator - repository:
(P1) Multicluster Gaps Issue #11731

zenhub spit out an error "Unknown error occured".  This is a duplicate so closing.