Bug: Farmer's Delight conflict

What happened?
It seems that if both Farmer's Delight and Paradise Lost is installed as mods, Paradise Lost will prevent the player from being able to plant things on Farmer's Delight's Rich Soil block. While unknown if it matters or not, this happens specifically in the Better Minecraft Modpack for 1.18.1 (Fabric). It may still occur with just these two mods, however.
To recreate the bug, simply have both mods installed, place a Rich Soil block from Farmer's Delight, Hoe it, and attempt to plant something on it. You will not be able to plant it. However, if the Paradise Lost mod is disabled, planting works as expected.
Mod Version
1.6.5 - 1.18
Fabric API Version
0.13.3
Relevant log output
[14:15:31] [main/INFO]: Loading Minecraft 1.18.1 with Fabric Loader 0.13.3
[14:15:32] [main/INFO]: Loading 61 mods:
	- cardinal-components-base 4.0.1 via the_aether
	- cardinal-components-entity 4.0.1 via the_aether
	- crowdin-translate 1.3+1.17 via the_aether
	- customportalapi 0.0.1-beta49-1.18 via the_aether
	- fabric 0.46.6+1.18
	- fabric-api-base 0.4.2+d7c144a865 via fabric
	- fabric-api-lookup-api-v1 1.5.3+d7c144a865 via fabric
	- fabric-biome-api-v1 6.0.2+d7c144a865 via fabric
	- fabric-blockrenderlayer-v1 1.1.10+3ac43d9565 via fabric
	- fabric-command-api-v1 1.1.7+d7c144a865 via fabric
	- fabric-commands-v0 0.2.6+b4f4f6cd65 via fabric
	- fabric-containers-v0 0.1.19+d7c144a865 via fabric
	- fabric-content-registries-v0 0.4.9+d7c144a865 via fabric
	- fabric-crash-report-info-v1 0.1.9+3ac43d9565 via fabric
	- fabric-dimensions-v1 2.1.10+a1d9bbf565 via fabric
	- fabric-entity-events-v1 1.4.6+d7c144a865 via fabric
	- fabric-events-interaction-v0 0.4.17+d7c144a865 via fabric
	- fabric-events-lifecycle-v0 0.2.9+d7c144a865 via fabric
	- fabric-game-rule-api-v1 1.0.11+d7c144a865 via fabric
	- fabric-item-api-v1 1.3.1+691a79b565 via fabric
	- fabric-item-groups-v0 0.3.7+3ac43d9565 via fabric
	- fabric-key-binding-api-v1 1.0.9+d7c144a865 via fabric
	- fabric-keybindings-v0 0.2.7+b4f4f6cd65 via fabric
	- fabric-lifecycle-events-v1 1.4.13+713c266865 via fabric
	- fabric-loot-tables-v1 1.0.9+d7c144a865 via fabric
	- fabric-mining-level-api-v1 1.0.7+d7c144a865 via fabric
	- fabric-mining-levels-v0 0.1.12+b4f4f6cd65 via fabric
	- fabric-models-v0 0.3.4+d7c144a865 via fabric
	- fabric-networking-api-v1 1.0.19+d7c144a865 via fabric
	- fabric-networking-v0 0.3.6+b4f4f6cd65 via fabric
	- fabric-object-builder-api-v1 1.11.5+737332ce65 via fabric
	- fabric-object-builders-v0 0.7.13+d7c144a865 via fabric
	- fabric-particles-v1 0.2.10+526dc1ac65 via fabric
	- fabric-registry-sync-v0 0.9.2+ad01bfbd65 via fabric
	- fabric-renderer-api-v1 0.4.11+b0b66fc365 via fabric
	- fabric-renderer-indigo 0.4.15+6825030165 via fabric
	- fabric-renderer-registries-v1 3.2.10+b4f4f6cd65 via fabric
	- fabric-rendering-data-attachment-v1 0.3.5+d7c144a865 via fabric
	- fabric-rendering-fluids-v1 0.1.19+3ac43d9565 via fabric
	- fabric-rendering-v0 1.1.12+b4f4f6cd65 via fabric
	- fabric-rendering-v1 1.10.6+713c266865 via fabric
	- fabric-resource-conditions-api-v1 1.0.2+d7c144a865 via fabric
	- fabric-resource-loader-v0 0.4.15+8906aafd65 via fabric
	- fabric-screen-api-v1 1.0.8+d7c144a865 via fabric
	- fabric-screen-handler-api-v1 1.1.12+d7c144a865 via fabric
	- fabric-structure-api-v1 2.1.3+d7c144a865 via fabric
	- fabric-tag-extensions-v0 1.2.9+d7c144a865 via fabric
	- fabric-textures-v0 1.0.10+3ac43d9565 via fabric
	- fabric-tool-attribute-api-v1 1.3.9+fb3b57b465 via fabric
	- fabric-transfer-api-v1 1.5.10+c329913d65 via fabric
	- fabricloader 0.13.3
	- farmersdelight 1.18.1-0.2.0
	- gud_csl 1.0.0 via the_aether
	- gud_recipe_confidence 1.0.2 via the_aether
	- incubus_core 1.6.6+1.18.1 via the_aether
	- java 17
	- minecraft 1.18.1
	- moretags 2.0.2 via the_aether
	- reach-entity-attributes 2.1.1 via the_aether
	- the_aether <IP_ADDRESS>+1.18.1
	- trinkets 3.1.0 via the_aether
[14:15:32] [main/WARN]: Mod `the_aether` (<IP_ADDRESS>+1.18.1) uses more dot-separated version components than SemVer allows; support for this is currently not guaranteed.
[14:15:32] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.8.5 Source=file:/D:/Users/re11d/Desktop/MultiMC/libraries/net/fabricmc/sponge-mixin/0.11.2+mixin.0.8.5/sponge-mixin-0.11.2+mixin.0.8.5.jar Service=Knot/Fabric Env=CLIENT
[14:15:32] [main/INFO]: Compatibility level set to JAVA_16
[14:15:32] [main/INFO]: Compatibility level set to JAVA_17
[14:15:38] [main/WARN]: @Inject(@At("INVOKE")) Shift.BY=3 on fabric-lifecycle-events-v1.mixins.json:client.WorldChunkMixin::handler$zeh000$onLoadBlockEntity exceeds the maximum allowed value: 0. Increase the value of maxShiftBy to suppress this warning.
[14:15:40] [main/WARN]: @Inject(@At("INVOKE_ASSIGN")) Shift.BY=2 on gud_recipe_confidence.mixins.json:IngredientMixin::handler$zko002$init exceeds the maximum allowed value: 0.

Other mods
No response
Additional Information
No response

Can you send us a log? They can be found in .minecraft\logs\latest.log

Can you send us a log? They can be found in .minecraft\logs\latest.log
Would you like a log of it loading with the whole modpack, or just the two mods?

The latter is preferable

I have updated the original post with the appropriate log file!

@gudenau, looks like this is caused by moretags here. "Overrides" farmer's delight's impl here.
Mind you, this is a primarily forge mod with a fabric port, so they may not be so open to adopting your dependency. I would recommend changing your redirect to do a similar thing their inject does.

Could this be fixed with a datapack? as a temporary solution

Well, Making a data pack let me plant the seeds. However, it does not act like rich soil, it acts like regular farmland. Maybe @gudenau can add a new tag type that does the random bonemeal thing that rich soil does?

@gudenau reminder


Add spanish language support

Always use next branch as destination branch for PRs, not main

I will add the suggested changes (@osauceda-ads).
Thanks @buttercubz and @osauceda-ads.


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>
When I open the Spyder, I shows Spyder had encountered an internal problem

Closing because we can't help you with so little info.


Fix BottomLink warning

During local development the component causes a warning to be logged due to a div being rendered inside a p tag.
This doesn't affect prod deployments seems to be dev mode only.
This change inverts the tags whilst maintaining appearance (a strong tag is also added to maintain the heavier font-weight - it could be a style though)
Before:

After:

Alternatives:
I tried simply removing the typography element but this affected the final line height.

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

this was just merged - try rebasing on that to see if the chromatic error goes away https://github.com/backstage/backstage/pull/7071


The file “auto edit.fcpxml” could not be imported. when the file name has spaces

The file “auto edit.fcpxml” could not be imported.
The resource could not be found. (asset: /fcpxml[1]/resources[1]/asset[1])
it forgets to add %20 in the file path

What export option are you using?

--frame_margin 8 --export_to_final_cut_pro


Header/Topbar

Hi, I already have my own topbar and I was wondering if it is possible to disable it in the router component, because my app looks like this:
http://puu.sh/k7qGI/8aabf3e6bf.png
Thanks.

Yup! <Router hideNavigationBar=true /> gets rid of it. Also you can move all those components you have into the navigation bar if you'd rather do that.

Thanks for your help @MikaelCarpenter but apparently it doesn't work, I guess I have to set true between braces { true } right?
Even so it doesn't work
http://puu.sh/k7BZF/f586548453.png

Ooh do you mean the content sits too low? If so I would just recommend moving your header components into the navbar. That's kind of what it's for..
That being said, hideNavigationBar=true should still move the content up to the top, so I'll have a fix out for that in like less than an hour :)

Oh that would be great.
I mean, maybe I could try to move my code to the navbar, but it seems like I can't even change the height on this navbar and I need more flexibility.
Thank you so much.

There ya go, PR merged :)

Sorry for open the issue again, your commit worked well, but I'm having another trouble with the top of the screen in my app, here is a screenshot: http://puu.sh/k7EBn/d1c0f42c01.png
It seems like some view inside the Router tag is adding some margin top and I don't know how to remove this :/
Thanks

yea that's supposed to be for the status bar (the data carrier, time, and battery). That margin is to account for that.

Yep, my status bar is hidden

k gimme like 10 min

You're awesome man.
I've seen another error, that I'd see it didn't happen before I updated with your changed, and it is when I go to another view, if I want to go back by slide from the left to the right, I get this error: http://puu.sh/k7Fkc/a3943c584b.png
Thanks.

Mmkay added a noStatusBar=true that works if hideNavigationBar is also true. And I'm not getting that error, my swipe to go back works fine.

Ok @MikaelCarpenter I'm very appreciate
Your fixes work really well, also I re-run the project in Xcode and it seems like I don't get this error when swipe back so it works fine. Perfect :+1:
Thanks.


ver. <IP_ADDRESS>.1741 Listening but not supported

I have found a solution in #1881 are same case to me, yet replacing the rdpwrap.ini doesn't work.
I am sure the rdpwrap.ini including the above ver.'s setting.
I have checked the latest released rdpwrap.ini by sebaxakerhtc, yet still no help.
Enclosed attached termsrv.dll for reference.

termsrv.zip

I have checked the latest released rdpwrap.ini by sebaxakerhtc, yet still no help.

