visudo

The sudoers line:
ALL ALL = (root) NOPASSWD: /usr/sbin/service
in the README didn't work for me. However,
%sudo   ALL=(ALL) NOPASSWD:     /usr/sbin/service
works fine.

I haven't been able to reproduce this, unfortunately. Any more details on the problem you ran into would be appreciated!

Went off a fresh install of Windows, and also wasn't able to reproduce the problem. I think it might have just been something with that specific machine.


Include rsatoolbox

https://rsatoolbox.readthedocs.io/en/stable/

I haven't looked, is it very different in capabilities from MNE-RSA? https://github.com/wmvanvliet/mne-rsa

I think it supports a larger variety of analyses and more visualizations. It was just an idea, I came across this package yesterday by accident :)


Default behaviour of retryOnConnectionFailure is dangerous for POST requests

Default behaviour of OkHttpClient.Builder to set retryOnConnectionFailure may result in POST requests being silently resent on network timeouts.
While this may be typically alright for GET requests, POST/PATCH/DELETE requests modify data, and re-submitting them without knowing whether they have been received at the other end.

This is also something that is a significant change in OkHttp v3 over v2. It would be good to include this in CHANGES.md

This has been our behavior forever.

I have investigated this further, and there is a change in behaviour between v2 and v3 here, which is in the way SocketConnectionTimeout is handled. In v2 the request was always dropped, in v3 the connection is retried unless retryOnConnectionFailure is set.
Compare https://github.com/square/okhttp/blob/parent-3.0.0-RC1/okhttp/src/main/java/okhttp3/internal/http/StreamAllocation.java line 336 to https://github.com/square/okhttp/blob/parent-2.7.5/okhttp/src/main/java/com/squareup/okhttp/internal/http/StreamAllocation.java line 358
This means that if the client sent a POST request, then the server received it but the response got lost due to network issues, the client will resend it again. While in v2 it would fail.

This is the change - https://github.com/square/okhttp/commit/3b44fa37675c1d68298283ae4b8b45cd5771888d and https://github.com/square/okhttp/issues/1736

@ktchernov could you write a test case? There are great examples in CallTest, https://github.com/square/okhttp/blob/master/okhttp-tests/src/test/java/okhttp3/CallTest.java

Along with https://github.com/square/okhttp/issues/2443, that's exactly what caused my development backend to explode: the multipart upload tooks slightly more time than my read timeout, causing Retrofit to silently retry over and over...

Retrofit doesn't retry.
On Sat, Mar 26, 2016, 3:40 PM Cerrato Renaud<EMAIL_ADDRESS>wrote:

Along with #2443 https://github.com/square/okhttp/issues/2443, that's
exactly what caused my development backend to explode: the multipart upload
tooks slightly more time than my read timeout, causing Retrofit to silently
retry over and over...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/square/okhttp/issues/2394#issuecomment-201918305

Retrofit doesn't retry.

I meaned the underlying OkHttp, used by Retrofit 2.

I have created two unit tests, a passing test on OkHttp 2.7 - demonstrating that the behaviour there was as expected: https://gist.github.com/ktchernov/2a1b6ad8a0b0f12634a55b9e2551395e  - when a timeout occurs on a POST request body, OkHttp 2 does not try to re-submit the POST.
Second is the same test adapted to OkHttp 3.2 https://gist.github.com/ktchernov/5785e6d6664a9f306c01632b95492fdd - this test fails. OkHttp 3.2 does re-submit the POST body - which could result in unexpected duplicate submissions.

Thanks for the test. I’ll take a look!

Sorry there was a mistake in those tests, which I've corrected now.

And this is the bug that we fixed when we changed this behavior.
https://github.com/square/okhttp/issues/1736

I think the nuanced fix we want is to recover from timeouts that occur during connect, but not during read.

https://github.com/square/okhttp/pull/2479


Typo found in banner while marking all observations as seen

I think it is "take" instead of "takes".

Indeed!


The runtime_rank was changed to runtime_percentile in LeetCode API

Hi, ianding1!
I am using your leetcode vim plugin. (Thank you!)
However, there was a problem with the runtime_rank when submitting the code. This is because the leetcode API results was changed.
The fixes are as follows.

runtime_rank is changed to runtime_percentile in code.
runtime_percentile is showed only when submitting.
Removed 'Failed Test case' header in result of test. Because the conditions for printing the header is invalid now.

You can check the changes by installing the plugin from my forked repository.
# Install
Plug 'devinjeon/leetcode.vim'

# Check the changes
:LeetCodeTest
:LeetCodeSubmit

Cute animal picture.

Thank you for your commits!


use released duckdb-r 0.10.1

I'd like to support the previous, the current, and the development version of duckdb, at any time.

I believe the remaining errors are upstream problems.


bindToModel View property

I have very often this pattern in some form:
SomeView = Backbone.View.extend({
  initialize: function() {
    this.model.bind('some:event:1', this.someAction1, this);
    this.model.bind('some:event:2', this.someAction2, this);

    this.collection.bind('some:event:3', this.someAction3, this);
    this.collection.bind('some:event:4', this.someAction4, this);
  },
  // onClose is called when view.remove()
  remove: function() {
    this.model.unbind('some:event:1', this.someAction1);
    this.model.unbind('some:event:2', this.someAction2);

    this.collection.unbind('some:event:3', this.someAction3);
    this.collection.unbind('some:event:4', this.someAction4);

    Backbone.View.prototype.remove.call(this);
  }
});

And I think it will be really great to make this just:
SomeView = Backbone.View.extend({
  bindToModel: {
    'some:event:1': 'someAction1',
    'some:event:2': 'someAction2'
  },
  bindToCollection: {
    'some:event:3': 'someAction3',
    'some:event:4': 'someAction4'
  }
});

The two special attributes bindToModel and bindToCollection will bind the events, and when view.remove() is called all events will be unbind before dom removal. I think this will save a lot of code (and bugs related to model event binding/unbinding). This will also make Backbone even more awesome :)
If you agree on having such API I'll be happy to provide an implementation, since I have several minor prototypes of this.

That's a great little pattern, but I don't think it's common enough to warrant passing along that API to everyone. Personally, I don't have vary many views which are bound to both models and collections...
But note that a big part of the idea with Backbone is that it's extensible, so feel free to add this functionality for your app, by doing:
_.extend(Backbone.View.prototype, mySpecialHelpers);

The idea, was not that I have both bindToModel/bindToCollection. The main idea is - that if you pass all events via this helper. When you do view.remove() then automatically you will be unbinded from all those events. And this will fix the ghost views problem, which a lot of people have. When removing  views bind to models (or collections), but forgetting to unbind them.
I I'm using this as simple helper method now in this format (and works great):
class myView extends Backbone.View
  initialize:
    @bindToModel
      'some:event:1': 'someAction1',
      'some:event:2': 'someAction2'

Since I don't know a nice way to make it a backbone marco ... as events, routes, defaults.


FAPI-1677 - Kafka version update

Update kafka version update to handle Kafka timeouts
add throws exception to sendDocumentGenerationMessage  method for error handling

should merge to release branch if this is release 1 then merge back to develop


Please help me to find Travis issue

Hi guys,
Somebody can help me to find why Jest doesn't exited after tests, but only on Travis. In local it works properly.
This problem started 3 months ago after https://github.com/moleculerjs/moleculer-web/commit/ef4385cf76e644bf2bac1699a4761472e1341b10
Travis build history: https://travis-ci.org/moleculerjs/moleculer-web/builds
Error message:
Ran all test suites.
Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.

I've checked open handles but nothing.
Thanks in advance!

@icebob I already checked your commit, ef4385c but itsn't correct one. After removing that test case, the error still occurred.
This error happened when some process still running even the last test case completed.
To prevent this, pls add --detectOpenHandles --forceExit into jest --coverage.
It should be:
jest --coverage --detectOpenHandles --forceExit

PS: I still working on this issue. If I found somethings I will create the P/R.

Thank @lucduong for your help. I really appreciate it.
I've changed the test script command what you suggest and test ran without timeout: https://travis-ci.org/moleculerjs/moleculer-web/jobs/461668270
So the --forceExit solved the issue, but there is no any information about why it is not working without this parameter.

@icebob I read all the Unit Tests in your integration test file. Anyway, I couldn't know which process still running after finishing all the tests.
There is only one information that light me is some processes still running.
--forceExit to stop those one.

Thanks. If I can reproduce it in local I will start to comment out all tests and give back one-by-one and check the result. But it will be too slow via Travis.


update setup.sh and add .idea files to .git ignore

Added:  pipenv run python manage.py migrate  to setup.sh
Added .idea/ files to .gitignore
deleted:    .idea/workspace.xml from git using:  git rm .idea/workspace.xml -f  command

What about this PR, there was another one in the same subject
https://github.com/redhat-beyond/AcadeMe/pull/51

Please rebase with upstream


Update to 3.0.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Condaforge uses gcc 7.5 while DAMASK requires at least gcc 8.0
CMake Error at cmake/Compiler-GNU.cmake:5 (message):
  GCC Compiler version: 7.5.0 not supported
Call Stack (most recent call first):
  CMakeLists.txt:170 (include)


hwmv2: series/ and families/ application folders

