Inconsistent preview-page-up/down between FzfLua git_status and FzfLua files

Info

Operating System: macOS
Shell: zsh
Terminal: alacritty
nvim --version: NVIM v0.9.0-dev-431+gaa4921273
fzf --version: 0.35.1 (brew)

[x] The issue is reproducible with mini.sh

fzf-lua configuration

require('fzf-lua').setup({
  keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = false,
  },
})

Description
With keys comb. Shift + Up/Down, the preview of git_* commands will scroll one line up/down at a time. While the preview of files seems to scroll half-page at a time. I expect that both should have the same behavior (if possible). I prefer the half-page one, but I think providing new options like preview-line-up/down will be great.

This is because you are using different previews, files uses neovim builtin previewer and git uses fzf’s previewer which behaves slightly differently, that said, fzf previewer should still scroll half pages up/down, I suspect this is something related to your setup (maybe $FZF_DEFAULT_OPTS in the shell?).

The echo $FZF_DEFAULT_OPTS output nothing both inside(terminal buffer) and outside(directly from zsh).

The echo $FZF_DEFAULT_OPTS output nothing both inside(terminal buffer) and outside(directly from zsh).

I can't say with certainlty what the issue is but it has to do with your specific setup, I just tested it again with mini.sh and it work as execpted, if your case is different I would start troubleshooting fzf --preview at the shell level.

@ibhagwan My apologies for answering in hurry. I will close the other thread as soon as possible. I forgot to mention that I indeed loaded these options during my testing:
require('fzf-lua').setup {
  fzf_cli_args = '-i', -- Case-Insensitive for: `Fzf files`, `buffers`.
  fzf_opts = {
    ['--cycle'] = '',
    ['--info'] = 'default', -- UI related: show item-list count, e.g. (42/42), on the next line.
    ['--header-lines'] = false, -- make current buffer selectable by `FzfLua buffers`.
  },

Would this impact the env. variable you just mentioned?

Run this in the shell and see if scrolling works as expected (this is exactly what fzf-lua does):
fzf --preview="cat {}" --preview-window="nohidden:down:50%" --bind="shift-down:preview-page-down,shift-up:preview-page-up"

The options you describe above shouldn't change thre preview behavior but it wouldn't hurt to test with and without, does running fzf-lua with mini.sh work as expected or still has the same issue?

Run this in the shell [...]

This scroll either half-page or full-page (I'm not pretty sure) and this is expected and I don't want to scroll one line at a time.
I will test it with mini.sh again.

@ibhagwan Yes, with mini.sh only (I changed the colorscheme since the default one so hard to read) the Shift+Up/Down will scroll 1-page at a time, and this is expected. As demo:
https://user-images.githubusercontent.com/24765272/205442981-55c54848-55b3-4991-abfa-ed6703d201f3.mov
But the problem is that this testing is in different start condition than the one I have reported. That is how do I add these lines to mini.sh? (I ran the terminal command sh -c "$(curl -s https://raw.githubusercontent.com/ibhagwan/fzf-lua/main/scripts/mini.sh)" to start neovim)
keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = false,
  },

@ibhagwan Yes, with mini.sh only (I changed the colorscheme since the default one so hard to read) the Shift+Up/Down will scroll 1-page at a time, and this is expected. As demo:

Not sure I understand, the demo appears to work as expected, the preview scroll does seem to scroll page up/down and not one line at a time.

But the problem is that this testing is in different start condition than the one I have reported. That is how do I add these lines to mini.sh? (I ran the terminal command sh -c "$(curl -s https://raw.githubusercontent.com/ibhagwan/fzf-lua/main/scripts/mini.sh)" to start neovim)

keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = false,
  },

I'm not sure if the above works, as explained in the README, if you wish the disable all of the default options sent to fzf you need to have an empty table not false:
keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = {},
  },

@ibhagwan Yes, I did test it with both false and {}. (when I was trying to solve this I read an issue saying that it can be set to false. I didn't know that it is outdated.) And now I just tested it again (I didn't use the mini.sh this time since I cannot set these configs) with {} but still get the same result. I will think about a way to delete my current config and use the mini.sh to test again.

Maybe I can help you better if I understand the issue better which I'm not even sure I am...
Whether false or {} works might not be the cause here at all, I don't understand why do you expect  fzf preview scroll to work if you're disabling the fzf binds, without specifying a keybind under keymap.fzf you aren't telling fzf what keys to use to scroll the preview up/down, what happens if you add these?
keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = {
      -- These lines must exist to let fzf know you want to use preview scrolling
      ["shift-down"] = "preview-page-down",
      ["shift-up"]   = "preview-page-up",
    },
  },

@ibhagwan:

[...] I don't understand why do you expect fzf preview scroll to work if you're disabling the fzf binds [...]

Lol, sorry for causing confusion. I was thinking about I was replying to #574. For #574 I expect it to not scroll when I pass either false or {} as the value. But the truth is that it still scrolls in a strange way: one line at a time.
And for this issue: you're right. I should test it with the config you just gave.

From man fzf I see there's an ignore option, try this:
keymap = {
    builtin = {
      ['<S-up>'] = 'preview-page-up',
      ['<S-down>'] = 'preview-page-down',
    },
    fzf = {
      ["shift-down"] = "ignore",
      ["shift-up"]   = "ignore",
    },
  },

@ibhagwan This question can be closed as with the following config it does scroll 1-page at a time:
fzf = {
      -- These lines must exist to let fzf know you want to use preview scrolling
      ["shift-down"] = "preview-page-down",
      ["shift-up"]   = "preview-page-up",
    },

I did ask a bad question cus I use fzf = false when I tested it. I will copy and link your reply above this comment to #577 as this will make things clear.

I did ask a bad question cus I use fzf = false when I tested it. I will copy and link your above reply to https://github.com/ibhagwan/fzf-lua/issues/577 as this will make things clear.

I may be wrong indeed, I can't remember every single issue and it's intricacies :-)


Memory Leak when calling RsNDArray.toByteBuffer()

Description
When calling NDArray.toFloatArray() or NDArray.toByteBuffer(), it appears to use native memory that is never released.
Expected Behavior
Native memory should not be allocated or should be released
Error Message
10's of GB of ram are used by the Java process and then the process gets killed with sigkill -9
How to Reproduce?
It is easily reproduced with the following code in a unit test or public static void main(String[] args) {...} method:
// Create a small float buffer and fill it with some 0's
final FloatBuffer buffer = FloatBuffer.allocate(3 * 128 * 384);
final float[] small = new float[384];

for (int i = 0; i < buffer.capacity() / small.length; i++) {
    buffer.put(small);
    buffer.rewind();
}

// Create an NDArray and constantly call array.toByteBuffer();
try (final NDManager manager = NDManager.newBaseManager();
     final NDArray array = manager.create(buffer, new Shape(3, 128, 384))) {

    for (int i = 0; i < 1_000_000; i++) {
        // Here, we can use array.toByteBuffer(false) or array.toByteBuffer(true) or array.toFloatArray(), it doesn't matter.
        array.toByteBuffer(false);
    }
}

Same result happens using the following code:
// Create a small float buffer and fill it with some 0's
final FloatBuffer buffer = FloatBuffer.allocate(3 * 128 * 384);
final float[] small = new float[384];

for (int i = 0; i < buffer.capacity() / small.length; i++) {
    buffer.put(small);
    buffer.rewind();
}

// Continually create a new NDArray to wrap the buffer, then convert to a float array
try (final NDManager manager = NDManager.newBaseManager()) {
    for (int i = 0; i < 1_000_000; i++) {
        buffer.rewind();

        try (final NDArray array = manager.create(buffer, new Shape(3, 128, 384))) {
            array.toFloatArray();
        }
    }
}

Steps to reproduce
Run the above code

I also encountered the same problem. Do you have any plans for when to release it @frankfliu

I also encountered the same problem. Do you have any plans for when to release it @frankfliu

See: https://github.com/deepjavalibrary/djl?tab=readme-ov-file#release-notes, for the mean time, you can use SNAPSHOT release for testing


Api fetch UUID url

Created two API routes:

API route to fetch bonsai from database based on UUID
API route to fetch bonsai from database based on URL

Aqui fomos pro carai


Select box submits remote form to select meter chart

Where we're doing this currently, e.g. on the pupil charts that allow both meter and date switching, we're using custom Javascript to trigger updates to Highcharts.
We didn't hit any cross-site issues here, so problems with embedding tokens and CORS look like they're specific to this UJS approach.
It looks like it triggers loading a section into the page, which means re-initialising Highcharts. I think you're likely to hit problems with the chart controls being initialised/working correctly. At the moment those are done on page load. For the pupil charts they relevant functions are called in the custom Javascript.
Given we can already add an mpan_mprn to a chart config, and some existing code for that, I'm wondering whether it'd be better to do this using the existing approach? Are there extra benefits to the approach taken here?
The only issue I can see is getting the start/end dates for the meter. But we could add those in as a further iteration. Either by updating the JSON the chart controller returns. Or by simply embedding the relevant dates into the page, so any custom Javascript can switch as required.


Question: Connect to H2 via RazorSQL - How can I convert walletNode.addressData from binary?

I'm accessing a watch-only wallet using a tool called RazorSQL that can read H2 databases directly in an attempt to download  transaction history from Sparrow Wallet for tax purposes.  In the H2 database, there are many fields (like walletNode.addressData) that are stored in as BINARY, so I'm trying to figure out how to convert them back into strings in the hope that I can see things like blockchain transaction ids to help me match-up self transfers across wallets easily.
Do you have any tips on how these binary fields are encoded and if they contain one piece of data per field (or are they compressed or store a bunch of proprietary other stuff used by the application natively)?   Any tips would be appreciated.  Thanks!

Update: I think we might have to use the rawtohex() function.  I tried this on blockTransaction table and it appears to return same info I see in the UI on screen.

These binary fields are converted to byte arrays in Java after retrieval. Does the transaction CSV (icon next to transaction count in the Transactions tab) not provide what you need?
Closing this off as a support request.


Fix 'Windows Issues' link in README

Link previously pointed to Internationalization section, fix to point at Windows Users section

Very well! Thanks


Feature/template files in kit modules