It's impossible. At least you should see "fully supported". Replace the file after stopping termservice or use my modded version.
Applicable to https://github.com/stascorp/rdpwrap/issues/1881

It's really not supported until now.
I have go through with your guideline(net start termserivce -> replaced  rdpwrap.ini -> net start termserivce), yet doesn't help.
Even pass over the update process to the autoupdate task, still not work.
Enclosed attached the log of the autoupdate services.
It showed the rdpwrap.ini is up-to-date also yet the configuration still show not supported.

There's some trouble this morning, I don't know is it related to this problem.
The service state is showed unknown this morning.
I tried to uninstall or reinstall the library in vain, it would stop and showed term service can not found.
Then after serval hours with reboot times and times, it becomes Running again, yet it showed not supported until now.
I can reinstall the library right now but it doesn't help.
rdpwrap.ini is updated to 2022-06-16, and I double checked the ver. 10.0.19041.1741 is on list.

rdpwrap.ini is updated to 2022-06-16, and I double checked the ver. 10.0.19041.1741 is on list.

Did you try reboot?

rdpwrap.ini is updated to 2022-06-16, and I double checked the ver. 10.0.19041.1741 is on list.

Did you try reboot? Do you have the same in after reboot?

Yes, I have tried reboot in following step:
net stop -> replace ini -> net start -> reboot = no help
net stop -> replace ini -> reboot -> = termservice auto re-run and no help
net stop -> run autoupdate.bat and update.bat with admin rights -> net start -> reboot = no help
net stop -> run autoupdate.bat and update.bat with admin rights -> reboot = termservice auto re-run and no help

I am experiencing the same issue as @CHSsamchan. I have also tried fully uninstalling and reinstalling rdpwrap overall, in addition to the permutations of replacing ini and rebooting mentioned above.

tried fully uninstalling and reinstalling

Just try my mod then

tried fully uninstalling and reinstalling

Just try my mod then

Tried your mod and fixed! Thanks a lot.

Applicable to https://github.com/stascorp/rdpwrap/issues/1881


[DO NOT MERGE] Disable local auth appconfig

Disable Local Auth in App Configuration

API change check
API changes are not detected in this pull request.

/azp run java - appconfiguration - tests


New device not recognised by Alexa

Just added a new device (1st one in a long time) called Reading Light
Shows up fine but Alexa says "Sorry, I didn't find a device named reading light"
All other devices working fine.
Any ideas?

Did you remember to ask "Alexa, Discover devices"?

#LOL
I did say it'd been a long time since I added one :-)


Custom TwoWire and begin()

#231 (1.14.0) added the option to use a custom TwoWire instance, which is great.
1.13.0 RTCLib's begin looked like this:
boolean RTC_DS3231::begin() {
  Wire.begin();
  Wire.beginTransmission(DS3231_ADDRESS);
  if (Wire.endTransmission() == 0)
    return true;
  return false;
}

it now looks like this:
boolean RTC_DS3231::begin(TwoWire *wireInstance) {
  RTCWireBus = wireInstance;
  RTCWireBus->begin();
  RTCWireBus->beginTransmission(DS3231_ADDRESS);
  if (RTCWireBus->endTransmission() == 0)
    return true;
  return false;
}

In my application I use custom SDA/SCL so I choose not to use RTC_DS3231::begin() but use my own that uses this  begin call:
  // rtc
  Wire.begin(_sdaPin, _sclPin);
  Wire.beginTransmission(DS3231_ADDRESS);
  if (Wire.endTransmission() != 0) {
    Log.warning(F("Initializing DS3231... Error!" CR));
  }