Is your enhancement proposal related to a problem? Please describe.
As one of the additions of hwmv2, it was added the possibility to factorize configuration (dts overlays, Kconfig fragments) for a given soc under a new application folder named soc/.
This new folder provide the same functionality of boards/ folder, but allows to put all configuration that depends on a soc into a single file, hence sparing the need to replicate these configurations in various boards that uses the same soc version.
This new possibility is likely pretty useful in down stream projects (see related golioth blog post as example.
Though, in zephyr tree, the possibility of usages of socs/ folder is relatively limited because this is not often that several boards share the exact same soc, and even if it happens, within in tree applications (samples, tests), we usually want to have one board for each soc but not more. Sometime even, we just want to have one board per whole soc series as aim is to maximize test coverage at series level while minimizing the CI load.
Describe the solution you'd like
In the same vein as socs\ folders, add series\ and families\ application folders.
Using these folder it would be easy to provide application specific configuration at the right level while minimizing the number of files to maintain, limit CI load and ensure tests and samples compatibility with the maximum of boards.
For instance:
Replace
samples/drivers/dac/
├── boards
│   ├── b_u585i_iot02a.overlay
│   ├── disco_l475_iot1.overlay
│   ├── nucleo_f091rc.overlay
│   ├── nucleo_f207zg.overlay
│   ├── nucleo_f429zi.overlay
│   ├── nucleo_f746zg.overlay
│   ├── nucleo_f767zi.overlay
│   ├── nucleo_g071rb.overlay
│   ├── nucleo_g431rb.overlay
│   ├── nucleo_g474re.overlay
│   ├── nucleo_h743zi.overlay
│   ├── nucleo_l073rz.overlay
│   ├── nucleo_l152re.overlay
│   ├── nucleo_l552ze_q.overlay
│   ├── nucleo_u575zi_q.overlay
│   ├── nucleo_wl55jc.overlay
│   ├── stm32f3_disco.overlay
│   └── stm32l562e_dk.overlay

with
samples/drivers/dac/
├── families
│   └── stm32.overlay

About CI load, one of the major issues in CI load is the frequent use of filter that impose to prebuild board configurations before being able to apply the filters. series/ and families folder could help reducing the usage of those filters as well.
For instance:
  drivers.spi.stm32_spi_16bits_frames.loopback:
    extra_args:
      - EXTRA_CONF_FILE="overlay-stm32-spi-16bits.conf"
      - DTC_OVERLAY_FILE="overlay-stm32-spi-16bits.overlay"
    filter: CONFIG_SOC_FAMILY_STM32
    platform_allow:
      - nucleo_h743zi
      - nucleo_h753zi
      - nucleo_h745zi_q/stm32h745xx/m4
      - nucleo_h745zi_q/stm32h745xx/m7

could be replaced by families/stm32.conf and families/stm32.overlay, with the additional benefit that this configuration would apply also when running west, not only when running twister.
Describe alternatives you've considered
Introduce Kconfig.defconfig files in samples and tests (if that's even doable).

^^ @zephyrproject-rtos/testing

This would be very useful.
A suggestion:
Could this be namespaced either in the folder name, or by being a set of subfolders? Eg.
samples/drivers/adc/
├── soc_series
│   └── rp2350.overlay
samples/drivers/dac/
├── soc_family
│   |── rpi_pico.overlay
│   └── stm32.overlay

or using subdirectories:
samples/drivers/adc/soc/
├── series
│   └── rp2350.overlay
samples/drivers/adc/soc/
├── family
│   |── rpi_pico.overlay
│   └── stm32.overlay

This might be easier to understand than families or series(es) without some kind of qualifier/prefix.


Add option to allow inclusion of generated unique id in mapping results

I am really reluctant to add a field to the produced mapping which is not in the source data, even if it is reproducible. Everyone using the mapping lists will need to special case the logic for that field, and it is so much easier to just test if all provided fields match. Moreover, I think some people could assume that an id field is definitive and only try to match against that (and not find anything).
So I would prefer to make this a configurable option with a negative default.
Originally posted by @cmutel in https://github.com/fjuniorr/flowmapper/issues/27#issuecomment-1827169378

In order to do the analysis for https://github.com/fjuniorr/flowmapper/pull/47#issuecomment-1841566693 it was extremely useful[^1] to have the generated unique id in the glad output.
[^1]: implemented in https://github.com/fjuniorr/flowmapper/commit/d161fb1005c5c15f3cf90bfa7b2502fa63d59ad2

Just a reminder that in https://github.com/fjuniorr/flowmapper/commit/d161fb1005c5c15f3cf90bfa7b2502fa63d59ad2 I did not expose a flag --ensure-id in the CLI command flowmapper map, which is also useful.


Backports 0.20 pr7

Issue being fixed or feature implemented

Bitcoin Backports
What was done?

Misc v20 Backports, check commit log to see changes.
How Has This Been Tested?

Compilation and tested unit tests locally
Breaking Changes

Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

Looks good. Pls squash fixes into corresponding "Merge ..." commits.

@Munkybooty see above

@Munkybooty Can you update the PR title to include the conventional commit backport:  prefix?


Fix CSRF for tx service

Why this change is necessary?

Beacause CSRF was not working. Also, there were some configuration parameters not used anymore since last versions of the tx service 😉

It's ok.


CI: update SCIPY_NIGHTLY_UPLOAD_TOKEN on CirrusCI.

Closes #18656
Update the token using my personal token as per the new requirements of SPEC4.
I went into the settings section of SciPy on CirrusCI and under Secured Variables I put the token and got back the encrypted string.

@rgommers @andyfaff as you set this up, could you check the security settings of CirrusCI? To me it seems that we should enable Require approval for builds from users without write permissions.

ah ok, I will do that to check then. I thought there was a manual trigger possible, like for GitHub actions with the manual dispatching.

ATM the upload script wouldn't run with a manual trigger.

ISTR that you need to allow manual triggers in the yml file. I can't manually run numpy builds on cirrus, but can rerun existing builds.

Well nothing happened 😅 https://cirrus-ci.com/build/5939126856318976

The cron job needs to be called nightly

I am also seeing that apparently we do a full git clone instead of fetching only the last commit? Is there a reason for that or can we change this? It's taking like 40s to do the clone.

We don't clone in the wheel build script. The clone occurs in general ci. The reason there's git ops is because default cirrus runs against the PR branch, not against the PR merged into main/maintenance.
I believe that a non shallow clone is required for PRs because the merge can be made to main or maintenance branches.

Yay, the token is working and we got new wheels up there. (And also the readme did not get messed up again with the update, so my manual edit stayed.)


Allow Service Instances and Service Bindings to be edited

Description
Changes proposed in this pull request:

Added an edit mode to the Service Instance and Service Binding
Fixed a link bug that showed a link to the resource that didn't exist

Related issue(s)
Fixes #1637

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-smoke-test-docker


Show how to reset Nudge's deferrals for people who use MDM

This section: https://github.com/macadmins/nudge/wiki/User-Deferrals#testing-and-resetting-nudge
Explains how to do it for people who don't push out the Nudge config via JAMF or another MDM. That command doesn't work for the MDM people.
Could we add a line underneath that that says:

If you've deployed Nudge's settings via Configuration Profile or JAMF's JSON Schema feature, the above file path won't exist. Preferences that are pushed via MDM are stored in a different directory, so please use this command instead:
defaults delete /Library/Managed\ Preferences/com.github.macadmins.Nudge.plist

Those are incorrect instructions. Those are the managed preferences coming from MDM. Nudge, whether it's managed via MDM or the json will contain user preference plist.
doing that command won't do anything.


NetworkSettings > IPAddress is sometimes "" in docker inspect, seems to cause empty address entry in Addresses

NetworkSettings > IPAddress is sometimes "" in docker inspect, which seems to cause empty address entry in docker-gen's supplied Addresses property which makes my templates yield empty addresses as targets. In all cases the container DOES actually have an IP, but it's only shown inside NetworkSettings > Networks > bridge > IPAddress.
I'm not sure if this is something docker shouldn't do or an unavoidable new thing with docker's new networking tools... however:

I don't use any special network settings at all. Everything uses the default network
Still, this happens and my templates break...

See https://github.com/docker/docker/issues/21658 for more details.
Since I have no idea on which side the problem cause is, I thought I might as well also add a ticket here to give you a chance of adding your thoughts

I got the same when using docker-compose version 2 networking,
pls patch docker-gen for this !
👍

I confirm it happens on docker-compose version 2 configs.
Is there a way to manually set it in the compose file?

Pretty late to the game but hope this might be useful to others. Took a long time for me to get this running but it is working now for my use case. Had to fish through the source code (generator.go , from line 382 onwards more specifically) to get at what container properties docker-gen is looking at and what variable names they map to.
I can confirm that IP Address is always blank for me. I am using this in the 2 container version of jwilder/nginx-proxy. I followed the code examples with the below changes.
Changed 'Addresses'
{{ range $index, $value := $containers }}     {{ with $address := index $value.Addresses 0 }}     server {{ $address.IP }}:{{ $address.Port }};     {{ end }} {{ end }}
to 'Networks'
{{ range $index, $value := $containers }}     {{ with $address := index $value.Networks 0 }}     server {{ $address.IP }};     {{ end }} {{ end }}
Please note that I didn't see port information with this change. In my case it is port 80 so I'm not specifying, but that might be an issue for others.

Even later to the game, but I just had this issue.
Seems when we define a custom network then there will be no IP address in the place where it's being retrieved. @botwhytho already helped with how to get the IP address, but the port can also be retrieved using the old way. I solved it this way:
{{ range $index, $value := $containers }}
    {{ with $port := index $value.Addresses 0 }}
        {{ with $address := index $value.Networks 0 }}
            server {{ $address.IP }}:{{ $port.Port }};
        {{ end }}
    {{ end }}
{{ end }}

So I just take the port like previously, but the IP address from the Networks section. This way you can get both.


Get-PolicyConfig update command

[Hi, a tiny request here...
Remove 'Azure' from the below command.
Get-PolicyConfig | format-list Azure Purview*
Thanks]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2f391208-c028-c931-ffab-f8f99e6d6dc2
Version Independent ID: c8186d8b-776b-8a39-a9e0-6d83a2028479
Content: Sensitivity labels in Azure Purview FAQ - Azure Purview
Content Source: articles/purview/sensitivity-labels-frequently-asked-questions.yml
Service: purview
Sub-service: purview-insights
GitHub Login: @ajaykar
Microsoft Alias: ajaykar

@ChristianJBergstrom  - Thanks very much! I've got those changes submitted. Should be live by later this afternoon!

#please-close


Single config fixes 2.

libcanberra is fixed as part of  #27314 but reviewers are not keeping pace.

@Neumann-A please fix the conflicts, thanks.

Thanks! :)


build_translations ported to python3

Hi!
I did some changes to support python 3.x. Should work with python 2.x also (tested locally on windows with python 2.7.11).

Thanks for this :)

Excellent, thanks!


Any chance to get it working for Cossacks 2 NW/BFE in the future?

That's really good thing, I appreciate your efforts in giving these games a chance to be played "normally", without Hamachi/Tunggle/GameRanger tools.
It would also be useful for mods for these games, like HoAE Reborn or C2 Gunpowder mod, which aim at rebalancing for MP purposes. Is there any chance the program will be updated to support C2 in the near future?