This adds a naive way how we can add some best practices terragrunt.hcl files (+ modules.hcl/platform.hcl to keep code dry) via a kit modules from collie hub like kit import azure/bootstrap
The mechanism is incredibly naive right now with some straight forward file copying driven by a conventional template/ folder in kit modules, but I think it's a good start in the right direction. We can iterate on this in the future.

See https://github.com/meshcloud/collie-hub/commit/aef46b03367f6e3c7445c5ecb53e80bc72b6db6e for the corresponding kit module that works together with this feature


Automatically create a commit based on commit message

Support specifying a list of auditors

You can already provide this list when a commit contains "Audit: username1, username2"


Section 2 Test

Hi there,
I repeated Section 2 test 4 times. Everytime i get 66%
I always get the first 2 questions correct and for the third question, i tried all 4 answers and all of them were incorrect.
I think the right answer should be:  a: a supported ingress controller
thanks,
Moe

Hi @mmagdyvm I am so sorry for my delayed response, I need to take some time to set up better filtering for my alerts as I set up some automations that alert me all the time and its making it difficult to ensure I see everything that comes in.
Please note that you do not need 70% on every test, you only need to average 70% overall grade across all the tests so if you hit that average score then you should be able to request the certificate without any problem.
I can definitely discuss the question and answer in further detail with you, but I would prefer to do that in a direct message if you could please reach out to me on slack, twitter or linkedin DM, or email<EMAIL_ADDRESS>I can share more detail about the test question.
Thanks so much!


Update sidecar example in Operator README

This PR updates the sidecar example in the Operator README, as it does not work. It changes the jaegerreceiver protocol to thrift_compact instead of grpc. This is also reflected in a PR on the opentelemetry-operator repository, 837.

@erichsueh3 please bump the operator chart version.

Let's make the example correct by making it be OTLP instead of jaeger.
otlp:
  protocols:
    grpc:
    http:
...
service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: []
          exporters: [logging]

I suggest doing the same in the operator repo's README

@TylerHelmuth The example does not work with the otlp receiver, I think because the myapp pod uses image: jaegertracing/vertx-create-span:operator-e2e-tests.

The example does not work with the otlp receiver, I think because the myapp pod uses image: jaegertracing/vertx-create-span:operator-e2e-tests.

I should've read down further to see the image.  Thanks for the clarification.

Do you know why grpc isn't working? It is the default protocol according to the receiver.

What do you mean by default protocol? A protocol must be specified in the jaegerreceiver configuration, and in the Getting Started section of that README it says "By default, the Jaeger receiver will not serve any protocol".

What do you mean by default protocol? A protocol must be specified in the jaegerreceiver configuration, and in the Getting Started section of that README it says "By default, the Jaeger receiver will not serve any protocol".

Sorry, "a protocol".  I would expect grpc as a protocol to work, unless the jaegertracing/vertx-create-span:operator-e2e-tests image doesn't know how to send over grpc.  My guess is it only knows how to send over thrift_compact?

Assuming jaegertracing/vertx-create-span:operator-e2e-tests can't send over GRPC and can send over thrift_compact then this looks good to me. I would hold off on merging until the operator PR is approved, to ensure this example stays up-to-date with any feedback from that PR.

Yes, after testing it myself, it seems like it could only send over thrift_compact so it's most likely that jaegertracing/vertx-create-span:operator-e2e-tests can't send over GRPC.


New vehicle is not displayed in GridView

Scenario:

Add new vehicle (e.g. Mercedes Paravan V-Class)
Click on Gridview, the new vehicle is not displayed

First noticed in dispo.tixizug.ch, this could be a data-quality issue (migrated data).

Same for adding new vehicle to existing category:

The error(s) cannot be reproduced with data from tixizug:
tixi_migrationII_repeatedOrders.sql 01. September 2016.
Reopen if this occurs again.


Possible NPE