In the latest version (1.14.0) I can't do this because begin now sets a protected var that I can't set from my code:
boolean RTC_DS3231::begin(TwoWire *wireInstance) {
  RTCWireBus = wireInstance;
  // etc..

I can also not use Wire.setPins(x, y) because the code still calls begin on Wire, which I want to do elsewhere.
So I'm stuck with 1.13.0. Any ideas how to work around this pesky situation?
cc @ubidefeo

Maybe add a parameter to the constructor for instructing it to skip the call to begin(). That parameter would default to false for backward compatibility:
In RTClib.h:
class RTC_DS1307 {
public:
  boolean begin(TwoWire *wireInstance = &Wire,
    boolean skip_begin = false);
  // ...
};

In RTClib.cpp:
boolean RTC_DS1307::begin(TwoWire *wireInstance, boolean skip_begin) {
  RTCWireBus = wireInstance;
  if (!skip_begin)
    RTCWireBus->begin();
  // ...
}

we would not take either PR, its non-standard. for ESP32, folks can use i2c.setpins() https://github.com/espressif/arduino-esp32/issues/3779


How to run on inside-out data?

Hi! Thank you for the excellent project!
I am going to run VolSDF on inside-out data such as indoor scenes.
Could you give me some advice on how to setup the parameters?

Hi!
Quick thinking for steps:

Turning the scene inside out.

Revert the initiliazation (make ||x||<r means outside, make ||x||>r means inside). This could be done by directly multiplying the weights with -1 after regular init.
Ensure that all cameras are inside the scene initially. This could be done by properly normalizing the cameras and initializing a sphere with large enough radius. (large enough model: surface: radius_init).
For VolSDF, make sure self.use_bg_sphere is False (since the cameras are already "inside" the whole scene, rays are already always-intersected-at-the-end), and use_nerfplusplus is False (since the camera is always "inside" and there are no infinely-far backgrounds).

Making the mapping function workable under the inside-out configuration.

As for VolSDF, it should be directly workable.
As for UNISURF, some ray-intersection mechanisms should be altered by some flags.
As for NeuS, some signs should be reversed when mapping sdf to alpha.

Some of the setup needs hard-coded modifications right now if you want to proceed. I will do some experiments and release changes so that everything is done simply adding some configs like model: inside_out: True in a few days, if that's needed :)


Large image size?

I might be doing it wrong here but after building both alpine-haskell-gmp and alpine-haskell-simple on my machine, the result images are quite larger than a standard image built on top of debian. Built images when I bump the base image to alpine:3.10.1 and stack to 2.1.3:
alpine-haskell-simple  8.6.5            8085be6b0318  1.98GB
alpine-haskell-simple  build-tooling    deb0f50d9977  151MB
alpine-haskell-simple  build-ghc-8.6.5  7f740dc48330  2.98GB
alpine-haskell-simple  base             2eedfb0ac8eb  121MB

alpine-haskell-gmp     8.6.5            38f62343dd94  1.98GB
alpine-haskell-gmp     build-tooling    a08d1803194e  153MB
alpine-haskell-gmp     build-ghc-8.6.5  e8257ef09cdf  2.98GB
alpine-haskell-gmp     base             bc0ba3d8334f  122MB

Removing cabal-install and bumping stack to 2.1.3 from this Dockerfile yields an 1.15GB image. The gap between the compressed versions isn't as bad but shouldn't we expect a better size for images built on top of alpine?
Thank you again for a good reference! This is just a question out of curiosity.

These images are, unfortunately, going to be quite large as they're going to include the development and compilation environment you need to produce Haskell applications under Alpine.
The intended purpose here is not for you to ship applications that run in these images, but for you to use these images as a "builder" for a multi-stage docker build. That way you can make your final step something like:
FROM alpine-haskell-gmp:8.6.5 as builder
RUN <install OS dependencies>
RUN <build application>

FROM alpine:3.9
COPY --from=builder <path/to/application>
RUN <install OS dependencies>
ENTRYPOINT [<run app>]

In this case, the final image should be quite small (it should just be the Alpine image + OS dependencies + your Haskell application.
Does this make sense?

Thanks for the clarification and yes, it does make sense.
I think our problem is that we're having 7 different Haskell services that need dev images with things like hot-reload included so the dev images are even more important at the moment. On top of debian, our compressed prod images are still only 50MB-75MB with dev images going up to over 850MB (Over 4GB uncompressed). Adding an extra uncompressed 800MB for each dev images would be very scary.
Now that I've got your confirmation, I think we can try developing on top of debian and testing, shipping a version on top of alpine in the future. We would need to scale a ton more to make the differences and extra mismatch worth it though.
Thanks again for your time, this issue should be closed now!

Thanks for the extra info!
I'm hopeful that future versions of GHC will ship with a binary distribution that targets Alpine, which would obviate a lot of this work, so hopefully by the time you've scaled up this shouldn't be necessary at all 😄


Query for last values outside time range

Fixes #139.
This requires the changes in https://github.com/grafana/grafana/pull/59444

The is the same query in Grafana 9.3.0 (without the changes in https://github.com/grafana/grafana/pull/59444)

@toddtreece Which version this be available and when ?

@toddtreece Correct me if I'm wrong, but @kkmeghan should be able to consume the changes which are now all merged (as mentioned here), and use the latest SiteWise release to test this out.

@taleena @kkmeghan this is available in 1.5.0 of the sitewise plugin. it will require using the grafana/grafana:main docker image, or building grafana locally since it's dependent on changes in grafana that have not been released yet.


Suggestion: add choice of models to switch to

Not entirely sure where to put tho can be added in the main list of actions that is invoked with :Gen
or can be added to just README as a suggestion for people to use if they want to conveniently switch
to different models for a given :Gen invocation. What do you think?
this is how I use it for myself:
local changeModel = function()
  -- take the first column of the output of ollama list after header row and trim whitespace
  -- so that systemlist returns a valid list of models
  local list = vim.fn.systemlist("ollama list | awk 'NR>1' | cut -f1 | tr -d ' '")

  vim.ui.select(list, { prompt = "Select a model: " }, function(selected)
    if selected == nil then
      return
    end

    require("gen").model = selected
    print("Model set to " .. selected)
  end)
end

return {
  "David-Kunz/gen.nvim",
  keys = {
    { "<leader>ai", ":Gen<CR>", mode = { "n", "v", "x" }, desc = "Local [AI]: Menu" },
    { "<leader>am", changeModel, mode = { "n" }, desc = "Local [AI]: Change Model" },
  },
  opts = {
    display_mode = "float",
    show_model = true,
    no_serve = true,
    debugCommand = true,
  },
}

@David-Kunz  I see the commit, epic thank you!

Hi @kapral18 ,
Thanks for the suggestion and code, I've implemented it in https://github.com/David-Kunz/gen.nvim/pull/44
Best regards,
David

Ha, you were faster 😄


Factor ConfigData out of ConfigContainer

Just pure refactoring.
The only noteworthy point is introduction of expected-lite. This adds a nonstd::expected type which is very similar to Rust's Result. Rust doesn't have exceptions, so replacing them with expected would be a prerequisite for porting.
I don't plan to port ConfigData to Rust right now because I still want to make a couple changes in this area. One of them I'll probably fit in before 2.20 release, but the other one is more risky, so I'll hold it off until after the release -- it'll get more "beta-testing" that way.
Reviews are welcome! Will merge in three days.

Coverage increased (+0.08%) to 57.135% when pulling 9eb119e389012694a39a7f5db036b519483236ef on feature/factor-out-configdata into d481c9c88a3de16bc106bebe609e921fa98a095c on master.


ion-datetime not showing months properly

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ ] 3.x
[x] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
It's simple, when using
<ion-datetime min="2017-11-24" max="2020-12-31"></ion-datetime>
control (please note the min value, the max value doesn't needs to be 2020-12-31 but needs to be at least 2 years in the future) and you tap over the control, if you change the "year" value first to "2018" the months doesn't change to "January, February, ...", they still the same as the min date value (in this case, November and December).
If you change the year to 2019 (after changing to 2018) then you'll notice that Months values changes. This bug is only happening the first time you change the year without closing the control.
NOTE: To replicate it, please don't change the day or month before changing the year value.
Expected behavior:
Change the months to "January, February, ..." when you change the year.
Steps to reproduce:

Create a new Ionic project with the specified version (see Ionic version below)
In your first Page put the specified above
Tap over the control (see the pop up showing in screen to change the values)
Change the year from 2017 to 2018
See the Month values not changing properly (they still in November, December)
Change the year again, but this time to 2019 and you'll see the Month values changing properly good

Related code:
<ion-header>
  <ion-navbar color="primary">
    <ion-title>Request</ion-title>
  </ion-navbar>
</ion-header>

<ion-content no-padding>
  <ion-list>
    <ion-item-divider text-wrap>Please enter a date</ion-item-divider>
    <ion-item>
      <ion-label>Request date</ion-label>
      <ion-datetime displayFormat="MMMM D, YYYY"
                    min="2017-11-24"
                    max="2020-12-31"
                    [(ngModel)]="requestDate">
      </ion-datetime>
    </ion-item>
  </ion-list>
</ion-content>

Above code is all the HTML Code I have (don't need more than this). In the Controller I just have the "requestDate" value set as "2017-11-24".
Other information:
No more info
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
This is my Ionic info
cli packages: (C:\Users\Juan J. Adan\Projects\ExampleProject\node_modules)

    @ionic/cli-utils  : 1.7.0
    ionic (Ionic CLI) : 3.7.0

global packages:

    Cordova CLI : 7.0.1

local packages:

    @ionic/app-scripts              : 2.0.2
    @ionic/cli-plugin-cordova       : 1.4.1
    @ionic/cli-plugin-ionic-angular : 1.3.2
    Cordova Platforms               : ios 4.4.0
    Ionic Framework                 : ionic-angular 3.5.3

System:

    Node : v6.11.3
    OS   : Windows 10
    npm  : 3.10.10

Thank you!

I just read your bug report, i haven't noticed any similar behavior.
You need to use ISO date string. new Date(date.toDateString() + ' UTC').toISOString()

Hello! Thank you for opening an issue with us! I was able to duplicate your issue and verify it is a duplicate Issue #12319 as @fssrepository pointed out, so I will close this one. Please track issue #12319 for further updates. Also please comment on that issue with any new information you may have to share.
@fssrepository - not sure what you are getting at with the ISO date but. The OP seems to be using ISO dates (just w/o the time, which is perfectly valid) everywhere from what I can see. More clarification may be needed.
Thank you for using Ionic


(FACT-1186) Update sparc pre-suite for solaris 11

This commit adds a package removal command for solaris 11, which
is not the same command as solaris 10.

Can this be handled in the jenkins job instead? I'd hate to have to do this in facter, hiera, puppet, ...

@joshcooper that would be AWESOME.
@justinstoller do you have suggestions how to wire this up in Jenkins (ala AIX LPAR reset)? I can take your response offline.

My understanding (per discussion in RE-5506) was that preparing non pooler platforms for testing and packaging was being abstracted away from the CI system via the pre-suite and vanagon.

This seems like a great task for a shared library of helpers that gets called. That way there is a single place to update and a small surface area that simply calls those helpers in each project/job.
I would recommend, if these steps require running Beaker, to put this into a Beaker DSL helper library (akin to what @kevpl has create at https://github.com/puppetlabs/beaker-template and has worked with @er0ck to pull out https://github.com/puppetlabs/beaker-hiera/). The pre-suite could call a generic prepare_host() type method and pass in the host in particular, and then the helper could contain the logic for doing this kind of thing.
This approach would allow to start with managing SPARC clean up, but could become a useful library in to reduce the shared setup code between the client projects.
An alternative would be to create a rake task akin to rake ci:test_against_preserved_hosts, which could be ran prior to the test rake task and could be packaged into a similar gem without the Beaker library template.

Since this is about uninstalling a package from a host, I think that Beaker's host abstraction would be the correct place to put general package removal details.
To @justinstoller's idea, it seems that if we put this into beaker-facter (in progress, woot @er0ck!), we would have to copy it into other Beaker libraries as well, just like @joshcooper was referring to above.
My opinion is that the work here should be done just to find the name of the package, and then host.uninstall_package should be used.  It looks like this does have support for solaris 10 & 11.  Is that not working in your testing, or has this avenue not come up in testing this so far?
Let me know if you have any questions about this, or reasons that this won't be a good approach, and hopefully we'll get it settled down and in soon.

Just to clarify, my idea wasn't to move this to a per-component helper library (I was just using those as an example of what a DSL helper library is). I was thinking more of a helper library that would eventually be a place where we could split out the foss_utils DSL code in Beaker, combine it with the copy-pasta'd acceptance/lib/puppet/acceptance/install_utils.rb in each component, and put things like this in there, so each component can just call an entry method, and as the processes to install puppet-agent components evolve those changes only have to go to one place.
That's not a requirement for this work, but a direction I think things are going in. I was just trying to say that we could begin heading in that direction with this. It does seem like utilizing the Beaker Host abstraction is probably the simplest solution to this problem.

On Wed, Sep 30, 2015 at 7:41 AM, Justin Stoller<EMAIL_ADDRESS>wrote:

My understanding (per discussion in RE-5506) was that preparing non pooler
platforms for testing and packaging was being abstracted away from the CI
system via the pre-suite and vanagon.

My apologies if I misunderstood or misrepresented the item of platform
preparation.
My understanding was that Beaker, and therefore, the CI testing jobs would
not be concerned with with preparation. We are realizing this by using the
"none" hypervisor. However, I was under the impression that a Jenkins job
for preparing the non pooler platforms would still be required as part of
the process. For example, we have an AIX LPAR reset job. I presumed that an
analogous job for SPARC would be needed when OPS finished creating zones
that could be rolled back. (https://tickets.puppetlabs.com/browse/OPS-6972).
I am not assuming that the pipeline is responsible for including the
'preparation' jobs. This would be the responsibility of the tester to run
these as needed prior to executing the manual pipeline.
In other words, the workflow would look like.

Tester kicks off 'preparation' job for non pooler platform. (e.g.
http://jenkins-compose.delivery.puppetlabs.net/view/Build AIX/job/AIX_Revert_LPAR(all_HOSTS)/
)
After successful completion of the 'preparation' job, the tester kicks
off the AIO manual pipeline for that platform. (e.g.
https://jenkins.puppetlabs.com/view/All in One Agent/view/Manual/view/Puppet Agent Manual (stable)/
)

I don't think anyone wants a bunch of duplication, whether it is having to
duplicate the code between puppet, facter, and hiera pre-suites by the
Client team or a bunch of jenkins jobs by the QE team.
This seems like a great task for a shared library of helpers that gets
called. That way there is a single place to update and a small surface area
that simply calls those helpers in each project/job.
I would recommend, if these steps require running Beaker, to put this into
a Beaker DSL helper library (akin to what @kevpl
https://github.com/kevpl has create at
https://github.com/puppetlabs/beaker-template and has worked with @er0ck
https://github.com/er0ck to pull out
https://github.com/puppetlabs/beaker-hiera/). The pre-suite could call a
generic prepare_host() type method and pass in the host in particular,
and then the helper could contain the logic for doing this kind of thing.
This approach would allow to start with managing SPARC clean up, but could
become a useful library in to reduce the shared setup code between the
client projects.

This clean-up step is really a stop-gap "preparation" step because we do
not yet have SPARC instances that we provision or roll back. So, I am
expecting it to be deleted within the next four weeks. However, even when
it is no longer necessary, we will still need a way to provision the SPARC
boxes. It seems like this should live outside of both the Beaker and
puppetlabs project code bases since it will be specific to our
infrastructure.

An alternative would be to create a rake task akin to rake
ci:test_against_preserved_hosts, which could be ran prior to the test
rake task and could be packaged into a similar gem without the Beaker
library template.
—
Reply to this email directly or view it on GitHub
https://github.com/puppetlabs/facter/pull/1182#issuecomment-144432738.

@joshcooper @justinstoller I will replace the changes here with a call to a new beaker helper to address this in a more agnostic manner. I will amend this PR with the updates.

@johnduarte Can you bump the minimum beaker dependency in the acceptance Gemfile (to a beaker version that supports the new method)?


SPF DNS record test fails if it encounters a CNAME?

Version: 1.2.1
It looks like the SPF DNS record is depreciated and should not exist test fails if it encounters a CNAME, such as when a subdomain lookup yields a CNAME response instead of A/AAAA records.
I would expect this to result in either an additional lookup, following the CNAME chain until it yields a definitive response, or to recognise it as the wrong answer, perhaps checking if it's properly formatted, such as starting with v=spf1 ?
Example: when testing 'www.ur.nl', it fails with the following error;
[FAIL] SPF DNS record is depreciated and should not exist (['apex.datatruckers.net.'])

The answer makes sense, since it is the CNAME record;
$ dig +short -t CNAME www.ur.nl
apex.datatruckers.net.

$ dig +short -t SPF www.ur.nl
apex.datatruckers.net.

$ dig +short -t SPF apex.datatruckers.net

Interesting one. Thanks for the report.
I have updated the check to filter to only SPF records. I wasn't aware that the CNAME record would be returned when quering for SPF records.
This passes for your domain now.
I've set up a test domain (subdomain-with-spf-record.b5n.sh) that has an SPF record to test the failure.
> python3 -m ready.ready subdomain-with-spf-record.b5n.sh --request-filter=dns --check-filter=spf
Domain: subdomain-with-spf-record.b5n.sh, Domain (no path): subdomain-with-spf-record.b5n.sh, First Level Domain: b5n.sh
[FAIL] SPF DNS record is depreciated and should not exist (['"v=spf1 -all"'])

I don't mind the idea of following the CNAME chain but it's probably slightly out of scope for this check. Someone using this tool could manually check their CNAME domain for the bad SPF record.
FYI - the other SPF checks do recursively follow includes.

Just noticed a typo in this check, by the way; 'depreciated' != 'deprecated'. Shall I file this as a separate issue?

Ooops. That's a typo / mistake that haunts me for some reason. Whenever I go to type deprecated, depreciated comes out if I'm not careful.

Yeah, it's sneaky one 😄


Fix clippy lints

This PR is based on #30 (after #30 has been merged I will rebase this PR on master)

Any progress on this?

Any progress on this?


[Live] Update the Max bid UI to use a scroller instead of steppers

From https://github.com/artsy/eigen/issues/1102

And we've come full circle in this issue, back we go to the scrolly picker!

I'm going to guess that getting this in would be a stretch for 2.6.1?

@ashfurrow Has this UI component been made before?

Not that I'm aware of.

#1737

done for now. Individual updates will be tackled with new issues/epics


Look into updating Pehkui dependency to avoid JitPack issues

Pehkui 3.6.0 seems to periodically disappear from JitPack for some reason. Newer versions (at least 3.6.1) don't seem to have this issue, so maybe we could just update the dependency version?
See also: https://github.com/Virtuoel/Pehkui/issues/497

We recently had this issue with a newer version as well. I think it's just a JitPack issue, not specifically with this dependency version.


[xds]: export discoveryReq/Resp resource count, payload size metrics to help understand network bandwidth cost of control plane.

Title: export discoveryReq/Resp resource count, payload size metrics to help understand network bandwidth cost of control plane.
Description:
export discoveryReq/Resp resource count, payload size metrics to help understand network bandwidth cost of control plane.
Metrics could be:
Per request/response resource{added, removed} count,
Raw protobuf config size
this way we can better understand the config plane network cost as well as data serialization/deserialization cost.
[optional Relevant Links:]

Any extra documentation required to understand the issue.

@AndresGuedez @adisuissa @htuch

eh, @wbpcode @adisuissa I think we want to give this a shot?

I would like to look into this, if no one else is working on it.


termsrv.dll 10.0.19041.84

Hi, attached the current termsrv.dll from the 05 2020 update which has been released in previews now
may someone can figure out how to get it working again ;)
termsrv.zip

Same situation too.

Here's the additions to rdpwrap.ini for this version for 64bit only.
Make sure there's a blank link at the end of the file.
[10.0.19041.84]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=87611
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=0BF0C
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=17ED5
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1BDFC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.19041.84-SLInit]
bInitialized.x64      = 103FF8
bServerSku.x64        = 103FFC
lMaxUserSessions.x64  = 104000
bAppServerAllowed.x64 = 104008
bRemoteConnAllowed.x64= 104010
bMultimonAllowed.x64  = 104014
ulMaxDebugSessions.x64= 104018
bFUSEnabled.x64       = 10401C

Entire file
https://github.com/DrDrrae/rdpwrap/blob/72e6b9ec967d50c9e213fce65422099edceecc6e/res/rdpwrap.ini

@DrDrrae thank you very much

Okay RDPConf.exe was all that we needed.... your dll is covered here.

Duplicate of https://github.com/stascorp/rdpwrap/issues/1004


New package: F6CTE.MultiPSK version 4.48.2

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Closes #113521.
Tested and works fine.
The application gets installed into its default location (C:\MULTIPSK). This is intentional - it does not work properly when installed into C:\Program Files (x86)\MULTIPSK.
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116640&drop=dogfoodAlpha

https://github.com/microsoft/winget-pkgs/issues/107639


Added Few Changes in the CSS such as Background font weight etc

If you are adding a SoC/WoC, please make sure

[ ] You have added the SoC/WoC in README.md file in correct table
[ ] You have added the SoC/WoC in index.html in correct table
[ ] ensure Website is tested on a deployment and looks okay

If you are fixing an issue please add

[ ] fixes issue #issue_number to PR description

This repository is not being maintained its owners anymore
Kindly redirect your pull request s to this repository https://github.com/deepanshu1422/List-Of-Open-Source-Internships-Programs


accessibility: add for atribut on ion-label and id on ion-input for correct display with VoiceOver

Hello,
To move from text field to text field in a form, VoiceOver has a function in the action rotor.
If I use a traditional ion-label and a traditional ion-input, there is no connection with rotor action navigation.
In html, so that VoiceOver can have the correct label for a text field, I will do:
 Name

How to do with ionic to add the for attribute to the ion-label tag, and an id corresponding to ion-input?
Thank you

Example html code :
<label for="name">Your name</label>
<input id="name" name="name" type="text">``

Thanks for the issue. Ionic Framework should link the label and input automatically:
<ion-item>
  <ion-label>Message Label</ion-label>
  <ion-input placeholder="Type a message"></ion-input>
</ion-item>

Can you please provide steps to reproduce the issue you are experiencing?

Precisely, if I do not want to add a placeholder, to avoid giving a double labeling of the field for users who do not move in the form with the actions rotor, this creates a disturbance for those who navigate with the rotor.
It should be understood that VoiceOver users can read a form in two different ways in the way of navigation.
The placeholder is good for those who move with the rotor, but it gives double labeling for the other way to navigate.
Conversely, if I don't put a placeholder, I disturb the users who navigate with the actions rotor.
The common solution for all navigation modes is the for attribute on ion-label, and the id attribute on ion-input, as recommended by aria.
I know it is not easy to understand. Do you think this optimization can be done?

Sorry, my code was confusing. The placeholder is not what links the two components. The linked label in this case is Message Label. Does the rotor not work when you do:
<ion-item>
  <ion-label>Message Label</ion-label>
  <ion-input></ion-input>
</ion-item>

The rotor works, the text field label is not offered.
VoiceOver changes fields but does not state the ion-label.
The user therefore does not know what value to write.

As I mentioned previously, some steps to reproduce or a full code reproduction of the issue would be very helpful. I am not familiar with the VoiceOver rotor -- everything appears to be working fine for me.


Add API endpoint for fetching all investment and service deliveries

Description of change
Adds a new API endpoint (/v4/dataset/service-deliveries-and-interactions-dataset) under the datasets app and associated tests.
Checklist

[x] Has a new newsfragment been created? Check changelog/README.rst for instructions
[x] Do any added or updated endpoints appear in the API documentation? See docs/Maintaining the API documentation.md for more details
[ ] Have any relevant search models been updated?
[ ] Have any relevant fixtures (fixtures/test_data.yaml) been updated?
[ ] Have any relevant select-/prefetch-related field lists in the views and search apps been updated?
[ ] Has the admin site been updated (for new models, fields etc.)?
[ ] Has the README been updated (if needed)?

@niross The title of the PR and the commit message mention 'investment', did you mean 'interactions'?

@niross The title of the PR and the commit message mention 'investment', did you mean 'interactions'?

Yeah, trying to do too many things at once. Thanks


deps: Update chroma

Updating chroma module to head to include some new language support added in chroma. Tried removing unused parts from go.sum but v0.7.0/go.mod gets re-added but seems to get added back when I run go test ./... and I'm not sure why.
Saw hugo does allow for packages to be referenced in between releases, but not sure if there is any other criteria.

This needs to be a tagged release.


[lit-html-server] Fix memory leak when handling result of unsafeHTML/unsafeSVG directives

Repeatedly rendering a template containing an unsafeHTML/unsafeSVG directive caused the templateCache to grow without limit. The templateCache is keyed on the unique and static TemplateStringsArray returned when calling a tagged template function. This strings array is guaranteed to be the same across invocations of the function, and therefore is a safe and performant way to cache Template instances by relying on referential identity.  Third-party directives should not do this.
return (this._templateResult = {
    // Cast to a known set of integers that satisfy ResultType so that we
    // don't have to export ResultType and possibly encourage this pattern.
    // This property needs to remain unminified.
    ['_$litType$']: this.constructor
        .resultType,
    strings,
    values: [],
});

This fix instead returns a Buffer of the string content to avoid Template processing altogether.
This fake TemplateResult technique is also used when handling innerHTML string content returned when rendering a custom element, and has been changed to ensure that the same strings array is returned each time.

Could you release an alpha branch that i can test within our application?

I just tested the compiled code and did a drop in into both our application (@janerikbr ) and the experiment.
This solves our problem thank you very much @popeindustries
Experiment with unsafe

Our App

It never crashes and the memory never surpases 40MB 👍🏽

Amazing!


Confusing to create REST with POST method

Hi, I'm writing a REST service with Flight. It seems promising. It's really good to use Flight for REST service with GET requests. But when it came to POST request, for example for a login function like this:
<?php
require 'flight/Flight.php';
require 'api.php';

Flight::route('POST /login', 'login');

Flight::start();
?>

Then in api.php I wrote this:
function login() {
	$username = $_POST['username'];
	$password = $_POST['password'];

	echo json_encode(array(
		"code"=>0,
		"message"=>"Succeed",
		"data"=>array(
			"username"=>$username,
			"realname"=>"Amri Shodiq"
		)
	));
}

It works somehow when the POST request came with complete data (username and password).
However, when I send only username, then we'll have:

500 Internal Server Error

Undefined index: password (8)

Which is true, because the password is not sent. But, I'd like to have my own request validation method, in order to give JSON formatted response like below.
{
  "code":1,
  "message":"Missing argument: password"
}

Is it possible? How to do that correctly? I don't see the documentation talking about how to deal with POST request in further detail.

That is not a Flight problem but a general PHP error. You're trying to access a key that doesn't exist so PHP is throwing an error. So you can either:

Disable strict error reporting in PHP
Or check if the key exists first using isset($_POST['password'])

Hi Mike,
Thnaks for the quick response.
Yes, I've implemented as you suggest.
I rewrote the code so I now have it like this:
function login() {
	$missingParameters = array();
	if (!isset($_POST['username'])) {
		array_push($missingParameters, 'username');
	}
	if (!isset($_POST['password'])) {
		array_push($missingParameters, 'password');
	}
	reportMissingParameters($missingParameters);

	$username = $_POST['username'];
	$password = $_POST['password'];

	Flight::json(array(
		"code"=>0,
		"message"=>"Succeed",
		"data"=>array(
			"username"=>$username,
			"realname"=>"Amri Shodiq"
		)
	));
}

function reportMissingParameters($missingParameters) {
	$parameters = implode(", ", $missingParameters);
	echo json_encode(array(
		"code"=>1,
		"message"=>"Missing parameter: ".$parameters.".",
		"data"=>null
	));
	exit();
}

It works very good. But somehow, I see this part:
	if (!isset($_POST['username'])) {
		array_push($missingParameters, 'username');
	}
	if (!isset($_POST['password'])) {
		array_push($missingParameters, 'password');
	}

is a bit clumsy. It should be better written with code like this:
function validateEmptiness($varArray) {
	foreach ($varArray as $value) {
		if (!isset($value) || $value == null) {
			return false;
		}
	}
	return true;
}

Then, I tested with the same condition I send POST request with username parameter but without password parameter. And the result is:

500 Internal Server Error

Undefined index: password (8)

#0 /Users/amrishodiq/Sites/existing/api.php(6): flight\Engine->handleError(8, 'Undefined index...', '/Users/amrishod...', 6, Array)
#1 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(160): login()
#2 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(143): flight\core\Dispatcher::callFunction('login', Array)
#3 /Users/amrishodiq/Sites/existing/flight/Engine.php(312): flight\core\Dispatcher::execute('login', Array)
#4 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->_start()
#5 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(142): flight\core\Dispatcher::invokeMethod(Array, Array)
#6 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(48): flight\core\Dispatcher::execute(Array, Array)
#7 /Users/amrishodiq/Sites/existing/flight/Engine.php(64): flight\core\Dispatcher->run('start', Array)
#8 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->__call('start', Array)
#9 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->start()
#10 /Users/amrishodiq/Sites/existing/flight/Flight.php(65): flight\core\Dispatcher::invokeMethod(Array, Array)
#11 /Users/amrishodiq/Sites/existing/index.php(10): Flight::__callStatic('start', Array)
#12 /Users/amrishodiq/Sites/existing/index.php(10): Flight::start()
#13 {main}

So, in this time I cancel the last step and make a note. I hope I would have a time to dig deeper.
I'll need to find out a way to escape from Flight's Dispatcher's callFunction method.
Thanks Mike Cao for your support.

These are PHP questions, not Flight questions. Your json encode function is
still tring to encode a variable that dosnt exists.
$something=reportMissingParameters($missingParameters);

Check if there is something in $something. If so, give a different
response, and don't call this:
$username = $_POST['username'];
$password = $_POST['password'];

On Sep 28, 2015 7:20 PM, "Amri Shodiq"<EMAIL_ADDRESS>wrote:

Hi Mike,
Thnaks for the quick response.
Yes, I've implemented as you suggest.
I rewrote the code so I now have it like this:
function login() {
$missingParameters = array();
if (!isset($_POST['username'])) {
array_push($missingParameters, 'username');
}
if (!isset($_POST['password'])) {
array_push($missingParameters, 'password');
}
reportMissingParameters($missingParameters);
$username = $_POST['username'];
$password = $_POST['password'];

Flight::json(array(
    "code"=>0,
    "message"=>"Succeed",
    "data"=>array(
        "username"=>$username,
        "realname"=>"Amri Shodiq"
    )
));

}
function reportMissingParameters($missingParameters) {
$parameters = implode(", ", $missingParameters);
echo json_encode(array(
"code"=>1,
"message"=>"Missing parameter: ".$parameters.".",
"data"=>null
));
exit();
}
It works very good. But somehow, I see this part:
if (!isset($_POST['username'])) {
    array_push($missingParameters, 'username');
}
if (!isset($_POST['password'])) {
    array_push($missingParameters, 'password');
}

is a bit clumsy. It should be better written with code like this:
function validateEmptiness($varArray) {
foreach ($varArray as $value) {
if (!isset($value) || $value == null) {
return false;
}
}
return true;
}
Then, I tested with the same condition I send POST request with username
parameter but without password parameter. And the result is:
500 Internal Server Error
Undefined index: password (8)
#0 /Users/amrishodiq/Sites/existing/api.php(6): flight\Engine->handleError(8, 'Undefined index...', '/Users/amrishod...', 6, Array)
#1 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(160): login()
#2 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(143): flight\core\Dispatcher::callFunction('login', Array)
#3 /Users/amrishodiq/Sites/existing/flight/Engine.php(312): flight\core\Dispatcher::execute('login', Array)
#4 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->_start()
#5 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(142): flight\core\Dispatcher::invokeMethod(Array, Array)
#6 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(48): flight\core\Dispatcher::execute(Array, Array)
#7 /Users/amrishodiq/Sites/existing/flight/Engine.php(64): flight\core\Dispatcher->run('start', Array)
#8 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->__call('start', Array)
#9 /Users/amrishodiq/Sites/existing/flight/core/Dispatcher.php(191): flight\Engine->start()
#10 /Users/amrishodiq/Sites/existing/flight/Flight.php(65): flight\core\Dispatcher::invokeMethod(Array, Array)
#11 /Users/amrishodiq/Sites/existing/index.php(10): Flight::__callStatic('start', Array)
#12 /Users/amrishodiq/Sites/existing/index.php(10): Flight::start()
#13 {main}
So, in this time I cancel the last step and make a note. I hope I would
have a time to dig deeper.
I'll need to find out a way to escape from Flight's Dispatcher's
callFunction method.
Thanks Mike Cao for your support.
—
Reply to this email directly or view it on GitHub
https://github.com/mikecao/flight/issues/209#issuecomment-143899979.

Sorry I was having difficulty accesing Github lately.
Wll, Shaneshuford, I'm afraid you've confused by the code. exit() function in reportMissingParameters() make it stop there. So the json_encode will never reached.


KAFKA-16968: Make 3.8-IV0 a stable MetadataVersion and create 3.9-IV0

Make 3.8-IV0 a stable MetadataVersion

Move KIP-966 out of 3.8, reflecting the fact that it's not ready yet.

Create IBP_3_9_IV0.

Remove IBP_4_0_IV0 since we won't need it until 3.9 is stabilized.

cc @jlprat We need this on in 3.8.

Thanks @dajac! Let's get this to 3.8 once merged

@cmccabe @AndrewJSchofield @dajac , there is another PR adding a new metadata version of 3.8.IV1(it will be the next production ready MV), it also tries to move KIP-966 from 3.8IV0 to 4.0IV0. https://github.com/apache/kafka/pull/15673/files
The PR has been modified for quite some time, If we want to make KIP-966 to 3.9IV0, I can do it in a separate PR.

@cmccabe @AndrewJSchofield @dajac , there is another PR adding a new metadata version of 3.8.IV1(it will be the next production ready MV), it also tries to move KIP-966 from 3.8IV0 to 4.0IV0. https://github.com/apache/kafka/pull/15673/files
The PR has been modified for quite some time, If we want to make KIP-966 to 3.9IV0, I can do it in a separate PR.

Thanks for pointing out this existing PR. As discussed on the mailnig list, 3.8 is done at this point. No new features are going into it. The changes from #15673 can be done in 3.9-IV0 once this PR creates it.

@cmccabe : https://github.com/apache/kafka/pull/15673 is fixing a mistake that shouldn't be in 3.8.0. We should have bumped up the API version for ListOffset, but we didn't. To me, that seems a blocker for 3.8.0, right?

hi @junrao I marked https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-16480 as a blocker for 3.8

@cmccabe : https://github.com/apache/kafka/pull/15673 is fixing a mistake that shouldn't be in 3.8.0. We should have bumped up the API version for ListOffset, but we didn't. To me, that seems a blocker for 3.8.0, right?

The discussion thread here seems to suggest that #15673 is adding a new feature.:

@junrao : To let the AdminClient use this, we need to add a new type of OffsetSpec and a way to set oldestAllowedVersion in ListOffsetsRequest.Build to version 9, right?
@clolov: Yes, correct, but I want to get this PR in before I move to that. I do not want to bunch all of these changes in the same PR

Additionally, the PR title is "KAFKA-16480: Bump ListOffsets version, IBP version and mark last version of ListOffsets as unstable #15673". But when I look at  clients/src/main/resources/common/message/ListOffsetsRequest.json in the PR, I do not see "latestVersionUnstable": true.
Maybe someone can explain more about what #15673 does exactly.

@dajac Just pushed

Maybe someone can explain more about what https://github.com/apache/kafka/pull/15673 does exactly.

@cmccabe : The main issue that https://github.com/apache/kafka/pull/15673 fixes
is described in https://issues.apache.org/jira/browse/KAFKA-16480.
https://issues.apache.org/jira/browse/KAFKA-16154 introduced the changes to the ListOffsets API to accept latest-tiered-timestamp and return the corresponding offset.

Those changes should have a) increased the version of the ListOffsets API b) increased the inter-broker protocol version c) hidden the latest version of the ListOffsets behind the latestVersionUnstable flag

So, let's hold off on merging this PR until we understand how to consolidate it with https://github.com/apache/kafka/pull/15673.

@junrao @clolov @dajac @jlprat : It seems like the client side of the KIP-1005 changes is not implemented. So I would propose we revert #15213 from 3.8 since the KIP is only half-complete, and feature freeze has come and gone. This will unblock the 3.8.0 release.
We can then retarget KIP-1005 at 3.9.0 as usual. As part of that, we can bump the ListOffsets version and mark the latest version of ListOffsets as unstable. This will all be in 3.9-IV0.
I'll update this PR in a moment with those changes

Hi @cmccabe

It seems like the client side of the KIP-1005 changes is not implemented. So I would propose we revert https://github.com/apache/kafka/pull/15213 from 3.8 since the KIP is only half-complete, and feature freeze has come and gone. This will unblock the 3.8.0 release.

Is this the accepted way forward to unlock the 3.8 release? If so, I'll prepare a revert PR.

@jlprat : In addition to reverting https://github.com/apache/kafka/pull/15213, it seems that we also need to change LATEST_PRODUCTION to 3.8 in 3.8.0 release.

@junrao I did both in this PR: https://github.com/apache/kafka/pull/16400
(reverting https://github.com/apache/kafka/pull/15213 and changing LATEST_PRODUCTION to IBP_3_8_IV0)

@jlprat : Is this the accepted way forward to unlock the 3.8 release? If so, I'll prepare a revert PR.

+1

@junrao : In addition to reverting https://github.com/apache/kafka/pull/15213, it seems that we also need to change LATEST_PRODUCTION to 3.8 in 3.8.0 release

Yes. We need to create IBP_3_8_IV0 and mark it as production in 3.8.

@cmccabe I did a change in the PR I mentioned above, but I guess I need changes in more places

@cmccabe Do we need to cherry-pick it to 3.8 branch too?

@dajac my understanding is that we wouldn't need to cherry pick this to 3.8 but rather have https://github.com/apache/kafka/pull/16400 instead.

My understanding is that we still need to create IBP_3_8_IV0 and to update LATEST_PRODUCTION in 3.8 branch. This is orthogonal to https://github.com/apache/kafka/pull/16400.

I added those commits to https://github.com/apache/kafka/pull/16400 as well

Ah, missed them. Then, we're all good. Thanks!

I decided to add both things in the same PR in an attempt to simplify blockers


Add ability to restrict namespaces being watched.

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] JIRA link(s): RHODS-2732
[x] The Jira story is acked
[x] An entry has been added to the latest build document in Build Announcements Folder.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious)

Testing:

Install rhods using https://gitlab.cee.redhat.com/data-hub/olminstall with catalogsource: quay.io/modh/rhods-operator-live-catalog:1.7.0-rhods-2732 from quay/modh/rhods-operator-live-catalog
Observe operator memory usage redhat-ods-operator using OpenShift "observe" dashboards
Make config changes in redhat-ods-applications, redhat-ods-operator and make sure the operator reacts appropriately (e.g. change replicas of deployment to 2 and watch it get reset by the operator).
Create 1000+ namespaces

for i in {1..1000}
do
   oc create ns dummyns${i}
done

Memory should not increase with namespaces
5. Uninstall rhods using the proper managed-odh config map with labels api.openshift.com/addon-managed-odh-delete: 'true'

/retest

/retest

@LaVLaS Can you let me know if you see a CI issue while you're reviewing?

/retest

@cfchase I tested the given live build on PSI cluster. I think we are accessing some cluster-wide resources, specifically https://github.com/red-hat-data-services/opendatahub-operator/blob/master/pkg/controller/kfdef/kfdef_controller.go#L613, limiting the scope might throw errors causing the controller to reconcile during uninstall.

The functionality is there, but I'm noticing weird behavior during uninstall. The redhat-ods-operator namespace (and contents) is sticking around... somehow

The functionality is there, but I'm noticing weird behavior during uninstall. The redhat-ods-operator namespace (and contents) is sticking around... somehow.
This is on OSD.

The probable cause for this might be that we are limiting the permissions for deleting the csv. As part of last step of uninstallation, we remove csv that is a requirement for addon deletion.

yeah, not looking good for this approach.  Will have to look a different method.  Unless I figure something out, I'll probably close this PR

@cfchase I tested the given live build on PSI cluster. I think we are accessing some cluster-wide resources, specifically https://github.com/red-hat-data-services/opendatahub-operator/blob/master/pkg/controller/kfdef/kfdef_controller.go#L613, limiting the scope might throw errors causing the controller to reconcile during uninstall.

Turns out this was the root cause, the CSV permissions worked.  That means the overall solution should work if we fix this.

Updated and retested on OSIA and OSD
@VaishnaviHire @LaVLaS @crobby ready for re-review
@LaVLaS anything I can do about the CI failures?
@anishasthana updated live build and ready for retest

@cfchase I tested the given live build on PSI cluster. I think we are accessing some cluster-wide resources, specifically https://github.com/red-hat-data-services/opendatahub-operator/blob/master/pkg/controller/kfdef/kfdef_controller.go#L613, limiting the scope might throw errors causing the controller to reconcile during uninstall.

Turns out this was the root cause, the CSV permissions worked. That means the overall solution should work if we fix this.

Looking at the last code update.  We just stripped out the part that dealt with certmanager?  Was it unnecessary code to start with?


Rotation does not work at all.

Using context.rotate will cause any attempts to draw to the canvas to result in nothing being drawn. Even doing context.rotate(0), which should do nothing, results in this.

Nevermind, I accidentally changed some code and forgot to change it back which resulted in nothing being drawn to the image.


Copy Path Shortcut

Issue Type: Bug
Keyboars Shortcut for Copy Path (Shift+Alt+C) doesn't any thing

VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz (6 x 3000)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.83GB (1.14GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

al-code-outline
and
1.0.48

vscode-eslint
dba
2.1.5

open-files
Div
0.0.4

macros
ged
1.2.1

gc-excelviewer
Gra
2.1.35

diff-tool
jin
0.0.1

vscode-smart-column-indenter
lmc
0.0.13

rainbow-csv
mec
1.7.0

remote-wsl
ms-
0.44.2

cpptools
ms-
0.28.2

vscode-typescript-tslint-plugin
ms-
1.2.3

vscode-react-native
msj
0.16.0

crs-al-language-extension
wal
1.2.4

@jockrow your screenshot is the context menu from a tab, right?
The corresponding entry in my Keyboard Shortcuts list has a !editorFocus when-clause:

I think that'll be why your clipboard content doesn't change when you type Shift+Alt+C
/confirmed

/confirm

Needs more info.

@jockrow your screenshot is the context menu from a tab, right?
The corresponding entry in my Keyboard Shortcuts list has a !editorFocus when-clause:

I think that'll be why your clipboard content doesn't change when you type Shift+Alt+C
/confirmed

Yes my screenshot is context menu from a tab, and I have same !editorFocus that you

Needs more info.

What info do you need?

How to reproduce the issue?

How to reproduce the issue?

I clicked any side in Text Editor from file that I want copy Path
I Pressed Shift+Alt+C
Result: not copy path :(

It should work if you configure this as keybindings:
{
	"key": "shift+alt+c",
	"command": "copyFilePath"
}


RemoveBasePathMiddleware to run mezzio application within a subdirectory

Feature Request

Q
A

New Feature
yes

RFC
no

BC Break
no

Summary

In mezzio/mezzio#69, the author requested a built-in feature for mezzio to allow the application be stored in a sub-directory.
This brings several issues, as the router and all tooling around it uses the incoming request path to match routes. So either, the routes are provided with the sub-directory in-place or something will interact with the request and removes the pre-configured base path (subdirectory) from the incoming request.
I've scribbled down my idea to do this during runtime in case someone does not have access to the webserver configuration and thus cannot add any rewrite rules to it.
WARNING: It is highly recommended to use the webservers configuration to ensure proper document roots and to block access to vendor/, config/, data/, e.g. directories!
final class RemoveBasePathMiddleware implements MiddlewareInterface
{
    private string $basePath;

    public function __construct(string $basePath)
    {
        $this->basePath = $basePath;
    }

    public function process(ServerRequestInterface $request, RequestHandlerInterface $handler): ResponseInterface
    {
        return $handler->handle($this->removeBasePathFromRequest($request));
    }

    private function removeBasePathFromRequest(ServerRequestInterface $request): ServerRequestInterface
    {
        $uri = $request->getUri();
        return $request->withUri(
            $uri->withPath(
                (string) \preg_replace(sprintf('!^%s!', $this->basePath), '', $uri->getPath())
            )
        );
    }
}

I think this middleware could be part of this package and thus adding the feature request here.

When we have this middleware in-place, @froschdesign brought up the idea to integrate a new installation step to the mezzio-skeleton. To make this an easy installation step, we might provide a laminas-cli command in here (or in the mezzio-tooling component, but I prefer to have it in the same component as the middleware itself), so it can be easily activated/deactivated. Thanks for that amazing idea, Frank!

There's one other aspect to this: it affects URL generation (e.g., via the UrlHelper)! We would also need "base path" integration in the UrlHelper to ensure that the base path is prepended to any generated URLs.

Ah, good catch!


can't crosscompile tensorflow lite c library using camke

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.17.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04.4 LTS
Mobile device
No response
Python version
No response
Bazel version
cmake version 3.22.1
GCC/compiler version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I need to use the tflite c library in a beaglebone black rev3 with this specs:
processor       : 0
model name      : ARMv7 Processor rev 2 (v7l)
BogoMIPS        : 995.32
Features        : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x3
CPU part        : 0xc08
CPU revision    : 2

Hardware        : Generic AM33XX (Flattened Device Tree)
Revision        : 0000
Serial          : 2218SBB15982
ldd (Debian GLIBC 2.28-10) 2.28
gcc version 8.3.0

i'm trying to build the library using this toolchain : gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
so like this tutto https://www.tensorflow.org/lite/guide/build_cmake_arm i used this command first:
mkdir tflite_build
cd tflite_build
ARMCC_FLAGS="-march=armv7-a -mfpu=neon-vfpv3 -funsafe-math-optimizations -mfp16-format=ieee"
ARMCC_PREFIX=${HOME}/toolchains/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
cmake -DCMAKE_C_COMPILER=${ARMCC_PREFIX}gcc \
  -DCMAKE_CXX_COMPILER=${ARMCC_PREFIX}g++ \
  -DCMAKE_C_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_CXX_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
  -DCMAKE_SYSTEM_NAME=Linux \
  -DCMAKE_SYSTEM_PROCESSOR=armv7 \
  ../tensorflow/lite/

but then i have errors when i run cmake --build . -j
Standalone code to reproduce the issue
mkdir tflite_build
cd tflite_build
ARMCC_FLAGS="-march=armv7-a -mfpu=neon-vfpv3 -funsafe-math-optimizations -mfp16-format=ieee"
ARMCC_PREFIX=${HOME}/toolchains/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
cmake -DCMAKE_C_COMPILER=${ARMCC_PREFIX}gcc \
  -DCMAKE_CXX_COMPILER=${ARMCC_PREFIX}g++ \
  -DCMAKE_C_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_CXX_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
  -DCMAKE_SYSTEM_NAME=Linux \
  -DCMAKE_SYSTEM_PROCESSOR=armv7 \
  ../tensorflow/lite/
cmake --build . -j

Relevant log output
No response

And I just test using Ubuntu 16.04.7 LTS and cmake version 3.20.5 but same problem

@saad-koukous Could you ensure your toolchain includes the necessary libraries and headers for building TensorFlow Lite on ARMv7? Please share the exact error messages or relevant excerpts if possible.
Thank you!

Hi @sushreebarsa, thank you for your response.
I am using the same toolchain presented in this tutorial TensorFlow Lite Guide: Build with CMake for ARM for the ARMv7 case. Attached are the logs from the cmake --build . -j command.
logs.log

I tried building following your command on ubuntu 20.04.6, cmake version 3.16.3,  but i ran into the below error , can you please take a look @pkgoogle
[ 10%] Building C object _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-5x4c8-minmax-neonbf16-bfmlal.c.o
cd /home/sawantkumar/work/tensorflow/_deps/xnnpack-build && /root/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc -DEIGEN_MPL2_ONLY -DFXDIV_USE_INLINE_ASSEMBLY=0 -DNOMINMAX=1 -DPTHREADPOOL_NO_DEPRECATED_API=1 -DXNN_ENABLE_ARM_BF16=1 -DXNN_ENABLE_ARM_DOTPROD=1 -DXNN_ENABLE_ARM_FP16_SCALAR=1 -DXNN_ENABLE_ARM_FP16_VECTOR=1 -DXNN_ENABLE_ARM_I8MM=1 -DXNN_ENABLE_ASSEMBLY=1 -DXNN_ENABLE_AVX512AMX=0 -DXNN_ENABLE_AVX512FP16X=0 -DXNN_ENABLE_AVXVNNI=0 -DXNN_ENABLE_CPUINFO=1 -DXNN_ENABLE_DWCONV_MULTIPASS=0 -DXNN_ENABLE_GEMM_M_SPECIALIZATION=1 -DXNN_ENABLE_JIT=0 -DXNN_ENABLE_MEMOPT=1 -DXNN_ENABLE_RISCV_VECTOR=1 -DXNN_ENABLE_SPARSE=1 -DXNN_ENABLE_VSX=1 -I/home/sawantkumar/work/tensorflow/third_party/xla/third_party/tsl -I/home/sawantkumar/work/tensorflow/third_party/xla -I/home/sawantkumar/work/tensorflow/xnnpack/src -I/home/sawantkumar/work/tensorflow/pthreadpool-source/include -I/home/sawantkumar/work/tensorflow/FXdiv-source/include -I/home/sawantkumar/work/tensorflow/FP16-source/include  -funsafe-math-optimizations -O3 -DNDEBUG -fPIC   -Wno-psabi -O2 -pthread -std=c99  -fno-math-errno  -march=armv8.2-a+bf16  -o CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-5x4c8-minmax-neonbf16-bfmlal.c.o   -c /home/sawantkumar/work/tensorflow/xnnpack/src/bf16-gemm/gen/bf16-gemm-5x4c8-minmax-neonbf16-bfmlal.c
cc1: error: invalid feature modifier in ‘-march=armv8.2-a+bf16’
make[2]: *** [_deps/xnnpack-build/CMakeFiles/microkernels-all.dir/build.make:43564: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/src/bf16-gemm/gen/bf16-gemm-5x4c8-minmax-neonbf16-bfmlal.c.o] Error 1
make[2]: Leaving directory '/home/sawantkumar/work/tensorflow'
make[1]: *** [CMakeFiles/Makefile2:7194: _deps/xnnpack-build/CMakeFiles/microkernels-all.dir/all] Error 2
[ 10%] Linking CXX static library libabsl_string_view.a
cd /home/sawantkumar/work/tensorflow/_deps/abseil-cpp-build/absl/strings && /usr/bin/cmake -P CMakeFiles/absl_string_view.dir/cmake_clean_target.cmake
cd /home/sawantkumar/work/tensorflow/_deps/abseil-cpp-build/absl/strings && /usr/bin/cmake -E cmake_link_script CMakeFiles/absl_string_view.dir/link.txt --verbose=1
/root/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-ar qc libabsl_string_view.a  CMakeFiles/absl_string_view.dir/string_view.cc.o
/root/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-ranlib libabsl_string_view.a
make[2]: Leaving directory '/home/sawantkumar/work/tensorflow'
[ 10%] Built target absl_string_view
[ 10%] Linking CXX static library libabsl_malloc_internal.a
cd /home/sawantkumar/work/tensorflow/_deps/abseil-cpp-build/absl/base && /usr/bin/cmake -P CMakeFiles/absl_malloc_internal.dir/cmake_clean_target.cmake
cd /home/sawantkumar/work/tensorflow/_deps/abseil-cpp-build/absl/base && /usr/bin/cmake -E cmake_link_script CMakeFiles/absl_malloc_internal.dir/link.txt --verbose=1
/root/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-ar qc libabsl_malloc_internal.a  CMakeFiles/absl_malloc_internal.dir/internal/low_level_alloc.cc.o
/root/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-ranlib libabsl_malloc_internal.a
make[2]: Leaving directory '/home/sawantkumar/work/tensorflow'
[ 10%] Built target absl_malloc_internal
make[1]: Leaving directory '/home/sawantkumar/work/tensorflow'
make: *** [Makefile:133: all] Error 2

I ran into the same issue as @sawantkumar, I have tested on master, nightly, and r2.17:
complete reproduce steps:
Install toolchain:
curl -LO https://storage.googleapis.com/mirror.tensorflow.org/developer.arm.com/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz
mkdir -p ${HOME}/toolchains
tar xvf gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz -C ${HOME}/toolchains

Install flatc:
sudo apt-get install flatbuffers-compiler

Download tensorflow:
git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow
mkdir arm64_build
cd arm64_build

Build:
ARMCC_PREFIX=${HOME}/toolchains/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu/bin/aarch64-linux-gnu-
ARMCC_FLAGS="-funsafe-math-optimizations"
cmake -DCMAKE_C_COMPILER=${ARMCC_PREFIX}gcc \
  -DCMAKE_CXX_COMPILER=${ARMCC_PREFIX}g++ \
  -DCMAKE_C_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_CXX_FLAGS="${ARMCC_FLAGS}" \
  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
  -DCMAKE_SYSTEM_NAME=Linux \
  -DCMAKE_SYSTEM_PROCESSOR=aarch64 \
  -DTFLITE_HOST_TOOLS_DIR=/usr/bin \
  ../tensorflow/lite/
cmake --build . -j

Hi @terryheo, can you please take a look? Thanks.

Hi, @saad-koukous
Thanks for raising this issue. Are you aware of the migration to LiteRT? This transition is aimed at enhancing our project's capabilities and providing improved support and focus for our users. As we believe this issue is still relevant to LiteRT we are moving your issue there. Please follow progress here: https://github.com/google-ai-edge/LiteRT/issues/62
Let us know if you have any questions. Thanks.


instructions for installing near-shell on windows can be simplified for happy case

I did not follow the extra steps to resolve permissions instructions and just ran a npm install -g near-shell on a relatively clean windows. I think we can recommend that people try that, and move the other instructions to some sort of "common problems troubleshooting" section.

Also let's reorganize the content so that it's tabbed by OS (similar to how we do assemblyscript vs rust in other places)

Link?

Okay, I think you're talking about this link:
Did you use Windows Subsystem for Linux? Those instructions are specific to that.
If you didn't use WSL that's great news. I think we should wait to remove it from the docs until we have create-near-app working on Windows through this PR. That won't run at all on Windows, but will run on WSL. As create-near-app is our primary entry point to getting started with NEAR, I'd rather tell every Windows user to use WSL, as it does in the docs for shell. Would have been great to have it in the create-near-app instructions, but let's get that working on Windows.
Phew, that was a lot of words. TL;DR: let's keep it until we merge the PR mentioned, then pull that whole section talking about Windows and WSL.

Notes for future self:

test the experience on our docs.near.org for windows
update the steps for windows for any discrepancies

PR #155 fixes this :)


Selenium's speed control property is not exposed through the seleniumlibrary

Originally submitted to Google Code by masterco... on 29 Dec 2008

Selenium has the ability to control how fast scripts execute via a speed
property. It would be great to have this exposed in the Robot framework
selenium library.

Originally submitted to Google Code by @yanne on 15 Jan 2009

Fixed in r135

Originally submitted to Google Code by @yanne on 15 Jan 2009

The implemented keyword is Set Selenium Speed


Added integration with Amazon API Gateway + bug fix in _answer_relevance.py

Closed other PR.

Merge with latest changes
Added integration with Amazon API Gateway
fixed bug in _answer_relevance.py, caused by text empty or NaN in the cosine_sim calculation

Hey @brunopistone
Thank you so much for helping us improve ragas with your PR ❤
Now since it's Christmas and all we wanted to send you a postcard and a couple of stickers as our way of saying thank you for your contribution. If you are interested could you shoot an email at<EMAIL_ADDRESS>and I'll tell you more?
Cheers 🙂
Jithin


fix: handle duplicate groupby keys

CATEGORY
Choose one: bugfix
SUMMARY
In a bubble chart, when picking the same Series and Entity against postgres, pandas chokes on something related to having a duplicate column name (SELECT foo, foo FROM bar)

stacktrace:
Traceback (most recent call last):
  File "/Users/maximebeauchemin/code/superset/superset/connectors/sqla/models.py", line 999, in query
    df = self.database.get_df(sql, self.schema, mutator)
  File "/Users/maximebeauchemin/code/superset/superset/models/core.py", line 992, in get_df
    if v.type == numpy.object_ and needs_conversion(df[k]):
  File "/Users/maximebeauchemin/code/superset/superset/models/core.py", line 963, in needs_conversion
    return not df_series.empty and isinstance(df_series[0], (list, dict))
  File "/Users/maximebeauchemin/code/superset/env/lib/python3.6/site-packages/pandas/core/frame.py", line 2927, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/Users/maximebeauchemin/code/superset/env/lib/python3.6/site-packages/pandas/core/indexes/base.py", line 2657, in get_loc
    return self._engine.get_loc(key)
  File "pandas/_libs/index.pyx", line 108, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 127, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 142, in pandas._libs.index.IndexEngine._get_loc_duplicates
TypeError: '<' not supported between instances of 'str' and 'int'

This addresses the issue by preventing dups in selects/groupby altogether

TEST PLAN

Codecov Report

Merging #8658 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8658      +/-   ##
==========================================
+ Coverage   65.76%   65.76%   +<.01%
==========================================
  Files         482      482
  Lines       23824    23825       +1
  Branches     2594     2594
==========================================
+ Hits        15667    15668       +1
  Misses       7984     7984
  Partials      173      173

Impacted Files
Coverage Δ

superset/connectors/sqla/models.py
84.83% <100%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update acf0753...88b2eaa. Read the comment docs.

@etr2460 not sure on how Druid would handle it and cannot reproduce / test in the absence of access to a Druid cluster (we're working on getting access to one at Preset ATM).
One thing is sure, it's never good to allow for a duplicate groupby to a query. Let me test this with calculated metrics.

Can we push this forward as it addresses a bug?


implement cannon

implement cannons in vanilla n normal sm64js (mmo)

it's on the to do list

it's on the to do list


Support for URI field

Please describe the feature that you want to propose
Currently, there's no handling for the URI field in the configuration form.
The goal would be to have this field updated with the parameters specified in the configuration form.
Prerequisites

https://github.com/KaotoIO/kaoto-next/issues/296

and also the other way round. If a user enters the uri, then the corresponding form fields need to be updated. Alternatively we can think about making the URI a readonly value or hiding it fully (we need to ensure that we can configure everything in the form fields before doing this)

note that when creating a "new route", the uri field with path parameter is used. if we fill the value from property panel ,this value is ignored at runtime.

note that when creating a "new route", the uri field with path parameter is used. if we fill the value from property panel ,this value is ignored at runtime.

This is very good information @apupier, thanks for bringing this up, maybe we could signal this on the UI side as well, so the user could know it also and avoid the surprise.

The more I think about it my conclusion is that we should not stick to the discouraged way of configuring nodes via URI parameters. Instead we should stick to the new preferred way and specify them as parameters. That means we take whatever the user enters / pastes as uri but then remove everything and place it in the parameters section instead.


create-tamagui-app Module parse failed: Unexpected token error in NextTheme.js

Describe the bug
Without modifying anything in app.
When running yarn web  Module parse failed: Unexpected token error is shown in NextTheme.js
To Reproduce

Created an app via create-tamagui-app
Gave command yarn
Gave command yarn web
The following error is thrown

wait  - compiling...
error -<EMAIL_ADDRESS>Module parse failed: Unexpected token (135:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     };
|   }, [theme, forcedTheme, resolvedTheme, enableSystem]);
>   return <ThemeContext.Provider value={contextValue}>
|     <ThemeScript {...{
|       forcedTheme,

Wasn't able to replicate with a fresh install but pushed something that may help anyway d3701afa56dbab3a7bcffbdaa7f2669cd8f5daea / beta 67

Thanks for the reply.
Just created another from npx create-tamagui-app@latest and then yarn web
Now the error is
C:\Users\AhmedRana\Documents\Dev\playground\reactnative\my-app>yarn web
➤ YN0000: » @my/ui
➤ YN0000:  >-> jsx
wait  - compiling...
error - ../packages/app/provider/index.tsx
Module parse failed: Unexpected token (6:46)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import { TamaguiProviderProps } from '@my/ui'
|
> export function Provider({ children, ...rest }: TamaguiProviderProps) {
|   return (
|     <Tamagui.Provider disableInjectCSS defaultTheme="light" {...rest}>

I am trying this on windows 11


Feature Request: Perspective-specific next/prev buffer switch

At least I know, perspective doesn't have features that is like switch-to-next-buffer or switch-to-prev-buffer using specific perspective.
In detail, there is no simple way to change C-x <C-left> (switch-to-prev-buffer) to perspective-relative one.
For example, suppose that I have 2 perspective perspA and perspB, and there are 5 buffers  in perspA, and there are 7 buffers in perspB. In this case, I can't traverse my buffers only which are in perspA, and while traversing, all buffers of perspB will join to perspA and everything is messed up.
Could you add these features(next/prev) to this wonderful package?

I use these functions to achieve the same behaviour you are asking for:
(defun isr/persp-get-buffers-list ()
  "Get filtered list of buffers, sorted alphabetically."
  (sort
   (cl-remove-if '(lambda (b) (if (stringp b) (string-match "^\[* \]" b) t))
                 (mapcar 'buffer-name (persp-buffers persp-curr)))
   'string<))

(defun isr/persp-next-buffer ()
  "My own version of `next-buffer'. Don't show internal buffers."
  (interactive)
  (let ((buffername (buffer-name (current-buffer)))
        (bufferlist (isr/persp-get-buffers-list)))
    (switch-to-buffer (or (cadr (member buffername bufferlist)) (car bufferlist)))))

(defun isr/persp-previous-buffer ()
  "My own version of `next-buffer'. Don't show internal buffers"
  (interactive)
  (let ((buffername (buffer-name (current-buffer)))
        (bufferlist (reverse (isr/persp-get-buffers-list))))
    (switch-to-buffer (or (cadr (member buffername bufferlist)) (car bufferlist)))))

@inigoserna
Thx for you info! I will try it!
Why don't you send a PR?

IMO it's a personal customization, not something everyone could be interested in.

But it's useful to have, isn't it?

Well, I use it daily ;)

@inigoserna I mean, it's useful, so there's worth to send a PR with this feature, isn't it?

Looking for something like this myself, and the functions above seem to not be compatible with current versions of perspective.  I'm getting Symbol’s value as variable is void: persp-curr.

Closing this unless someone convinces me that Perspective-aware buffer switchers are inadequate, and that there's a reasonably simple implementation path.

I don't know if this is right, as this seems almost too easy, but I think I've achieved the desired behaviour using
  (defun +titi/persp-skip-buffers (window buff bury-or-kill)
    (not (persp-is-current-buffer buff)))
  (setq switch-to-prev-buffer-skip '+titi/persp-skip-buffers)

basically just forbidding the [previous|next]-buffer functions to switch to buffers that are not part of the current perspective. Doing this preserves the chronological order of last viewed buffers.
This conversation maybe predates the switch-to-prev-buffer-skip variable.

@titibandit Yeah, if I know correctly, it is introduced 27.1 or so, which comes after this issue. But anyway, thank you for providing the snippet!

Very nice! Thank you @titibandit.
I’m open to automatically setting switch-to-prev-buffer-skip when Perspective is activated on Emacs 27+, but it’s mildly annoying to do in a way that respects the user’s existing settings of switch-to-prev-buffer-skip. (I think the right way is to add a “customize” setting to opt out of setting switch-to-prev-buffer-skip, then save the user’s existing setting when persp-mode is turned on, and restore it when persp-mode is turned off.)

Oh I thought since this is a user setting, it should be, from the perspective (pun not intended) of this package, left alone and only hinted at in the Readme. But it's true that this behavior makes just so much more sense. Having it set automatically by persp-mode is a real improvement to the package I think.


Toolchain resolution breaks when default toolchain is overridden

Steps to reproduce:

Create build folder.
Run rustup override set nightly in it.
Try building the project.

Result:
CMake Error at /home/egeretto/XXX/build/_deps/corrosion-src/cmake/FindRust.cmake:166 (find_program):
  Could not find Rust_CARGO_CACHED using the following names: cargo
Call Stack (most recent call first):
  /home/egeretto/XXX/build/_deps/corrosion-src/cmake/Corrosion.cmake:11 (find_package)
  /home/egeretto/XXX/build/_deps/corrosion-src/CMakeLists.txt:39 (include)

Cause:
When running in a folder with an overridden toolchain, the output of rustup toolchain list --verbose looks like the following:
stable-x86_64-unknown-linux-gnu (default)	/home/egeretto/.rustup/toolchains/stable-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu (override)	/home/egeretto/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu

However, the following regex does not take the (override) into account:
https://github.com/AndrewGaspar/corrosion/blob/2e4c62c9f001487b485c2f8c923dba348607b41c/cmake/FindRust.cmake#L96

Thank you for pointing exactly to the line at issue! I should probably go look at exactly what rustup outputs for this command so I can see if there's anything else unexpected that it does.
I've been busy, but I'll try to fix this soonish. Happy to accept PRs, too.

Thank you for pointing exactly to the line at issue! I should probably go look at exactly what rustup outputs for this command so I can see if there's anything else unexpected that it does.
I've been busy, but I'll try to fix this soonish. Happy to accept PRs, too.


⚠ Bofrost.es has degraded performance

In 96c5f3c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1553 ms

Resolved: Bofrost.es performance has improved in d048c81 after 10 minutes.


Initialise EntityGubbins array fields as actual arrays

Coverage remained the same at 100.0% when pulling ae1081b1659333fe71ff0beb21b9d3a914c4418a on CyberiaResurrection:FixEntityGubbinsAssociations into 17395a8fa43bb206b6dc2096b59651c9c23596f8 on Algo-Web:master.

Coverage remained the same at 100.0% when pulling ae1081b1659333fe71ff0beb21b9d3a914c4418a on CyberiaResurrection:FixEntityGubbinsAssociations into 17395a8fa43bb206b6dc2096b59651c9c23596f8 on Algo-Web:master.


RotationX and rotationZ in the layer-browser example doesn't work

A main problem with layer rotations is defining the center point that the modelMatrix rotates around.

For layers using METER_OFFSET projection mode the layer specifies the center. Rotations should work for layers using this mode. Among the examples, I believe METER_OFFSET is currently only used by the PointCloudLayer example, the center point is the "anchor point" just below the floating sphere.

However, for LNG_LAT mode, the center point is 0, 0 in the partially projected mercator world coordinates, which is at one of the far corners of the world map, which makes no sense to the user. So even a tiny rotation angle with respect to such a distant center would move the layer out of view. So the example does not apply rotation to these layers.

A possible solution is to support a LNG_LAT_OFFSET mode where we can still specify coordinates in [lng, lat] but also a center point, and do a delta operation in the shader. Apart from helping the rotation case, there are interesting precision/performance implications of such a mode.

Naturally it is also possible to handle these things by increasing the number of operations in the shader. The current constraint has been that we want to do only a single matrix multiplication in the shader, and do all matrix premultiplications in the CPU. If we sent multiple matrices to the shader we could be more flexible, at the cost of some rendering performance.

From the library perspective it could be argued that this is an enhancement rather than a bug.
Still, I agree that the for the user of our main example it is quite confusing that these sliders don't do anything for most layers. So we might e.g. want to hide the sliders, or add a tool tip that explains what is going on.

Then, let's remove the sliders in the layer-browser example.

@shaojingli I believe you just commented out this code.


Git for Windows update 2.26.1 causing git-remote-keybase.exe to not work?

Issue
I recently just had Git for Windows update to 2.26.1 and I tried to clone/push to a keybase Git remote from an existing git repo. Kept saying error: failed to push some refs to ' keybase://private/user/repo_name'. I also tried creating the symlink to the git-remote-keybase.exe in the C:\Program Files\Git\cmd\ directory.
However, after symlinking it again, and cloning the repo instead of adding it as a remote to the existing repository, I was able to upload the repository to Keybase.
Version Information
Git for Windows Version
C:\Users\preda\Downloads
λ  git --version
git version 2.26.1.windows.1

Keybase Version
C:\Users\preda\Downloads
λ  C:\Users\preda\AppData\Local\Keybase\keybase.exe --version
keybase version 5.3.0-20200310141357+4f2689009b

Windows Information
C:\Users\preda\Downloads
λ  Get-ComputerInfo -Property "Windows*"

WindowsBuildLabEx              : 18362.1.amd64fre.19h1_release.190318-1202
WindowsCurrentVersion          : 6.3
WindowsEditionId               : Professional
WindowsInstallationType        : Client
WindowsInstallDateFromRegistry : 4/1/2020 12:11:31 AM
WindowsProductId               : 00330-80836-81775-AA897
WindowsProductName             : Windows 10 Pro
WindowsRegisteredOrganization  :
WindowsRegisteredOwner<EMAIL_ADDRESS>WindowsSystemRoot              : C:\Windows
WindowsVersion                 : 1909
WindowsUBR                     : 752

Same here.


Improve tests for Reify and UnzipFields

It depends on #570, so please review this one after that.
Added missing serialization tests for Reify and UnzipFields and modified Reify tests to use assertTypedEquals to ensure the reified values' singleton-ness.

LGTM. Many thanks ... merging! :-)


Error when table does not have a replica identity

When a table included in the referenced publication does not have a replica identity, pg_replicate crashes on start
-- Create a table with no replica identity
create table foo(
  id int,
  body text
);

create publication abc for table foo;
drop publication abc;

Test the stdout example
cargo run --example stdout -- \
  --db-host=db.<ref>.supabase.co \
  --db-port=5432 --db-name=postgres \
  --db-username=postgres \
  --db-password=<PW> \
  cdc abc my_pub_slot

Results in

That occurs because
select pg_get_replica_identity_index('foo'::regclass::oid)

returns null
https://github.com/imor/pg_replicate/blob/815e96d36c8a29ada355b8b3737c80ee9b4aa780/pg_replicate/src/clients/postgres.rs#L136-L139
which causes i.indkey to be null, and then is_identity to be null.
Logical replication on tables without a replica identity is support for inserts but not for updates or deletes.
If an update or delete is found, an error is thrown.
I think it would make sense to ignore that nuance ^ and enforce that all tables in the publication have a replica identity before startup. If any of them do not have a replica identity, then raise an error message explaining that they need to add a unique key or set the replica identity to full.

dupe of #18