I do plan on expanding the capabilities of the emulator by the end of February. The goal of this project is to cover all titles powered by the DMCR engine, including the demos (archival purposes).
As for the support for mods such as HoAE Reborn or C2 Gunpowder, I haven't looked into these as of yet, so I will follow up with an answer at a later date.

Any update on this? If contributions are welcome, I might be able to contribute to adding support for Cossacks 2.

Hi, thank you for your patience. Yes, most definitely. I had to postpone the release due to several reasons, one of them being that I've found a vulnerability allowing to spoof user sessions in at least some of the GSC games. I had to find a workaround to allow users to get the most out of the game. Due to some private reasons I didn't have much time to work on it, but things have changed. Stay tuned.


As a user, I can choose a continent and input a number (N) to see the top N populated countries in that continent.

good job


Basic course grade calculation

As a teacher I want to trigger grade calculation using the formula selected for the current course instance, to determine the final course grades.
Teacher should be able to trigger this manually, when she/he determines that the assignments are now completed. Also recalculation should be possible, in case assignment points change later on, or new points come late. Assignment categories should have labels that are used to match points also from earlier course instances (within a specified time period). The system should be able to show and propose the possible assignments to use in calculation, considering their expiry date.
DoD: Grade calculation can be completed and also redone if points have been updated. Has been tested with multiple consecutive calculation cycles, also with large numbers of students.

[ ] Frontend implementation for calculating grades @kiiamakir
[ ] API for calculating grades in backend @Gskartwii @no-comma
[ ] TypeScript function for calculating weighted average @Gskartwii

Typescript function close to completion
Route definition is clear
Frontend button done


Security Issue

DO NOT PROVIDE ANY DETAILS HERE. Please privately report to https://github.com/louislam/uptime-kuma/security/advisories/new.
Why need this issue? It is because GitHub Advisory do not send a notification to @louislam, it is a workaround to do so.
Your GitHub Advisory URL: https://github.com/louislam/uptime-kuma/security/advisories/GHSA-vq2r-42qf-wq5p

Replied.


Filter

Hey,
I wanted to try your new shiny impromptu.filter, but I can't get it to work. I've tried this:
  impromptu.filter{
    header = "HEADER",
    lines = {
      { description = "Line 1" },
      { description = "Line 2" },
    },
    handler = function(b, opt)
      print("option: "..tostring(opt))
      return true
    end,
  }

but I'm getting an error about line 150 of filter.lua getting a nil argument to ipairs. Did I miss something?

Apparently I mistyped the argument name in the docs. It should be options instead of lines.

Ah yeah, the docs were somewhat unclear on that, it says lines here, but options here, but since the latter also has too many braces, I figured that would be wrong without really thinking about that :)
Other than that, seems to be working. You did not document the keys, but I found <C-k> and <C-j> somewhat surprising, and would personally prefer <C-n> and <C-p> in accord to the usual vim usage.

Two more observations:

I wasn't bitten by this, but lua's find takes a pattern, which might be surprising. Try e.g. filtering by %. I suggest passing plain = true to find as a default.

The dots as a separator look pretty ugly, at least in my setup, due to spacing reasons (they are drawn in the middle of the cell, which make the space above the typed characters larger then below them). I suggest simply changing it to an underscore.


github: build_and_deploy: update to v0.0.11

Changelog-entry: update build and deploy workflow to v0.0.11
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@balena-ci I self-certify!


Binding the React element to a Handsontable instance

With this new version 1.0.0, and since Handsontable is no longer part of the React wrapper and can't be accessed using a reference, how can we bind the React element to a Handsontable instance and invoke its API?
I tried the following approach, but it didn't work – it actually added a new table to the DOM:
const container = document.getElementById(...);
const settings = ...;

const hot = new Handsontable(container, settings);

HotTable component has hotInstance property which is the instance that is already binded to the DOM. You can create a reference to HotTable component to access it's properties.

Thanks for your help! It might be worth adding this to the README.


Sensors stop updating a few seconds before 12:00

All sensors stop updating a few seconds before 12:00. What could be the cause?

Check Event Log to see if there are any startup messages.
Check HA developer tools > started to see if HA added a _2 extension to the sensor names. It probably did and the ones being displayed are not the ones being updated.

I don't understand what i have to check in "Check Event Log to see if there are any startup messages."
About "started to see if HA added a _2 extension to the sensor names" i already verified this and is not the problem, the sensor not update the correct sensor name and this happen at around midnight for all sensors.
I tried also to uninstall and install again the integration but the result is the same Thanks

A lot of info is displayed in the Event Log where icloud3 starts. An error would be displayed when setting up the entities if there was a problem with names and alerts would be displayed if the Apple account was not being logged into. A device that is tracked will have an enter for each event.
Try Event Log > Actions > Relocate All Devices and review each device to see if it was located and updated.
If it was located and messages are displayed, then the problem is probably with entity names. Look on HA Developer Tools > States for your entire, their names and their candies.

I probably didn't explain my problem well, so I'll try using a translator which might be better than me in English.
I have completely uninstalled the integration, I have done it several times, and then reinstalled it. Everything works perfectly throughout the day, but when midnight arrives, all sensors stop updating.
There is no problem with the sensor names which I have checked multiple times to be correct.
Any ideas?

So you are saying that it rung ok during the day and then just stops tracking everything at midnight?
The only thing iCloud3 does at midnight is to roll over the log file and rebuild the Waze History data base files.
Are there any iCloud3 error messages in the HA logs? (HA Sidebar > System > Logs) Are you using the Waze? Than the history data base would be enabled. Disable it on the Configure Settings > Waze  screen to see if that does anything.

