Flip images are tiny on phone screen

Two screenshot from my OnePlus 7 phone today at the end of this post. The flip images are so tiny, that I had absolutely no way of making anything out of them. Failed the validation with 1/6. (Please note that the images here show so large that you can actually make out their contents - imagine the full image shrinked to the size of a phone screen).
Two suggestions based on this:

Fix the image size.
Allow the user to zoom in/out on the app. With zooming, it would have been possible to complete the validation (even if cumbersome). Especially because the phone layout seems very much work-in-progress at the moment, i.e. there is unnecessary panning left/right when all elements don't fit the screen. It doesn't make any sense to disallow zooming.

Training validation looks completely fine on my phone, by the way.

Hi, please provide your idena address.

Please open the issue again if the problem still exists.


Never get prompt to enter PIN

I have installed Domoticz on my pi and am able to access it from the web and have created a dummy device and test lights on the site
latest commit of homekit is also installed on the pi and the config file is set up to point to local address and port 8080
I can see the devices in the insteon+ app however after selecting the device, I never get a pop up to enter the pin and eventually the device times out and i get the following printed to the console
[Domoticz] There was a problem connecting to Domoticz.
An Error Occured on HAP side connection, { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
Server Disconnected

I think @joepv will have to comment here ... I'm not very familiar with this system.

@salimyzadeh: the PIN is only asked when adding a device. This looks like a configuration issue. Is the Domoticz server running on the same host? If not use the correct IP/PORT and not <IP_ADDRESS> (localhost).

Yes it's running on the same host and port 8080
I then tried to run directly through HAP-NodeJS using command "node core.js" and removed the persist directory and reset the phone configuration but get the same error. I can see the sample devices in the insteon+ app and after tapping "Add anyway," I never get a prompt for the pin
the console shows the following:
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister
Parsing accessory: Fan_accessory.js
Parsing accessory: GarageDoorOpener_accessory.js
Parsing accessory: Light_accessory.js
Parsing accessory: Lock_accessory.js
Parsing accessory: Thermostat_accessory.js
HAP-NodeJS starting...
Cannot find secret key, creating One...
TCP server accepting connection on port: 51826
HAP Server is listening
Cannot find secret key, creating One...
TCP server accepting connection on port: 51828
HAP Server is listening
Cannot find secret key, creating One...
TCP server accepting connection on port: 51832
HAP Server is listening
Cannot find secret key, creating One...
TCP server accepting connection on port: 51838
HAP Server is listening
Cannot find secret key, creating One...
TCP server accepting connection on port: 51846
HAP Server is listening
New Session 49202
Client Disconnected
An Error Occured on HAP side connection, { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
Server Disconnected

So just HAP-NodeJS by itself doesn't work with the "sample" accessories? If so, I might post this issue on that repo.

To test please remove all your accessories from the config en run only the Domoticz platform shim.
Also remove the key file in the homebrigde folder for the devices to get a fresh start pairing everything.

You might also want to try resetting HomeKit on your device under Privacy > HomeKit or try a different device if you have one.  Are you running the latest (public release) of iOS?

after starting from scratch i now have everything working
looks like best way to install node is:
apt-get update
apt-get install git-core libnss-mdns libavahi-compat-libdnssd-dev -y
wget http://node-arm.herokuapp.com/node_latest_armhf.deb
dpkg -i node_latest_armhf.deb
thanks

Good to know - I'll add this to the wiki.

What OS are you running on your pi? And are those the complete instructions?

I'm running the latest version of rasbian and yes those are the complete instruction. I then followed the instruction listed in the readme


Wave effect bugs

So I have found minor bugs and here it is, 1. Redstone wave, 2. Deepslate spikes(I dont know whats it called) wave. Edit:I found another bug, 3. Amythest wave.

_**`

`**_

I already noticed those issues  since I added wave effect on flowers, saplings and etc.
this detection checks were the polygon vertex is.
if it's not on 16x16texture grid, sharder treats as wavable block.
this is why accidentally detects Amethyst and Dripstone.
But Redstone is defferent.
I'll fix Redstone in next release.

Ok

I forgot to say that campfire wave too


Render output in a tree instead of a flat list

We have a fantastic divider to structure test output in a tree.
It's files.
We could group the list of green ticks by which file the test('...') occur in.
The only problem is I'm not sure how to place file meta information in tap output or when calling faucet from the cli directly.

Are subtests parsed to TAP as something you can use in Faucet? Example with tape:
test('Card component', (t) => {
  t.test('  should show header', (t) => {
    // some assertions
    t.end();
  });
  t.test('  should show age', (t) => {
    // some assertions
    t.end();
  });
  t.test('  should not show age when not available', (t) => {
    // some assertions
    t.end();
  });
  t.end();
});


Missing 'name' attribute in 'GCSFile' object when accessing PDF files

Description:
In the context of using gcsfs with llama-index for reading files from a GCP bucket, an error occurs for PDF files indicating that the 'GCSFile' object has no attribute 'name'. This issue does not occur when accessing DOCX files. It suggests that there may be an inconsistency or a bug in how gcsfs handles file metadata, specifically for PDF files.
import google.auth
from llama_index.core import SimpleDirectoryReader
from gcsfs import GCSFileSystem
from fs_gcsfs import GCSFS

def __load_gcp_bucket(bucket_path: str):
    credentials, project_id = google.auth.default(
        scopes=["https://www.googleapis.com/auth/devstorage.read_only"]
    )

    gcp_fs = GCSFileSystem(project=project_id, token=credentials)

    reader = SimpleDirectoryReader(
        input_dir=bucket_path,
        fs=gcp_fs,
    )

    documents = reader.load_data()
    return documents

documents = __load_gcp_bucket("<bucket-path>/")
print(documents)

Version:

gcsfs: (specify the version you're using, e.g., 2023.6.0)

Steps to Reproduce:

Use GCSFileSystem from gcsfs to access files in a GCP bucket.
Attempt to read metadata from both .pdf and .docx files.
Compare the behavior and output to identify the absence of the name attribute in the case of PDF files.

Relevant Logs/Tracebacks:
Failed to load file <GCS bucket path>/file.pdf with error: 'GCSFile' object has no attribute 'name'. Skipping...

Please show the full traceback, so we can see what llama_index is trying to do. You may also want to cross-post on their tracker. No GCSFile has a .name, but they do have a .path .


[$500] mWeb/Safari - Chat - Compose box disappears while editing a message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.5-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to any conversation
Tap & hold on sent msg
Select edit comment
Add some message
With the edit message box still open, tap anywhere outside
Click the green tick mark

Expected Result:
After modifying the message, we should see the compose box
Actual Result:
The compose box disappears when we modify the message
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3c02074b-5b15-4000-b38e-edf3c457a6ca
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01dc941d9d412023ac
Upwork Job ID:<PHONE_NUMBER>591545344
Last Price Increase: 2023-11-29

I'm checking this out. I didn't find anything in the list of PRs that I thought could cause this. I am now trying to run git bisect to find what caused this to change.

I was able to reproduce this on production. I am going to remove the deploy blocker label and we can work on this like a normal bug.

Actually @lanitochka17 I am not able to reproduce this on staging or production either - are you still able to?

@slafortune Only 2 out of 4 testers were able to reproduce this issue
https://github.com/Expensify/App/assets/78819774/2577af32-fab6-45cd-bf56-1ca0200fc150

I see 2 edit boxes when I am trying to reptoduce. Is that expected as per UI design? but this looks confusing to me as an end user.

Looking into the root cause in either case. Once I have my investigation complete, will submit a proposal.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Composer disappears when close or save the unfocused edit composer
What is the root cause of that problem?
When close or save the edit composer, deleteDraft is called. This function changes the onyx focused state to false like below
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L288-L290
This changes the onyxFocused state and composerFocusKeepFocusOn is called
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L139-L141
If the edit composer wasn't focused, isFocused is false and so the the edit composer input gets focused again
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/libs/actions/InputFocus/index.website.ts#L19-L22
So onFocus callback is called the main composer is hidden
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L418
This is the root cause
Note: Clean up function is called when the edit composer gets unmounted. Why doesn't the main composer appear again?
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L207
All effect callbacks are called after the rendering and all clean up functions are called after the effect callbacks are called. In effect callback we focus the edit composer input and the setIsFocused was called inside the onFocus callback. But setIsFocused is asynchronous and isFocused becomes true at the next rendering. Since clean up functions are called after the effect callbacks are called before the next rendering, there is no chance for isFocused to become true. So isFocusedRef.current is still false at the time clean up is called and isActive would return false and the clean up will return early. That's why the clean up function wasn't able to show the main composer again
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L194-L196
What changes do you think we should make in order to solve the problem?
We change the onyxFocused state in the deleteDraft function and this causes the refocusing. We can move this code to the clean up function
Move the below code
https://github.com/Expensify/App/blob/ef3d8cd3f9f069a2d917ac7c1ee0a5baf7baaffa/src/pages/home/report/ReportActionItemMessageEdit.js#L289-L290
before this line
This would haven't any side effects and works perfect

Result
https://github.com/Expensify/App/assets/126839717/c6c3eb7a-b2af-41ff-9ec0-ff12f00182a3

What alternative solutions did you explore? (Optional)
We can set the isFocusedRef.current to true in the onFocus callback. This makes sense since it synchronizes the focused state and the isActive function

Reviewing

@Krishna2323 your RCA is not complete and I don't think adding a new state is a good idea. We don't want to trigger composerFocusKeepFocusOn's useEffect altogether.

@s-alves10 your RCA is correct and very detailed. I agree with your solution, rearranging code is the best approach here.
We can go with @s-alves10 's proposal
C+ reviewed 🎀 👀 🎀

@alitoshmatov
PR is ready for review: https://github.com/Expensify/App/pull/32598

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/22984
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/22984/files#r1440314704
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No need
Determine if we should create a regression test for this bug: No regression needed

@slafortune This one is ready for payment

All paid!  Thanks @alitoshmatov !


Update README.md

Fix indentation of code blocks so that numbering of the ordered list works properly.

Oh thanks!


Support for .vhd / Azure

I'd be awesome to create a .vhd image that I could upload / run easily on Azure.

Sorry that we let this hang for so long. I had a quick look today and started some quick draft work in https://github.com/osbuild/bootc-image-builder/pull/634

I think this should be re-opened as https://github.com/osbuild/bootc-image-builder/pull/634 has not been merged in yet to be added to bootc-image-builder.


Transition to elections models in python-opencivicdata-django

As the implementation of the election models solidify in python-opencivicdata-django, we need to move things around a bit.

[x] Clean up calaccess_processed/models/__init__.py.
[x] Clean up calaccess_processed/admins/__init__.py.
[x] Move PartyManager loading logic to a loadparties management command.
[x] Move BallotMeasureContestManager logic to a loadballotmeasurecontest management command (some of what we need might be in ElectionsManager).
[x] Move CandidacyContestManager logic to a loadcandidatecontests management command (some of what we need might be in ElectionsManager).
[x] Create a loadofficeholders management command, which will follow from #46.
[x] Create a loadretentioncontests management command from recall-related logic in ElectionsManager.
[x] git rm calaccess_processed/models/opencivicdata/
[x] git rm calaccess_processed/admins/opencivicdata/


Wrong most recent date in hover tip

When I hover over the a signal in the survey dashboard it tells me the most recent data available was from Sept 23 but you can see from the spark line that it's actually available all the way until Sept 25.

Rating Scale (1 is minor, 7 is severe): 1

https://api.covidcast.cmu.edu/epidata/covidcast/meta?signal=fb-survey:smoothed_wcli
shows:
"max_issue": 20210927,
"max_time": 20210925,
"min_time": 20200406,
"name": "COVID-Like Symptoms (Weighted 7-day average)",
"short_description": "Estimated percentage of people with COVID-like illness ",
"signal": "smoothed_wcli",

however, when querying the data
https://api.covidcast.cmu.edu/epidata/covidcast/?signal=fb-survey:smoothed_wcli&geo=nation:us&time=day:20210924-20211010
the last entry is
{
"geo_value": "us",
"signal": "smoothed_wcli",
"source": "fb-survey",
"geo_type": "nation",
"time_type": "day",
"time_value": 20210926,
"direction": null,
"issue": 20210928,
"lag": 2,
"missing_value": 0,
"missing_stderr": 0,
"missing_sample_size": 0,
"value": 1.4717249,
"stderr": 0.0337678,
"sample_size": 196205
}

The tooltip is based on the meta data the sparkline on the real data. This explains the discrepancy.

iirc this was a wontfix -- the "most recently available" comes from metadata, and metadata is only updated daily. The behavior is still visible in the current dev preview:

Ok let's leave this issue open so we can schedule a hotfix at some point, but this shouldn't hold up v3 release.
I don't want this to be wontfix indefinitely---we should either disable this hovertip completely or ensure it's showing the right information.

I wonder how expensive it is that the server computes for a given list of signals what the maximum date it. So far we don't have an simple api to compute that. However, that is essentially the main discrepancy between the meta data and the real data.

@sgratzl Just a reminder about this for v3.1. Thanks!

see also https://github.com/cmu-delphi/delphi-epidata/issues/793 for a server side solution to this problem

Thanks @sgratzl. I'm happy for you and @krivard to decide on what's the best solution for this one.


Cannot return null for non-nullable field (nexus-prisma)

Nested @embedded relation returns null from nexus-prisma, while prisma-client works fine.
I have a simple data model:
type Polozka{
  id: ID! @id,
  nazev: [Preklad!]!,
  mnozstvi: Float!,
  cena: Float!,
  createdAt: DateTime! @createdAt,
  updatedAt: DateTime! @updatedAt
}

type Preklad @embedded{
  jazyk: Jazyk!,
  text: String!,
}

type Jazyk{
  id: ID! @id,
  nazev: String! @unique,
  kod: String! @unique,
  createdAt: DateTime! @createdAt
}

Description
Two identical queries:
query{
  polozkas{
    id
    nazev{
      text
      jazyk{
        id
        nazev
        kod
      }
    }
  }
}

Return different results. Prisma client returns correctly all nested relations, but nexus-prisma returns null on the nested jazyk relation. I checked the mongodb in the docker and the database is correct with all the relations etc. It seems that nexus-prisma can't handle an embedded relation, which has a link relation. Implementation of nexus-prisma server code was done by following the official tutorial and github examples, everything is exposed, etc.
I expose the queries as following, I also tried to modify the resolver and see what's happening:
    t.prismaFields(['polozkas'])
    /*t.field('polozkas',{
      type: 'Polozka',
      list: true,
      resolve: async(parent: any, object: any, ctx: Context, info: GraphQLResolveInfo) => {
        console.log(info);
        return await ctx.prisma.polozkas({}).then(polozky => {
          polozky.forEach((element: any) => {
            console.log(element) //the jazyk relation is undefined here
          });
          return polozky;
        })
      }
    })*/

Screenshots

Hey there, are you using mongo?
If so, try adding databaseType: document to your prisma.yml file

I do have databaseType: document
My prisma.yml:
endpoint: http://<IP_ADDRESS>:4466
datamodel: datamodel.prisma
databaseType: document
hooks:
  post-deploy:
    - prisma generate
    - npx nexus-prisma-generate --client ./generated/prisma-client --output ./generated/nexus-prisma

generate:
  - generator: typescript-client
    output: ../src/generated/prisma-client/

Forgot the version details, so here we go:
Versions:

Connector: MongoDB
Prisma Server: 1.34.0
prisma CLI: prisma/1.34.0, node-v10.15.1
OS: Windows 10
other dependencies: nexus-prisma 0.3.7, nexus 0.11.7, graphql-yoga 1.17.4


Formatter: allow spaces in keyword arguments

Hi!
I ran into a minor snag with ruff format: a number of my projects format keyword arguments like name = value, for accessibility/readability reasons, which doesn't seem to be configurable yet.  For instance:
with NamedTemporaryFile(
	dir = target.parent,
	prefix = target.stem,
	suffix = target.suffix,
	delete = False,
	mode = "w",  # otherwise the file would be opened in binary mode by default
) as new: ...

was reformatted as
with NamedTemporaryFile(
	dir=target.parent,
	prefix=target.stem,
	suffix=target.suffix,
	delete=False,
	mode="w",  # otherwise the file would be opened in binary mode by default
) as new: ...

I tested under ruff 0.6.3, with an empty configuration, and searched for existing formatter issues containing keywords or spaces, prior to opening a new one.

Hi @nbraud
I prefer the formatting you described, which I'm familiar with from the JS ecosystem. However, we designed Ruff's style guide to follow PEP8, and the PEP8 recommendation for keyword arguments is not to use a space.

Don’t use spaces around the = sign when used to indicate a keyword argument, or when used to indicate a default value for an unannotated function parameter:
[source]

Introducing an option that makes this configurable is a possibility. Still, we've been intentional about only supporting few configuration options because the formatter's goal is to reduce the formatting-related discussions on PRs and configuration options only shift those discussions from the PR to discussing configuration options. You can read more about the motivation in Prettier's option philosophy.


Tutorial Problem - Report a problem should open a new tab

URL: /tutorials/email-web/send-an-email.html

When I click on "Report a problem" I would prefer it opens a new tab.

Thanks for suggesting this. It is much needed. It will be fixed with #144.


Selection area grows faster than scrolling

What is the problem?
Selection area grows faster than scrolling.
What is the current behavior?
When trying to drag selection-area beyond boundaries to initiate scroll, the area doesn't stick to a point in the scrolled content, but grows and gets bigger and bigger.
Please provide the steps to reproduce and create a CodeSandbox.

Go to https://simonwep.github.io/selection/.
Scroll down to the last example.
Start selecting selectables.
Drag the selection-area to the bottom border so that the content starts to scroll.
Observe that upper border of the selection-area moves faster than the scrolled content.

What is the expected behavior?
Upper border stays always at the same point relative to the content.
Your environment:
OS: Windows 10
Browser: Chrome, Firefox, latest versions
Environment: Official demo website (https://simonwep.github.io/selection/)

Seems to be broken as of the latest minor version... I'll fix it this weekend! :)

Okay, this was caused by the bug-fix for safari in #140 - should now work in all browsers equally good 😅

Wow! That was fast 😎!
Thanks!

Version 3.2.4 is out with a fix for this :)


Connection issues using router IP

Hello,
I'm running a vanilla minecraft server on my personal NAS at home and I'm getting a quite annoying issue for which I can't find any solution. I'm currently running Rockstor, and installed the container using the rocks-on feature of the distro.
Installation was easy and quick. However: I'm only able to access my MC server from the local network. I set up NAT forwarding and even opened ports in my routers firewall, but I keep getting a "timed out" error when trying to connect using my routers IP. Connecting with the local IP of the MC server works just fine.
Iptables and Ifconfig shows up the servers activity, and it doesn't seem like anything is wrong there. I looked through the internet for a solution but couldn't find one. Maybe you will give me one?
Thanks a lot

It sounds like a problem I had using the router provided by my internet provider. I finally discovered the NAT on their router didn't support hairpin routing. When removing the ISP's router and using my original router I was able to access my server by both its LAN IP address and my public IP address.

Don't think that's the issue. I already hosted a MC server on another machine under Ubuntu without having any issues using the routers ip to connect to the server inside the local network.
I also have a VPN running on my NAS which is accessible with devices logged in the local network but using the server ip to connect. (the VPN isn't installed in a Docker container).

I am going to close this since I'm afraid this issue is beyond the scope of this container/repo.


Add links to templates

Fill in the links section on templates, pointing to main UI elements in cluster.

this might be a bit misleading to users since these aren't actually used in any open source code.  but 👍 to the code

It's documented in the API docs, I think.


Implement var and std for Gaussians

Resolves #209

Codecov Report

Merging #210 (2e81178) into main (055d4c7) will decrease coverage by 0.10%.
The diff coverage is 75.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #210      +/-   ##
==========================================
- Coverage   95.64%   95.54%   -0.10%
==========================================
  Files          26       26
  Lines        1056     1055       -1
==========================================
- Hits         1010     1008       -2
- Misses         46       47       +1

Impacted Files
Coverage Δ

src/gaussians.jl
75.00% <50.00%> (-2.78%)
:arrow_down:

src/solution_plotting.jl
97.43% <100.00%> (ø)

src/initialization/common.jl
95.83% <0.00%> (-0.17%)
:arrow_down:

src/diffusions.jl
98.63% <0.00%> (-0.02%)
:arrow_down:

src/solution.jl
98.64% <0.00%> (-0.02%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


IIS interaction

Finally (/sadly) I have to start using .NET core now to host stuff. Been following it for many years but like many others in the IIS support community have been keeping at arms length and seeing how your little project pans out.
Are there any plans for proper IIS interaction for asp.net core stuff?
GUI stuff, similar information/diagnostic tools, WPI install components, etc. Stuff that over the decades I have been used too.

Are there any plans for proper IIS interaction for asp.net core stuff?

There are no plans to bring back an integrated pipeline if that's what you mean.

GUI stuff, similar information/diagnostic tools, WPI install components, etc. Stuff that over the decades I have been used too.

Can you be more specific here? I'm not exactly sure what you mean.
/cc @shirhatti

I don't mean the integrated pipeline.
I mean actually using IIS to manage asp.net core/kestral websites. Like you would with other technologies.
I am unclear how much understanding you have with IIS. But there is very little about IIS that says you
Take asp.net you see a load of icons, etc in the GUI irrespective of the pipeline used.
And example might be have IIS show up in the app pool that a .net CLR version might have a option of reverse proxy to Kestrel or something.
Other none native technologies to IIS like PHP have stuff like PHP manager that help manage PHP. You get a GUI icon and things to interact with. We don't even have that a net core or kestral thing to help.
I am unclear how much thought has been to have these sort of interactions with IIS. I presume you have spoken to people inside Microsoft. shrug I can say with confidence that no-one has reached out to the IIS community at https://forums.iis.net/ which I help look after.
WPI = Web Platform installer
As the future of asp.net seems to be core now. I am surprised there hasn't been more movement in this area.

Ah! You just mean pure management features. This was discussed very early on in the project but nothing ever came of it because we haven't invested the time. Now that 2.0 is coming to a close, it makes sense to revisit Thanks for the reminder.

I am unclear how much thought has been to have these sort of interactions with IIS. I presume you have spoken to people inside Microsoft that write/support IIS. shrug I can say with confidence that no-one has reached out to the IIS community at https://forums.iis.net/ which I help look after.

The overall team owns both ASP.NET Core, IIS and ASP.NET.

WPI = Web Platform installer

You'd like a web pi way to install .NET Core? That could be done but I would say the main difference is that things are alot less coupled to IIS (because obviously we need to run on all platforms now). That said, we could do more here to integrate at whatever level makes sense though I'm still unclear how much would actually add value. It would actually be good to get that kind of feedback. Most of the discussion around ASP.NET Core and IIS has been happening on:

https://github.com/aspnet/IISIntegration
https://github.com/aspnet/aspnetcoremodule

The team unfortunately hasn't been looking (AFAIK) at the IIS forums for ASP.NET Core feedback. We should make an ASP.NET Core section on the IIS forums to meet the community where they are at.
BTW @shirhatti is the IIS and ASP.NET Core Server PM, so we do have people working on both things 😄

I suppose I would expect it to be similar if not better support on Windows then previous iterations of  MS languages.
Although you have this as multi platform it see like Windows is neglected or at least given little love.
I would still expect the majority of hosting asp.net core stuff to be on Windows platforms. And for that there is a natural expectation of more interaction with IIS and Windows.
Even tools that don't exist for other platforms to be there or at least first on Windows.
Perfmon counters (hundreds and hundreds of asp.net non-core ones), detailed failed request tracing integration, etc are areas useful and established for troubleshooting that I would expect see. Probably by default windows event logging too.
WPI just seemed a logical pace for it to be and where some people would go to find it. And with no mention there it made it seem unofficial/incomplete and it just didn't seem ready for prime time for a language I would want to support in production.
tbh I don't know enough about core to know what other useful things will be.
It seems strange not to try and get the same or better experience for a new language than we have had previously. Maybe as you had little dialogue with people that look after the sites and the focus has been solely on the dev and engaging with the other open source community platforms it explains you direction.

The overall team owns both ASP.NET Core, IIS and ASP.NET.

Nice to see someone is managing the IIS product, All the IIS product team I knew left to join Azure, it seems, a few years ago and didn't actually know who was left.

Thanks for the feedback. We'll use it in future planning of ASP.NET Core + IIS features.

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


operator: ignore identity delete conflicts

Please ensure your pull request adheres to the following guidelines:

[X] For first time contributors, read Submitting a pull request
[X] All code is covered by unit and/or runtime tests where feasible.
[X] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[X] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[X] All commits are signed off. See the section Developer’s Certificate of Origin
[X] Provide a title or release-note blurb suitable for the release notes.
[X] Are you a user of Cilium? Please add yourself to the Users doc
[X] Thanks for contributing!

Ignore CiliumIdentity delete conflicts during the gc run (by skipping deletion and emitting a warning), allowing gc to continue if a subset of identities are conflicted. Prior to this change conflicts would cause gc to error, which could lead to an unexpected accumulation of stale CiliumIdentity objects.
Fixes: #33142
Ignore CiliumIdentity delete conflicts during the gc run (by skipping deletion and emitting a warning), allowing gc to continue if a subset of identities are conflicted. Prior to this change conflicts would cause gc to error, which could lead to an unexpected accumulation of stale CiliumIdentity objects.

I would consider this kind/bug.

/test

/test


chore: add gdata and wso2

This PR does the following:

Adds G DATA to the adopters page, network policy use case page, and security industry page
Adds WSO2 case study to adopters page, SaaS industry page

G-Data doesn't seem to be on the security vertical page?

G-Data doesn't seem to be on the security vertical page? maybe the case study section needs to be added?

It’s intentional, I was thinking since the logo is there it didn’t matter and the security page links to the network policy page, that’s where I added the G DATA case study.

WSO2 logo missing here and it should also be added to the network policy and Hubble pages

 WSO2 logo missing here and it should also be added to the network policy and Hubble pages

Hmmm, I wonder why it’s not displaying, I actually added it there, I’ll check what went wrong because I double checked it, probably the image format. I’ll investigate

security page is broken now

Hubble quote is good

 security page is broken now

Broken? I'm not sure what you mean by that


RHEL support

This script https://raw.githubusercontent.com/torch/ezinstall/master/install-deps doesn't support RHEL. Can you please let me know how can I use torch in Red Hat?

Hi, if you have the admin account, you can still use yum to install the packages, which is similar to CentOS depending on the RHEL version you have. If you are a normal user on a server, the only thing you could do is to compile the following libraries from the source, and export the path to Lua to let it access the libraries. Some modifications might be needed in the 'install.sh' file to make it work. It might take a bit of time though.
The libraries you need to compile are,
git-core libqt4-core libqt4-gui libqt4-dev libjpeg-dev libpng-dev ncurses-dev imagemagick libzmq3-dev gfortran unzip gnuplot gnuplot-x11 ipython

I wanted to install Torch on a cluster running RHEL 7.3 and was surprised that the install-deps script cannot handle this OS.
Before I tried to install on my local CentOS machine and it the script worked well.
The first problem is that the case
elif [[ -r /etc/redhat-release ]]; then
        DIST_VERS=( $( cat /etc/redhat-release ) ) # make the file an array
        DISTRO="${DIST_VERS[0],,}" # get the first element and get lcase
        VERS="${DIST_VERS[2]}" # get the third element (version)

is not executed because the condition before if [[ -r /etc/os-release ]]; then is true.
This results in DISTRO='rhel' which is not handled below.
Therefore I push this old issue.

Hello, just wanted to ask if there has since been an update on Torch support for Redhat, namely Redhat 8.0?
At the very least, can a list of prerequisites that are Redhat-specific be provided?  It seems that some of the packages in the list given above (git-core libqt4-core libqt4-gui libqt4-dev libjpeg-dev libpng-dev ncurses-dev imagemagick libzmq3-dev gfortran unzip gnuplot gnuplot-x11 ipython) cannot be installed through yum.


Enhancing the Scrollbar

In the website  the scrollbar color is nearly same as the website color due to which it is not properly visible, secondly there is no hover effect on scrollbar .I will change the design of scrollbar so that it matches with the website color .Can you assign this to me under hacktoberfest?

assigned to you.


Make features and benefits editable

The rules around editing features and benefits are:

Maximum of 10 items per list
Each item can't be more than 10 words in length
If there is a gap between submitted items, it should be filtered out

Javascript parts aren't working, closing temporarily…

Edit: going to raise a separate pull request for adding Javascript enhancement. Review away.

Looks great, request.form is a nitpick, happy to merge as is :+1:


Linking error when trying to build project with elastix 5.0.1

Hello, I upgraded to elastix 5.0.1 and ITK 5.1.1 (with ITK_LEGACY_REMOVE ON) from elastix 5.0.0. The build for both libraries was successful but when I tried to build my own project I got an error stating that it cannot link to "elastix.lib". However, I noticed there is no "elastix.lib" library but rather "elastix-5.0.lib".
The solution for me was to change the line:
https://github.com/SuperElastix/elastix/blob/90122eff6b37a17adc9f5bb3d7bc08608e9c14a6/Core/CMakeLists.txt#L198
to
set( ELASTIX_LIBRARIES elastix_lib transformix_lib PARENT_SCOPE )

Setup:

Windows 10
VS 2017
CMake 3.17.2
Release mode

@ntatsisk Thanks for reporting this issue, Konstantinos! Your solution looks good to me  😃  Do you want to make it a pull request? Or would you prefer us to fix the issue?
For the record, the convention of adding the elastix major and minor version to library file names was already here in version 4.9.0: https://github.com/SuperElastix/elastix/blob/4.9.0/CMake/elastixExportTarget.cmake#L16 I made some adjustments for version 5.0.1, in order to support building exe and lib of elastix and transformix together: https://github.com/SuperElastix/elastix/blob/5.0.1/CMake/elastixExportTarget.cmake#L18 But I think those adjustments did not fundamentally change the library naming conversion of elastix.

Thanks for the info, feel free to fix the issue without a pull request from my side!


new fields in diff-array cause undefined access error

I wrote a test that show cases the problem and a fix that seems to work

OK, I've merged the other change, so can you rebase again?
thanks!

sorry i overlooked the part with the rebase, I just merged in your changes :(

@mxab awesome!


Events page and event details modal

Fixes #6
Prior PR was a fork: https://github.com/stt-datacore/website/pull/360
Addressed feedback left on prior PR

fixed featured crew so it's actually correct
still figuring out how to add filtering to the page
as discussed in Discord, there are a few issues with event IDs making it a little challenging to make these static pages (which they really ought to be)

Everything looks good. I made a small change in anticipation of a forthcoming fix to the events util, which will properly identify all bonus crew for skirmishes.
I also added an announcement so that visitors will know about the new page. Feel free to change the wording if you'd prefer something else.
I'd also note that #12 continues to be an issue, though I'm not sure where we can verify the old leaderboards. The fix for this is outside the scope of this PR, but I just wanted to make a reminder about it here.

Everything looks good. I made a small change in anticipation of a forthcoming fix to the events util, which will properly identify all bonus crew for skirmishes.

I noticed the same thing about Skirmish events, and saw the note in the util method about using the traits to generate the list. I did something similar to what you added, and filtered the crew list to get the ones with those traits. The one thing I was concerned about was that crew that is added to the game after the event would be in the list when you view it (since it's generated dynamically), even though it would not have been in the list at the time of the event. Is that a concern?

I also added an announcement so that visitors will know about the new page. Feel free to change the wording if you'd prefer something else.

Looked good to me. Thanks!

The one thing I was concerned about was that crew that is added to the game after the event would be in the list when you view it (since it's generated dynamically), even though it would not have been in the list at the time of the event. Is that a concern?

It's something to keep in mind in case we add filtering by bonus crew, but for now I don't think many people will need a completely accurate list of bonus crew for past skirmishes. And if anyone does need it, the wiki should have it.


based:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

I have read and followed the submission guidelines and, in particular, I

[x] selected a name in conformance with the guidelines
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] ensured that my submission does not infringe upon the rights of a third party
[x] tested my package locally on my system and it worked
[x] named this PR as name:version of the submitted package
[x] agree that my package will not be removed without good reason

Description: Encoder and decoder for base64, base32, and base16 (hex).

The name is based!


May want to indicate that docker compose needs to be installed

For the uninitiated, may want to ensure they deploy docker compose per the below instructions:
https://docs.docker.com/compose/install/
Prior to deploy.
Otherwise, very nice work. Thank you.

Should be clear enough now : )


Lightbulb for @model ClassName cannot fix full namespace prefix only add @using

This issue has been moved from a ticket on Developer Community.

While refactoring I noticed that the Lightbulb option om a razor view with @model ClassName offers both options, ie. adding a @using to the namespace, or prefixen the ClassName with the namespace.
But in my Version 16.11.0 Preview 2.0 I could no choose the second option. It would simply not apply. This second option also did not show any preview of the change that would be applied.

Original Comments
Johan Bennink on 7/21/2021, 06:13 AM:
Perhaps related. But I hadd to do above because a refactoring of the ClassName to a new namespace with lightbulb “Move contents to namespace…” did not change the namespace prefix  I had in place for the abvoce mentioned model.
Also I noticed that some of my Views seemed to have the namespace prefix replaced by a series of spaces. At least, the code did compile befire and afterwards it looked like:
@model ClassNameViewModel
where is was
@model Application.EntityName.Queries.ClassNameViewModel
before my “Move contents to namespace”
Feedback Bot on 7/22/2021, 01:56 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Feedback Bot on 7/26/2021, 03:34 PM:
This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.
Johan Bennink on 8/6/2021, 04:18 AM:
I updates to VS2019 Version 16.11.0 Preview 3.0 and now if I just have @model ClassName where ClassName is available in another project that is included there is no lightbulb anymore. It just states:
CS0246: The type or namespace ‘ClassName’ could not be found (are you missing a using directive or an asembly reference)
But to test the previous behaviour is simply removed the @using line I manually had to insert before.  The ClassName is definitely available because when I type in a .cs it finds ClassName and adds the using automatically.
I would have expected to have a similar behaviour but at least the lightbulb option.
Also tried VS2022 Version 17.0.0 Preview 2.1 there the razor editor does give me the lightbulb, but also the second option does not work and the first option does! I attached a little screenshot of the lightbulb with the two options shown, and the second option does not work!

Original Solutions
(no solutions)

@NTaylorMullen assigning to you to verify this is fixed

So we add usings now but we don't allow fully qualifying. Investigating


Top and Left positioning not working within *ngFor loop

Hello all,
within the component PopoverContent, consider replacing the offset calculation in the method position by
    protected position(nativeEl: HTMLElement): ... {
...
...
        return {
            width: boundingClientRect.width || nativeEl.offsetWidth,
            height: boundingClientRect.height || nativeEl.offsetHeight,
            top: elBCR.top,// - offsetParentBCR.top,
            left: elBCR.left// - offsetParentBCR.left
        };
    }

That would make popup work within ngFor.
Regards,
Hans

Thanks for reporting this, I will take a look later

Took a look at it. but could not find a place to implement this.


feat: Use salus to run additional security scanners on the code

Submitted a tentative fix to salus for the errors we're seeing: https://github.com/coinbase/salus/pull/829
For now, until this (or another) fix is available, I'll just keep installing tools until this thing works.


Sveltekit testing, android fetch not working.

**Is your feature request related to a problem?
Unable to fetch data with android.
Data is fetched in ios if the codes live in a .svelte file.
Note that fetching data from a graphql api works fine in desktop mode for codes in .server file (the main project is a ssr pwa configured to work as a spa with adapter static / ssr disabled and prerender on)
Describe the solution you'd like
A clear and concise description of what you want to happen.
Behave like the desktop app to have the same base for multiplatform dev.
.server.ts files contain actions that works on desktop
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Would you want to assign yourself to implement this feature?

[ ] Yes
[ ] No

Additional context
Add any other context or screenshots about the feature request here.

Please provide a minimal reproducible repo, also try building for release to see if it is just an issue with development mode.

Thanks for the reply, awesome project.
I will test with the release as you suggested and share the result.
Note that ios (dev) fetch from the graphql api only when codes live on a .svelte file unlike the desktop who work like a charm with .server.ts (adapter-static)


fix(BetterCodeHub): Move bettercodehub.yml to the root

@nicojs Turns out I placed the yml file in the tasks folder by accident..


"ONBUILD ADD" cache invalidation

I think there could possibly be a bug in the behaviour of ONBUILD ADD in that it fails to invalidate the cache when building downstream images. It seems as if when building the downstream image, the cache for ADD won't be invalidated as it would without ONBUILD. I have confirmed it works fine without ONBUILD. Details follow.
Output of docker version:
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.5.1
 Git commit:   76d6bc9
 Built:        Tue Nov  3 21:17:48 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   76d6bc9
 Built:        Tue Nov  3 19:20:09 UTC 2015
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 10
Images: 116
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 136
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov  3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 996.2 MiB
Name: dev
ID: EKO2:K55Q:QJNW:2DI5:2JMS:SRIV:MU7V:GEVV:CO4A:VEOV:RAP7:2YYR
Debug mode (server): true
 File Descriptors: 12
 Goroutines: 20
 System Time: 2016-02-24T22:07:40.321894847Z
 EventsListeners: 0
 Init SHA1:
 Init Path: /usr/local/bin/docker
 Docker Root Dir: /mnt/sda1/var/lib/docker
Username: felixschl
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
1

Provide additional environment details (AWS, VirtualBox, physical, etc.):
Virtualbox
List the steps to reproduce the issue:

Create an image with ONBUILD ADD . .
Use the image created in (1) using FROM.
Build the image
Change a file
Re-build the image

Describe the results you received:
Step 1 : ADD . .
 ---> Using cache

Describe the results you expected:
Step 1 : ADD . .
 ---> Removed intermediate image

(or similar)
Provide additional info you think is important:
I am on OSX, using docker-machine with the virtualbox provider.

/cc @duglin perhaps you can have a look (haven't tried to reproduce yet)

@felixSchl when you say "change a file" - did you actually modify a file or just "touch" it?
A change in timestamps won't trigger a re-running of the ADD because mtime isn't taken into account.
I tried it myself and it does seem to work.

I have definitely modified the file in both cases.

can you prove me with your Dockerfile and the exact steps you did on the cmd line so I can try to reproduce it?

Absolutely, should be able to do so later today

Huh, now I am actually also unable to reproduce this in the simplest case. It must be something else causing this in other image. Seems like this can be closed until proven otherwise.

@felixSchl ok, feel free to reopen it if you're able to give us a testcase that shows it.


⚠ Bofrost.at has degraded performance

In e2af4da, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1432 ms

Resolved: Bofrost.at performance has improved in 0021fa8.


script_history add submit_time and refactor execTimeout

script_history table add field submit_time
refactor execTimeout

Hi, @progr1mmer, could you help to review this?


bdd download error

Thanks to the author for such a great job!
But when I use conversion/download_bdd.py,
" https://bdd-data-storage-release.s3.us-west-2.amazonaws.com/bdd100k/2021/bdd100k_seg_track_20_labels_trainval.zip" and "https://bdd-data-storage-release.s3.us-west-2.amazonaws.com/bdd100k/2021/bdd100k_ins_seg_labels_trainval.zip" can't download, how to solve this problem.

@zwhus Hi, it seems the original links of these two files from BDD100K official website have been broken. We have just upload these two files to our onedrive. You can manually download bdd100k_ins_seg_labels_trainval.zip and
bdd100k_seg_track_20_labels_trainval.zip from onedrive.

Thanks, I will try it again!

@zwhus Hi, have the answer solve your issue? If the issue has been solved, please consider closing it. Thanks  :)

Now, i have new question, when i run prepare_bdd.sh, Error while finding module specification for 'bdd100k.label.to_coco' (ModuleNotFoundError: No module named 'bdd100k'), how tosolve it ?

@zwhus Hi, please refer to MOTS to install bdd100k package.
git clone https://github.com/bdd100k/bdd100k.git
cd bdd100k
python3 setup.py develop --user
pip3 uninstall -y scalabel
pip3 install --user git+https://github.com/scalabel/scalabel.git
pip3 install -U numpy
cd ..

@zwhus Hi, I don't quite understand the question. According to VIS Tutotial, Youtube-VIS dataset can be downloaded from colab. Then you can unzip zipped files and put them under datasets folder.

ok, thanks for your reply

HI， when i use VIS Tutotial to downlaod youtube_vis_2019, the annaotations id

@zwhus Hi, please just rename train.json and valid.json to instances_train_sub.json and instances_val_sub.json respectively.

ok，thanks,


Unified API for effects with extension methods

The current design of kyo keeps effect types segregated, so that a separate import is required for each one, and each has a separate API.
import kyo.options.*
import kyo.ios.*
import kyo.fibers.*

val optEffect = Options.get(Some("hello world"))
val ioEffect = IOs(println("hell world"))
val forkedEffect = Fibers.init(ioEffect)

val handledOpt = Options.run(optEffect)
val handledIo = IOs.run(ioEffect)
val handledFiber = IOs.run(Fibers.run(forkedEffect))

It would be much easier for the developer to use a single export for core effects, and have extension methods on T < Fs to more easily handle effects. I'm obviously thinking of the ZIO API here:
import kyo.*

val optEffect = KYO.fromOption(Some("hello world"))
val ioEffect = KYO.attempt(println("hello world")
val forkedEffect = ioEffect.fork

val handledOpt = optEffect.runOptions
val handledIo = ioEffect.runIO
val handledFiber = forkedEffect.join

I think moving effects to extension methods of > would hurt usability given that users would have to browse over several methods to encounter the ones related to the effects they need to use. Calling effect methods explicitly doesn't introduce much syntax overhead and makes code more friendly to newcomers IMO.
I agree that'd be nice to avoid having to import each of the effects, though. I used to have a kyo.all object that would export all core effects but I removed it once I introduced Scala 2 support. Kyo also has multiple modules now, which complicates things a bit. Maybe we could have a kyo-all artifact that depends on all other modules and exports all effects?

From what I can see, everything that I would want to be in the unified export is in the core module (Aborts, Envs, Options, IOs, Fibers), so I'm doubtful another module would be necessary, at least for my own needs.
One more plug for using extensions methods:

using static functions on objects like Options, Aborts, etc, requires "back-tracking." You come up with an expression, and then you have to return to the beginning of the expression to then handle those effects, rather than calling a method at the end of the expression at the end, which is where you were when you thought of it:

val effect = Consoles
    .readLine
    .map(line => Tries.catching(v.toInt)
    .map(int => Options.get(Try(23 / int).toOption))
    // At this point I realize I want to handle `Tries` and `Options` to just get an `Option[Double]`
    // but now I have to go back to the top and wrap this all in an `Options.run { }`
    // I'd like just call something like:
    .triesToOptions
    .runOptions

You end up with super nested function calls that make it harder to follow what's happening

// Simple dependency
final case class Dep(int: Int)

val effect = for {
    int1 <- Envs[Dep].get.map(_.int)
    int2 <- Options.get(Some(23))
    int3 <- Aborts[String].get(Right(50))
    _ <- Consoles.println((int1 + int2 + int3).toString)
} yield ()

// To handle I have a super-nested expression:
Envs[Dep].run(Dep(900)(Options.run(Aborts[String].run(effect)))

// It would be much cleaner to be able run them in order
effect
    .runAborts[String]
    .runOptions
    .runEnvs[Dep](Dep(900))

At any rate, as I've started playing with this, I very quickly came up with a bunch of extension methods to use to make it less cumbersome managing the different effect types.

How do you feel about this issue after some more contact with Kyo? I agree that extension methods would make Kyo's API more fluent for advanced users but I worry if it could make it more difficult to onboard newcomers since it tends to produce more terse code. The way Kyo's effects are structured should also facilitate learning since it's possible to teach each effect in isolation and people might have an easier time to form a mental model of which effects they should use for each task.

I've been think about this. I still strongly feel that I would prefer a fluent zio-like API. Whenever I've done experiments with kyo, I've ended up just rolling my own API for convenience. I certainly wouldn't try to build a proper application without one. That said, I do understand your concern about onboarding -- you may be right that it's easier to get your head around.
I've been toying with the idea of making a separate "zikyo" library that just puts a ZIO facade on kyo.  (This is basically what I've already been using locally.) If you are interested, I could make it a separate, optional module in within kyo. However, the added complexity of having multiple ways of doing this could create an obstacle to adoption.

Yeah, I think this tension between designing a library for both newcomers and advanced users is one of the main challenges of the project. Looking at your examples, maybe we could have a single generic method to enable the fluent use? It might a good compromise.
// Simple dependency
final case class Dep(int: Int)

val effect = for {
    int1 <- Envs[Dep].get.map(_.int)
    int2 <- Options.get(Some(23))
    int3 <- Aborts[String].get(Right(50))
    _ <- Consoles.println((int1 + int2 + int3).toString)
} yield ()

// new pipe method?
effect
    .pipe(Aborts[String].run)
    .pipe(Options.run)
    .pipe(Envs.run(Dep(900)))

Regarding a ZIO-like facade, I think it might make sense to facilitate learning and adoption. I'd be open to having it as a separate repo under getkyo.

I think a pipe method would be even more confusing to a new-comer than the combinators I had in mind, although at least would not clutter the namespace. But I'm pretty sure pipe can be imported from the standard library anyways.
I'll push my own code in a repo in my namespace and let you consider whether you want it under getkyo.

Cool! Makes sense, if you prefer to keep it separate it’s fine with me as well. I’m looking forward to seeing it! Hopefully we can find some ways to bridge the gap between advanced users and newcomers :)

Something I wanted to encourage you to do is to think of the ideal API rather than the one that fits with Kyo's current core. Making major changes to the library is still feasible at the current phase of the project, and in the end, I think this is more about syntax than how effects are organized, which is my main concern. The recent discussion with Kit on https://github.com/getkyo/kyo/issues/201 is a good example of how to experiment with Kyo's core. I'd be glad to help!

In general, I do find the ergonomics of methods defined upon an instance to be preferable to "free functions," a.k.a methods defined on a companion object. For me, the companion object is the ideal place for constructors, or perhaps n > 2 arity methods—ZIO.collectAll for instance. (This one of the reasons why I don't think I could go back to ML style languages.)
There's definitely a tradeoff; especially with a library like Kyo, where we don't have a single, unified Effect type to serve as the logical home for these methods. Instead, we would need to define extension methods. Though, we could have these all defined in one file, in order to regain some of that discoverability through source-spelunking. Additionally, I believe autocomplete is probably the most powerful factor in the discoverability and ergonomics of a library.
When you have free functions spread across multiple companion objects, the user might have a difficult time figuring out what options are even available to them. Conversely, with extension methods, the user could simply type out myKyo. and have their IDE present all relevant* possibilities.
(*With extension methods, we could ensure that only the relevant methods appear in autocomplete. For instance, if your Kyo does not depend on the Aborts effect, then autocomplete wouldn't be polluted with Aborts-specific, error handling methods. Libraries tend to not do this, but I think it could be worth experimenting with.)
It could be quite nice to call catchAll/catchSome on a Kyo directly to handle an Aborts. In fact, I explored that a bit, and found a way to successfully infer the new set of effects, subtracting the Aborts[E].

@kitlangton  good idea. Here is a gist with the API I've been using locally. Scroll to the bottom to see a simple demo: https://gist.github.com/johnhungerford/8430b93fb2eebf4de40ab0808eee010e
Keep in mind I just sort of threw this together quickly and haven't tested most of the options. I also can't get it to compile with scala-cli, but it runs in my local sbt project.
@fwbrasil I'll keep your recommendation in line

Sorry for the delay to reply here. I've been thinking about this and it's still not clear to me what a good direction could be. My main concern is keeping Kyo's design philosophy of having simple and isolated effects with a small set of canonical APIs.
I'd say that's an important departure from ZIO's approach, which focuses more on high-leverage combinators. Combinators are great for advanced users but significantly increase the API surface, making onboarding new users more challenging. Kyo's current API surface seems significantly smaller than ZIO's while still covering a large portion of its functionality.
Another important aspect is the direct syntax experience. Since the goal is to compose computations without a monadic API, providing statically-accessible APIs is a necessity, and operators we add to < might not even be available in the direct syntax.
That said, I think Kyo ideally should position itself as a solution to bridge the gap between newcomers and advanced FP users. Maybe we could have separate interoperable APIs with different levels of complexity? We could still keep the same organization of effects but presented in different ways:

Direct syntax: This is what I'd expect the majority of Kyo's users to use.
Simplified monadic: Using the current monadic APIs + isolated effects.
Rich combinators: A ZIO-like user experience.

I'd be okay with the "rich combinators" API being in a separate project but we could also keep it in Kyo proper to facilitate maintenance. In case we see newcomers don't need to fall back to the "simplified monadic" APIs too often, we might even be able to eventually remove it (but somehow keeping the direct syntax experience and Kyo's design philosophy). I think if we're able to provide a seamless experience that allows advanced users to provide solutions newcomers can easily leverage in the direct syntax, it can become avenue for the evolution of functional programming in a way that has the chance to become a mainstream paradigm.
Regarding autocomplete, I'm not sure it's a very relevant concern. Going forward, the kind of autocomplete that matters the most is the one produced by AI copilots. Kyo's current organization of effects is great for example to put in a LLM system prompt since it's relatively compact. The clear separation of concerns in effects should also hep direct the LLM's reasoning and attention better.

Regarding auto-completion vs. LLM: LLMs already today can limit their output to grammars specified in BNF. I think it is a logical next step to limit or refine the output according to completions provided by e.g. LSP. Otherwise the model would have to be fine-tuned every time the API changes or it would need to do constant RAG documentation lookups.
I think auto-completion would help both humans and in the near future also LLMs.

@nightscape that's a good point! Constraining the output to a grammar can be quite useful but I believe there aren't any major providers with this feature yet. I think both Kyo's current APIs and a combinator-focused approach could be expressed as a grammar, though.

@johnhungerford I think we can close this issue now that the work is continuing in https://github.com/getkyo/zikyo?

Sounds good!


Canonicalize uri for dummy diags

getTypecheckedModuleGhc' returns diags with canonicalized URIs so dummy diags with un-canonicalized URI is always inserted to diags map.
Which leads to LSP client overwriting actual diags with dummy ones because both URI are treated the same.
Fixes #560

Looks good.


Fix image names in "Using Old PHP Versions"

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

Did they change how the images are tagged? I tested this originally, and those images were correct then...

I'm not really sure, but the images are named differently here. Perhaps they've streamlined them?

Hmm, https://hub.docker.com/r/devilbox/php-fpm-5.2 is still there and appears to be maintained... ???

Yes and if I test it today it works without any issues.
Wonder what went wrong yesterday. /closed


dock-cli docker:install fails with gnu-sed installed

This is caused by the differing parameter order between sed implementations. I normally install gnu-sed so that it matches other implementations.
RUN sed -i '' 's/docker/zzz-dinghy/' /usr/local/Cellar/dinghy/3.0.1/cli/dinghy/dnsmasq.rb
ERR sed: can't read s/docker/zzz-dinghy/: No such file or directory

  [Symfony\Component\Process\Exception\ProcessFailedException]
  The command "sed -i '' 's/docker/zzz-dinghy/' /usr/local/Cellar/dinghy/3.0.1/cli/dinghy/dnsmasq.rb" failed.
  Exit Code: 2(Misuse of shell builtins)
  Output:
  ================
  Error Output:
  ================
  sed: can't read s/docker/zzz-dinghy/: No such file or directory

Uninstalling gnu-sed resolves the issue however a system check to evaluate the version of sed installed and construct the command accordingly may avoid recurring issues with new users.

So we have 2 options:

Based on the experiment I made, we can check if the result of sed --version contains "GNU sed". Important, the sed --version command with OSX is failing so we need to silent the error and conclude that the version used in the OSX one.
As this sed command is only used to fix the code source of dinghy to change the name of the DNS masq they are using, we may use another solution than this one or better, contribute a --no-dns option to dinghy.


an adding fot CanvasKit

hello,
can you add something that allows to detect the position of a text

you can do it?


Embed build script in the dockerfile

So that we leverage docker build cache a bit more.

@nanosonde can you please check this?

@felipecrs Have you tested this already?
The DESTDIR env var is now set globally also for the normal “make all”.
The trick is to run “make all” without DESTDIR and only run „make install“ and „make samples“ with DESTDIR set.
I have to check the Makefile again.

Ops, I didn't mean to change what's working. Fixed. Can you check again @nanosonde?

I needed some sleep. ;-)
As you merged it already >I have tested everything again with the whole develop branch.
BTW: How you test your changes locally?

BTW: How you test your changes locally?

Currently I'm building in my home's Home Assistant. I checkout the code there and keep rebuilding.
But I use the SSH addon to rebuild (cd /addons/asterisk-hass-addons && docker build asterisk) so at least I know what's happening. Then, when I click to rebuild from the addon page, it rebuilds quickly thanks to the build cache.
Don't forget to comment out the image line in config.yaml, and also, if you make changes to config.yaml, HA may struggle to pick them, so make sure to always bump the version to ensure HA will pick up changes to config.yaml.


Inconsistent package list in cluster deployment

Describe the bug

The bug demostrates that verdaccio with s3 backend is stateful, with package-list cached in memory, and caused inconsistent and racing issues in a clustrer env. The solution is attached, and discussion are welcome.
I've setup a minimal cluster verdaccio deployment, using two verdaccio instances, s3 store and nginx as reverse proxy. The s3 plugin is slightly modified, but nothing really hit the core logic.
Before the test, I already have one package (com.littlebigfun.addressable-importer) in verdaccio.
# space is an alias for aws-cli

$ space ls s3://openupm/verdaccio/
                           PRE com.littlebigfun.addressable-importer/
2019-11-27 00:26:39        126 verdaccio-s3-db.json

$ space cp s3://openupm/verdaccio/verdaccio-s3-db.json -
{"list":["com.littlebigfun.addressable-importer"],"secret":"..."}

Let's publish another package (com.bastianblokland.enumgenerator) for testing.
$ npm --registry=my-registry publish
...
+<EMAIL_ADDRESS>
Logs show that the return code is 201, the publish is successful. The NotFoundError is harmless for new package. Notice the publish job is executed by verdaccio instance 0 (the log prefix tells).
0|verdaccio  |  info <-- <IP_ADDRESS> requested 'PUT /com.bastianblokland.enumgenerator'
0|verdaccio  |  error-=- s3: [S3PackageManager writeTarball headObject] { NotFoundError: no such package available
0|verdaccio  |  http <-- 201, user: openupm(<IP_ADDRESS> via <IP_ADDRESS>), req: 'PUT /com.bastianblokland.enumgenerator', bytes: 1683542/53

The added package is verified in S3.
$ space cp s3://openupm/verdaccio/verdaccio-s3-db.json -
{"list":["com.littlebigfun.addressable-importer","com.bastianblokland.enumgenerator"],"secret":"..."}

$ space ls s3://openupm/verdaccio/
                           PRE com.bastianblokland.enumgenerator/
                           PRE com.littlebigfun.addressable-importer/
2019-11-27 01:08:59        162 verdaccio-s3-db.json

Now the buggy part, let's curl the package list, twice. Notice that only the second call return the new added package.
# first pass - wrong
$ curl https://my-registry/-/verdaccio/packages
[
  {
    "name": "com.littlebigfun.addressable-importer",
    ...
  }
]
# second pass - correct
$ curl https://my-registry/-/verdaccio/packages
[
  {
    "name": "com.bastianblokland.enumgenerator",
    ...
  },
  {
    "name": "com.littlebigfun.addressable-importer",
    ...
  }
]

Logs show that the second correct curl result is from verdaccio instance 0, the one just executed the publish command. The incorrect curl result is from verdaccio instance 1. We can run it for multiple times, the result is the same. The verdaccio instance 1 never return the new added package.
1|verdaccio  |  info <-- <IP_ADDRESS> requested 'GET /-/verdaccio/packages'
1|verdaccio  |  http <-- 200, user: null(<IP_ADDRESS> via <IP_ADDRESS>), req: 'GET /-/verdaccio/packages', bytes: 0/4070
0|verdaccio  |  info <-- <IP_ADDRESS> requested 'GET /-/verdaccio/packages'
0|verdaccio  |  http <-- 200, user: null(<IP_ADDRESS> via <IP_ADDRESS>), req: 'GET /-/verdaccio/packages', bytes: 0/7787

This behavior seems implying that verdaccio has some sort of local cache in memory of package list (verdaccio-s3-db.json). So until I restart verdaccio instance 1, there's no way to notify verdaccio instance to refresh the cache. I haven't check the source code yet, so it is just my guessing. But if this is true, it means verdaccio is not scalable, can only run with one instance. Well this isn't my expectation when discussing with @juanpicado on https://github.com/verdaccio/verdaccio/issues/1459#issuecomment-529123708, where I ask for the the behaviour of how to handle a shared package list in cluster env.
I need some time to read getLocalDatabase method of https://github.com/verdaccio/verdaccio/blob/dbf20175dc68dd81e52363cc7e8013e24947d0fd/src/lib/storage.ts, to figure it out. But please guide me if you think there's something obvious I missed.
To Reproduce
You will need a simliar deployment - two instances of verdaccio managed by pm2, s3 backend. Nginx isn't necessary.
Expected behavior
All verdaccio instances should return the latest package list right after new package added (or removed).
Configuration File (cat ~/.config/verdaccio/config.yaml)
storage: ./storage
plugins: ./plugins
max_body_size: 200mb
listen: <IP_ADDRESS>:4873

server:
  keepAliveTimeout: 60

middlewares:
  audit:
    enabled: true

web:
  enable: true

auth:
  htpasswd:
    file: ./htpasswd
    max_users: -1

packages:
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    unpublish: $authenticate

  '**':
    access: $all
    publish: $authenticated
    unpublish: $authenticated

store:
  aws-s3-storage:
    bucket: openupm
    region: sfo2
    endpoint: ...
    accessKeyId: ...
    secretAccessKey: ...
    s3ForcePathStyle: true
    keyPrefix: 'verdaccio/'
    tarballACL: public-read
    tarballEdgeUrl: ...

convert_to_local_tarball_url: false

Environment information

verdaccio: 4.3.4 (modified: https://github.com/verdaccio/verdaccio/pull/1580)
s3-plugin: 8.4.2 (modified: https://github.com/verdaccio/monorepo/pull/249)
My modifications are made for https://github.com/verdaccio/monorepo/issues/250, which is not related to this bug.
Debugging output

$ NODE_DEBUG=request verdaccio display request calls (verdaccio <--> uplinks)
$ DEBUG=express:* verdaccio enable extreme verdaccio debug mode (verdaccio api)
$ npm -ddd prints:
$ npm config get registry prints:

Additional context

Continue the dicussion.
local-storage
The package list (data) is cached in memory via _fetchLocalPackages() since verdaccio started. When add/remove a package or set secret, the package list is synced back to disk via _sync. The local-storage backend is designed for simple case, which works just fine in 1 verdaccio instance. But it's not useful for cluster deployment, due to lack a way to sync the mutable package list to other running instances.
aws-s3-storage
The package list is (lazy-)loaded and cached in memory via _getData(). When add/remove a package or set secret, the package list is synced back to disk via _sync. The _sync writes the package list in the memory of the current verdaccio instance, back to disk. This pretty much same as local-storage backend, it handles files in S3 instead of local storage, not work with cluster.
I'm digging a related but old cluster thread. Where @wzrdtales original asked for how to solve the .sinopia-db file in a cluster env. Later on @juanpicado steps in and suggest to create a plugin (adapter) structure first (as we have today, thanks for it). But the original question is not solved. @wzrdtales said will have a look, but the conversation stops there.
Solution A: remove the cache of package list. It seems a no-brain choice. However it has racing problem. Say two users publish two new packages at the same time, two verdaccio instances both read the package list from S3, add the package name, write back to S3. The second write overwrite the first write, the first new added package is missing.
Solution B: get rid of package list file. Use the directory name to present an exist package.

add/remove no longer maintain a list file, just upload package.json and tarball is enough.
get package list performs a ls action.
setSecret/getSecret, I wonder why not just force it presented in the configuration file. Auto generation secret and stores in storage, doesn't bring much benefits.
Will this approach work for all kind of edge cases? need comments from verdaccio dev.
Also need research for S3 list performance, it seems okay from what I was reading here.

Solution C: move the package list file to redis or other database. Take redis as an example, it faster enough so you don't need to worry about performance. And we can save the package list as a hash, i.e. pkg:name: {data if have}. Then add/remove/search can be refactor to be more efficient version. There's no racing issue, since verdaccio instances are working on different hashes (i.e. pkg:pkgname-a: {} and pkg:pkgname-b: {}). The problems are

Redis is not a strong persistent database, you need configure it carefully to get what you want.
The storage is mixed of two things, S3 and Redis (or others). Perhaps the naming looks a bit weird aws-s3-redis-storage

Thought?

Updated solution B in https://github.com/verdaccio/monorepo/pull/275, added scope package support. I implemented solution B first, since it's the most clean one without changing the structure of verdaccio storage plugin.
Solution C however, depends on how we mix redis into the system.

Simplest way is to implement a new aws-s3-redis-storage backend to fuse redis and s3 for cluster.
Or add an option to store package-list and secret into redis. If redis is enabled, the storage backend is only used to store tarball and package-info json.

For curious, I have a look at the google-cloud storage backend, created by @griffithtp. Surprisingly the implementation shall work well on cluster (but I'm not using google cloud :-(). This can be a good reference to help understand the issue.
In the google-cloud storage,

It stores package.json and tarball into google-cloud/storage, a s3-like simple object system.
It stores secret and package present info (the package list) into google-cloud/datastore, a no-SQL database, think about redis/couchdb/mongodb, which handle the concurrent IO for you. The underlying data structure is a lot like a hash in redis

VerdaccioDataStore:
  package-a: {name: 'package-a'}
  package-b: {name: 'package-b'}

To get package list, it querys VerdaccioDataStore key and get all key names.
Hence, it doesn't need the concept to sync the whole package list back to storage.

Based on the information, I'm more confident to implement soltuion C as option C-1, a new storage backend called aws-s3-redis-storage. Because s3 backend and google-cloud backend are probably the only two backends care about the concurrent issue, and in fact the google-cloud backend already handle it well. The implementation will be similar to the google cloud,

It stores package.json and tarball into s3 as before.
It stores secret and package present info (the package list) into redis.


Adding New Feature To Fetch Question Based on Topic

Description:

Adding ;topics cmd which will show a user options of topics ( MENU ) like string , array , stack ,etc.
After User Clicks on this topic , Random Question of that topic will be fetched and given to him.

@jinx-vi-0 Please assign this task to me

Assigned @ParasY1724


add ability to pull in data from shared symphony directly from composer.

I've added a new optional argument -u / --url. This option causes the parser to treat the infile arg as the url of a shared, public symphony on Composer.trade. It will then download the symphony directly and pull in the correct data. I've changed the constructor and the readFile methods on the InFileReader object to support this.

i'll accept the changes and then lets find out.


Incompatibility with JRuby v<IP_ADDRESS> due to problem with http_parser.rb v0.6.0.

See http_parser.rb bug report.

We have plans on switching http parser. If I will have some time this weekned - will try to work on that.

Def interested in this working with jruby 9.2 asap, following.

I have cut 5.0.0 pre release version of gem with switch to updated http parser. This should be fixed now.

Oh nice!  Thanks!
Are there release notes or a URL to a relevant PR or commit about the changed http parser?  I'm curious about the details, if what's used in MRI and Jruby both changed, to the same thing, what it is, etc.;
since previous http parser (at least in jruby?) was a third-party thing that ended up unmaintained, interested in looking at social context of the new parser and it's maintainance story.

This is the commit: https://github.com/httprb/http/commit/f1db84f38601960f94ce7defa3a546967b292f00
Right now we switched to maintained ffi-based http parser: https://github.com/cotag/http-parser
But in future I plan on getting rid of 3rd party dependency and have our own ffi bindings to joyent's http parser (mostly because I don't like http-parser's (gem) API).

Thanks! So nice to see http.rb getting maintenance!


refactor: use execSync for tests

@bcoe can you help me out here? Not sure why execSync returns Buffer rather than string (more like when does it return which).


Request to use a fork of vim-tmux-navigator tpm with resize support

Hello!
Have you considered forking vim-tmux-navigator (the tmux config, not the vim plugin) so that we could push the resize config into that repo? Main motivation is I'd rather have the tmux conf snippet for resizing moved into the tpm plugin, rather than copy pasting it into my own (and everyone else's) tmux.conf.
I could create the tpm plugin for myself, but I think it'd be beneficial for everyone to be able to do just:
set -g @plugin 'aserowy/tmux.nvim'

I can submit a PR if you'r open to it.
Thanks!

Heho, PR are always welcome!


elasticsearch: java.net.MalformedURLException: unknown protocol: jrt

systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2019-03-13 08:55:02 EDT; 19s ago
Docs: http://www.elastic.co
Main PID: 5715 (code=exited, status=1/FAILURE)
Mar 13 08:54:46 host1 systemd[1]: Started Elasticsearch.
Mar 13 08:54:47 host1 elasticsearch[5715]: java.security.policy: error adding Entry:
Mar 13 08:54:47 host1 elasticsearch[5715]: java.net.MalformedURLException: unknown protocol: jrt
Mar 13 08:54:47 host1 elasticsearch[5715]: java.security.policy: error adding Entry:
Mar 13 08:54:47 host1 elasticsearch[5715]: java.net.MalformedURLException: unknown protocol: jrt
Mar 13 08:55:02 host1 systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Mar 13 08:55:02 host1 systemd[1]: Unit elasticsearch.service entered failed state.
Mar 13 08:55:02 host1 systemd[1]: elasticsearch.service failed.

Hi @anelshaer, can you share more details about the commands you ran to get to this point, operating system and version, and Java version? It's definitely a Java problem, and if we can figure out what went wrong, we can get it into the troubleshooting section.

Same issue.
RPM installation, followed instructions exactly.
Java 1.8
CentOS 7.6.1810
Same error shows on first run but ES shows running.
`[root@odfe ~]# service elasticsearch status -l
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2019-03-13 11:51:22 MDT; 8s ago
Docs: http://www.elastic.co
Main PID: 11869 (java)
Tasks: 14
CGroup: /system.slice/elasticsearch.service
└─11869 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX...
Mar 13 11:51:22 odfe.it.usu.edu systemd[1]: Started Elasticsearch.
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt
`

Same issue.
RPM installation, followed instructions exactly as written.
Java 1.8
CentOS 7.6.1810
$systemctl start elasticsearch
$systemctl status elasticsearch -l
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2019-03-13 11:51:22 MDT; 8s ago
Docs: http://www.elastic.co
Main PID: 11869 (java)
Tasks: 14
CGroup: /system.slice/elasticsearch.service
└─11869 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX...
Mar 13 11:51:22 odfe.it.usu.edu systemd[1]: Started Elasticsearch.
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.security.policy: error adding Entry:
Mar 13 11:51:23 odfe.it.usu.edu elasticsearch[11869]: java.net.MalformedURLException: unknown protocol: jrt

Thanks @rlk5546. I'm able to reproduce and am looking into it with engineering. Looks to only be a problem on Java 8.

Hi everyone, our engineers tell me that those errors are nothing to worry about. If Elasticsearch fails to start, it's likely an incorrect symlink. I've added some information here: https://github.com/opendistro/for-elasticsearch-docs/commit/b4df35ffe69eef1a74c2941bd05a43b0297ce79a

Thanks! It is refreshing to see such a quick response.

I'm Still having the same Issue.
ln -s /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>.b12-1.el7_6.x86_64/lib/tools.jar /usr/share/elasticsearch/lib/
systemctl status elasticsearch  -l
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2019-04-03 05:41:20 EDT; 2min 23s ago
Docs: http://www.elastic.co
Main PID: 19812 (java)
Tasks: 78
Memory: 1.2G
CGroup: /system.slice/elasticsearch.service
└─19812 /bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/tmp/elasticsearch.u9DTuoT1 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/lib/elasticsearch -XX:ErrorFile=/var/log/elasticsearch/hs_err_pid%p.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -Xloggc:/var/log/elasticsearch/gc.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=32 -XX:GCLogFileSize=64m -Dclk.tck=100 -Djdk.attach.allowAttachSelf=true -Djava.security.policy=file:///usr/share/elasticsearch/plugins/opendistro_performance_analyzer/pa_config/es_security.policy -Des.path.home=/usr/share/elasticsearch -Des.path.conf=/etc/elasticsearch -Des.distribution.flavor=oss -Des.distribution.type=rpm -cp /usr/share/elasticsearch/lib/* org.elasticsearch.bootstrap.Elasticsearch -p /var/run/elasticsearch/elasticsearch.pid --quiet
Apr 03 05:41:20 Test1 systemd[1]: Started Elasticsearch.
Apr 03 05:41:21 Test1 elasticsearch[19812]: java.security.policy: error adding Entry:
Apr 03 05:41:21 Test1 elasticsearch[19812]: java.net.MalformedURLException: unknown protocol: jrt
Apr 03 05:41:21 Test1 elasticsearch[19812]: java.security.policy: error adding Entry:
Apr 03 05:41:21 Test1 elasticsearch[19812]: java.net.MalformedURLException: unknown protocol: jrt

i'm still having this Issue, and when i do systemctl status logstash
i get the following errors:
[WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://localhost:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [http://localhost:9200/][Manticore::ClientProtocolException] localhost:9200 failed to respond"}


Bugfix/80 disable browser intent for tv

Current coverage is 0.00% (diff: 100%)

Merging #84 into develop will not change coverage

@@           develop   #84   diff @@
====================================
  Files            1     1
  Lines           27    27
  Methods          0     0
  Messages         0     0
  Branches         0     0
====================================
  Hits             0     0
  Misses          27    27
  Partials         0     0

Powered by Codecov. Last update c13391e...6452979


Get rid of the resilience from method Player.setVelocity()

As a matter of fact, when Method Player.setVelocity applied to a client player, a resilience happens, which prevents us to give particular player an instant velocity and move to a expected place. However when it comes to an entity which is not a client player, including simulated player, the method runs well. I hope that it could be working well on client players soon. That's all.

This method runs also on client players, i have done some tests and velocity was applied always on player, there was problem with client side, client side didn´t know about velocity change.
Player.prototype.setVelocity is disabled on players.
U can close this issue.


wp_nav_menu Languages

I'm currently using the wp_nav_menu to render the language options of my network.
But for custom post type with a custom post base for each language, the menu is not rendering correctly.
Let's say if I have site A in English:
http://www.example.com/en/browse/projects/project-2016/introduction
where "browse/projects/" is the custom post base
And site B in Portuguese:
http://www.example.com/pt/navegacao/projectos/projecto-2016/introducao
where "navegacao/projectos/" is the custom post base
When I navigate trough site A (English), the language menu will render the following urls:
English - http://www.example.com/en/browse/projects/project-2016/introduction
Portuguese - http://www.example.com/pt/browse/projects/projecto-2016/introducao
Or if I navigate though site B (Portuguese), the language menu will render the following urls:
English - http://www.example.com/en/navegacao/projectos/project-2016/introduction
Portuguese - http://www.example.com/pt/navegacao/projectos/projecto-2016/introducao
After digging into the MLP code I figured out it's calling the get_permalink function of Wordpress in order to get the urls and as far as I know the get_permalink will look into the rewrite rules structure from the site to return the permalink, however site A (English) will never have the rewrite rules of site B (Portuguese) or vice-versa.
So far if I disable the pretty permalink function the urls work correctly.
I would like to ask the authors if you have any solution for this custom post base issue or is there any way I could set only the language menu to don't use the pretty permalink?
For ex. if I access via post ID it works correctly:  http://www.example.com/en/?p=123
Thanks!
Luis

This is related to #192. I'm closing this as a duplicated (which it is not completely, but it depends on incorrect custom rewrite structures).


TST: NumpyVersion dev -> dev0

Just a test that changing dev to dev0 doesn't bother NumpyVersion too much.  This is for https://github.com/scipy/scipy/pull/4512.

Tests look good, except that they should now be using .dev0+ instead of .dev0-.

And thanks for taking care of this loose end!

they should now be using .dev0+ instead of .dev0-.

Fixed.

Thanks, merged.


Release 1.5.0

Time has come.
I can try cutting a release on Friday morning (CEST).

+1

Release Notes

chore: Remove Camel Sources support from Knative trait #2460 (astefanutti)
chore: Update embedded camel-catalog-1.8.0-SNAPSHOT.yaml #2459 (astefanutti)
chore: Remove unsupported probe-path property from container trait #2458 (astefanutti)
fix: Filter influencing traits to lookup matching kits #2457 (astefanutti)
Align to Quarkus documentation #2455 (oscerd)
fix: Unrecognized configuration from quarkus-logging-json #2454 (astefanutti)
fix: Correct Quarkus default health probe path #2453 (astefanutti)
Remove the unnecessary indefinite articles in the list. in documentat… #2452 (apupier)
Remove the unnecessary indefinite articles in the list. in documentat… #2451 (apupier)
fix cron trait issue #2448 (liurui-1)
Revert "Temporarily disable qute due to Camel Quarkus issue #2701" #2447 (orpiske)
Fix #2441: parse parameters in YAML DSL #2442 (nicolaferraro)
chore(api): Remove obsolete failure field From Integration API #2440 (astefanutti)
doc: readme cleanup #2433 (squakez)
chore(doc): drop Minishift from documentation and install script #2428 #2431 (tadayosi)
chore: Remove Camel Sources support #2430 (astefanutti)
fix(doc): examples link #2429 (squakez)
feat(trait): jvm classpath #2427 (squakez)
Sync main with the latest changes from camel-main #2426 (orpiske)
feat(knative): upgrade Knative to 0.23 #2343 #2424 (tadayosi)
fix(cmd/run): secret/configmap as property file #2423 (squakez)
[e2e-tests] cli test (without kamel debug) #2422 (vsokolov00)
fix(trait): never fallback to client-side apply unless server-side apply is incombatible #2421 (tadayosi)
chore(ci): upgrade Knative versions in CI to latest possible #2420 (tadayosi)
fix(cli): resource path with quotes and spaces #2419 (squakez)
Precise requirements on Minikube instance for development #2416 (apupier)
refactor(trait): use bool pointer util functions in knative trait #2415 (tadayosi)
chore(build): Some more go.sum updates #2413 (astefanutti)
chore(e2e): Check Deployment progressing condition after re-run #2412 (astefanutti)
Doc: new configuration explained #2411 (squakez)
fix(cli): Use Patch with optimistic lock to update Integration #2410 (astefanutti)
chore: Upgrade Kubernetes API to v0.20.2 #2407 (astefanutti)
Update link to video to debug in VS Code #2406 (apupier)
chore(build): Upgrade Go to version 1.15 #2404 (astefanutti)
chore(trait): Polish Logging trait documentation #2403 (astefanutti)
fix(e2e): Remove image pull secret e2e test race conditions #2402 (astefanutti)
chore: Upgrade controller-runtime to v0.8.3 #2401 (astefanutti)
fix(trait): ImagePullSecrets are not configured when the Integration is running #2399 (claudio4j)
chore(build): Cancel s2i Build on context cancellation or timeout #2398 (astefanutti)
fix(RBAC): Add permission to send termination signals to builder pods #2393 (astefanutti)
chore(e2e): allow e2e to use nexus mirror to speed up testing #2387 #2392 (tadayosi)
chore(doc): Tidy observability documentation #2390 (astefanutti)
chore(doc): Add autoscaling with Knative documentation #2386 (astefanutti)
Fixes website build #2385 (oscerd)
S3 dependencies #2383 (johnpoth)
doc(kamelets): debugging simple notice #2381 (squakez)
Removed the deprecated --logging-level option (issue #2000) #2377 (orpiske)
chore(doc): Fix Pod trait documentation formatting #2373 (astefanutti)
chore(e2e): remove duplicate test in knative tests #2372 (tadayosi)
Fix #2361: allow multiline properties by correctly encoding them #2369 (nicolaferraro)
chore(doc): Remove deprecated Camel Sources documentation #2368 (astefanutti)
chore(ci): kourier versions not necessarily bound to knative-serving #2367 (tadayosi)
chore(ci): Do not execute e2e tests on documentation changes #2366 (astefanutti)
chore(doc): Update high-level architecture diagram #2362 (astefanutti)
Make it possible to define the container image without IntegrationKit #2360 (lburgazzoli)
Update README to reflect where Sample.java is #2359 (bentito)
feat(cmd/run): resource option refactoring  #2355 (squakez)
Related to #2165: account for annotations when checking if integratio… #2352 (nicolaferraro)
feat(cli): add sub command kamel kamelet for get and delete #2312 #2351 (tadayosi)
fix(cli): stop printing <nil> at the end of kamel describe output #2350 (tadayosi)
chore(build): Cancellable Maven operations #2348 (astefanutti)
feat(cli): support k8s api shortnames for kit & platform with kamel describe #2346 (tadayosi)
feat(cli): initial support for describing Kamelets with kamel describe #2312 #2345 (tadayosi)
chore(api): Encapsulate Maven properties #2344 (astefanutti)
Starting deadline seconds #2342 (zach-robinson)
Add link to the github repo #2340 (davidlanouette)
feat(cmd/run): --config option flag #2339 (squakez)
Fix #2165: allow configuring traits via annotations #2338 (nicolaferraro)
kamelets: add condition to report when an integration is stuck waiting for them #2337 (lburgazzoli)
doc(dev): add instruction for deploying custom images to remote clusters #2336 (tadayosi)
feat(cli): make kamel delete command aware of KameletBindings #2332 (tadayosi)
feat(cmd/run): property configuration refactoring #2329 (squakez)
Extra repositories #2328 (johnpoth)
Added K3s to the registry section of navbar #2325 (oscerd)
Nav Bar: Titles fixed #2324 (oscerd)
Fix Route Trait Crash #2323 (Kyle-Cooley)
Updated the nav bar with all the installations #2322 (oscerd)
[TEST] Increase timeouts for slow infra #2319 (bouskaJ)
Fix #2315: Add leader-election flag to Operator command #2316 (johnpoth)
Fix #2236: Add Service Binding E2E test #2314 (johnpoth)
Check if the environment can produce structured Maven logs before parsing them #2311 (orpiske)
chore(ci): Use github.ref instead of github.head_ref as concurrency group key #2310 (astefanutti)
feat(cmd): build-property flag #2309 (squakez)
Fix #2237: add flag to disable installation of default kamelets #2308 (nicolaferraro)
chore(ci): Cancel running workflows when PRs are updated #2304 (astefanutti)
chore: Make phase structured logging key a string #2303 (astefanutti)
chore(cli): Update CRDs when force installing cluster resources #2301 (astefanutti)
chore: Update .asf.yaml file with project page link #2300 (astefanutti)
chore: Update README badges #2298 (astefanutti)
chore(e2e): config test #2295 (squakez)
fix(test) - toleration trait test #2294 (tplevko)
Added documentation about installing Camel K on Kind #2293 (orpiske)
fix(integration) Integration not marked as Failed when Camel is unabl… #2292 (claudio4j)
Configure kubernetes to use structured log #2290 (orpiske)
fix(doc): camel website error fixes #2288 (squakez)
chore(e2e): Assert upgraded integration Pod uses new version Kit #2285 (astefanutti)
chore(e2e): Remove obsolete operator upgrade e2e test #2283 (astefanutti)
fix(doc): broken links #2282 (squakez)
fix(e2e): Fix OLM upgrade e2e test #2281 (astefanutti)
Normalize the Spectrum log messages #2279 (orpiske)
Doc: generated API #2274 (squakez)
Use different job id names to avoid confusion when using GH CLI #2272 (orpiske)
Normalizes Maven build logs #2270 (orpiske)
feat(build): Cancellable Build and global timeout #2269 (astefanutti)
Added support for configuring the log format #2267 (orpiske)
Consolidate make targets used in Github actions #2264 (orpiske)
Added support for displaying Maven logs in JSON #2262 (orpiske)
Remove a reference to the old logging configuration page #2261 (orpiske)
Replaced the logging configuration documentation with the logging trait documentation #2259 (orpiske)
Support adjusting the log level for integrations #2258 (orpiske)
fix(olm): Update CSV base template #2257 (astefanutti)
fix(cmd): run file system stat errors #2255 (squakez)
Fix typo #2254 (apupier)
fix(api): Fix error handler types deepcopy generation #2253 (astefanutti)
Added support for the json log format via the logging trait #2252 (orpiske)
fix(ci): Upgrade Kubernetes to version 1.21.1 #2251 (astefanutti)
refactor(example): error handler using a real Kafka topic #2248 (squakez)
fix(source): yaml route steps #2247 (squakez)
Improve readability of error messages in Camel K #2245 (orpiske)
doc(install): operationalize options #2244 (squakez)
fix(ci): Use Docker to build OLM index image #2242 (astefanutti)
fix(build): Default to routine build strategy for local IntegrationPlatform #2240 (astefanutti)
chore: ugprade Service Binding Operator v0.7.1 #2235 (johnpoth)
chore: change references to use "main" #2234 (nicolaferraro)

Release of the kamelet catalog and the runtime are done. Full Camel K release will be completed during the weekend.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

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


Add proxy env vars to deployment template

Towards https://github.com/giantswarm/giantswarm/issues/16859
Checklist

[ ] Update changelog in CHANGELOG.md.

Tested on beaver. Proxy environment variables were applied from the installation appcatalog values correctly and the operator ran on cluster creation without any manual changes.