If revocableHashSignature is null (https://github.com/cloudfoundry/uaa/blob/391163ebad397b8f3eb5298aa01412dd94c9a176/server/src/main/java/org/cloudfoundry/identity/uaa/util/TokenValidation.java#L366) it would have caused a NullPointerException above (https://github.com/cloudfoundry/uaa/blob/391163ebad397b8f3eb5298aa01412dd94c9a176/server/src/main/java/org/cloudfoundry/identity/uaa/util/TokenValidation.java#L361).

Closing due to inactivity.


Scroll updation

In operations tab scroll bar updated

PR needs to be for Releases/Official branch and not for master


Why can't ingest the metadata of foreign table in postgresql?

When run metadata-ingestion on postgreSQL,  it couldn't ingest the metadata of foreign table in postgresql. I can't found where could config it.

Hi @Echelon77 - we introduced Foreign Key support in late September - here are some resources that might help!

FK demo
DataHub Docs- Schema Metadata
DataHub Docs - ForeignKeyConstraint


NiFi-9817 Add a Validator for the PutCloudWatchMetric Processor's Unit Field

NiFi-9817 Add a Validator for the PutCloudWatchMetric Processor's Unit Field

PR Description:
The AWS PutCloudWatchMetric processor has a Unit property that requires a value from AWS's CloudWatch API specifications. This value is a constant from a predefined set of string parameters. The API enforces casing so a unit value of "bytes" fails to make a successful API request, whereas "Bytes" succeeds.  This fix validates if a user is typing the correct Unit value parameter prior to starting the PutCloudWatchMetric processor.
The proposed fix includes a new Validator() to warn the user about the issues prior to starting the PutCloudWatchMetric processor and a set to determine the partitions for the Unit field in API requests to AWS. There are also updates to the integration tests and unit tests to check the validity of the processor.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[x] Have you verified that the full build is successful on JDK 11?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

@joewitt let's try this again. The original fork was all sorts of FooBar. would you mind taking a look at this at your earliest convenience?

@MikeThomsen wonder why the MAC JDK8 is ok on some runs and others it fails. Do we just rerun in this case? Maybe I should pull changes from main into my commit?

@MikeThomsen wonder why the MAC JDK8 is ok on some runs and others it fails. Do we just rerun in this case? Maybe I should pull changes from main into my commit?

I have seen some intermittent failures related to that particular test method, but the most recent commits in main should resolve those issues. For now, I restarted the macOS build.

@MikeThomsen I probably just screwed this all up, but rebased from master. Sigh, may have to revert.

@nandorsoma right on! I'll work on these changes. Yeah, I tried to rebase and git threw a fit. Let me find some time to review the changes and rebase main off of my commit.

@nandorsoma ok made the changes, if you like them I'll rebase. Forgive my ignorance here, but everytime i attempt to rebase I get a boatload of commits from other folks. What's the best way to keep this clean?

Hey @patalwell ! Sorry for the delay, I'll review this today or in worst case tomorrow!

@nandorsoma wicked! no worries!

@nandorsoma ok, all set. Please let me know if there's anything else I may have missed!

Ran the flow locally with valid, invalid, and blank Unit field. Works as expected. Please let me know if there is anything else we might need. Sorry been busy with work! New gig! @exceptionfactory @nandorsoma

Thank you for your recent changes @patalwell! It's a more robust one, I like it. However it is lacking the empty string as a valid unit which was supported in the previous version. I've added a test suggestion to ensure that we support it and backward compatibility is not affected.
Edit: Before accepting my suggestion... This review was based on the recent changes. But after checking again the original code, I see that empty unit was not allowed because NON_EMPTY_VALIDATOR was used. Probably I missed that in your original change. Now I'm a bit confused and I'm not sure which one was your intention.

Thanks for persevering through the feedback @patalwell, I think this is just about good to go!
@nandorsoma As you noted, the NON_EMPTY_VALIDATOR would prohibit an empty value for the unit. With that fact, do you have any additional feedback?

No, I haven't got @exceptionfactory. I was just curious that it was an unintentional change until the last commit and I missed that during the review cycles or the opposite of that.


Just print out name string, not the entire Name struct

Objective
This is just an oversight on my part when I implemented this in https://github.com/bevyengine/bevy/pull/7186, there isn't much reason to print out the hash of a Name like it does currently:
Name { hash:<PHONE_NUMBER>325729304, name: "Suzanne" } (7v0)

Solution
Instead it would be better if we just printed out the string like so:
"Suzanne" (7v0)

As it conveys all of the information in a less cluttered and immediately intuitive way which was the original purpose of DebugName.

Some thoughts after thinking through this again: Should we even be printing out the hash for Name? In some ways I feel like it might make sense to just forward the Debug impl to the string.


If cims can't 'park and ride' due to lack of parking, they need to adapt better

Description
I first watched this weird behavior after I added some bus stops to the main arterial leading into the city. Instead of following the road, cars are now driving into the neighborhood next to it and are searching for a parking spot. If they find one, they'll walk to the next bus stop, but more likely they are driving around round after round, because everyone else parked there and used public transport for getting into the city. While this behavior is probably a real world city planners dream, it's not very helpful in the game. I'll try to build a park and ride facility, but it shouldn't be like that.
To reproduce this error, it is probably necessary, to have a city without a highway network, so that the problem concentrates around one or two exit ramps. It will probably spread out if there are multiple options and become indistinguishable from normal behavior.
Reproduction Steps

Add public transport near an important highway exit.
Watch.

Mod List
Only listing mods that could possibly affect this. For a full list look at the output log file.

TM:PE 10.20
-- improved AI enabled
-- Realistic parking enabled
Improved Public Transport 2 [r4.3.1]
WG Citizen Lifecycle Rebalance v2.6 (I tried to disable it, didn't help, I don't think it messes with the pathfinding for the citizens but only alters the destinations of their journeys)

Output Log

https://drive.google.com/file/d/1gfELnYu1S1UrvXaLFOSe2aJz69EKuBqF/view?usp=sharing
Savegame (Optional)

https://steamcommunity.com/sharedfiles/filedetails/?id=1755969736
Screenshots (Optional)

What would you expect them to do?

I'm expecting them to behave a little bit more like real people and drive to their destination instead of queuing up for parking in the first neighborhood they are finding.

So if Parking AI is enabled, and a cim can't find parking to transfer to Public Transport (PT), they should instead drive to where that PT was going to take them to and resume their journey from there?
For example, if the planned route was:
drive to bus stop ---> get bus to next district ---> walk to shop

And there was no parking near bus stop, then their route would become:
drive to bus stop --> no parking, so drive to next district --> walk to shops

Issues might arise if they can't use car to get to next district (eg. only way is a dedicated bus lane road), and also what happens if there's no parking in next district (do they give up and go home or 'pocket car' or...)?
Overall, I like the idea that a car driver would skip a PT portion of a route if they can't 'park and ride'. Just need to work out to do in scenarios above.

This, or a lower amount pf sims that try to park and ride. In reality, it is hard to convince people to use these P+R options, so it shouldn't be that extreme in game.

Yup, I think this would be good enhancement.
So, to summarise all this:

A percentage of cims try park and ride

That percentage could be based around how much parking (total, irrespective of available) within range of where they start their journey

If no parking when they get there, they either:

Drive to destination (preferred, that's what a driver would do)

Or whatever the next stop would be on the PT route?

Walk (if no driving route)

If all else fails (no parking, driving or walking possible) they give up and go home

Ideally some way to flag up the problem to user - either via info view, chirp, or whatever
Cim happiness should reduce as direct penalty to user for not providing enough parking

Update.  After they weren't able to find a spot, they start to drive around this place in a big circle (over the big roundabout intersection, to the next, heading into the city and driving out again), only to search a parking spot on the same roads where they came from again ...
I think the easiest, temporary solution would be a flag to disable the park and ride behavior altogether.

Something has changed. They now don't even try to drive to a parking spot nearby, but are straight up driving to the bus stop and are waiting there in the lane, while thinking about where to go.
I've made a video of it.
This only happens with the improved AI, but if I turn off the realistic parking AI, they start to just despawn their cars at this point.
So two problems:

Massive overuse of the P+R mechanic.

Cars stopping while searching for a parking spot.

We're working on a load of bug fixes to the parking AI at the moment, so hopefully the 10.21 release will solve this issue.

Would you be willing to help us test the updates to parking AI? If so:

Unsubscribe any workshop versions of TM:PE first
Download and extract TrafficManager.zip
Depending on what you use to unzip the file, there might be multiple TrafficManager folders;  you want the one that contains a bunch of .dll files.
Put the TrafficManager folder that contains .dll files in to the following location:
C:\Users\USERNAME\AppData\Local\Colossal Order\Cities_Skylines\Addons\Mods replacing USERNAME bit with whatever your Windows username is.

That will add a beta version of TM:PE v10.21 which contains most of the parking AI fixes. You'll need to enable it in Main Menu > Content Manager > Mods.

I only geht Version 10.20 from doing so. Am I missing something?

Ah, the version number in that zip isn't bumped yet (we usually only do that during release process). So yea, it will still say 10.20, but it's got the updated parking AI code from pull request #359 in it.

As far as I can tell, they seem to distribute better over the available parking spots and stopped piling up in the first neighborhood.
But the issue with cars stopping right before the bus stop isn't solved.

Thanks for testing and the feedback. It's good to hear that it's improved some aspects of the parking.
For the park and ride aspect (eg. piling up at bus stop) we need to do some more extensive changes so it will probably be a while yet before that's fully sorted.

I guess that before path-finding starts the road segment with the bus stop is treated as having road-side parking spaces. But as they approach the segment they realize that parking is not possible there. That would be even an issue of the base game itself. I will check my theory.

That might also be why cims aren't parking near my lakeside pier (as per earlier comments in #359). I have a bus stop there, but by time cims try and park they'll likely find better alternatives to the opposite side of the road.

This is only solvable by adding an indication to each segment whether

road-side parking is possible (= has parking spaces and no bus stop) and/or
whether a parking building with free parking spaces is present within a short range.

Tagging #176


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3847

Questions ?
Please refer to the Backport tool documentation


Use native-tls instead of openssl

The openssl library is a PITA to build on windows, the native-tls library uses the host's tls implementation (schannel on windows, security-framework on osx and openssl on other platforms)

Can't find native-tls in crates.io 😞

It's a good idea, but native-tls is quite young. I think we have to keep this issue till native-tls released.

Some people have offered to provide OpenSSL binary distributions for selected operating systems.
https://indy.fulgan.com/SSL/
https://wiki.openssl.org/index.php/Binaries

In https://github.com/blackbeam/mysql_async you could use https://crates.io/crates/tokio-rustls
and for rust-mysql-simple you could use https://crates.io/crates/rustls .
rustls is built on top of https://github.com/briansmith/ring and https://github.com/briansmith/webpki .
ring is a fork of Google's Boringssl, which aims to rewrite as much as possible (and meaningful) in Rust. rustls can even be used with hyper, the most popular rust http library, with https://crates.io/crates/hyper-rustls . With using the system's native TLS implemenation we would not profit from Rust's advantages to have a secure TLS implementation.

sfackler to the rescue: https://github.com/sfackler/rust-native-tls


[Bug] [Flink] Not support YarnPerJobClusterDescriptorAdapter for FlinkSQLComputationExecutor

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-commons
What happened + What you expected to happen
当 linkis 有启用个人函数功能，streamis 运行oncejob sql任务时，会导致Not support YarnPerJobClusterDescriptorAdapter for FlinkSQLComputationExecutor 的异常。

I want to fix this issues，you can assign it to me

why just remove this wds.linkis.engine.connector.hooks property ,can fix this bug ?

I want to fix this issues，you can assign it to me. @jackxu2011 @casionone


policy: Add e2e test for ICMP CNP

Related: #14609
Add e2e test for ICMP Cilium Network Policies.
Note: this PR should be merged after ICMP CNP is implemented without a feature flag.

This PR has been integrated https://github.com/cilium/cilium/pull/20174.


fix: only cancel cancelable touchmove events

We are receiving a reasonable amount of ReportingObserver errors on our swiper component. The error is:
ReportingObserver [intervention]: Ignored attempt to cancel a touchmove event with cancelable=false, for example because scrolling is in progress and cannot be interrupted

To be honest I am not sure how to test this as I havent been able to trigger this issue myself, but I used this SO as reference and the error it self also exactly explains what the issue is: https://stackoverflow.com/questions/26478267/touch-move-getting-stuck-ignored-attempt-to-cancel-a-touchmove

thanks, merged


Grammar fix

:laughing: Does this not make sense? I thought it was a good line

Input your wealth to visualize it's physicality...

Any thought's on the rest of the code?

It does make sense, however it reads rather unnatural lol.


Add Poisson node

ReactiveMP.jl is missing Poisson node.
The node exists in ForneyLab.jl.
Any volunteers to port?

Fixed with #132


F#2142 lineage view

Description
The lineage view tab is added to the metadata information of mdm
'This tab is still a prototype stage'
Related Issue :
#2142
How Has This Been Tested?

Create a Wrangled dataset in the following format
( upstream_meta_name, upstream_meta_col_name, downstream_meta_name, downstream_meta_col_name, description )
the metadata name must be a value that actually exists
go to the detail view of the wrangled dataset
click the make linage button
go to [Management - Metadata - Metadata Details - Lineage View tab]
There will be a lineage diagram for the metadata

Need additional checks?
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional Context

run build
deploy to 1

Complie error 확인 바랍니다.
[INFO] WARNING in Empty property 'display' at 28520:43. Ignoring.
[ERROR] ERROR in src/app/meta-data-management/detail/component/lineage-view/lineage-column-view.component.html(17,55): : Property 'closeInfo' is private and only accessible within class 'LineageColumnViewComponent'.
[ERROR]
[ERROR] npm ERR! code ELIFECYCLE
[ERROR] npm ERR! errno 1
[ERROR] npm ERR<EMAIL_ADDRESS>prod: `npm run package-reinstall && node --max_old_space_size=10240 ./node_modules/.bin/ng build --deploy-url /resource/ --output-hashing all --prod --base-href /app/v2/`
[ERROR] npm ERR! Exit status 1
[ERROR] npm ERR!
[ERROR] npm ERR! Failed at the<EMAIL_ADDRESS>prod script.
[ERROR] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ERROR]
[ERROR] npm ERR! A complete log of this run can be found in:
[ERROR] npm ERR!     /data1/jenkins/.npm/_logs/2019-07-03T08_46_25_318Z-debug.log

run build
deploy to 6

run build
deploy to 6

run build
deploy to 6

run build
deploy to 6

run build
deploy to 2

Response에는 포함되어 있는데 그려지지 않는 line이 있습니다.
"연임테스트03" -> "연임테스트"
"test_nfl" -> "연임테스트"

response

lineage

run build
deploy to 2


fix(net): check for handshake disconnect

P2PStreamError::as_disconnect did not consider the P2PHandshakeError::Disconnected
also adds some additional traces

Codecov Report

Merging #596 (48eb195) into main (4e677b5) will increase coverage by 0.01%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##             main     #596      +/-   ##
==========================================
+ Coverage   71.96%   71.98%   +0.01%
==========================================
  Files         250      250
  Lines       25245    25265      +20
==========================================
+ Hits        18168    18187      +19
- Misses       7077     7078       +1

Flag
Coverage Δ

unit-tests
71.98% <91.30%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/net/eth-wire/src/error.rs
68.75% <80.00%> (+7.21%)
:arrow_up:

crates/net/network/src/error.rs
70.21% <93.33%> (+9.60%)
:arrow_up:

crates/net/network/src/peers/manager.rs
79.41% <100.00%> (-0.06%)
:arrow_down:

crates/net/network/src/peers/reputation.rs
64.86% <0.00%> (-2.71%)
:arrow_down:

crates/stages/src/stages/bodies.rs
93.69% <0.00%> (+0.38%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


show release notes in PR

:tada: This PR is included in version 1.0.27 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Remove ReadOnlyArray from type parameters

I want to hardcode the concrete type of an interpolation object as a field of a struct. In my opinion it shouldn't be required to have ReadOnlyArrays as an explicit dependency of my package to do this. I start to like this wrapper less and less 🙃
Maybe a good way forward is to get rid of this wrapper, make caching parameters opt-in and properly document that if you do this you should not update u, t. This has the advantage that the default setting is more compatible with AD packages. Then we should only make sure that AD packages do not try to differentiate w.r.t. cached parameters.

That sounds reasonable. Indeed array wrappers always tend to introduce other problems. I think one other I saw was GPU support.


nixos/tests/networking: Alleviate race in scripted test

This step often failed both locally and on Hydra. This change appears to greatly alleviate it on machines that are not very busy at least.

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This seems reasonable: setting the MTU on these interfaces is, iirc, controlled by the .link files and based off a udev trigger. I don't know if there's a better way to make sure that's happened.

@ofborg test networking.networkd.virtual networking.scripted.virtual

Fun, that's a different failure. I don't think it's related.
@ofborg test networking.networkd.virtual networking.scripted.virtual

Hah, yeah, looks like that's a different flake. Turns out sleeping 10 seconds does not a reliable test make...

Who would have thought! :D


App keeps crashing on iOS 10

Hi @mikaelkindborg,
I'm experiencing issues on iOS 10. Scanning and connecting works, but the app crashes to background immediately after connecting. I don't have any error messages because I yet don't have XCode 8 installed, but just want to ask if you can confirm your plugin and the methods are working correctly on iOS 10. I will try to provide more information ASAP.
Marc

Just had the opportunity to test this with XCode 8. This is the actual error message:
Assertion failed: (![self.commands isEmpty]), function -[EVOPeripheral assertCommandAvailable], file /Users/qpwr/CordovaApps/SmartRace/platforms/ios/SmartRace/Plugins/cordova-plugin-ble/EVOBLE.m, line 289.

Would be great if you'd be able to shed some light on this very soon, because the app is currently not usable on iOS 10 :-(

@mikaelkindborg, do you already have an idea whats wrong? Do you think there is a chance you could provide me with some sort of quickfix?

@qpwr Hi, sorry for slow response, have been upgrading iOS and Xcode now and done testing. Here is a test report and an analysis.
Test result
Tested BLE on iOS 10.0.1 on iPad Mini.
Could no reproduce the problem you found. Tested various of the Evothings BLE example apps using different models of the TI SensorTag.
Possible causes
The assertion happens when a native callback (delegate method) in iOS occurs, but no corresponding JavaScript callback (Cordova command) exists. This is a bit nasty, it would be fault-tolerant to use conditionals and only call the JavaScript callback when a command exists.
I can think of two causes for this happening:

iOS 10 has some behaviour causing a delegate method to be called, or be called multiple times, even though no corresponing request has be made (no JavaScript function have been called to trigger the delegate method callback).

The app has some behaviour that causes this to happen (not seen this previously however).

Further test data
Do you have any details on which JavaScript function (in the BLE plugin API) is causing this? Would it be possible for you to log what is happening up to the assertion occurs? That would be helpful in finding the problem. Also details on which BLE device you are using could be helpful.
Possible workaround
The workaround I can think of is to replace the method call to assertCommandAvailable with a conditional, in the file EVOBLE.m. That is 7 occurrences.
Add this method:
- (bool) noCommandIsAvailable
{
    return [self.commands isEmpty];
}

Then replace this (7 places):
[self assertCommandAvailable];

With this:
if ([self noCommandIsAvailable]) return;

Not sure how this would work out, but is worth trying.
Related issues
Possibly related:
https://github.com/don/cordova-plugin-ble-central/issues/311
https://forums.developer.apple.com/thread/63704

Hi @mikaelkindborg, thanks A LOT for your response. The workaround you proposed works great and I will hopefully be able to release a new version of my app tonight after some more testing. I will try to dive a bit deeper into the issue and what you mentioned as possible causes afterwards and try to give you some more feedback on it. Big thanks so far!

@qpwr Great to hear it works! Perhaps we should put this fix into the plugin production code? Any hints you may have regarding what causes the situation with the assert would be useful for finding out what goes wrong. Best of luck with your app!

What is the status of this issue? Should we put the fix into the plugin? Anyone seeing crashes on iOS 10?

For what its worth, my app works fine on iOS 10.  I scan for and connect to
devices, read services, read/write characteristics and register for (and
receive) indications all exactly as I did before.
On Mon, Oct 10, 2016 at 2:35 PM, Mikael Kindborg<EMAIL_ADDRESS>wrote:

What is the status of this issue? Should we put the fix into the plugin?
Anyone seeing crashes on iOS 10?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/evothings/cordova-ble/issues/119#issuecomment-252725544,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACpRcgHSqeMTLcCNv0n96lHRO2GvEbCKks5qypN5gaJpZM4J_3a_
.

Well, I can only say that the app was reproducably crashing on iOS 10 without the fix and does now no longer. I still don't know the exact reason, but I know its fixed now :-D - so I would vote for adding the fix to the plugin. Thanks!

@sjrcgtek @qpwr Many thanks for the input! Will have a look at adding the fix on iOS.

Fix added in this commit: https://github.com/evothings/cordova-ble/commit/074e0a8de77f25ccb145211c77ffe3f270022724


Convert submodules to meta?

Hi!
Often I get detached HEADs when working with submodules in a meta project (which is immense pain).
How can I move from submodules to meta? I want to work in a single project root and split commits into their own module-repo's.
Thank you.

To add to @patrickleet's suggestion for just importing them as new meta child projects, you can always have meta repos within meta repos. So, if you have, say, a meta repo now with a bunch of child repos that each use submodules – just turn those child projects into meta repos and add the used-to-be-submodules as child repos of that meta repo.


HIP and Spack

Compile HIP directly without hipification
Updated CMake config to simplify spack package implementation
Organize N-body code into more translation units and remove duplicate upsweep and mass-center implementations

cscs-ci run


UpdateDataSource failed

Hello,
I am working on a DataWarehouse project and I am trying to develop an easy CICD integration for PowerBI.
I work on three environments, DEV UAT and PROD.
Thanks to the action called "Power BI Action: Publish", I am able to deploy a report on the different workspaces in app.powerBI.com.
As I am also working with different OLAP SSAS databases, I need to change de connection at every step of the release (to link the UAT report to the UAT SSAS database)
I am currently stuck in the changing data source step. I found the action called "Power BI UpdateDataSource" but I get the following error.
ReleaseLogs_480.zip
Here you can see what rules I have followed.

For the field "Workspace name", I put the one that I see in the left side of the screen on app.powerBI.com.

For the field "Dataset name", I put the one that I see in the workspace with a type label set to "Dataset"

For the fields "Old server" and "New server", I put the same server (the two databases are on the same one) found on SSMS.
For the fields "Old database" and "New database", I put the
databases names found on SSMS.

Am I doing something wrong?
Thanks in advance,

i am having same issue.

@maikvandergaag  here is the screenshot. I think the API call to update data source is failing

Hello,
I managed to solve the problem. I had to add two steps, the first is "take ownership of the dataset" and the second is "update gateway". Also, I had to add the Power BI service as the gateway owner. The whole solution now works fine for me.
Thanka lot for your work !

@nicomont can you please provide details on these steps please. I bet i might have same issue.

1- The first step is the same that the one to publish report on DEV workspace

2- We have to take the ownership of datasets

3- We need to update the gateway for each report

4- Finally, we can update the datasource from DEV to UAT

Note that I had to set the Power BI service as the owner of the gateway for the service to trigger it.

@nicomont  I see. So I am using SQL as DataSource type above and on Update Datasource step I get Invalid Request exception when invoking API. As in screenshot above.
@maikvandergaag any thoughts?


FindCursorContext.options are shared between requests and affect the output

If I reuse a single instance of MongoClient between independent requests, a limit value of one request limits the number of items of the second request.
I use a single client for all my requests:
const FIND_OPTIONS: FindOptions = { noCursorTimeout: false };

const client = new MongoClient();

try {
  await client.connect({ ... });
} catch (err) {
  console.error('Error connecting to MongoDB', err);
  throw err;
}

const database = () => {
  return client.database("test");
};

First request has the limit call:
export const allPositions = async (limit: number, offset: number) => {
  const db = database();

  const positions = db.collection<PositionSchema>("positions");

  return await positions.find(filter, FIND_OPTIONS).skip(offset).limit(limit).toArray();
}

Second request is supposed to return all items:
export const allLocations = async () => {
  const db = database();

  const locations = db.collection<PositionSchema>("locations");

  const items = await locations.find({}, FIND_OPTIONS).toArray();

  return items;
}

Output:

/allLocations Returns 70 locations (70/70)
/allPositions?limit=30 Returns 30 positions
/allLocations Returns 30 locations (30/70)
/allPositions?limit=5 Returns 5 positions (because limit equals to `5)
/allLocations Returns 5 locations (5/70)

If this is the expected behavior, how should I manage the MongoDB connections then?

Thank you for submitting this issue. I'll check it out on the weekend

The problem is in this line:
const FIND_OPTIONS: FindOptions = { noCursorTimeout: false };

If I had created a new FindOptions object for each call, I wouldn't have faced this issue.
I don't know if you consider this as an issue, but I've created a PR just in case.
The PR creates a new options object every time you call skip, limit, and sort.


DNS configuration via Terraform-native options, Issue #216

I was not able to test this against your latest commit due to a recent issue #225 that I filed - but this should work, I deployed successfully prior to your latest push.
I also just realized this includes the fix for issue #213 as well; this should have been two separate commits/pulls,  sorry for the sloppy branch naming

Hey @wompapmow - I'm going to try and test this in the next day or so. Sorry for the delay, it's been a really hectic week.

No worries! I’ve already got my lab up and running with this code, so its
not hanging over me
On Thu, Mar 14, 2019 at 22:18 Chris Long<EMAIL_ADDRESS>wrote:

Hey @wompapmow https://github.com/wompapmow - I'm going to try and test
this in the next day or so. Sorry for the delay, it's been a really hectic
week.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/clong/DetectionLab/pull/226#issuecomment-473144133,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEWGqaYn3mP6pJubSNuRXelELcL1KUXnks5vWxEHgaJpZM4brlGh
.

--
Sent from my LG Washing Machine

Just tested this and it works great - thank you!


Add jax.default_device context manager

This currently only supports setting a specific Device object, not a
platform like "cpu". That should be added in the future.
Bumps the minimum jaxlib version in order to include
https://github.com/tensorflow/tensorflow/pull/53656

Sorry this is so huge; I can break up into smaller changes if that'd be helpful. I'll also create a CL if you prefer to review that.

👀


Spatial data and census 3 - tag issue

Hi @ValentineHerr,
I'm running through my R code again to add the 2022 mortality data and I've encountered a problem. I did update my local GitHub repository, so everything should be up-to-date.
In the scbi.stem3.csv  there are two stems with the same coordinates but different species:

tag
StemTag
sp
quadrat
gx
gy
MeasureID
CensusID
dbh

30365
1
fram
308
59.6
141.8
240749
3
1001

33331
1
quru
308
59.6
141.8
240750
3
180

But in scbi_stem_utm_lat_long_2018.csv there isn't a 33331 tag:

tag
StemTag
sp
quadrat
gx
gy
MeasureID
CensusID
dbh

30365
1
fram
308
59.6
141.8
240749
3
1001

30365
1
fram
308
59.6
141.8
240750
3
180

I think this must be a similar issue to 133461 and 131352 (can't find the issue on GitHub!) I initially thought 30365 must just have two stems, and before my update I believe 30365 was showing as having two stems in the census data. Is this a recent correction that wasn't passed to the UTM file? It looks like 133461 and 131352 are still categorized wrong in the UTM file as well.

tag
StemTag
sp
quadrat
gx
gy
MeasureID
CensusID
dbh

131352
1
fram
1316
245.5
303.3
212439
3
1020

133461
1
fram
1316
245.5
303.3
212440
3
321

Oh… I’ll fix that asap. (I closed the issue, that is why you can’t find it)
Get Outlook for iOShttps://aka.ms/o0ukef

From: jess-shue @.>
Sent: Thursday, March 16, 2023 12:37:26 PM
To: SCBI-ForestGEO/2023census @.>
Cc: Herrmann, Valentine @.>; Mention @.>
Subject: [SCBI-ForestGEO/2023census] Spatial data and census 3 - tag issue (Issue #14)
External Email - Exercise Caution
Hi @ValentineHerrhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FValentineHerr&data=05|01|herrmannv%40si.edu|84b3fe4a8ecb41d54dda08db263cba66|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|638145814485615899|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=2YT42%2Ft%2BIcLqVz346%2BorSlVEmrcr0N4vEweJW7S5A34%3D&reserved=0,
I'm running through my R code again to add the 2022 mortality data and I've encountered a problem. I did update my local GitHub repository, so everything should be up-to-date.
In the scbi.stem3.csv https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSCBI-ForestGEO%2FSCBI-ForestGEO-Data%2Ftree%2Fmaster%2Ftree_main_census%2Fdata%2Fcensus-csv-files&data=05|01|herrmannv%40si.edu|84b3fe4a8ecb41d54dda08db263cba66|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|638145814485615899|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Vzre0xkdC5YwkQu3Lm8owlykmfIcsLzxxFv0%2BdIVk%2FY%3D&reserved=0 there are two stems with the same coordinates but different species:

tag     StemTag sp      quadrat gx      gy      MeasureID       CensusID        dbh
30365   1       fram    308     59.6    141.8   240749  3       1001
33331   1       quru    308     59.6    141.8   240750  3       180
But in scbi_stem_utm_lat_long_2018.csvhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSCBI-ForestGEO%2FSCBI-ForestGEO-Data%2Fblob%2Fmaster%2Fspatial_data%2FUTM%2520coordinates%2Fscbi_stem_utm_lat_long_2018.csv&data=05|01|herrmannv%40si.edu|84b3fe4a8ecb41d54dda08db263cba66|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|638145814485615899|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Iuzdh5%2BtocwNNKcqJapUvqy8K94lZWfjcBqScZ902G8%3D&reserved=0 there isn't a 33331 tag:

tag     StemTag sp      quadrat gx      gy      MeasureID       CensusID        dbh
30365   1       fram    308     59.6    141.8   240749  3       1001
30365   1       fram    308     59.6    141.8   240750  3       180
I think this must be a similar issue to 133461 and 131352 (can't find the issue on GitHub!)
—
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSCBI-ForestGEO%2F2023census%2Fissues%2F14&data=05|01|herrmannv%40si.edu|84b3fe4a8ecb41d54dda08db263cba66|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|638145814485615899|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QZ7uNcxJ2bZdtt0mPy0fPddUgB%2FQcA9pIfkMmvrkNzg%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEWDCIKWMLCPW46DNTIFDKDW4M6UNANCNFSM6AAAAAAV5OSV6M&data=05|01|herrmannv%40si.edu|84b3fe4a8ecb41d54dda08db263cba66|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|638145814485615899|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=KeHU7xQN%2BXZfzAEAs%2BfaUZCz3Qu%2BBFOqEkPE%2Fz2yJtk%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@ValentineHerr Thank you! Looks good now - that's great you got to see Erika!

She says hi! :-)
(Closing issue now)


Replace checksum and sha256 with std/hash

Should we replace
export { Hash } from<EMAIL_ADDRESS>export { sha256 } from<EMAIL_ADDRESS>
with<EMAIL_ADDRESS>as it is official hash and it supports both Hash and sha256.

They are replaced in commit https://github.com/denodrivers/mysql/commit/613a4317724a672bf7c4538159c66654088d8d4b .


support stream responses

Looks like you can use the stream parameter and curl's --no-buffer argument to stream responses.
However I've overrun my gpt quota so I can't test it.

implemented in d50e1f6


New feature to export all the URLs and their stats in a csv format

export the list of URLs to a .csv


[Bug]: "Name" field in the Contact Us section -Validation

Bug Summary
The "Name" field in the Contact Us section allows users to input symbols and special characters.
Bug Description
The "Name" field in the Contact Us section allows users to input symbols and special characters, which may lead to invalid or spam submissions.
Steps to Reproduce

Go to the Footer Section of Home Page
Click on Contact.
Scroll down to Contact Us section.
Type numbers and symbols into the Name field and submit.
See there is no Error.

Expected Behavior
Name field should only accept Alphabets.
Actual Behavior
Currently it accepts symbols and special characters too.
Screenshots or Logs (Optional)

Severity
Major - impacts significant functionality
Environment

[X] Local Development
[X] Staging
[X] Production
[ ] Other

System Information (Optional)
No response

Please assign me this issue


Labels and Error bars not working on grouped/stacked

I removed, them please replace them and clean up the plot.

fixed in 83ca0aa


Add npm semantic-release workflow

This mr adds a npm semantic-release workflow to publish the diffenrent kinds of eslint configs to npm.
Before merge, please make sure to have the NPM_TOKEN setup correctly in the repo settings to be able to publish the packages to npm.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ignore Tests that throw exception in background thread

Fixes #
Proposed Changes

Can one of the admins verify this patch?


About gitignore

Hi, I have a question about .gitignore.
When I init my project, .gitignore in website/,but in this file, ignore list is website/yarn.lock,I think this should be yarn.lock. website/yarn.lock match file like this website/website/yarn.lock.

@balancelove Hi. I think there is a bug in the creation of the .gitignore when you run docusaurus-init. Is that what you ran to get that bad .gitignore file?

Just confirmed this bug. Refer to the following screenshot

@yangshun, @yykamei - see #533 for a fix (I hope 😄)


bug(drag-drop): cdkDragHandle is not working on table resp. columns

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
In a table row only a specific coulmn should be to initiate the dragging. now its the whole row.
Reproduction
Steps to reproduce:

go  to https://stackblitz.com/edit/angular-467iil-rbkkrf?file=src%2Fapp%2Fcdk-table-basic-example.ts,src%2Fapp%2Fcdk-table-basic-example.html
only "No." column should be possible to initiate the drag not another column

Expected Behavior
on a table i want to define that the first column can be used to initiate the dragging.
Actual Behavior
i can specify which column has like an drag start event listener. now the whole row is like a listener.
Environment

Angular: 15.1.1
CDK/Material: 15.1.1
Browser(s): chrome
Operating System (e.g. Windows, macOS, Ubuntu): windows

In your example, the code shows that the row is the one being dragged:
  <tr (cdkDragStarted)="onDragStart($event)" cdkDrag cdk-row *cdkRowDef="let row; columns: displayedColumns;"></tr>

Nothing indicates that only a column should be dragging

@andrewseguin sure cause otherwise the row is not draggable? how would you do it?


Actions: Improve "stop-commands" example code

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions
What part(s) of the article would you like to see updated?
The section Stopping and starting workflow commands has an example of using stop-commands:
echo "::stop-commands::pause-logging"
[...]
echo "::pause-logging::"

This example uses a hardcoded resume token, which is not best practice. Also, it's confusing that the command to resume processing is ::pause-logging::
There's a much better example in this blog post: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
# disable command workflow processing
echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`"

# log untrusted output
echo "untrusted output"

# enable workflow command processing
echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::"

This creates a resume token based on the GITHUB_TOKEN, so it's different on every workflow run. Doing this makes it almost impossible for the untrusted output to resume command processing.
UPDATE:
An example based on this code would be ideal: https://github.com/actions/runner/issues/807#issuecomment-916236648
It adds a mask for the resume token, so it can never appear in the workflow run logs.

@rcowsill
Thanks so much for opening an issue! I'll triage this for the team to take a look :eyes:

Just noticed PR #9426, which relates to this issue.

@rcowsill Please link this issue and PR if the PR mentioned fixes this issue. That way, when the PR is merged, this issue will be closed 🐬


Action bar stutter on glowing icons.

Getting a heavy stutter when I activate trap launcher on my hunter with the action bar module enabled. Gone back to dominos for now for the bars. I think it has to do with how the glowing trap icons are triggered since the stutter also happens when you cancelaura the trap launcher and the icons deluminate.

https://streamable.com/w5p3vq
https://streamable.com/prut4r
Links to both

Should be fixed with 3ab42a5899c897d28a2b4032af612baf6bc398f0
I'll try to push a manual update to curseforge. (Working on a very big update going live in a few days, and the main branch is already too far along for a small fix update with the automatic upload action 😑 my bad)


[release-1.18] deploymentcontroller: add support for ProxyConfig CRD

Please provide a description of this PR:
This is a manual cherry-pick of #44916.

@hanxiaop @ksubrmnn @pmerrison could you approve this PR?

@jewertow Could you explain why it meets this criteria https://github.com/istio/istio/wiki/Istio-Release-1.18#how-do-i-get-my-changes-into-the-release?

This change was merged into master in #44916 and adds missing functionality that exists in 1.17, but was removed from master as a side effect of deployment controller refactoring. If it won't be included in 1.18, ProxyConfigs applied to k8s Gateways will no take effect in existing Istio deployments.

@jewertow Thanks for the explanation. I've checked the changes and I think it's great to have this one in the release.


[LLM] Support baichuan2-13b paddle52.

PR types

New features
PR changes

Models
Description

Support baichuan2-13b paddle52.

LGTM, 添加一下单测基本上就可以合入了。


Getting test to pass x509.UnknownAuthorityError

--- FAIL: TestTLSTransport_EnvironCert (0.09s)
	test_logger.go:26: time="2017-12-01T11:12:18+08:00" level=debug msg="accepted connection" from="<IP_ADDRESS>:53266" node="<IP_ADDRESS>:53264"
        Error Trace:    tls_transport_test.go:77
	Error:		Expected nil, but got: x509.UnknownAuthorityError{Cert:(*x509.Certificate)(0xc420572000), hintErr:error(nil), hintCert:(*x509.Certificate)(nil)}

	test_logger.go:26: time="2017-12-01T11:12:18+08:00" level=error msg="Failed to decode incoming command" error="remote error: tls: bad certificate"
        Error Trace:    tls_transport_test.go:78
	Error:		Expected value not to be nil.

FAIL

As advised by @arrivets I tried running
cd config
./rootca
./testca

before running the tests with make test again but I am still getting the same error.
Is there any other steps I am missing when running my tests so that TestTLSTransport_EnvironCert passes?

What version of go are you running?
This test uses a feature of go 1.9 (https://golang.org/pkg/crypto/x509/) that uses the environment variable SSL_CERT_FILE to point to trusted root CA certificates.

1.9.2

Ok.
I still think it has something to do with loading the system CA pool.
They talk about it in this issue https://github.com/golang/go/issues/14311
I can't reproduce this from my machine. Working on getting OSX VM..

This should work bd45bc3010b5824d276428cdd848ca2d521dc0f8
Part of the entire pull request. Everything seems to work now except for the stats not show up on MacOS (i.e. watch.sh does not render any stats).
Everything else works, including the simple chat demo.

Sure it works but it is not the same test anymore.
The idea is to test loading CAs from the system if a CA pool is not explicitly provided.

could you please try replacing
err := os.Setenv("SSL_CERT_FILE", filepath.Join(test.testdata, "ca.crt"))
with
err := os.Setenv("SSL_CERT_DIR", test.testdata)
and not providing a pool to the tls transport?

Tested with SSL_CERT_DIR. It still gives x509.UnknownAuthorityError.

damn..
regarding the watch script, maybe try using gawk instead of awk

Yes, I am using gawk.
brew install gawk --with-default-names will set my terminal to use the gnu version of such coreutils program by default

what happens if you remove the tr and awk statements in the watch script.. just leave curl?

curl doesn't return anything at all.
So it is most likely a macOS docker IP/port mapping difference (in comparison with how ubuntu does IP/port mapping).

Reviewing https://github.com/golang/go/blob/release-branch.go1.9/src/crypto/x509/root_unix.go#L42, x509.SystemCertPool() should be getting the SSL_CERT_FILE environment variable so I have no clue why it will fail to load the correct certs.

The thing is that we are not even using the TLS transport yet.
I am tempted to move tls_transport and corresponding test to a separate branch for now
We will write better tests when the time comes to actually use TLS

Interesting article about limitations of docker with macOS.. I had no idea.
We could create an extra container just to launch the watch script.


[Documentation] Grammatical mistake in the SQL Connector sample

Grammatical mistake in the SQL Connector sample
https://ballerinalang.org/docs/by-example/sql-connector
Before run the sample copy the JDBC driver to the BALLERINA_HOME/bre/lib folder.

Fixed with #3625


Added virtual pins functionality to io_place.py, and io_placer in the designs folder

You can now use virtual pins in the pin_order configurations file by using $<number_of_virtual_pins>.
This functionality will give the user more flexibility while placing their i/o pins
You can use virtual pins to place your actual pins closer together, further separate them or shift them towards a certain edge
All changes were made only to the scripts/odbpy/io_place.py file
There is an added design called io_placer which is a replica of the caravel_upw design except it uses the virtual pins concept in the pin_order.cfg file; you can run the flow on both of these designs and check the log file under <run_path>/logs/floorplan/4-place_io.log to see how the placement of the pins was changed.
The algorithm uses the same logic that was used for placement before, so no change will be noticed if no virtual pins were used.
An example of how to use the feature; in the pin_order.cfg file if you wrote:

#N
x
$20
y

The algorithm will consider that there are 22 pins on the north edge, will place x in the first assigned pin slot and y in the last slot and there will be 20 empty slots in between them.

Why is OL maintaining a separate IO pin placer from the one in OR?  If there any capabilities needed in OR then please file an issue (or PR).

@maliberty Would anyone from the OpenROAD team be willing to put in the time and effort to port all existing pin placement files to be OpenROAD-compatible? Do note this includes Caravel, DFFRAM and a litany of dependent projects.

Lint...


chore: update docker compose config and make targets for API development (API and geoprocessing)

Overview
Update docker-compose configuration, restoring what we had commented out.
Services that are not needed now will not start anymore if we use make start-api.
make start will attempt to spin up all the services, though the app one is not fully configured yet, so this target should not be used for now.
Additionally, it's now trivial to enter a psql console both for the API db (make psql-api) and for the geoprocessing db (make psql-geo).
Designs
N/A
Testing instructions
Stop all the Marxan services (make stop).
make start-api should start api and geoprocessing services, plus their backing pg services and the redis-api service (not used yet, but we may soon).
make psql-api and make psql-geo should lead to the psql console for the api and geoprocessing db, respectively.
Feature relevant tickets
N/A

Checklist before submitting

[x] Meaningful commits and code rebased on develop.
[ ] If this PR adds feature that should be tested for regressions when
deploying to staging/production, please add brief testing instructions
to the deploy checklist (docs/deployment-checklist.md)
[ ] Update CHANGELOG file

@aagm I think this PR will help to keep configs tidy, while allowing us to spin up locally only services that we need/are ready (I already added the redis-api service as dependency as it should be relatively lightweight and I think we'll need it soon in any case).

@aagm I think this PR will help to keep configs tidy, while allowing us to spin up locally only services that we need/are ready (I already added the redis-api service as dependency as it should be relatively lightweight and I think we'll need it soon in any case).

Works, Ready to Rebase


more graceful header handling

fixes #197
basically, this PR only changes the behavior when the output type is github (markdown).
When generating markdown, we only strips Weave header (i.e. options) and preserver all the other headers.
This PR also improves the regex to match YAML Header so that it will fix #304 as well

This is still broken for hugo as an output type.

nice reminder, thanks !


Add basic string functions to BSTR

A larger effort is coming to provide more comprehensive and uniform string support for the various historical string types in the Windows API. For now, this just makes using BSTR a little easier to use.

@kennykerr realize you probably didn't see my previous message since it was after the pr was merged.


obs_route step should take into account the margins to create the obstructions

The current obstructions don't cover the whole chip area because they don't take into account the hmargin and wmargin:

Redundant. obs_route has been removed.


Zephyr builds fail when using app-manager or other advanced WAMR features

When building on the current version of Zephyr there are a number of errors due to incorrect header files being specified (example below).  It seems that the current support for Zephyr is a bit outdated.  This issue is similar to #1726.  However, that issue only fixed the code used for the minimal example.  Code that references the app manager of graphics libraries fails to compile on current Zephyr versions.
Example compile error:
/src/project/wasm-micro-runtime/core/app-mgr/app-manager/platform/zephyr/app_mgr_zephyr.c:9:10: fatal error: zephyr.h: No such file or directory
    9 | #include <zephyr.h>
      |          ^~~~~~~~~~
compilation terminated.

The fix is straightforward, and I'm working on a pull request and will submit it once I've tested it.

Changes merged.


v0.3.2 SHOW CREATE TABLE doesn't fetch values

Since v0.3.2, SHOW CREATE TABLE doesn't fetch any values via dbt load_result()

Steps to reproduce:
Macros:
{% macro show_create_table2(relation) %}
    {% call statement('show_create_table', fetch_result=True) %}
        SELECT
            create_table_query AS ddl
        FROM system.tables
        WHERE
            name = '{{ relation.identifier }}' AND
            database = '{{ relation.schema }}'
    {% endcall %}

    {% do return(load_result('show_create_table').table) %}
{% endmacro %}

{% macro show_create_table3(relation) %}
    {% call statement('show_create_table', fetch_result=True) %}
        SHOW CREATE TABLE {{ relation.schema }}.{{ relation.identifier }}
    {% endcall %}

    {% do return(load_result('show_create_table').table) %}
{% endmacro %}

then in python console:
import os
import time
from clickhouse_connect.driver import HttpClient
from dbt.adapters.clickhouse import ClickHouseAdapter, ClickHouseRelation
from dbt.adapters.factory import get_adapter_by_type
from dbt.contracts.connection import Connection
from dbt.contracts.relation import Path
from dbt.lib import get_dbt_config
from dbt.tests.util import get_connection
config = get_dbt_config('/usr/app/')
ch_adapter = ClickHouseAdapter(config)
adapter = get_adapter_by_type(ch_adapter.type())
with get_connection(adapter) as conn:
    rel=adapter.get_relation(None, 'internal_analytics_src', 'src_dsas_datasources')
t1=adapter.execute_macro('show_create_table2', kwargs={"relation":rel})
t2=adapter.execute_macro('show_create_table3', kwargs={"relation":rel})

t2 is empty here, should be a table

I assume this is due to Handle queries that are actually commands, simply and clean up tests
But this command should load a table value, and it's counter-intuitive why it doesn't now.

tagging @genzgd, dbt relevant)

@Barsoomx This should be fixed in 0.3.3.
I'm curious as to how this is dbt relevant.  I don't see any use of SHOW CREATE TABLE in DBT, am I missing something?

No, I thought it's relevant because of load_result. The macro I showed you is in dbt, albeit it's mine, sorry for the confusion, there's no such code in base dbt


Configure / My Settings / Default Views - hide the Services table when empty

The Services table was empty for self service users, it's now shown only if the user has rights for any of the items inside.
https://bugzilla.redhat.com/show_bug.cgi?id=1190667

haml-lint warnings fix

@dclarizio Please review.

Verified fix.


GoogleAuthCallback & GithubAuthCallback endpoint returning json response on error

Describe the bug
Currently, the GoogleAuthCallback and GithubAuthCallback endpoints in our application are not functioning as expected when an error occurs during the authentication process. Instead of redirecting the user to the client URL with an error message, they are returning a JSON response.
To Reproduce
Steps to reproduce the behavior:

Go to the google auth url, usually http://localhost:3006/api/v1/auth/google
using the url in the json response, navigate to the google authentication screen
Sign in
Make the app just error in anyway

When an error occurs during the authentication process, the GoogleAuthCallback and GithubAuthCallback endpoints should redirect the user to the client URL specified, appending an error message in the query parameters. For example: https://client-url.com?error=authentication_failed or use headers.
Actual Behavior:
Instead of redirecting to the client URL, the GoogleAuthCallback and GithubAuthCallback endpoints are returning a JSON response containing the error details. This behavior is not consistent with the expected behavior.
Additional context
Add any other context about the problem here.

Currently saying from the context of what I see here...the idea I'm presuming is that the backend handles the entire authentication process (communicating with Google and generating auth URLs) except for after the redirect occurs. I see this convention as the most common amongst users but Google does not really specify how one should go about this.
Ideally, the only specification Google has is that, if your application has a backend, then you just need to provide it with the ID token cos that's essentially everything needed in the end. As opposed to re-inventing the wheel of auth URL generation etc, what I always advise is for the FE to do the entire gymnastics, it's very straightforward thanks to the Firebase SDK. And once the auth is done, the Firebase SDK returns the auth user to the FE and the FE can call Firebase.User.getIdToken() to retrieve the ID and send it over to the BE, and from there on, the BE can verify that the token is valid using Google Auth Library and check if one of such already exists in the database. If one exists, a session (JWT) is generated afterward, however, if none exists, an account and a session are generated.
Resources
https://developers.google.com/identity/sign-in/web/backend-auth
https://cloud.google.com/run/docs/authenticating/end-users

@opensaucerer , thanks for this insight.. actually never crossed my mind about this approach.. @ShowBaba , the FE team has not started integration. We should discuss this further. From this, we have one less endpoint, not much of a problem but fair enough. I also believe this would be a better UX imo


freeciv: 3.0.4 -> 3.0.8

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

3 packages built:

freeciv (freeciv_gtk)
freeciv_qt
freeciv_sdl2


Illegal instruction (core dumped)

i am using latest tensorflow and i am getting error. kindly help me to fix this issue.
i saw some fixes they said me to use tensorflow version 1.5 but i have to use tensorflow version 2 is there any other ways to fix it?

Try downgrading tensorflow-estimator to 2.6.0. If you use pip, run
pip install -U tensorflow-estimator==2.6.0
as described in #819.

Thank you for your response. I will try.
On Mon, Nov 1, 2021, 9:01 PM Willi Gierke @.***> wrote:

Try downgrading tensorflow-estimator to 2.6.0. If you use pip, run
pip install -U tensorflow-estimator==2.6.0
as described in #819 https://github.com/tensorflow/hub/issues/819.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/hub/issues/820#issuecomment-956335644, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANFZUCUH43WM3NTFP4ZW5QDUJ2XGXANCNFSM5HEJG6QA
.

it doesn't work.

@Mohammedirfan25
Could you please move this to closed status as it is resolved. Thanks


Imaginstruments [PCSA00113]

Game summary

Game name: Imaginstruments™
Game serial: PCSA00113

Vita3K summary

Version: v0.1
Build number: 523
Commit hash: https://github.com/vita3k/vita3k/commit/32e9a31

Test environment summary

Tested by: IllusionMan1212
OS: Windows 10 Pro
CPU: AMD Ryzen 5 1600
GPU: NVIDIA GTX 1050Ti
RAM: 8 GB

Issues
Crashes on scePvfNewLib
Screenshots
Not available at the moment
Log
vita3k.log
Recommended labels

Crash

Vita3K summary

Version: v0.1
Build number: 1776
Commit hash: https://github.com/vita3k/vita3k/commit/146fd1c2

Screenshots

Log
vita3k.log

as of https://github.com/Vita3K/Vita3K/commit/5e0b62ccf38329e9e785f0d1e47e9cbdf5e4342c, the game looks fine to me. Didn't notice any graphical issues or softlocks.
Screenshots

Logs
vita3k.log
Recommended Labels

Playable


feat(helm): Merges helm-template plugin into cli.

Sets up the template command using cobra, and adds tests to ensure
the command is working properly.
Closes #1887

this is a duplicate of https://github.com/kubernetes/helm/pull/2781 which is pretty close to being merged.

Shoot, so it is. Sorry about that, I missed the duplicate issue and pending PR.


Installation fails on microk8s

Bug Report
Operator Lifecycle Manager install.sh script fails to install on a new microk8s cluster on a clean Ubuntu 20.04 installation.
Some observations

The install script fails with CSV "packageserver" failed to reach phase succeeded.
kubectl get csv -n "olm" packageserver -o jsonpath='{.status.phase}' returns Installing.
Additionally, CPU usage hangs at 100% (1 full CPU core). (seems to be overall cluster CPU utilization; not tied to any container in particular)
Persists even if we enable cluster add-ons dns, storage, metallb, helm3.
Persists even after microk8s/machine reboots.

Steps to reproduce:

Get an instance in Hetzner Cloud (I got a 16-core, 32GB RAM, just in case…)
apt update && apt upgrade -y && apt install snapd -y && snap install microk8s --classic && snap install kubectl --classic
mkdir ~/.kube && microk8s config > .kube/config
Pick a version of OLM to install:

v0.20.0: curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.20.0/install.sh | bash -s v0.20.0
v0.21.1: curl -sL https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.21.1/install.sh | bash -s v0.21.1 This fails because of https://github.com/operator-framework/operator-lifecycle-manager/issues/2767
https://github.com/operator-framework/operator-lifecycle-manager/pull/2771: curl -sL https://raw.githubusercontent.com/exdx/operator-lifecycle-manager/33e86c2850975a793e121b200476a95511179dc6/scripts/install.sh | bash -s v0.21.1

Expected
# kubectl get csv -A
NAMESPACE   NAME            DISPLAY          VERSION   REPLACES   PHASE
olm         packageserver   Package Server   0.20.0               Succeeded

Actual Result
# curl -sL https://raw.githubusercontent.com/exdx/operator-lifecycle-manager/33e86c2850975a793e121b200476a95511179dc6/scripts/install.sh | bash -s v0.21.1
customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/olmconfigs.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/operatorconditions.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/operators.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/olmconfigs.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/operatorconditions.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/operators.operators.coreos.com condition met
customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com condition met
namespace/olm created
namespace/operators created
serviceaccount/olm-operator-serviceaccount created
clusterrole.rbac.authorization.k8s.io/system:controller:operator-lifecycle-manager created
clusterrolebinding.rbac.authorization.k8s.io/olm-operator-binding-olm created
olmconfig.operators.coreos.com/cluster created
deployment.apps/olm-operator created
deployment.apps/catalog-operator created
clusterrole.rbac.authorization.k8s.io/aggregate-olm-edit created
clusterrole.rbac.authorization.k8s.io/aggregate-olm-view created
operatorgroup.operators.coreos.com/global-operators created
operatorgroup.operators.coreos.com/olm-operators created
clusterserviceversion.operators.coreos.com/packageserver created
catalogsource.operators.coreos.com/operatorhubio-catalog created
Waiting for deployment "olm-operator" rollout to finish: 0 of 1 updated replicas are available...
deployment "olm-operator" successfully rolled out
Waiting for deployment "catalog-operator" rollout to finish: 0 of 1 updated replicas are available...
deployment "catalog-operator" successfully rolled out
Package server phase: Installing
CSV "packageserver" failed to reach phase succeeded

# kubectl get csv -A
NAMESPACE   NAME            DISPLAY          VERSION   REPLACES   PHASE
olm         packageserver   Package Server   0.20.0               Installing

Environment

Kubernetes version information:

Client Version: v1.24.0
Kustomize Version: v4.5.4
Server Version: v1.23.6-2+2a84a218e3cd52

(Checked microk8s version v1.23 and v1.24)

Kubernetes cluster kind: single-node microk8s

Additional context
Installing operators works fine, even if packageserver stays Installing (e.g. running kubectl create -f https://operatorhub.io/install/strimzi-kafka-operator.yaml)

@joaomlneto Awesome - should we close this out, or do you think this is worth documenting? We mainly dev/test on kind and OCP clusters, although we have a daily action that runs OLM's quickstart instructions on minikube clusters. It might be possible to also extend those tests to microk8s clusters, but it's unclear whether this is worth the extra maintenance over time.

@joaomlneto good to see that you got it working. This issue can serve as documentation for any other users that look to install OLM onto microk8s. They would have to enable RBAC on the cluster via microk8s enable rbac for packageserver to install successfully.


Design QA: Portfolio - Open Orders

Designs:
https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=2629%3A4491
HEADER COPMPONENT:

[x] Check header component is up to date

LABELS COMPONENT

[x] Check this is up to date
[x] Line up Outcome label 16px from left

MARKET TITLE COMPONENT
https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=2599%3A866

[x] Check text style is up to date

ORDER DETAILS COMPONENT:
https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=2599%3A1314

[x] Check all text styles are up to date

ORDER DETAILS COMPONENT - EXPANDED STATES

[x] Check styles and colours and spacing for sort by recently traded outcome

https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=10719%3A7986

[x] Remove indent on market title

[x] Update background colours

[x] Check updates are applied when most recently traded market is selected
![image.png]
https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=10718%3A4468

DIVIDERS:

[x] When sorting by most recently traded outcome 1px dark grey divide is 16 px from left and right edges. See image:

[x] When sorting by market keep the 1px dark grey divide 16 px from left and right between outcomes but between markets use a full width 2px dark grey divide. See image:

@Chwy5 @matt-bullock @cillianhunter0
Is this up to design review snuff?

Yes, but those guys have not been able to get on to v2 to test this and about 14 other tickets


fleet and Velociraptor and Guacamole can't install in logger

Hi dear
after Install all  VM dc wef win10 all thing its OK
but the logger VM Stop here 👍 <IP_ADDRESS> logger logger
logger: mysql: [Warning] Using a password on the command line interface can be insecure.
logger: --2021-09-10 17:20:07--  https://github.com/fleetdm/fleet/releases/download/v4.0.0-rc2/fleet.zip
logger: Resolving github.com (github.com)... <IP_ADDRESS>
logger: Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
logger: Unable to establish SSL connection.
logger: unzip:  cannot find or open fleet.zip, fleet.zip.zip or fleet.zip.ZIP.
logger: cp: cannot stat 'fleet/linux/fleetctl': No such file or directory
logger: cp: cannot stat 'fleet/linux/fleet': No such file or directory
logger: /tmp/vagrant-shell: line 298: fleet: command not found
logger: cp: target '/opt/fleet/' is not a directory
logger: Created symlink /etc/systemd/system/multi-user.target.wants/fleet.service → /etc/systemd/system/fleet.service.
logger: [17:20:26]: Waiting for fleet service to start...
fleet and Velociraptor and Guacamole can't install in logger

I’m guessing you are on a network with some sort of SSL interception enabled since its failing to make an SSL connection to GitHub. Solution is to run this on a network without interception turned on.
If that’s not the case, let me know

On Sep 10, 2021, at 11:23 AM, Altwety @.***> wrote:

Hi dear
after Install all VM dc wef win10 all thing its OK
but the logger VM Stop here 👍 <IP_ADDRESS> logger logger
logger: mysql: [Warning] Using a password on the command line interface can be insecure.
logger: --2021-09-10 17:20:07-- https://github.com/fleetdm/fleet/releases/download/v4.0.0-rc2/fleet.zip
logger: Resolving github.com (github.com)... <IP_ADDRESS>
logger: Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
logger: Unable to establish SSL connection.
logger: unzip: cannot find or open fleet.zip, fleet.zip.zip or fleet.zip.ZIP.
logger: cp: cannot stat 'fleet/linux/fleetctl': No such file or directory
logger: cp: cannot stat 'fleet/linux/fleet': No such file or directory
logger: /tmp/vagrant-shell: line 298: fleet: command not found
logger: cp: target '/opt/fleet/' is not a directory
logger: Created symlink /etc/systemd/system/multi-user.target.wants/fleet.service → /etc/systemd/system/fleet.service.
logger: [17:20:26]: Waiting for fleet service to start...
fleet and Velociraptor and Guacamole can't install in logger
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

The problem is still after changing the network setting
After several attempts, all failed to slove SSL GITHUB

@Altwety I think you may be misunderstanding. The network that your host machine on appears to have SSL interception enabled, which means all SSL connections being made by the DetectionLab hosts are going to fail.
I'm unable to reproduce this, so I'm quite confident this is an issue with the network you're using on your host machine.


Booking request end up on the wrong date.

When a booking request is submitted in the app, a confirmation response is returned from the server with the date of the booking request. However when this data is loaded in the App calendar after a requesting it
from the  server, the request ends up on the day immediately prior to the intended booking date.

Looking into possible app side causes.


Allow this package to be installed with pip

converting setup.py to pyproject.toml
add dependencies from conda environment to pyproject

should lay most of the groundwork for #140
@pariterre

@bernikr I can take it from here :)


position: sticky autoprefix

just saw that although there are some lines about position: sticky, was unable to support Safari v11 (Mac OS) and Safari Mobile (on iOS 11.4).

for work properly on these devices the line:
div {
  position: sticky;
}

should be:
div {
  position: sticky;
  position: -webkit-sticky;
}

sorry guys 😅 i wasn't using the latest version
(styled-components didn't update it in their stable yet)


All systems operational to all syatems are operational

This comes from a template we use, I think it is better to send the changes to the original template https://github.com/upptime/upptime. So I will close for now


Add links to Contributors Twitter accounts.

Are you positive these are the correct Twitter profiles for each involved, maybe we should only link those who are 100% correct.

Oh, good call. I thought that's what you were implying with the @ symbol but I guess it's probably best to link to their Github accounts instead. Are those their Github usernames?

Jep, these are actually GH usernames, but if available we could link both, i.e. the @xyz to link to GitHub and if available a link like e.g. [Twitter](https://twitter.com/lukw), what do you think?

I think linking to their Github account would be just fine. They'll have their twitter account on their profile page. Good catch!
Lemme update the PR.

Okay, updated. Only sinsiliux was not a valid profile so I just removed the link for him/her.

cool thanks.

:+1:


Ideas

use lalrpop_proc_macro::{Parse, Process, tokens::{LParen, RParen}};

#[derive(Parse)]
enum Term {
	Num(i32),
	Term(LParen, Box<Term>, RParen),
}

impl Process for Term {
	type Output = i32;

	fn process(self) -> Self::Output {
		match self {
			Num(n) => n,
			Term(_, t, _) => t.process(),
		}
	}
}

Would be similar to the lalrpop grammar
pub Term: i32 = {
    <n:Num> => n,
    "(" <t:Term> ")" => t,
};

Pros: only rust. Don't have to learn yet another language. Type completion and syntax highlighting support out of the box.
Con: code is larger

Pros: only rust. Don't have to learn yet another language. Type completion and syntax highlighting support out of the box.
Con: code is larger


feat: add toggletip component

Description
Created new <Toggletip/> component.
Also, removed the <Tooltip\>'s toggletip functionality.
Links
Implemented based on Tooltips & Toggletips

Note: In Chrome (on Mac) VoiceOver announced the live area text with significant delay when the DevTools was open. Make sure it closed during testing.


Grey background with white icons. Almost unreadable

Hi!
Awesome add-on, however the colors palette seems a little awkward with the grey and white colors. Please change it for the new gmail.

Thanks.

It seems you have the dark theme set in Gmail. Unfortunately, this extension only works correctly with the default theme.

Yes, I see. Thanks for the clarification. I changed it to the default theme.


Filesystem selection through partition id and explicit instantiation

Right now the filesystem is "autodetected," and only FAT can be detected. Instead we want the user to be able to instantiate his own filesystem if he wants. In addition, we want to install handlers for what happens when we mount specific partition ids, starting with all FAT ids automatically instantiate a FAT filesystem. The first because it will help development of or porting filesystems, the latter because not all partitions are FAT and it would be very flexible and amenable to correction without having to recompile the kernel.

Support for instantiating custom filesystem was added with fce1932a2347b093939a0337d05dc70458292a53

Not interested in auto-detecting filesystems for now, due to no standard.. so, closed for now


Change SonarCloud settings to disallow Python 2 compatibility mode

Per this warning in the SonarCloud interface:

@aaronsteers Something like https://github.com/edgarrmondragon/citric/blob/master/.sonarcloud.properties might be needed

Thanks, @edgarrmondragon . And to clarify, do you know if we need this once per project or if it can live in a org-wide repo used for settings.

@aaronsteers Unfortunately I think this has to be set per-project 😥

Thanks, @edgarrmondragon - A moderate headache for sure, but not impossible to manage. 👍


Importer should support File Geodatabase

Context
If you're trying to load data from a number of public sources, you'll find they now provide the data exclusively in FGDB format. It's becoming the new Shapefile, since it's the default format in Esri now.

In GDAL - ESRI File Geodatabase (OpenFileGDB) (Available in GDAL >= 1.11), so our base libraries already support reading it, "just" need the rails / UI support.
Plus the US Census Bureau publishes FGDB
Also, from time to time, File GDB and Personal Geodatabases are in State and City data portals.
It's supported in QGIS
OSGEO4W supports it

File Geodatabase is a really robust format for creating GIS data, w/ domains, and topology rules, it is really great for creating new data. Certain industries in GIS really love the database schema's and guidelines w/ FGDB put forth by Esri and other industry leaders. Also, it can hold a huge amount of data.
Expected result
When imported, a FileGDB should create new datasets for each table in the file.
Additional info
Support and sales have indicated there is customer interest in this format cc/ @andrewbt @jaimecartodb

See #4282 which was just "closed" today (?!?!) cc @CartoDB/solutions

@pramsey any advantage to FGDB over GeoPackages? We had an interesting discussion around .carto today and other formats for it...

There's no technical advantage of FGDB over GeoPackage, actually a slight disadvantage, since from an open source point-of-view, they are read-only. However, the market advantage of FGDB is immense. There's lots of public domain data in FGDB and none in GPKG. There's lots of software that creates FGDB, and very little that creates GPKG (maybe w/ QGIS supporting GPKG there will be more GPKG use, but I kind of doubt it, since QGIS doesn't try hard to force a default working format).

Ran into some FGDB's today...basta!

Duplicates #2610

Tracking for comms here

Santiago, I'm not sure if this is for me.
On Tue, May 29, 2018 at 6:31 PM, Santiago Giraldo Anduaga <
<EMAIL_ADDRESS>wrote:

Tracking for comms here
https://docs.google.com/spreadsheets/d/1BwjxRGzikRSOxRz7mV0PuHX9H06_8UMwuo25TSV9Uh4/edit#gid=0
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/10730#issuecomment-392842259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AImXTSG_TqrgrvFUonzYJs6B23I4IqpDks5t3XfKgaJpZM4K0gG9
.

--
Abel Gibert Matas
EMEA Account Manager
(+34) 91 144 18 58
carto.com

https://carto.com/blog/fgdb-gpkg/


Chore: Add icon and readme package update

Based and blocked by #9

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


update inference library to 1.8.1

更新WindowsC++预测库文档链接

 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.root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


TOTP: TimeStepWindow

TOTP: TimeStepWindow can be changed from the default 30 seconds.
This pull request also contains code from the https://github.com/radprogrammer/rad-authenticator/pull/10 pull request.

Closing, don't want the code reformat