Also this night at midnight sensor update stop to works
There are no icloud errors in logs
I don not use waze
Restarting Home Assistant work again
I use Here
In the sensor setup something happen at 12:00 see the screenshot
In the logs this error for Here
Registratore: homeassistant.components.here_travel_time.coordinator
Fonte: helpers/update_coordinator.py:382
Integrazione: HERE Travel Time (documentazione, problemi)
Prima occorrenza: 09:05:03 (27 occorrenze)
Ultima registrazione: 09:45:04
Unexpected error fetching here_travel_time data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 382, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/here_travel_time/coordinator.py", line 89, in _async_update_data
response = await self._api.route(
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/here_routing/here_routing.py", line 190, in route
response = await self.request(uri=ROUTES_PATH, params=params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/here_routing/here_routing.py", line 121, in request
raise HERERoutingUnauthorizedError(json.loads(decoded_contents)["error_description"])
here_routing.exceptions.HERERoutingUnauthorizedError: Sentry-EUM Error. EUM returned HTTP response code of 401 for https://account.api.here.com/authentication/v1.1/extendedApiKeys/ImXC-5u4V2*****. The Server error message was {"errorId":"ERROR-2ed2ceef-3daa-46cd-b665-e32f52f3cfaf","httpStatus":401,"errorCode":401311,"message":"Requesting client hB759D5hYnws2lgRywMd status is not active.","error":"invalid_request","error_description":"errorCode: '401311'. Requesting client hB759D5hYnws2lgRywMd status is not active.","correlationId":"b06896b4-af1f-4886-aea2-199b60650111"}. The Sentry cache was therefore not updated. X-HERE-TID="null" The Server error message was {"errorId":"ERROR-2ed2ceef-3daa-46cd-b665-e32f52f3cfaf","httpStatus":401,"errorCode":401311,"message":"Requesting client hB759D5hYnws2lgRywMd status is not active.","error":"invalid_request","error_description":"errorCode: '401311'. Requesting client hB759D5hYnws2lgRywMd status is not active.","correlationId":"b06896b4-af1f-4886-aea2-199b60650111"}. The Sentry cache was therefore not updated. X-HERE-TID="null"

It does look like another HA Integration also gets disconnected when your router is rebooted and the http cannot connect with its data source. To fix this, you will need to restart HA after your router is rebooted. I would create an automation to restart HA using the home_assistant.restart Action with the time you want it to restart. There are probably examples in the HA docs.

It's a coincidence that this morning I had to restart the router, but the issue with iCloud3 is not related to this. It occurs even without restarting the router.

It looks like you have an in zone interval of 1-min. If that is true, increase it to at least 5-min. The errors above your screen shots are about communication problems and your router losing its connection with the internet.
httpStatus":401,"errorCode":401311,"message":"Requesting client hB759D5hYnws2lgRywMd status is not active."
It does not appear that this its an iCloud3 issue.

It seems really difficult to understand each other.
You asked me if I use Waze and I replied no, instead I use "HERE." "Here" is an integration, and I posted an error that is related to "HERE," not iCloud3. It seems clear and evident to me!!!
It's clear that this error is not related to iCloud3!!!
The problem with iCloud3 is that it stops to work at midnight and has done so again now!!!
This is the problem, and it is only related to iCloud3. I don't know how to explain it any other way!!!
You wrote to set the interval from 1 to at least 5... but which interval, where is this setting??? Where can I make this change??? Thank you

You asked me if I use Waze and I replied no, instead I use "HERE." "Here" is an integration, and I posted an error that is related to "HERE," not iCloud3. It seems clear and evident to me!!!
You wrote to set the interval from 1 to at least 5... but which interval, where is this setting??? Where can I make this change??? Thank you

"It looks like you have an In zone interval of 1-min. If that is true, increase it to at least 5-min." is what @gcobb321 said.  This is a picture of what he's referring to:

Very Thanks I not have nothing setting to 1 min... Now I disabled waze route service and waze history database... Now i have only to wait what will happen tonight at midnight... I will tell you Thanks Again

@giugit
The values on the inZoneParameters … screen are default values and only used when setting up a device.  The in zone and fixed interval settings being used are set for each device on the Configure Settings > Update Devices screen. Your values may be correct and the value i noticed may have been the interval being used in that tracking event.
My comment of the error you posted was that your internet connection was interrupted and effected all apps that used it to include HERE WeGo and iCloud3.
Can you change the time your router reboots to another time?

Last night it didn't stop... maybe the problem is solved... let's see what happens next night at midnight.
If the problem is solved, it was due to Waze being enabled without the integration installed.
Very Very Thanks!

Actually, the Waze option does not use the integration. It sends a time/distance directly to the Waze servers. But that’s good it continues to run without problems.

I confirm that the problem is solved by disabling Waze, everything works now!
The values of the various devices have now started to update more slowly (several minutes) whereas before they were updating continuously.
I have also enabled the Waze integration and will try to re-enable the options that disabled WAZE ROUTE SERVICE and WAZE HISTORY DATABASE even though I'm not entirely sure what their purpose is.
Thank you.

You do not need the Waze integration. iCloud3 calls Waze directly and does not use it.

I confirm that reactivating the WAZE HISTORY DATABASE at midnight causes updates to stop... just to complete the post.
That’s how it works for me... Thanks for the support.

The iCloud3 End-of-day maintenance was changed to 12:15 to avoid conflicts with other integrations. Let me know if this persists.


Update SQLite, Android dependencies

Update Android dependencies except io.mockk.mockk.
Reported a problem with it here. Might be our fault.
After this is merged people should update to Android Studio Jellyfish.
SQLite Update
This pull request also updates SQLite, because this warning now became an error:

/home/runner/work/maplibre-native/maplibre-native/vendor/sqlite/src/sqlite3.c:38937:8: error: incompatible integer to pointer conversion assigning to 'char *' from 'int' [-Wint-conversion]

This was patched but this patch was not included in a release yet.
Note for reviewer: updating sqlite.c is a bit tricky, because it's impossible to review the changes. Something malicious could hide in there.
You can run
scripts/vendor/sqlite.sh

to verify that the working directory stays clean, i.e. that this is just the released version of SQLite plus the patch applied.

Looks OK to me, but I do not use Android studio so I do not want to give the defining approval 😊


flashplayeractivex : replace outdated download url with the new one

The base url used to download the flashplayer has changed from :
_https://download.macromedia.com/pub/flashplayer/pdc/${CurrentVersion}/_
to
_https://fpdownload.macromedia.com/pub/flashplayer/pdc/${CurrentVersion}/_

@Pyrrvs
Actually it was changed from:
https://download.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_<majorVersion>_active_x.msi
to
https://download.macromedia.com/pub/flashplayer/pdc/${CurrentVersion}/install_flash_player_${majorVersion}_plugin.msi
The changes however was never pushed because of the upstream version scheme.
This is also why the url and checksum haven't been changed in the install script.
I've been planning to look into being able to update the flashplayer packages, but unfortunately have yet to get around to it.
The url you have used in this PR is to the round robin servers,
as such I'm afraid I'll have to close this PR

Thank you for this explanation and sorry if I've bothered you with this PR. I would have a question however about the 'upstream version scheme' you were talking about because I'm not quite sure to understand what you mean by that. So if you have a moment to explain it to me, I might be able to help you in the future.
Regards

Don't worry about bothering us with the PR.
What I mean by upstream versioning scheme, is that Adobe releases flashplayer using a 4-part version.
i.e <IP_ADDRESS>, and since chocolatey only supports maximum 4 parts we are unable to update these packages without changing this version.
I've added a PR just now that adds a script we can use while updated such packages by padding the revision number (the last part of a 4-part versioning) so we can update all packages making use of that script.

Thank you, it makes much more sense now !


Framework invocations of saveLayer should show the checkerboard diagnostic

Some rendering objects in the framework Dart code may call Canvas.saveLayer (notably ClipRRect and PhysicalModel with a rounded rectangle shape).
The framework's usage of saveLayer doesn't currently support the checkerboardOffscreenLayers diagnostic flag.  We should make the framework draw the checkerboard in these cases.
@chinmaygarde

@chinmaygarde Do you still want this?

Yes please.

We ditched the checkerboard features, so closing this.


Extend openbmc dump scripts to cater additional details to aid in debug

Extending BMC dumps to capture additional details - phase 1
Follow commits are pulled from master
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/52299/7
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/52317/9
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/52368/11
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/52369/12
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/52370/13

Can one of the admins verify this patch?

@devenrao it will be good to share the Dump collection time with all the new plugins. System with Full journal log.

@devenrao it will be good to share the Dump collection time with all the new plugins. System with Full journal log. Also test results during BMC quisce and Host ipl window.
sure


Reference X not showing up when X>=2, in web app

Describe the bug
The answer object sometimes does not display all the used sources (clickable) to generate the answers.
Expected behavior
The answer should contain all the references of the retrieved sources - see screenshot below
How does this bug make you feel?

Debugging information
Steps to reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots

Logs
If applicable, add logs to help the engineer debug the problem.

Tasks
To be filled in by the engineer picking up the issue

[ ] Task 1
[ ] Task 2
[ ] ...

Heya @cherifbenham, I'm not sure I understand the issue. From the screenshot, it looks like it's retrieved all of the data from one reference correctly. Could you explain a bit more? Thanks

Thanks @adamdougal Adam for your reactivity
The issue is that one could expect that since the generated answer mentions 2 candidate sources, it should also return 2 clickable URLs but it is not the case: 2 candidate docs are cited in the answer but only one reference URL is displayed as ref
Does it make more sense?

Gotcha! That's an odd one. Can you see the reference documents being returned in the logs of the backend application? Are they both there? It could be that the OpenAI System prompt needs tweaking.

Hey @cherifbenham - Could you please re-test this and let us know if the issue persists?

Closing this issue since we haven't received any updates from the user.
Hey @cherifbenham, feel free to reopen it if you continue to experience the issue.
Happy to Help!


Internal Server Error at Japanese site of

Japanese site of This link makes Internal Server Error.
https://developers.google.com/maps/documentation/utilities/polylinealgorithm?hl=ja

@FuruhashiFumihito Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.

This issue seems to have been solved now. 🙂

Thanks!


Addition of authentication middleware for Routes.

For example.
case Method.GET -> Root / "health" => Response.ok
to
case Method.GET -> AuthRoot / "health" => ...

@aposto You can checkout this example added here — https://github.com/dream11/zio-http/pull/175/files#diff-0b5120d305a9d6ec4ea512ff2b965bfe94ea7c69a0a6e93162c7ceb6ecca87ee

@tusharmath Thank you so much for this support.
I think we can introduce it to our lightweight micro-services.

Fixed in #175


Compatible version of j4ts with JSweet 1.2.0 release

Could we get a release that is compatible with the recent 1.2.0 release of JSweet?

Unless I am mistaking, I think that org.jsweet.candies:j4ts-0.3.0-SNAPSHOT is compatible. Do you want me to release 0.3.0?

So what we are trying to achieve is having a version of j4ts that has been built using your latest prod jsweet-transpiler release. It looks like 0.3.0-SNAPSHOT is using 1.1.1 of the transpiler.

Right. Version 1.2 is an intermediate release before version 2. Version 2 will be more open than version 1.x, which will allow everybody to modify candies and contribute easily. The core reason behind it is that we want to give more freedom to the users since maintaining all the candies ourselves it too much of a work.
So, since 1.2 is fully compatible with 1.1.1 candies, I have decided not to release any candies for that version. You should still use 1.1.1 candies, even if you get warnings. All this will be fixed soon with version 2. Of course, if you find an issue with the candy, please tell me and we will fix it.

Please note the 0.5.0-SNAPSHOT, (develop/v0.5.0 branch) which is now compatible with JSweet v2.


Use of /common endpoint is obsolete?

This article goes through the use of the /common endpoint of Azure AD.
Isn't this obsolete and article needs to be updated?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 326f7173-a654-fda7-2438-6905da3fdbef
Version Independent ID: 7dbc5a10-9d61-26e1-f532-973b4bdfae9a
Content: Build apps that sign in Azure AD users - Microsoft identity platform
Content Source: articles/active-directory/develop/howto-convert-app-to-be-multi-tenant.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

Seems like asp.net does this behind the scenes and that you should not add "/common" to the endpoint manually.

Thanks for sharing the update.


Nesting: part 2

Continuation of #3.

[x] Add test verifying enter throws with an already entered drop target
[x] Add test verifying leave throws with a non-entered drop target
[x] Add test verifying enter A, B, C, D and leave B keeps A active, but B, C and D inactive
[x] Add test verifying that removing an entered drop target midflight has the same effect as calling leave on it
[ ] Add test verifying both drop and endDrag completely clear active drop targets
[ ] Add and test context.isOver(dropTarget, shallow=false) that tells whether we have entered the drop target. With shallow=true, returns true only if that drop target is innermost entered one.
[ ] Change drop implementation that, instead of simply choosing innermost target, will run drop on each nested active target, from the innermost to the outermost. It will skip drop targets for which context.canDrop returns false. Each target will be able to access previous' result in context.getDropResult() and learn if there was a previous one by reading context.didDrop(). Each will be able to either return undefined (means don't touch drop result) or a different object (means replace drop result with the one returned from drop). Test that.

Found a little bug with the Registry Actions.
Fix is inside, I need to work out a good way to specifically test the actions... There is some shared state between the registry and the DnD store that we need to have good tests on

That's great, thank you!

I'm going to move tests relying on getTargetHandles into context tests, and later add manager tests verifying the same by snooping on drop calls. (So contract is tested independently of data.)

Yeah I am having lots of trouble with sorting tests not to mention writing the descriptions :P
Spent more time staring at it('...', () => {}); than I did writing tests for sure.


mssql-conf without standalone installation (deb)

I need to to the following:
sudo mssql-conf set network.privilegedadaccount <username>

But I need to do that for a SQL instance running in a docker container while I do not have the standalone version of SQL server installed (deb).
How can I configure this property if the mssql-conf is not available?

Nevermiiiind 😄 It's here mssql.conf format


[Accelerate] [Quadrature] New Quadrature Overlay

A class that simplifies approximating the definite integral of a function.
This PR contains a new class, Quadrature that simplifies the API to quadrature_integrate_function and quadrature_integrate (see existing docs here).
cc: @moiseev @airspeedswift @stephentyrone

@swift-ci please test

Can we define some verbose and descriptive aliases of .qng, .qag, and .qags?

Can we define some verbose and descriptive aliases of .qng, .qag, and .qags?

Added aliases: qng -> nonAdaptive, qag -> adaptive, qags -> adaptiveWithSingularities.
(pending push)

@swift-ci Please test macOS platform

@swift-ci Please smoke test Linux platform

Build failed
Swift Test OS X Platform
Git Sha - 0ab641764a99df69a990a583e7dcc0ce8005fa6e

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - b25cb01f416ca892d4658ab78526cceb551891a5

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test linux


Implement toolkit Python Auth Samples

Build Pipeline -
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/12179035402


xWindowsUpdateAgent: Fix Get-TargetResource returning incorrect key - Fixes #55

Get-TargetResource was returning the Source (WindowsUpdate/MicrosoftUpdate) under a key of 'Service' instead of 'Source' as the property is named. This was causing Get-DscConfiguration to fail (as seen in #55 ).
This fixes that incorrect key and the places it's used, tests are also updated to correctly expect that value.

This change is

@ChrisLGardner,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #56 into dev will not change coverage.
The diff coverage is 100%.

@@        Coverage Diff        @@
##           dev   #56   +/-   ##
=================================
  Coverage   59%   59%
=================================
  Files        2     2
  Lines      307   307
=================================
  Hits       183   183
  Misses     124   124

Looks like overall code coverage is being impacted by the xWindowsUpdate resource, I'll see if I can fix that in another PR.

@kwirkykat any chance this could get reviewed? I'm aware it's failing on overall code coverage but I haven't had much time to work on another PR to fix that yet.


api: prevent early output retrieval

Change the API endpoint to prevent retrieving monitor-output from a
running instance. Instead, we require the caller to exit the API context
before querying the monitor-output. This guarantees that the api-thread
was synchronously taken down and scheduled any outstanding events.
This fixes an issue where a side-channel notifies us of a buildroot
exit, but the api-thread has not yet returned from epoll, and thus might
not have dispatched pending I/O events, yet. If we instead wait for the
thread to exit, we have a synchronous shutdown and know that all
ordered kernel events must have been handled.
In particular, imagine a build-root program running (like echo in the
test_monitor unittest) which writes data to the stdout-pipe and then
immediately exits. The syscall-order guarantees that the data is written
to the pipe before the SIGCHLD is sent (or wait(2) returns). However, we
retrieve the SIGCHLD from our main-thread usually (p.join() in our test,
and BuildRoot() in our main code), while the pipe-reading is done from
an API thread. Therefore, we might end up handling the SIGCHLD first
(just imagine a single-threaded CPU that schedules the main task before
the thread). To avoid this race, we can simply synchronize with the
api-thread. Since we already have this synchronization as part of the
api-thread takedown, it is as simple as stopping the api-thread before
continuing with operations.
Lastly, if a write operation to a pipe was issued, we are guaranteed
that a SIGCHLD synchronization across processes is ordered correctly.
Furthermore, the python event-loop also guarantees that stopping an
event-loop will necessarily dispatch all outstanding events. A read is
guaranteed to be outstanding in our race-scenario, so the read will be
dispatched. The only possible problem is _output_ready() only
dispatching a maximum of 4096 bytes. This might need to be fixed
separately. A comment is left in place.

(rebased on master; running now a property)


run-tests: Mount modules

Signed-off-by: Quique Llorente<EMAIL_ADDRESS>

This one fails on my CentOS Stream 8 VM: https://paste.centos.org/view/3c3fbbb8
It actually runs podman.


Improvements for STM32 ADC

Summary
This PR adds new operations to the STM32 ADC low-level interface:

setup and shutdown can be called without access to upper-half ADC
EXTSEL/JEXTSEL configuration

Impact
Testing
Tested with the following examples:

nucleo-f302r8/highpri
stm32f429i-disco/highpri
stm32f429i-disco/adc

Hi Mateusz,
It is reporting some a compilation error:
chip/stm32_adc.c:656:20: error: initialization of 'void (*)(struct stm32_adc_dev_s , uint32_t)' {aka 'void ()(struct stm32_adc_dev_s , unsigned int)'} from incompatible pointer type 'int ()(struct stm32_dev_s , uint32_t)' {aka 'int ()(struct stm32_dev_s *, unsigned int)'} [-Werror=incompatible-pointer-types]
656 |   .jextcfg_set   = adc_jextcfg_set,
|                    ^~~~~~~~~~~~~~~
chip/stm32_adc.c:656:20: note: (near initialization for 'g_adc_llops.jextcfg_set')
chip/stm32_adc.c: In function 'adc_llops_setup':
chip/stm32_adc.c:4140:1: error: no return statement in function returning non-void [-Werror=return-type]

Yes, my mistake. It should be fine now

Thank you!


problem with latest angular-cli

I just updated angular-cli to the latest version... Now I cant build my project with sortablejs:
ERROR in Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 194:50 in the original .ts file), resolving symbol NgModule in<EMAIL_ADDRESS>resolving symbol SortablejsModule in node_modules/angular-sortablejs/dist/src/sortablejs.module.d.ts, resolving symbol SortablejsModule in node_modules/angular-sortablejs/dist/src/sortablejs.module.d.ts
Can you please help?

Hi deinega, could you solve this problem ?

Hi. I solved it somehow... Thanks!

i have same problem. Could you help me ?

I don't remember what I did, but I think I didn't downgrade cli version.

hi @YamanSehzade
have you found a solution for that?

hi @smnbbrv, i gave up using sortablejs.

Hi guys,
I have a fix for this issue. I already added a PR, but in the meantime you can check there for the temporary fix for your selves.


use bytearray buffers instead of deque buffers

I have bug in this project with recent tornado version. Tornado have used bytearray instead of deque.

thanks.


Configure Azure Pipelines by Sebastian

This configuration builds the application and produces builds for both Debug and Release configurations.

reviewsd


Fix walreceiver and safekeeper bugs

There was an issue with zero commit_lsn reason: LaggingWal { current_commit_lsn: 0/0, new_commit_lsn: 1/6FD90D38, threshold: 10485760 } }. The problem was in send_wal.rs, where we initialized end_pos = Lsn(0) and in some cases sent it to the pageserver.
IDENTIFY_SYSTEM previously returned flush_lsn as a physical end of WAL. I'm not sure if walproposer actually relies on it, but now it returns flush_lsn (as it was) to walproposer and commit_lsn to everyone else including pageserver.
There was an issue with backoff where connection was cancelled right after initialization: connected! -> safekeeper_handle_db: Connection cancelled -> Backoff: waiting 3 seconds. The problem was in sleeping before establishing the connection. This is fixed by reworking retry logic.
There was an issue with getting NoKeepAlives reason in a loop. The issue is probably the same as the previous.
There was an issue with filtering safekeepers based on retry attempts, which could filter some safekeepers indefinetely. This is fixed by using retry cooldown duration instead of retry attempts.
Some send_wal.rs connections failed with errors without context. This is fixed by adding a timeline to safekeepers errors.

New retry logic works like this:

Every candidate has a next_retry_at timestamp and is not considered for connection until that moment
When walreceiver connection is closed, we update next_retry_at using exponential backoff, increasing the cooldown on every disconnect.
When last_record_lsn was advanced using the WAL from the safekeeper, we reset the retry cooldown and exponential backoff, allowing walreceiver to reconnect to the same safekeeper instantly.

I'm not sure if walproposer actually relies on it
do, it doesn't


Build formal separation from metadata [WIP]

This is the start of an experimental effort to add the ability to add normal ECMA format metadata to reflection as an optional piece of work.
Included in this change is some ideas on to have both ECMA and NativeFormat metadata blobs co-existing in the binary (see handling of RuntimeAssembly and such), as well as some progress towards separating the NativeFormat metadata processing from basic reflection objects such as RuntimeNamedTypeInfo. I'm looking for opinions as to whether the general techniques I am using are reasonable, and any particular comments that you may have. I explored the idea of making this work via the long series of different assemblies, and found that it became even more complex than what we wrote out on the whiteboard, so instead I propose we'll have #if logic and some conditional compilation. (none of the #if logic is in place yet) These changes do not successfully run, but they do allow me to at least build the reflection core assembly.
PTAL @AtsushiKan @MichalStrehovsky
DO NOT MERGE THIS PR, its purpose is for review and comment only.

Having the subclassing hierarchy pivot on both the existing pivots and the metadata format could get out of hand.
Since you’ve decided to go for conditional compilation rather a parallel assembly universe, have you considering using partial classes (splitting things like RuntimeGenericParameterTypeInfoForTypes into agnostic and metadata-specific partial classes) for those Runtime* classes that
have no metadata format affinity in the signatures of their public (that is, public/internal/protected) members?
RuntimeNamedTypeInfo is the one guy that probably requires subclassing for this reason – I don’t think all the others do, though.

There’s no need to add a “reflectedType” parameter to CoreGetDeclaredConstructors(). Its omission wasn’t an oversight - BindingFlag lookups never probe inherited constructors, by fiat.)
Why was it made “virtual” rather than an “abstract”?

There’s no need to add a “reflectedType” parameter to CoreGetDeclaredConstructors(). Its omission wasn’t an oversight - BindingFlag lookups never probe inherited constructors, by fiat.)

Never mind – I was looking at the commits in isolation.

Which leads me to my next question: what is the purpose of the new “contextType” parameter? The “this” is already supposed to be the contextType with AnchoringTypeDef being the guy that maps it back to the definingType.

The purpose is that since the code now delegates to the defining type to generate the complete enumerator, the code that is generating the enumeration no longer has the right this. Therefore, it needs a parameter to know what to specify into the contextType of the constructed reflection method/property/event/field etc.

In reply to: 254835198 [](ancestors = 254835198)

I’m not sure why you didn’t just virtualize (or separate into a partial class) the metadata-specific parts of this method like you did with the other stuff. This is mixing up the purpose of the definingType/contextType separation.
Also, you turned the conditional “yield return” into a “return”. This is going to cause the enumeration of the synthetic methods and constructors to be skipped. (i.e. arrays of generic instances will no longer return their “special” methods.)

I'm not quite sure what you mean by this (split by partial classes). As far as I know one cannot have a C# file that can be used twice within the compilation of a single binary regardless of what you do with #if commands, unless we bring along the C++ preprocessor into the build. (Which would make me very sad) There is very little non-metadata specific logic in the generic parameter type infos, and the named type info is pretty reasonable that way as well. Additionally, there seem to be quite a few places that use the RuntimeNamedTypeInfo class as a construct directly to represent code that is working with a metadata based type, and I didn't want to lose that ability.
As far as the question, does this feel like the subclassing hierarchy is out of hand... well, generally yes, it feels like its very close to out of hand; however, this model of having a hierarchy of forms of type, intertwined with a hierarchy of metadata suppliers is what we've built in CoreRT land as well, and while it feels close to unworkable, it seems to stay just on the line of workable. I expect when I'm done to have about 20 files which are format specific, and the rest be ... normal.
For the specific case of the GenericParameterTypeInfo, and the method vs type variants of it, the current logic does seem pretty unfortunate. I believe we could refactor that so that the method vs type stuff was handled in a base class, and wasn't reliant on subclassing as well. Instead of storing a well typed typeinfo or methodinfo we could store an object reference, and use casting to determine what we should actually be doing. Is that what you'd prefer to see?

In reply to: 254827570 [](ancestors = 254827570)

So far as I can identify, AnchoringTypeDefinitionForDeclaredMembers returns null in all cases where SyntheticMethods/SyntheticConstructors are useful.

In reply to: 254890352 [](ancestors = 254890352)

Hmm… okay so it’s really single binary that can switch metadata formats at runtime. Subclasses, it is then. Good thing we got rid of the EEType/InspectionOnly pivot.

Instead of storing a well typed typeinfo or methodinfo we could store an object reference, and use casting to determine what we should actually be doing. Is that what you'd prefer to see?
Ummm… no.

I would prefer not to have that bit of luck be a hidden assumption.

I would still prefer, though, that the part of “CoreGetX()” that’s metadata-dependent be its own protected abstract member, and the existing GetCore() remain a non-virtual that delegates to that. Having these two distinguished only by contextType being null or not null is too subtle.

Ok, making CoreGetX non-virtual that can delegate to a virtual that implements the defining metadata model... that works for me. I'm just trying to avoid extra allocation of wrapper enumerators and such.

In reply to: 254917692 [](ancestors = 254917692)

Alright, so I'll make the detail that if there is an anchoring definition then we don't use the synthetics much more explicit.

In reply to: 254917051 [](ancestors = 254917051)

Well, this is really single binary that can actually do both formats at the same time. Agreed on the good thing we don't distinguish by EEType/InspectionOnly any more. That would have been ... messy.

In reply to: 254916854 [](ancestors = 254916854)

@AtsushiKan @MichalStrehovsky, I've added a new set of commits that finish up the work, and I believe I've resolved Ati's comments. Could you two take a look? My next step is to double check with testing that these changes are in fact completely non-impactful in terms of functional behavior.

The outer CoreGetDeclared* methods don’t need to be virtual anymore, right?
(as an aside, it’s unspoken convention in this assembly that any method that’s virtual or non-sealed override needs to have a comment stating what overrides it and why. Please do a pass to make sure we maintain that.)

Please add a comment for “#pragma warning disable CS0282” – what the warning is, and why we need to suppress it.

I think the new generic version of RuntimeNamedMethodInfo can just be called RuntimeNamedMethodInfo<> (without the "WithMetadata".) The name is already quite long.

On RuntimeEventInfo, you have new "internal protected" members. Who are the non-protected callers?

Now that VirtualRuntimeParameterInfoArray has been thrown out of the nest, it should be in its own source file.

NativeFormatRuntimeAssembly (and its overriding members) can be sealed, right?
(yes, it's another unwritten convention of S.R.Core to seal everything that isn't overridden/derived now. With such a complex hierarchy, every signpost helps...)

The ComputeGuidFromCustomAttributes overrides look like they could be sealed.

RuntimeGenericParameterTypeInfo#152 - there's a reference to NativeFormat that looks out of place in a format-agnostic file.

Addressed most of the feedback (except for moving VirtualRuntimeParameterInfoArray and a scrub for new comments on newly overrideable apis).
Also, replaced the extern alias use with somewhat uglier global:: namespace referencing to appease the internal build.

I'd rather see EcmaMetadataReaderExtensions.cs be named MetadataReaderExtensions.Ecma.cs to be consistent with other split files.
I don't care too much what the extension holder class is named - I think it's fine to leave it named "MetadataReaderExtensions" as this will catch ambiguous overloads that much faster.

Does Github really find it necessary to put a "close and comment" button right next to the "comment" button? :-(

"if (typeDefOrRefOrSpec.Reader is global::Internal.Metadata.NativeFormat.MetadataReader)"
this won't be the only time we have to ask this question: can you put a predicate (or MetadataFormatType property) on QTypeDefRefOrSpec?

Please add a comment for “#pragma warning disable CS0282” – what the warning is, and why we need to suppress it.

The outer CoreGetDeclared* methods don’t need to be virtual anymore, right?
(as an aside, it’s unspoken convention in this assembly that any method that’s virtual or non-sealed override needs to have a comment stating what overrides it and why. Please do a pass to make sure we maintain that.)

Any specific reason for renaming “RuntimeNamedMethodInfo” to “RuntimeNamedMethodInfoWithMetadata”? (the names here are already long…)

Deleted the last three "stale" comments - I made them yesterday from Outlook and Github apparently finally got around to surfacing them.

BTW, something to keep in the back of the mind - the longest path in this commit is about 50-60 characters away from hitting MAX_PATH (this is assuming that most people keep their repo's under c:\users<name>\Documents...) And there's of course, the ProjectN enlistments which add even more characters.
We might want to think about a few shortening strategies, though not as part of this commit...
Internal\Reflection rather than System\Reflection\Runtime (these never ended up being api'ized after all so they don't really belong under System)
TypeInfo -> Type for the RuntimeTypeInfo guys. TypeInfo is for all practical purposes a dead concept.
Maybe NativeFormat/EcmaFormat -> Native/Ecma.
Not sure if we need separate subfolders for Native vs. Ecma.

I imagine everything in MetadataReaderExtensions.cs is N-format tied, so probably want to rename that to MetadataReaderExtensions.NativeFormat.cs.

@MichalStrehovsky @AtsushiKan  I've now addressed what I believe to be all comments, and would like to see codereview for checkin. Ati, thanks for working with me on this.

Below is list of overrides which I think could be marked sealed (there may be false positives.) Can you do a quick pass over these.

QTypeDefRefOrSpec.Reader and Handle.
I wonder if these could be exposed as strongly typed extension methods (i.e. NativeFormatReader(), EcmaReader()), each set preferably in Native/Ecma-specific namespaces so that callers don't see the wrong one in Intellisense. (We could even elide the "NativeFormat" prefix from the method names in this case.)
It looks like there are only a couple of callers for Reader/Handle now so this would be good time to get on top of that before we start introducing casts from object/int everywhere.

"struct AssemblyBindResult" - this looks like it should be in file named AssemblyBindResult.NativeFormat.cs

Is "$(EcmaMetadataSupport)' == 'true'"" going to be true as part of the regular build (to avoid bit-rotting the Ecma part?)

MetadataReaderExtensions: "using NativeFormatAssemblyFlags = global::Internal.Metadata.NativeFormat.AssemblyFlags;"
I don't think the renaming/selective import is needed here. You already segregated the Ecma-dependent stuff into its own file.
There's similar instance in TypeLoader (except that there, AssemblyFlags isn't renamed to NativeFormatAssemblyFlags.)

Is the partial method "partial void GetNativeFormatRuntimeAssembly" really needed now? I would think AssemblyBindResult would eventually acquire a boolean property that tells you which format was returned.

About the AssemblyBindResult structure information that is specific to NativeFormat. I'd like to hold off on that change until we can make that delta from our internal build environment. Otherwise, I'll have to deal with a build break on integration.

The renaming/selective import is critical, as AssemblyFlags is in the System.Reflection namespace in the ecma metadata reader. This is why there are seemingly non-sensical fully qualified names in a variety of places.

I don't believe we should change the QTypeDefRefOrSpec handle to have extension methods etc, more than it does now. I don't believe I have a good handle on what a better api surface would be, as I don't have a sufficient understanding of what will actually use these other than the existing TryResolve and Resolve extension functions (which look fine to me).

AssemblyBinder.cs: sp "garaunteed".

If you move an override down into new subclass (specific example is RuntimeAssembly.Equals/GetHashCode being moved down to NativeFormatRuntimeAssembly, but there are likely others), please add an "abstract override" declaration to the original. This serves as a forcing function to ensure that the all leaf classes override the (not useful but impossible to change) versions in the public api type (in this case, System.Reflection.Assembly)
This will be especially useful in cases where you haven't yet added the Ecma version of the subclass.

Below is a list of api implementations that I believe are now "leaking" from the public api types into the Runtime versions. Just add an "abstract override" for these. (Yes, another unspoken discipline in this assembly...)
System.Reflection.Runtime.Assemblies.RuntimeAssembly
==========================================================================================================
CustomAttributes.......................
DefinedTypes...........................
Equals(Microsoft.Cci.DummyNamespaceType

ExportedTypes..........................
GetHashCode()..........................
GetManifestResourceInfo(Microsoft.Cci.D
GetManifestResourceNames().............
GetManifestResourceStream(Microsoft.Cci

System.Reflection.Runtime.EventInfos.RuntimeEventInfo
==========================================================================================================
Attributes.............................

CustomAttributes.......................
Equals(Microsoft.Cci.DummyNamespaceType

EventHandlerType.......................
GetHashCode()..........................
MetadataToken..........................

System.Reflection.Runtime.FieldInfos.RuntimeFieldInfo
==========================================================================================================
Attributes.............................
CustomAttributes.......................
Equals(Microsoft.Cci.DummyNamespaceType
GetHashCode()..........................
MetadataToken..........................

System.Reflection.Runtime.PropertyInfos.RuntimePropertyInfo
==========================================================================================================
Attributes.............................
CustomAttributes.......................
Equals(Microsoft.Cci.DummyNamespaceType
GetConstantValue().....................
GetHashCode()..........................
MetadataToken..........................

RuntimeMethodCommon.cs should now be named IRuntimeMethodCommon.cs.
RuntimeMethodHelpers should be in its own file.

@AtsushiKan I believe I am up to date with all of your comments

Ok, assuming it passes CI, it LGTM.


Adds verify + secure boolean to ClickhouseCredentials

Allows users to specify clickhouse-driver Client options:

secure if their ClickHouse instance is behind a secure port
verify if ssl verify should be performed.

(both defaulted to False)

Thanks!


Detect/correct invalid HP/LP settings in EDF/BDF/GDF

Fixes #8582. EDF/BDF/GDF files can contain invalid LP/HP filter settings (cutoff frequencies for HP can be greater than the one for LP). This PR (1) issues a warning and (2) sets HP/LP values for affected channels to None.

@apospraf loading files from BCI Competition IV 2B works as expected with this PR.

NumPy installation fails in one job?

Please go ahead and add a test, I won't have time until tomorrow.

I don't think the current approach quite works properly, for example it doesn't handle '0.0' and '0.000' because they are strings
>>> '0.0' < '0.000'
True

Moreover sometimes edf_info['highpass'] can have length zero and edf_info['lowpass'] can have length n_channels, which fails the NumPy < comparison on latest NumPy dev. It seems safer to deal with these being reversed when actually setting info['highpass'] and info['lowpass'], but maybe not. I'm pushing a commit with this approach and a test that asserts it works for the monkeypatch code at least.

@cbrnr all good now?

Yes, perfect!


[NSE-243]adding mvn scalafmt

Signed-off-by: Yuan Zhou<EMAIL_ADDRESS>What changes were proposed in this pull request?
adding scalafmt tool
How was this patch tested?
no tests required

@weiting-chen this can help to fix some of the scala format issue
mvn -pl native-sql-engine/core mvn-scalafmt_2.12:format


producer never recovers after network split

I have no good steps to reproduce, especially since this requires breaking the network (or killing the broker) in the right way and is potentially timing related. I'm especially hazy on how to get into this state, though I'm fairly certain on the effects this causes in racecar. I'll provide the investigated variant, though I have more production logs available on demand.
Roughly:

racecar is up and operating fine
introduce a network split to lose connection to all brokers. Everything will be considered down from librdkafka point of view.
eventually restore connection again
racecar will clear stuck rdkafka consumers through ConsumerSet#reset_current_consumer in certain scenarios. This was enough to eventually receive messages again.
publish a message (in reaction to the just received ones). Adding it to librdkafka's queue will work. However, it will fail in Consumer#deliver! since there is no broker connection, so rdkafka eventually throws a WaitTimeoutError. Note that the method exits before calling @delivery_handles.clear. This is fine, a handle can be waited upon multiple times.
The error bubbles into the pause handling, pausing this topic-partition for some time.
eventually we will receive another message; doesn't matter which partition it is from. Eventually it will try to @delivery_handles.each(&:wait) again, which waits on the first message described in step 5.
after enough retries, and once message.timeout.ms is exceeded, librdkafka will throw msg_timed_out which means that it has given up. The message will not be sent.

At the very least, racecar should remove these finally failed messages/handles from @delivery_handles. Even if the producer eventually recovers, these failed messages will result in head of line blocking. Of course, as is today, racecar should still fail on those so that the single message or the whole batch block gets retried.
That being said, this might not be enough. From the statistics librdkafka makes available, I know that all producer broker connections were in state: "INIT". I still have to check if this is the default and librdkafka only connects on first use, or if it indicates librdkafka was additionally stuck for another reason.

(I intend to provide a PR on this, but I need to finish the investigation first)

nope, even for consumer only the producer will be in state: "UP" immediately after boot. So I'd say the producer was additionally stuck. I propose the following:

if we run into unrecoverable producer errors like msg_timed_out, we reset the producer in a similar fashion we already to for the consumers – close them, and recreate.
we clear the @delivery_handles whenever the producer is (re)set.

I'll see how to get that in without breaking API changes, since former is handled in runner.rb, but latter are on the consumer.rb. The similar handling for consumers in the consumer_set.rb, so this will be some fun.


Athena: changing schema in SQL Editor does nothing

System information:

Operating system (distribution) and version Win10
DBeaver version 21.1.5
Additional extensions

Connection specification:

Database name and version Athena

Describe the problem you're observing:
Queries are always executed on default schema even if it is changed in SQL editor
Steps to reproduce, if exist:

Change schema in SQL editor to any other than default
Run select form a table from selected schema

Expected: Query is executed from correct schma
Actual: Query is executed form default schema

I think this relates to https://github.com/dbeaver/dbeaver/issues/11196


Move docs to ko.build

This copies content from README.md into separate docs in docs/, and uses mkdocs-material to generate a static site that's served from GitHub Pages, in the gh-pages branch.
A preview of this site served from https://github.com/imjasonh/ko.build is available at https://ko.build -- when this merges and is published I'll update the domain to point to this repo's site and archive that one. I'll also update our README.md to link to ko.build instead of duplicating content.
This also moves generated CLI docs from doc/ to docs/reference/, so we don't have to keep two copies in sync.

Codecov Report

Merging #749 (5e43025) into main (9139f45) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #749   +/-   ##
=======================================
  Coverage   51.19%   51.19%
=======================================
  Files          44       44
  Lines        3313     3313
=======================================
  Hits         1696     1696
  Misses       1404     1404
  Partials      213      213

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 9139f45...5e43025. Read the comment docs.

Flipping this to Draft since we'll need a google GH org admin to set up the domain. This shouldn't block the 0.12 release.

I'd like to get this merged so we can start running ko.build out of this repo instead of out of my personal repo.
This change also sets us up for the ko.build importpath, which will let us change the module name in 0.13 (e.g., go install ko.build, import "ko.build/pkg/build", etc.


Support auth for QueryRunner

Support auth for QueryRunner
Some refactor

We're currently processing your upload.  This comment will be updated when the results are available.

Should this AuthUtils class be part of pinot-tools? or should it be in pinot-common ?
Reason being, we may want to avoid running into issues where any changes in Auth handling aren't replicated in the pinot-tools class and thus breaking the commands.

Should this AuthUtils class be part of pinot-tools? or should it be in pinot-common ?
Reason being, we may want to avoid running into issues where any changes in Auth handling aren't replicated in the pinot-tools class and thus breaking the commands.

moved


Version has weird suffix

Do we want to keep the post0 suffix?
https://pypi.python.org/pypi/afp-cli/1.2.0.post0

Let's talk about this topic in #6


examples: fix crash

If the initial window size does not fit on the screen, a resize event is triggered. This occurs at the very beginning after pushing to the canvas, at a stage when the buffer should not be accessed and changing the target is not possible. To prevent this situation, resizing is paused until rendering to the initial target is completed.

@mgrudzinska could you please check with this fix? https://github.com/thorvg/thorvg/pull/2469

yes, I'll check, this is one not the correct way of solving this problem, so I'll close it


Ensure the body parameter name is preserved

For https://github.com/swagger-api/swagger-parser/issues/966
Related: https://github.com/swagger-api/swagger-parser/issues/748

Is there any feedback on this PR?
Are you rejecting the proposition?
Or have you any concerns about this?
A while ago I did open a similar issue about preserving the name of the body parameter from the v2 Spec as extension in v3: #748
Back then I proposed an other approach (an other name, an other position of the extension), but the idea is the same and for me this would also be OK.
Please let us know if we can do anything to help this feature to moving forward (this PR can be rewritten if an other design decision is considered)

please build

@wing328 could you please describe the purposes of this "x-codegen-request-body-name" extension. I am trying to figure out it and decide is it needed in my case or not. Am I right that it's needed for code generation in some languages?


Spanner: TestDataTypes timing out on CI

After 10 minutes. (Locally it passes after around 2 minutes.)
I've skipped it in #1001 but it should be looked at.
One thing would be to separate out in single tests. At least we could isolate the culprit easier.
@skuruppu feel free to assign to someone from your team that can take care of it.

I hadn't noticed this flakiness since it seems to run fine locally. I didn't mange to dig into this today but I will take a look early next week.

Yes, no rush, when you can. Admittely I've been noticing more timeouts than usual this past couple of weeks, not just Spanner, but other APIs as well.

Yikes, it's been almost a week and I still haven't had a chance to get to this. @laljikanjareeya would you please be able to take a look at this test? Thanks so much.

Thanks both.
@laljikanjareeya I wasn't able to reproduce locally. I think that separating out into single tests might help with finding out where it's really timing out.


Revert option to programatically add lasers and dacs

Hi Seb,
I am working with Gijs on his project.
In the project we use the sendRawPoints on the 3 lasers we have. this method uses the lasernumber as value.
Because the lasers cannot programatically be set now with the new version, we can never make sure they are set.
Currently I get a vector out of range in the update loop. As the update loop starts running directly after boot and directly tries to send points to a laser that does not exist yet.
If we revert the option to programatically set the lasers (with dac (IP) setup) it is again possible to setup the laser setup at application startup. I think this can work the same way as the add laser button in the gui does.
What are your thoughts about this?
Greetings Friso

Hey Friso,
Thanks for letting me know about this. My suggestion is :
1 : Let me fix the code so it doesn't throw an error when the laser number
is out of range
2 : You can set up the 3 lasers within the app... every time you run it
from now on the 3 will be set up.
3 : Choose the relevant etherdream from the dropdown menu in the laser
settings (it no longer relies on IP address so will always find the DAC
based on its MAC address)
When you restart the app, the etherdream allocation should be remembered by
the system. But for now you will have to click the "Refresh controller
list" button as it doesn't always find the ether dreams during the start up
process. (I will fix this in a later release so that the dac list will be
updated automatically as they are discovered).
Hope this helps!
Seb
On Mon, 21 Jun 2021 at 14:15, Friso Modderman @.***>
wrote:

Hi Seb,
I am working with Gijs on his project.
In the project we use the sendRawPoints on the 3 lasers we have. this
method uses the lasernumber as value.
Because the lasers cannot programatically be set now with the new version,
we can never make sure they are set.
Currently I get a vector out of range in the update loop. As the update
loop starts running directly after boot and directly tries to send points
to a laser that does not exist yet.
If we revert the option to programatically set the lasers (with dac (IP)
setup) it is again possible to setup the laser setup at application
startup. I think this can work the same way as the add laser button in the
gui does.
What are your thoughts about this?
Greetings Friso
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sebleedelisle/ofxLaser/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA3CEVAMFZGVV3WH4NKPNTTT43P3ANCNFSM47BR7KKA
.

I think this would be a good solution, I'm looking forward to the fix.

OK I've implemented those changes, let me know if they work for you!

I'm gonna close this for now, let me know if you have any more issues, thanks!

works like a charm! thanks!


Weather app project

In this project I:

Wrote functions that ht API returning weather location.
Wrote functions that processes fetched JSON data
Set up a form for location search
Display information on page
Add styling to the UI

Thanks @uche-inyama for the review and the good to have suggestions.


[METADATA UPDATE][Merge by 2024-01-26] Retiring the ms.prod and ms.technology metadata attributes from the Learn platform (values moving to ms.service)

A Pull Request has been made from the Learn Platform's Metadata Management System. Please review and merge this Pull Request within 5 days. If you have any questions or concerns about the purpose of these metadata updates, please contact<EMAIL_ADDRESS>If you are not the correct contact for this content and repository, please notify<EMAIL_ADDRESS>If this Pull Request is not merged within 14 days, it will be automatically merged by our system to ensure the timeliness of the metadata update. This includes bypassing the Repository's Branch Policy, including if Review Required is enabled. Please notify<EMAIL_ADDRESS>if you have questions or concerns or would like Pull Requests for metadata updates to merge automatically in future.
Summary
In Germanium, we will be retiring the ms.prod and ms.technology metadata attributes from the Learn platform and consolidating values into ms.service and ms.subservice for reporting on content by product.
C+E Skilling Content Architecture manages internal, business-facing taxonomies that enable reporting on key metrics for content published on Microsoft Learn. Authors manually apply values from these taxonomies to populate metadata attributes.
Two of these taxonomies are ms.prod/ms.technology and ms.service/ms.subservice. "ms.prod" and "ms.service" were distinctions carried over from legacy systems that predated the Learn platform, intended to differentiate on-prem products from cloud services.
In Germanium, we will retire ms.prod/ms.technology and migrate metadata to the ms.service/ms.subservice attributes. We plan to rename the attributes from ms.service and ms.subservice in a future semester.
Why are we making this change?
For the business: Accuracy of reporting metadata directly impacts the accuracy of content analytics, so it's important that related taxonomies reflect the current state of the business. Most product taxonomies within Microsoft no longer distinguish between "on-prem" and "cloud service."
For content authors: We eliminate the need to choose between two similar attributes when applying reporting metadata to content or filtering reports.
For engineers, data scientists, and taxonomists: Simplifying and reducing underlying metadata attributes reduces the cost and complexity required to extend metadata capabilities on the platform.
Frequently Asked Questions
Why does this Pull Request appear to be made by the Repository Owner? We open Pull Requests two different ways.
For Git Repos with a permissioned Service Account, we open the PR from our Document Build Service Account.
For Git Repos that we either do not have Service Account permission for or the repo is in Azure Repos (ADO) we open the Pull Requests in an automated way with the PR creator as the Repo owner.
How can I revert a Pull Request that has been merged and created an unexpected issue? Whether a PR has been merged manually or automatically, you can revert it if an issue arises. See Reverting a pull request - GitHub Docs.

directly merge, other left ms.prod to unblock other retag work


WIP Fix needed when stack_uuid is set for standalone containers

For standalone_containers, service_uuid is nil, so added a check before we look up the service using the service_uuid for containers. Otherwise this thrown nil panic.
This is WIP because this depends on cattle:master (to add stack_uuid to container metadata)
This PR is part of rancher/rancher#8790

We are not going to do this for 1.6


chore(autoware_pcl_extensions): refactored the pcl_extensions

Description
Refactored the former tier4_pcl_extensions to autoware_pcl_extensions
Related links
Parent Issue:

Link

How was this PR tested?
Checked that the filter using the classes from this package could be launched correctly
Notes for reviewers
None.
Interface changes
None.

Effects on system behavior
None.

@technolojin
PCL extensions are usually kept inside the pcl namespace, so I did not change them to the autoware one for now. If you consider it necessary, I will move it though.

@drwnz remember this one please :pray:

@drwnz


[WIP] Make Markdown formatter math-safe

Addresses #228
Only failing tests for the moment - see notes below. Some of them should be failing (because the formatter formats them) but others are definitely bugs.
The formatter is run twice, to turn up additional bugs where the "formatted" output is not stable under repeated formatting.

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

@jonatanklosko FYI, I've had reasonable success today with rewriting MarkdownHelper to manipulate the output of EarmarkParser.Parser.parse_markdown directly; by working at the level of EarmarkHelper.Block structs instead of HTML AST we could avoid a lossy blocks -> AST -> Markdown flow.
A two-line change to EarmarkParser saves the "fence" characters in the Block.Code struct, which allows a straightforward fix to tests like code block with fences inside it (put the same fence back that was used in the original)
Aiming to push up more changes tomorrow AM; stay tuned.

I wonder if adding optional math jax support to Earmark is a simpler route to tackle this.

@josevalim The ultimate motivation of this work is to add optional MathJax support (at least with $ and $$ delimiters). Somewhere under all this yak hair... :P
My approach so far has been to add tests that probe the current behavior of the parser / formatter to ensure that changes don't accidentally break existing livemd files. (Or lead to undesirable behavior - I did a buggy refactoring that had every \n doubling every time a file was formatted!)
The biggest issue that this has turned up is with escaped characters - rendering to HTML un-escapes them. For instance
In that test, the internal Block.Para still has the escaped text:
%EarmarkParser.Block.Para{attrs: nil, lines: ["\\[foo\\]()"], lnb: 1}]

Based on that, I'm trying the previously-mentioned rework of MarkdownHelper.markdown_to_ast" to use lists of blocks. After that I plan to try updating LiveMarkdown.Import.rewrite_astandLiveMarkdown.Export.rewrite_ast` to transform blocks instead of HTML AST; should be mostly adjusting pattern-matches.
The last step: add plumbing to earmark_parser to optionally return new Block.Math (bad name) structs when it sees $$ fences, and update Livebook to handle those. Very Kent Beck

@al2o3cr I tried a simpler approach in #487 and copied the relevant tests. Thanks for all the investigation so far, it's been very helpful! If you have any thoughts on the solution let me know :)

:cat2:

@jonatanklosko In general, I'm not a fan of re-parsing the output of EarmarkParser.AstRenderer solely to undo its work; adding an option to skip part of that work doesn't seem like the correct direction.
I'm also suspicious that this still doesn't solve the whole problem - going to poke at what happens when a $$ block contains Markdown-looking text, like:
Plain text plain text plain text

$$
1. Blah blah blah
$$

@al2o3cr what do you mean by re-parsing? What now parse the blocks structure (which we need to properly interpret livemarkdown), but we skip inline parsing of paragraphs, which we don't need to look at and just treat them as opaque.


Any plan to make it for textarea?

I'm building application like iconfinder / flaticon the tags input is in table, the full td is the size of image 512x512 a line of input doesn't seem nice, even if i try to expand the size with min-height:100% the tags go in middle of input type='text' and all empty space on top and bottom are useless. any suggestions?

Would something like this work? You basically set the size of the wrapper div instead of manipulating the input field.
If not, can you provide a JSFiddle?

Please have a look on this fiddle I've reproduce the problem i am facing, the tags and the input cursor are in middle, what i want is to make them natural like textarea or like that image you have display above.. Please let me know where i am doing wrong, and if there is any possibility for textarea tagsinput update
Thanks, looking forward for your response.


Model checkpoints are not available

The link doesn't seem to work.

Same.
Failed to reach the google drive link.

Hi guys, I apologize for the inconvenience. The school Google Drive hosting our model checkpoint has been terminated. I'm looking into retrieving it and will update you as soon as possible.


[stable/jenkins] Add different Deployment Strategies based on persistence

RollingUpdate isn't supported when using persistence, since it doesn't support sharing a RWO PV.
PR add supports for having Recreate as a strategy if persistence is enabled, as opposed to the default RollingUpdate
What this PR does / why we need it:
Fixes https://github.com/kubernetes/charts/issues/3154
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
From OpenShift docs (https://docs.openshift.com/container-platform/3.6/dev_guide/deployments/deployment_strategies.html):
When to Use a Recreate Deployment [...] When you want to use a RWO volume, which is not supported being shared between multiple replicas.
Signed-off-by: Tore S. Lønøy<EMAIL_ADDRESS>

No sure what is failing, let me know if I can help

@toredash you'll need to increment the version number in Chart.yaml (as per the output from circleci).

@jlegrone sorry for not catching that, fixed

/ok-to-test

/assign @lachie83

/test all

@lachie83 anything else that I can help with ?

/assign @ lachie83

I'm not sure what I can do to get this merged?

/assign

/retest

/retest

@toredash please undo c36e080851d392aa004f9e2b506f265797701129 (perhaps you rebased after merging master?) and rebase your branch from master so that only your commits show up in the pull request.
You are also now required to sign off on your commits, which you can do by using the --signoff flag with git commit.  To sign off on your latest commit, you can run git commit --amend --signoff.
Thanks! 😄

The DCO instructions are not to clear, when I try to sign of as requested it includes other commits not from me.
Clearly I do not know this well enough

@jlegrone Finally all the check passes, thanks for being patient and giving me instructions on how to proceed.

/lgtm


Ensure type for Widget class parameters. See #984

Added a method to General class to facilitate variable type check. Useful in other areas as well.
Amended Widget class with parameter type check. See #984.
Thanks !

All in all pretty solid approach. It can be cleaned up a little when we move to a PHP5.3 only codebase, but for now this will help. I'll pull in once the inline changes are done and do some regression and performance testing.
Thanks very much :)

All in all pretty solid approach. It can be cleaned up a little when we move to a PHP5.3 only codebase

What could be improved with 5.3?

What could be improved with 5.3?

Reflection is more stable in PHP5.3+ from my experience

Wait with this one. There are a few glitches with Widget::Input(). some extensions (resaveentries, multilingual_field and SBL for the moment), use the $value parameter as integer. That isn't so bad, but the current constraint allows only strings => very bad.
Possible fixes:

Accept integer as well for $value parameter.
or
Update all extensions that send an integer instead of string.

Pulled in and implemented. Thank you for this and sorry for taking so long!