api_documentation: Document "/invites/multiuse/{invite_id}" endpoint.

This PR adds API documentation for "/invites/multiuse{invite_id}" endpoint.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@Vector73 - Looks good to me! Marking for integration review.

Merged, thanks @Vector73!


Check for existing Starfield's save file before proceeding

#24

Thanks for the PR, but I'm not quite sure if skipping possibly missing parts can produce working save files.
From what I gather, the missing files can be caused by incomplete cloud save synchronization.

Thanks for the PR, but I'm not quite sure if skipping possibly missing parts can produce working save files. From what I gather, the missing files can be caused by incomplete cloud save synchronization.

I tried to extract save files and it is work. But the lastest save file is empty(0 byte).
Starfield limited storage size of save directory, and it would not create a new save and notice you to delete some save files when you want save game. And i think the empty save file is cause by this reason.
After i use this modified main.py to extract saves, i pick up the latest and not empty files import to xgp and readable by game.
i highlight a save entry in "containers.index". with your code, the "s4" string in the picture seem to definition which folder contains this save file. so if this folder just an empty folder so it's not have "container." file, and skip this folder seem jsut skip a save entry.

I added checks and warnings for missing files in 1e07f59.


[CAMEL-17841] Add checkpoint batch size & timeout parameters

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/main/CONTRIBUTING.md

So maybe make a PR that is batch size only as a first PR. And then work on timeout/interval as a 2nd PR that uses a background thread.

implemented but not tested yet

@kevinlacire can you please rebase?

@kevinlacire can you please rebase?

I'll take some time to do it tomorrow

Do you have an example ? I can take a look to adapt it using Camel's ExecutorServiceStrategy

Maybe take a look at LRASagaService how it creates the thread pool and start/stop it etc.

This has been merged


why not scrollHeight ?

I clone your plugin and change offsetHeight by scrollHeight to fixe a bug.
Because my slide has margin.
An little example : https://codepen.io/anon/pen/BYGvEw
https://github.com/kunukn/react-slide-toggle/blob/970b7dcf642eef7bcbb0f0534f29fd0ac93004e7/src/library/ReactSlideToggle/SlideToggle.js#L25

I added it to a const so you can easy change it to scrollHeight if needed. const GET_HEIGHT = 'offsetHeight';  It is correct that this version with offsetHeight does not (currently) support margin. In my examples i use a wrapper div and applying padding instead of using margin.
The reason I chose to use offsetHeight over scrollHeight  in this library is because I have experienced that the calculation was not always correct with scrollHeight  for some browsers when the content has flexbox with images. I might be wrong and could do some more testing for clarification. It remember it was due to usage of scrollHeight when the element is collapsed that gave some wrong values with combination of flexbox and images content. I remember the browser being Safari but can't say for sure.

Ok , finaly, I use a wrapper div and applying padding instead of margin. And it's works.
Nice works!


Feature | Added LineNumbers Property to Code Block

Closes #1241

@LukeHagar I made a number of changes:

Moved the CSS to Element styles, to match conventions with the rest of the library
Improved the line number spans to have a fixed width. Otherwise each digit would shift things to the right by that amount. (ex: 10, 100, 1000 would be uneven)
Adjusted the demo text just slightly and implemented the opt-in typography
Dropped a const no longer used in the codeblock logic

Per the typography, this is a new addition this release. Be sure you're doing your PRs against the lastest dev updates, it seemed you were a bit behind so the title and code tag showed like this:


Update the port to be an integer.

Fix the port to be an integer. Use the format function for string formatting.
ref #3667

Thanks @NikosVlagoidis. I've also added a tweak to make the trigger name match between the yaml & .py - they were not in sync before, which causes issues with dispatching triggers.

@LindsayHill Yes, I think I correct it manually too but forget about it. Nice!


[WFCORE-4716] Upgrade Byteman to 4.0.8

https://issues.jboss.org/browse/WFCORE-4716

@ropalka thanks


Trojan:AndroidOS/Multiverze

pip-unpack-q1g8gukw\pyinstaller-5.7.0-py3-none-win_amd64.wh

This has been reported to Microsoft


JavaScript heap out of memory only when serving via Vue UI ( --dashboard argument causes issue )

Version
4.5.12
Environment info
Environment Info:

  System:
    OS: Windows 10 10.0.19042
    CPU: (12) ia32 AMD Ryzen 5 5600X 6-Core Processor
  Binaries:
    Node: 14.18.2 - C:\Program Files (x86)\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.15 - C:\Program Files (x86)\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.55)
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.0
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.13
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.13
    @vue/cli-plugin-babel: ^4.5.13 => 4.5.13
    @vue/cli-plugin-eslint: ^4.5.14 => 4.5.14
    @vue/cli-plugin-router:  4.5.13
    @vue/cli-plugin-typescript: ^4.5.15 => 4.5.15
    @vue/cli-plugin-unit-jest: ^4.5.13 => 4.5.13
    @vue/cli-plugin-vuex:  4.5.13
    @vue/cli-service: ^4.5.13 => 4.5.13
    @vue/cli-shared-utils:  4.5.13 (4.5.14, 4.5.15)
    @vue/component-compiler-utils: ~2.6.0 => 2.6.0 (3.2.2)
    @vue/eslint-config-standard: ^5.1.2 => 5.1.2
    @vue/eslint-config-typescript: ^9.1.0 => 9.1.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/test-utils: ^1.0.0-beta.30 => 1.0.0-beta.30
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^8.0.1 => 8.0.1 (7.20.0)
    eslint-plugin-vuetify: ^1.1.0 => 1.1.0
    jest-serializer-vue: ^2.0.2 => 2.0.2
    portal-vue: ^2.1.7 => 2.1.7
    typescript: ^4.5.4 => 4.5.4
    vue: 2.6.14 => 2.6.14
    vue-analytics: ^5.12.3 => 5.16.2
    vue-apollo: ^3.0.5 => 3.0.5
    vue-chartjs: ^3.3.1 => 3.4.0
    vue-cli-plugin-vuetify: ^2.4.3 => 2.4.3
    vue-clipboard2: ^0.2.1 => 0.2.1
    vue-eslint-parser:  7.11.0 (8.0.1)
    vue-hot-reload-api:  2.3.4
    vue-input-facade: ^1.3.7 => 1.3.7
    vue-jest: ^3.0.5 => 3.0.5
    vue-loader: ^15.9.8 => 15.9.8 (16.8.2)
    vue-router: 3.5.3 => 3.5.3
    vue-style-loader:  4.1.3
    vue-template-compiler: 2.6.14 => 2.6.14
    vue-template-es2015-compiler:  1.9.1
    vue2-dropzone: ^3.5.2 => 3.5.2
    vue2-google-maps: ^0.9.6 => 0.9.8
    vuetify: 2.6.0 => 2.6.0
    vuetify-loader: ^1.7.3 => 1.7.3
    vuex: 3.6.2 => 3.6.2
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
Cannot be reproduced outside of current environment/project. However this thread seems to indicate far more devs have had this issue: https://github.com/vuejs/vue-cli/issues/1453
Only occurs when running serve through the Vue UI. It appears that the --dashboard argument triggers this problem. Without it, serving runs just fine.
What is expected?
That the vue cli operates as expected when serving
What is actually happening?
It builds, and then crashes. But only when the --dashboard argument is present

This problem cropped up after adding TypeScript support, and upgrading most of our packages. I have been unable to narrow it down to anything specific.
Build Log/Error:
NOTE: I added --max-old-space-size=4096 in an attempt to resolve the issue, it did not have any effect.

npx --max-old-space-size=4096 vue-cli-service serve --mode development --dashboard

INFO  Starting development server...
Starting type checking service...
Using 1 worker with 2048MB memory limit
65% building 639/687 modules 48 active ...node_modules\core-js\modules_shared.jsBrowserslist: caniuse-lite is outdated. Please run next command npm update
98% after emitting vue-cli-dashboard-plugin
DONE  Compiled successfully in 46972ms                                                                                12:51:03 PM
No type errors found
Version: typescript 4.5.4
Time: 11382ms
WARN
Couldn't parse bundle asset "C:\Users\Douglas\Documents\01 Programming\Platt\Sales\Sales.Frontend\dist\js\0.js".
Analyzer will use module sizes from stats file.
<--- Last few GCs --->
[7572:00A40598]    50576 ms: Scavenge 842.4 (1005.1) -> 842.0 (1007.9) MB, 1.5 / 0.0 ms  (average mu = 0.988, current mu = 0.863) allocation failure
[7572:00A40598]    50725 ms: Mark-sweep (reduce) 842.0 (1007.9) -> 837.2 (989.3) MB, 148.9 / 0.0 ms  (average mu = 0.962, current mu = 0.461) last resort GC in old space requested
[7572:00A40598]    50898 ms: Mark-sweep (reduce) 837.2 (977.3) -> 835.8 (965.8) MB, 173.1 / 0.0 ms  (average mu = 0.906, current mu = 0.000) last resort GC in old space requested

Given when the error happens, after building,  and only when the --dashboard flag is present (Which enables IPC to cli-ui nodejs server ) is this issue occurring in another process?
What further debugging can be done to figure out where/how/why this is occurring, and what workaround are available?

If you are using Windows like me, you can try to use cross-env NODE_OPTIONS=--max-old-space-siz e=4096 node 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js' run serve


Custom Environment with Discrete (Binary) Action Space Always Choosing 0

Describe the bug
I am trying to implement a relatively simple custom environment with a Discrete (Binary) action space. However, as soon as I start the learning process I get the following error coming from the call to
tf.clip_by_global_norm(grads, self.max_grad_norm)
in self.setup_model()
InvalidArgumentError (see above for traceback): Found Inf or NaN global norm. : Tensor had NaN values 	 [[node loss/VerifyFinite/CheckNumerics (defined at c:\users\ben\documents\stable-baselines\stable_baselines\ppo2\ppo2.py:168) ]]
If I set max_grad_norm=None, then the learning process runs, but the loss immediately goes to NaN. For the record, this is the case for several RL algorithms (PP02, ACER, ACKTR) using an MlpLstmPolicy.
Could this be a problem with how I've defined by environment, or is this a known issue?
I'd appreciate any guidance.
UPDATE: Out of curiosity, I switched the action space to box, and the actions are nan at the start of learning

@bglick13 did you find a solution for this? I'm currently seeing the same thing with a custom environment and discrete action space.

Hey @Jyosua, I'm not sure I ever did. I think I ended up using a different library. Sorry!

Related #358


Changed testnet superblock cycle from hourly to daily for more realistic testing (requested by Evan)

I suggest we hold off on merging this.  We still have some issues to debug with governance object propagation and this PR will make testing very slow.

@tgflynn I agree we should hold off merging this

I was just using daily as an example, I think hourly was probably better actually. More chances to test will yield better results for us I think


Converting HEIF to PNG does not work

Possible bug
When doing:
const data = await sharp(input)   .png()   .toBuffer();
On a HEIF type of file,
I get:
"heif: Unsupported feature: Unsupported codec (4.3000)]"
Is this a possible bug in a feature of sharp, unrelated to installation?

[ X] Running npm install sharp completes without error.
[ X] Running node -e "require('sharp')" completes without error.

Are you using the latest version of sharp?

[ X] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

Is the HEIF file using AV1 (AVIF) or HEVC (HEIC) compression? Did you see https://sharp.pixelplumbing.com/api-output#heif ?

Support for patent-encumbered HEIC images using hevc compression requires the use of a globally-installed libvips compiled with support for libheif, libde265 and x265.

Yes I am using HEIC as the input. Do you have any instructions for installing libvips globally and getting the conversion to work?

Did you see https://sharp.pixelplumbing.com/install#custom-libvips ?

Did you see https://sharp.pixelplumbing.com/install#custom-libvips ?

I doubt this can work inside of a Google Cloud Function. I couldn't find any ways of using Meson inside of Google Cloud to install dependencies.
Unless you know any work arounds?

Waiting for the HEVC patents to expire (c2036) will probably take less time. Good luck!

@lovell I'm a bit confused, so what exactly do we do to solve this issue?

If you're dealing with patent-encumbered HEVC-compressed HEIC files and use a third-party runtime environment over which you have limited control then sharp is probably the wrong solution to your problem.


fix sample code in docs/core/events.md

Added argument event if necessary, and removed argument if unnecessary in sample code in docs/core/events.md

Nice, thanks!


Control Center Release 1.5.0

@MarkvanMents for your awareness of Cloud info in Control Center, please take a look and see if you have any changes.


Error details from various state

This adds an ability to append context to an error, from various feature contexts.
Sometimes it is important to have some state listed when a step fails, this state may be gathered from a number of different contexts.

This example shows how it can be used. What is your opinion on this @mroth in general, user might create and wrap error in the same way, but that would introduce some boilerplate. Though, godog may manage it correctly for various formatters and indentation.

Codecov Report

Merging #83 into master will decrease coverage by 0.32%.
The diff coverage is 58.33%.

@@            Coverage Diff            @@
##           master     #83      +/-   ##
=========================================
- Coverage   80.73%   80.4%   -0.33%
=========================================
  Files          15      16       +1
  Lines        1879    1909      +30
=========================================
+ Hits         1517    1535      +18
- Misses        277     289      +12
  Partials       85      85

Impacted Files
Coverage Δ

suite.go
78.14% <100%> (+0.06%)
:arrow_up:

fmt_progress.go
100% <100%> (ø)
:arrow_up:

fmt_pretty.go
72.44% <7.14%> (-2.97%)
:arrow_down:

errors.go
85.71% <85.71%> (ø)

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 92fbee7...1349d7b. Read the comment docs.

Hmm, I can't immediately think of a case where I don't have access to the context in my actual steps (since I'm typically writing them as methods on a context), but since this only gets wrapped later, from an end-user perspective you can still simply return a normal error when writing a step, it doesn't seem to add too much complexity.
It may also be possible to do this by simply rewriting the error message (e.g. appending "\n" + foo) in the after step, but that obviously gives you less formatting control than a collection of attachments.

For big projects, you may have various contexts. Like: QueueContext, APIContext, SeleniumContext, UserContext all of them may provide some steps and some of them may have internal state, which may be useful to see if one of steps fails, like

SeleniumContext - making a screenshot and saving html body, if selenium is used for that scenario
QueueContext - may dump all items currently in the queue
APIContext - could dump last response received information
UserContext - currently logged in user, his permissions

In general, each of these contexts, could append some of the details after any step fails. That often makes things much more visible and saves debugging time.
Since this extension, does not add much to public interface and will most likely be useful for attachment like behavior, which may be built in into the gherkin, I may include it later after some more testing.

@l3pp4rd should we close this PR?

Yes should be closed and instead hooks should return error


Matrix to Layout Conversion

Because the key matrix and the actual keyboard layout may be different, it would be nice to be able to write a keymap with a different layout from the key matrix, like the QMK Firmware layout macro.
https://beta.docs.qmk.fm/developing-qmk/c-development/hardware_keyboard_guidelines#less-than-keyboard_name.h-greater-than
If the Ruby syntax can handle this, I hope you can provide a sample of how to write it.

@e3w2q
Thanks for the suggestion.
I'm not 100% sure that I understood the concept of QMK's LAYOUT macro.
But I came to think something like this will be helpful:
kbd.add_layer_with :ANSI, :default, [
  nil,
  nil,
  %i[ KC_TAB ],
  nil,
  %i[ _ KC_AT ]
]

In this example,

You can easily configure the ANSI layout for the default layer, and

The first, second, and fourth rows will be the same as the ANSI
the first column of the third row (which should be CapsLock by default) will be overridden with the TAB key
the second column of the fifth row (which should be Win/Apple by default) will be overridden with the @ key

_ in the fifth row just keeps the key on the boilerplate ANSI layout

Does this make sense?
Tell me if I'm off the point that you're talking about.

When we made matrix, we can place keys (to PCB) anywhere we want.
Use 4 GPIO pins.
row pins A, B
col pins a, b

We can place keys in matrix order.
Aa  Ab
Ba  Bb

Also, we can place keys freely.(Different from matrix order)
Aa  Ba
Bb  Ab

In 1st case, we can write kaymap.rb as we look actual keyboard.
In 2nd case, can't imagine actual keyboard from keymap.rb.

@hasumikin
Thanks for the reply.
My intentions are similar to @jpskenn .
For example, see the image in the middle of the following URL.
https://www.ibbotson.co.uk/hardware/keyboards/2020/12/06/firmware.html
This keyboard has a very different matrix and layout.
In QMK, in such a case, you can convert it with a layout macro, as shown in the following URL.
https://github.com/qmk/qmk_firmware/blob/master/keyboards/melody96/melody96.h
This allows you to set the keymap as per the layout, not as per the matrix, as shown in the following URL.
https://github.com/qmk/qmk_firmware/blob/master/keyboards/melody96/keymaps/default/keymap.c

OK, now that I get it (hopefully)
So let's say,
Phisical layout:
Aa Ba
Bb Ab

Logical layout:
Aa Ab
Ba Bb

Then, you want to convert those through a conversion map something like this for example:
kbd.add_layer_with_matrix :default,
                          %i[ KC_1 KC_2 KC_3 KC_4 ],
                          ConversionMap.new(
                            %i[ Aa Ba Bb Ab ],
                            %i[ Aa Ab Ba Bb ]
                          )

You can also write in this way:
map = ConversionMap.new(%i[ Aa Ba Bb Ab ], %i[ Aa Ab Ba Bb ])
kbd.add_layer_with_conversion :default, %i[ KC_1     KC_2     KC_3     KC_4 ],    map
kbd.add_layer_with_conversion :raise,   %i[ KC_A     KC_B     KC_C     KC_D ],    map
kbd.add_layer_with_conversion :lower,   %i[ RGB_HUI, RGB_HUD, RGB_VAI, RGB_VAD ], map

How is this?

Thanks.
That mapping looks nice.
I'll try it ASAP.
But, before trying, I need some learnig.
Because "keymap.rb" is my FIRST code with Ruby 😁

That is just one idea.
Tell me if you think it will work enough even in a Duplex Matrix
and, if you come up with a better API.
Thanks!

Sorry for my hasty decision.
I'll think about that.

Is this mapping allows to remove unused matrix position?
Physical layout: 3 keys only
Aa
Ba Bb

Logical layout:
Aa Ab
Ba Bb

Mapping:
map = ConversionMap.new(
%i[
  Aa
  Ba Bb
],
%i[
  Aa XX
  Ba Bb
])

And we can write keymap as the keyboard looks.
kbd.add_layer_with_conversion :default, %i[
  KC_1
  KC_2  KC_3
], map

Without mapping, assigning 'KC_NO' to keymap will result same.
kbd.add_layer :default, %i[
  KC_1 KC_NO
  KC_2 KC_3
]

But the meaning of KC_NO should be "No keycode" or "Ignore(NOOP)" not "No key", I think.

I don't think it makes sense.
I think the physical layout should have exactly four keys because there is a possible point that can be called Ab even if you didn't put a footprint of a key at the point.
In other words, physical shouldn't mean a layout of keys' footprint but a layout of the circuit.

I understand your possible point.
With that, how do we define mapping 5*15 marix with unused 12 possible point? (= 60% keyboards)
Yes, Any order to fill unused point may work.
Is this non-strict rule acceptable?

how do we define mapping 5*15 marix with unused 12 possible point?

As you know, it is KC_NO.
This issue is to discuss converting logical layout to physical layout, right?
It should be really helpful when the difference between logical layout and physical one is quite big like your first example here https://github.com/picoruby/prk_firmware/issues/43#issuecomment-986763302
But skipping keys is not an essential topic, I guess.

I

I don't think it's a problem.
Please be back to the original issue.

Ok. Let's go back.
Mapping idea at https://github.com/picoruby/prk_firmware/issues/43#issuecomment-987510193 is still looks nice.
My favorite is 2nd example
map = ConversionMap.new(%i[ Aa Ba Bb Ab ], %i[ Aa Ab Ba Bb ])
kbd.add_layer_with_conversion :default, %i[ KC_1    KC_2    KC_3    KC_4 ],    map
kbd.add_layer_with_conversion :raise,   %i[ KC_A    KC_B    KC_C    KC_D ],    map
kbd.add_layer_with_conversion :lower,   %i[ RGB_HUI RGB_HUD RGB_VAI RGB_VAD ], map

The reason is ...

Mapping and assigning keycodes are separated.
It makes each lines simple.
Easy to understand what is done by this.
Logical layout and physical layout is paired.
Not to forget another.

In addition to this, it is enough to work with Duplex Matrix.
With Duplex Matrix, @rows.size (or @cols.size) of new_map Array in add_layer_with_conversion method (function?) will be doubled, because Duplex Matrix scans its matrix bidirectionally.
This also affects to add_leyer method (function?).
This is my thoughts.
There's no problem exist now👍

Thanks!
@e3w2q What do you think?

This more "physical" implementation looks nice to me.
It may provide us freedom of pin assignment.
I have a minor concerning, not directory related to this new implement method.

Matrix scan performance
(I don't know well about hardware and internal logic of PRK's matrix scan...)
How PRK scans each matrix point which defined at kbd.init_matrix_pins?
Changing row at each matrix column?
COL2ROW requires "wait delay" when change row.
Too much change may affect matrix scanning performance.
In QMK, it is 30ms.
https://github.com/jpskenn/qmk_firmware/blob/e4d3ff2374142fe6431b68874f6604a471732fae/quantum/matrix_common.c#L8-L10
https://github.com/jpskenn/qmk_firmware/blob/e4d3ff2374142fe6431b68874f6604a471732fae/quantum/matrix.c#L117-L121

I'm not so worried.
The speed of RP2040 is always greater than I imagine 😀


dpiframe_initialization_failed - http://freewheel has not been whitelisted for client ID ...

Expected Behavior
using sample code from "Browser Quickstart"  with http://freewheel/index.html
https://developers.google.com/drive/api/v3/quickstart/js#prerequisites
no error message
(Include the sample name)
Actual Behavior
"error": "idpiframe_initialization_failed",
"details": "Not a valid origin for the client: http://freewheel has not been whitelisted for client ID<PHONE_NUMBER>25-0805lu8fmgtrevplaeleaealh0qqkcrk.apps.googleusercontent.com. Please go to https://console.developers.google.com/ and whitelist this origin for your project's client ID."
JavaScript Console Output
no errors
Specifications

Browser Chrome
OS Windows

The quickstart set up for the client ID only sets up localhost as a valid origin (even though localhost and your hostname point to the same machine, they're not exactly the same thing.). Either:

Go to the console and add your hostname as a valid origin (might have to fully qualify it)
Access the page at http://localhost instead.


Issue 14621, 14624, 14625 - Fix bugs in array operator overloading semantics

Issue 14621 - [REG2.066] ICE: Assertion failure: 'global.gaggedErrors || global.errors' on line 752 in file 'statement.c'
Issue 14624 - The array operator overloading fallback is not correct
Issue 14625 - opIndex() doesn't work on foreach container iteration
Shorten the length of gagged semantic path, and improve ArrayExp as the entry point of array operator overloading.

To @WalterBright and other committers: Please review this to fix regression Issue 14621,  toward 2.068-beta2 release.

I really don't like the gag technique, even though I came up with it, it's been nothing but trouble. There's got to be a better way, and there is - the TOKerror method. Also, at this point, this looks like a very large and disruptive change for this late in the beta cycle, especially since this regression was introduced well over a year ago.

Did you decide not to fix issue 14621 in 2.068 release?

Right, I think this fix is risky to insert into the 2.068 beta, not worth it because it's an old issue and hasn't caused much problems.

Ok, make sense.

If it's an old issue, please downgrade the bug from regression to something else.
We should still fix this on master.

It's not so old. The gagging issue is since 2.066, that introduced when the new operator overloading feature is added.

This PR has been moved to #4948, for the transplanting to stable branch.


Broken link for "Contribute to Refinery CMS"

Fixed this to point to http://refinerycms.com/guides/contributing-to-refinery.
Also, the link for "Contribute" in the nav bar of the guides is similarly broken but I haven't found the source for that.

Closed source unfortunately. I will be looking to open source the website shortly once I check it for anything sensitive


KV Improvements shopping list

This issue to maintain all discussed improvements throughout the development of lakeFS over KV store.
Feel free to add /modify as needed:

Actions migration improvements: https://github.com/treeverse/lakeFS/pull/3427#discussion_r892799808
ListRepositoryRuns: add validations in controller level https://github.com/treeverse/lakeFS/pull/3422#discussion_r885495612
Followup on combined key separator: https://github.com/treeverse/lakeFS/pull/3444#discussion_r888328961
Add test for migrate after successful migrate
Add test for migrate after failed migrate
TBD

@N-o-Z can we track each one under an issue? Otherwise it's a never ending list and this issue will remain open forever.

I think we should hold off migration optimizations until we benchmark them in #3571

This specific optimization I agree. But I do think we need to optimize the staging migration


feat: upgrade to ethers v6

Summary
Bumps ethers to v6—plus, OpenZepplin and Hardhat packages that need v6 as a peer dependency.
Details
N/A
How it was tested
Tested deployment scripts:

Locally on hardhat node
On Seplolia here

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@sanderpick realized i didn't add tests here since i was rushing to test amoy support 😅 ...added. also, hardhat dropped node 16 support, so i updated the gh action to use node 18 (and technically, they say they only support node LTS).


Fail on 5 and 10 km grid

@jonasjucker I tried out both R2B8 and R2B9 grids but they fail. I thought at least the 10 km would go through. Or is there another reason?

DOM_1_extpar.log
DOM_1_extpar_ndvi_to_buffer.log

@mjaehn @jonasjucker these failures seem to be a problem in the conservative remapping algorithm of the latest CDO releases. CDO-2.0.5 still works and I got feedback from the CDO developers that it is also fixed in the development version. So the next release might resolve this.
It seems to happen when single grid points of the source and target grids are collocated. The chances of this to happen in combination with a regular lon/lat grid are higher for R2Bk grids than for R3Bk grids since the points are located on circles of latitude.
Currently possible workarounds

Rotate the grid slightly to avoid the collocation of grid points. E.g. #62 rotates by 36 degrees which is also done operationally at DWD to avoid a pentagon point over Europe which is half the distance between two pentagon points (72 degrees).
Use cdo-2.0.5 until a new release fixes the issue
Use a different interpolation algorithm. Is bilinear an alternative?

Thanks @drieg for pointing out the source of this problem!
So next cdo release is 2.4.5? Would it make sense to rotate the grid by default?
@jonasjucker Can we try out bilinear remapping?

Would it make sense to rotate the grid by default?

You can still run into the same issue, so I think the answer is no.
More generally, anyone creating a grid should think about rotating the grid to avoid pentagon points in the target region. But this is really up to the user and their specified target region. I don't think that an algorithm can cover this in a satisfying way since it requires to know the preferences of the user

Honestly I want to limit the amount of work put into fixing Extpar by bugs discoverd by extpar-request to a minimum.
So my fix will be to lock cdo to a version that does not show the crash.
To adress this issue in Exptar at some point it makes sense to open an issue there.


chore : use latest "alpine" image and install latest "iperf3" package

@Rajpratik71 : We prefer to use exact versions, instead of latest. Latest will not provide great reproducability.
If you would like to get it updated please update this PR with exact version both in the base image as well as for iperf.
Thank you!


[INLONG-9543][Dashboard] Cls, Pulsar and ES sink support saving sortTaskName and sortConsumerGroup

Prepare a Pull Request
(Change the title refer to the following example)

Title Example: [INLONG-XYZ][Component] Title of the pull request

(The following XYZ should be replaced by the actual GitHub Issue number)

Fixes https://github.com/apache/inlong/issues/9543

Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve?
Modifications
Describe the modifications you've done.
Verifying this change

The task name of standalone may not necessarily match the datanode name, and it is not recommended to assign tasks by selecting a datanode through the front-end, and then automatically assign tasks through backend policies.


Custom markers don't always disappear even though they are being counted in the cluster

Implementation is as follows, happy to share more if needed.
<MapView
    ref={this.mapRef}
    style={{ height: '100%' }}
    initialRegion={region}
    showsUserLocation
    showsMyLocationButton={false}
    showsPointsOfInterest={false}
    showsCompass
    clusterColor={colors.purple}
    radius={radius}
    animationEnabled={false}
    onRegionChange={this.onRegionChange}
    onRegionChangeComplete={this.onRegionChangeComplete}
    loadingIndicatorColor={theme.colors.loadingSpinner}
    loadingBackgroundColor={theme.colors.mapViewBackground}
>
    {hikeData.map(({ id, coordinates, distance }, index) => (
        <HikeMapMarker
            key={id}
            identifier={id}
            distance={distance}
            markerRef={(ref) => this.assignRef(ref, index)}
            coordinate={{
                latitude: coordinates.center.lat,
                longitude: coordinates.center.lng,
            }}
            onPress={this.markerPress}
            tracksViewChanges={tracksViewChanges}
        />
    ))}
</MapView>

Upgraded to 3.3.9 and appears to now be worse? Markers are now also disappearing at random and the clusters don't appear on region change until I actually move the map around after zooming in or out.
Happy to provide more code samples if that's helpful.

Anything I can do here to provide additional context or code samples?

Fixed in version 3.4.0

Fixed in version 3.4.0


Update parking_lot to 0.12

Small version bump. Checked the changelog and ran tests locally, and everything seems fine.

Is there a specific reason why we need to update parking_lot?

To update parking_lot, it allows us to avoid having two versions of the crate being built when used with other crates that use parking_lot 0.12. Although ssh2 does not expose the type of parking_lot as an external interface, updating can still contribute to reducing compilation time and binary size even if we do not face version-incompatibility hazards.

I did not realize we had multiple versions of parking_lot in our dependency graph.
It looks like your current PR has a merge conflict. If you do a quick rebase I'd be happy to merge it.

I have opened #299, which is just your commit rebased on master.


Docker client installation instructions

@squillace, here:
http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-docker-with-xplat-cli/

Follow the Docker installation instructions to install Docker locally on your computer. For most operating systems and distributions, this means typing apt-get install docker.io. Confirm that the Docker version is at 1.0 or greater.

docker.io package is not maintained by Docker and usually falls behind newer versions.
We must suggest users to follow the commands here https://docs.docker.com/installation/ubuntulinux/

@ahmetalpbalkan Thank you for the suggestion.  Since you are a MSFT employee, we ask that you use the GitHub capability to contribute to the article by submitting a change and a pull request through the process.  If you need guidance on how this works, please see the contributors guide here: https://github.com/Azure/azure-content-pr/blob/master/contributor-guide/contributor-guide-index.md

@squillace can do better than I can, English is not really my native language. :-)

@squillace Can you please assist on this issue?  Looks like @ahmetalpbalkan has deferred to you on this one.

Hey cats--just landed. @ahmetalpbalkan @dehena ill get to this today or tomorrow morning.

Reviewing this now. Seems that docker has changed their tunes about docker.io, which was previously precisely their description about how to get the client on Ubuntu (as there used to be a debian package called, precisely "docker" so they had to call out the docker.io part). Now it might read:

Follow the Docker installation instructions to install Docker locally on your computer.

and I'll just remove the part about docker.io -- as docker has documented that. Note, however, that debian still has the docker.io requirement. :-) https://docs.docker.com/installation/debian/

@squillace the general installation command curl https://get.docker.com | sh  just works fine on debian too.
If users want to use docker.io pkg they must add jessie-backports apt repo to their debian setup (as documented). It might be smart to just redirect users to the docs.docker.com for that.

@ahmetalpbalkan back from vacation; time to fix this.

fixed. email offline.

@ahmetalpbalkan Thanks again for raising the issue.  The issue appears resolved now.  Please comment if the issue remains a problem and we'll reopen this issue.


Setup retrospective for performance test regressions

...once we've gotten back to a reasonable level of performance.

The goal would be to figure out why our performance tests didn't predict the regressions we've seen on real builds (including whether they in fact did and we missed the signal), what we could do to make this more unlikely in the future, and what changes we should make in the short term.


Removed memoization for T and E

Removed memoization for T and E matrices, expect order decrease to space complexity.


Remove redundant per-namespace locks

Also removes some verbose logs from the new object controller.
Tested: this one's hard to test. I manually created a namespace with 10
children and restarted the controller, and the root is only reconciled
twice even though each of the children try to enqueue it. Then again, we
barely testing multithreading before enabling it and the client code
referenced in
https://github.com/kubernetes-sigs/multi-tenancy/issues/212 seems pretty
clear, so I think this is fairly safe.
Fixed #212
/assign @Fei-Guo
/assign @yiqigao217

/lgtm
/hold

/hold cancel


Write ELF image and instantiate code_memory from it

The following refactoring is a first step towards #1779 .
The main idea is to create object/ELF image as the result of the compilation (which can be saved/serialized in the future). The linker will work with this image directly after it is allocated in the CodeMemory. In the past, we did the similar thing with debug image created for GDB JIT interface. Now, we can use the ELF image created after compilation, and convert it to an loadable object.
There is somewhat common/duplicated code in cranelift-object and creates/obj, this PR is not refactoring these crates yet. It is a work for follow up PRs.
The changes:

Create the ELF image from Compilation
Create CodeMemory from the ELF image
Link using ELF image
Remove creation of GDB JIT images from crates/debug
Move make_trampoline from compiler.rs
Pilot usage of serde to save all compilation artifacts

Items to verify:

[ ] AArch64
[ ] Windows unwind info

CC @pchickey, would be good to get your input on the general approach here.

There is somewhat common/duplicated code in cranelift-object and creates/obj, this PR is not refactoring these crates yet. It is a work for follow up PRs.

Can you give some details on why this should be done as a follow-up? I think it might be good to do this refactoring as part of the initial landing if possible.

There is somewhat common/duplicated code in cranelift-object and creates/obj, this PR is not refactoring these crates yet. It is a work for follow up PRs.

Can you give some details on why this should be done as a follow-up? I think it might be good to do this refactoring as part of the initial landing if possible.

cranelift-object is more generic backend for creating (ELF) object files, and does not fully reflect what is needed for wasm atm. crates/obj is close to what we need though it emits information such as tables or data segments into object file (as well as supporting other formats than ELF).
Once we define how crates/obj and "wasm2obj" are used, we can merge/refactor its and this PR code to remove duplicated logic. I wonder who are the users of these crate and utility. @pchickey, are you using it these in some way?

One of my main thoughts when reading this is about the various copies happening. To make sure I understand thing, can you double check this?

When generating code for the first time, we first invoke cranelift which emits function code into a buffer for each function.
Next we copy (?) each buffer into an object data structure to create an ELF image
Next we copy that ELF image into the final executable page residing in CodeMemory

That is about to be correct. Notice that we generated the ELF image for GDB JIT code, so for debug mode nothing is changed is term of copies.
I'm looking into making object to emit image directly into CodeMemory, where we can directly protect regions for execution. Alternatively, the last copy operation can be removed when the code becomes PIC, so we don't have to patch the image, so there is a potential to use mmap+fs, and compete with current caching logic.

[ ] check if https://github.com/gimli-rs/object/issues/240 will help with copy reduction

Ok, it seems reasonable to go ahead with this in the meantime if more refactoring is required internally to get to the goal of "mmap and go". I'd want to make sure we don't paint ourselves into a corner where that's not possible, but it sounds like that's not the case.
Can you ad some high-level documentation somewhere for this, too? It'd be good I think to have a doc block describing how a wasm module is transformed into an ELF image, so whenever we read/write that we can refer back to those docs about what should go where.

Items to verify:

AArch64

@cfallin could you verify if I refactored Arm64Call properly ? Not sure how to test it.

Windows unwind info

@peterhuene I think the Windows Unwind stuff where properly refactored and tests are passing. If you have time, can you glance the changes?

The unwind changes seem reasonable to me.

Information related no absolute relocations code discussion:
@sunfishcode @alexcrichton to observe relocations, I'm adding dump of the generated ELF at
diff --git a/crates/jit/src/compiler.rs b/crates/jit/src/compiler.rs
index 46280c120..96aed7a51 100644
--- a/crates/jit/src/compiler.rs
+++ b/crates/jit/src/compiler.rs
@@ -189,4 +189,7 @@ impl Compiler {
         })?;

+        let mut file = ::std::fs::File::create(::std::path::Path::new("test.o")).expect("file");
+        ::std::io::Write::write_all(&mut file, &obj).expect("write");
+
         Ok(Compilation {
             obj,

I after cargo run -- tests/all/debug/testsuite/reverse-str.wasm && gobjdump -xD test.o the following can be observed:
...
    16b:       48 b8 00 00 00 00 00    movabs $0x0,%rax
     172:       00 00 00
                        16d: R_X86_64_64        _wasm_function_0
     175:       49 89 fe                mov    %rdi,%r14
     178:       4c 89 ef                mov    %r13,%rdi
     17b:       4c 89 f6                mov    %r14,%rsi
     17e:       44 89 fa                mov    %r15d,%edx
     181:       40 ff d0                rex callq *%rax
     184:       44 8b bc 24 0c 00 00    mov    0xc(%rsp),%r15d
...


UI: Login with MFA

As an enduser I want to be able to login my user with multi factor.
Acceptance Criteria

[ ] Ui checks what kind of authentication methods should be shown depending on the settings of the organization or instance and the configuration the user has
[ ] If settings tell to have mfa and user doesn't have it configured, step up is shown
[ ] If otp is configured, input field for code is shown
[ ] If webauthn is configured challenges should be started automatically without the user clicking a button
[ ] If only one possiblity we show it directly
[ ] If both options are configured we show webauthn per default and then otp
[ ] If options are in package, we want to be able to configure the check order  of the factors

Issue is moved to new repository: https://github.com/zitadel/typescript/issues/18


cryptorito shuffle

GPG/Keybase code has been moved to the cryptorito project.
Before this gets merged the following needs to happen

[ ] Add some tests to cryptorito
[ ] Someone else look at this code

I have no idea why the push build is failing.

Not deleted, just moved haha.


Link to usage of pkg description instead of referring to nix-env

Description of changes
Updates meta.chapter.md with a reference link to the usage of the package description field instead of referring to nix-env

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2023-09-14-documentation-team-meeting-notes-80/33033/1


Doesn’t encode object with NSSet? property

I'm trying to encode the following model:
final class ManagedHabit: NSManagedObject, CoreDataCodable {
    @NSManaged var id: String
    @NSManaged var name: String
    @NSManaged var notifications: NSSet?

    enum CodingKeys: String, CoreDataCodingKey {
        case id
        case name
        case notifications
    }
}

final class ManagedNotification: NSManagedObject, CoreDataCodable {
    @NSManaged var id: String
    @NSManaged var userNotificationId: String
    @NSManaged var enabled: Bool
    @NSManaged var habit: ManagedHabit

    enum CodingKeys: String, CoreDataCodingKey {
        case id
	case userNotificationId
	case enabled
    }
}

…

let encoder = JSONEncoder()
let jsonData = try encoder.encode(object)

I get an error.
The CoreDataEncoder class contains a method
private func encode (_ relationship: NSRelationshipDescription, object: ManagedObject, key: Keys, container: KeyedContainer) throws
that uses NSStringFromClass in its implementation, which always returns nil. This is because you need to use NSClassFromString(“<ModuleName>.<ClassName>”). I checked this and it works.
The same problem is present in the CoreDataDecodable extension in the method
private func set (_ relationship: NSRelationshipDescription, from container: CoreDataKeyedDecodingContainer <Self>, with codingKey: CodingKeys) throws
Please, can you fix this?

It works with my tests if I set current module in the Module setting within the class definition in the model file. I guess you use “global namespace”, aren’t you?. I’ll check if I can find a universal solution.

Yes, I use "Global namespace". Thanks.

I am trying to write a failable tests of your issue but I can't. Could you point me to some sample project so I can check it?

I could but I need some time.


Adding new subtype resets Debit and credit fields.

To Reproduce
Steps to reproduce the behavior:

Go to 'Accounts Page'
Click on '+Voucher'
Add 2 lines credit and debit side.
Add new Sub type.

Actual Result
Resets debit and credit fields.
Expected behavior
Should affect debit and credit fields.

It's reset by default, as it is required  in new entry or reset entry


Keyboard on TextField not showing after tapping on picker, found using BottomPicker.dateTime

Hi,
I really enjoy using this package but it keeps having an issue in combination with TextField. First time entering the screen I can tap on the textfield and after tapping on the InkWell the picker appears. After closing the picker and tapping again on the textfield the keyboard opens and instantly closes again. From this moment the textfield can no longer be edited.
I've already tried a lot with focus, controllers and so on. To me it turns out that its problem with your BottomPicker.
return Scaffold(       body: SingleChildScrollView(         child: Column(           children: [             TextField(               onTapOutside: (event) {},               key: GlobalKey(),               controller: controller,               maxLines: 3,               keyboardType: TextInputType.multiline,             ),             InkWell(               onTap: () => _openDateTimePicker(context),               child: InputDecorator(                 decoration: InputDecoration(                   labelText: 'Voraussichtliches Ende',                   suffixIcon: Icon(                     Icons.date_range,                     color: primaryColor,                     size: 20.0,                   ),                   border: OutlineInputBorder(                     borderRadius: BorderRadius.circular(10.0),                   ),                 ),                 child: Text(                   vm.expectedEndDateString,                   style: TextStyle(fontSize: 16, fontWeight: FontWeight.normal),                 ),               ),             ),           ],         ),       ),     );
Hope you have an idea.

@adessoli thanks for sending me your feedback and issue I'll check it out

Hi @koukibadr @adessoli, adding readOnly and setting it to true in the TextField prevent the keyboard from opening after choosing an item from the bottom picker


硬件SPI 7567那部分，为何显示不全？

看起来只有上面一点能显示出来想要的字符
下图是我用Fill(1)的结果

问题出在了偏移量上吗？我的也是ST7567

确切来说，只显示了上面8行，下面的都没显示。

I met this problem before, some ST7567 doesn't support row/page shift, so the following code might not work
void ST7567_UpdateScreen(void)
{
    ST7567_WriteCommand(ST7567_SET_PAGE_ADDRESS | (0x00 & ST7567_SET_PAGE_ADDRESS_MASK));
    ST7567_WriteCommand(ST7567_SET_COLUMN_ADDRESS_MSB);
    ST7567_WriteCommand(ST7567_SET_COLUMN_ADDRESS_LSB);
    ST7567_Transmit(ST7567_Buffer_all, sizeof(ST7567_Buffer_all), ST7567_TIMEOUT);
}

You need to update it page by page like this. The following code might not work out-of-box, just for your reference.
void ST7567_UpdateScreen(void)
{
    uint8_t i = 0, *pt = ST7567_Buffer_all;
    for (i = 0; i < ST7567_PAGES; i++)
    {
        ST7567_WriteCommand(ST7567_SET_PAGE_ADDRESS|(i & ST7567_SET_PAGE_ADDRESS_MASK));
        ST7567_WriteCommand(ST7567_SET_COLUMN_ADDRESS_MSB|(ST7567_X_OFFSET >> 4));
        ST7567_WriteCommand(ST7567_SET_COLUMN_ADDRESS_LSB|(ST7567_X_OFFSET & 0x0F));
        ST7567_Transmit(pt + (ST7567_WIDTH * i), ST7567_WIDTH, ST7567_TIMEOUT);
    }
}

Thank you for your Tips ~
After I use your reference code, the screen can be fully displayed, but a new problem has appeared,
It seems to be displayed a bit misplaced.

Adjust the following configurations, depends on your hardware and display mode
// Additional bytes in each row
#define ST7567_SEG_EXPAND 4
// X orientation
#define ST7567_X_ORIENT ST7567_SEG_DIRECTION_REVERSE
// Y orientation
#define ST7567_Y_ORIENT ST7567_COM_DIRECTION_NORMAL

and
#if ST7567_X_ORIENT == ST7567_SEG_DIRECTION_REVERSE
    #define ST7567_X_OFFSET  ST7567_SEG_EXPAND
#else
    #define ST7567_X_OFFSET  0
#endif

Adjust the following configurations, depends on your hardware and display mode
// Additional bytes in each row
#define ST7567_SEG_EXPAND 4
// X orientation
#define ST7567_X_ORIENT ST7567_SEG_DIRECTION_REVERSE
// Y orientation
#define ST7567_Y_ORIENT ST7567_COM_DIRECTION_NORMAL

and
#if ST7567_X_ORIENT == ST7567_SEG_DIRECTION_REVERSE
    #define ST7567_X_OFFSET  ST7567_SEG_EXPAND
#else
    #define ST7567_X_OFFSET  0
#endif

Thank you so much for your fast reply, I will try.

I change it to this,finally it works.
// Additional bytes in each row
#define ST7567_SEG_EXPAND 0
// X orientation
#define ST7567_X_ORIENT ST7567_SEG_DIRECTION_NORMAL
// Y orientation
// #define ST7567_Y_ORIENT ST7567_COM_DIRECTION_NORMAL
#define ST7567_Y_ORIENT ST7567_COM_DIRECTION_REVERSE

Cool!

Thanks a lot for your open source library,
it's very cool !

You are welcome.


Adding Sleep Time Env Variable

Adding Sleep Time Env Variable so user can configure how often the script check if DNS need modification.

Thanks, I'll get a new tag and image pushed up soon!

Thanks!


bug: 2 users of the same name in reward dropdown

https://www.dropbox.com/s/slr11a2xgbxyddb/Screenshot 2016-02-25 12.07.35.png?dl=0

Are we scoping reward recipient dropdown by current slack instance?
Hm, what we should be doing is downloading a full list of all usernames in that slack instance, which is a whole other story.  Closing this bug.


A good starting point

This is a checkpoint at which we can start writing codelab custom elements.
Notable updates and changes:

Replaced rules_closure's phantomjs-based test runner with real browsers
reusing the work from rules_webtesting: https://github.com/bazelbuild/rules_webtesting.
The runner is now a simple Go program, connecting to a selenium hub
instantiated by web_test_suite rule and checking results via G_testRunner.
See //demo:hello_test target and tools/webtest.go.

The closure_js_{library,binary} now have suitable default attribute
values. See //demo:hello_lib and //demo:hello_bin targets.

A minimal readme, doc comments and updated license.

/cc @skarEE @markmcd @arkassay

Just added another commit: forgot to say about bazel run //tools:server.
PTAL

LGTM


Minor (I think) confliction of "authentication" & "authorization" usage

There's a possible (definate?) conflict of text here - user will either see You're not authorized or Authentication in progress - one would expect both phrases to refer to "authentication" or both phrases to refer to "authorization".
I believe the latter is correct, hence this PR, but there are potentially other similar confusions of "authentication" / "authorization" in this markdown page, which aren't covered by this PR.

Hello @GregTrevellick ... It's best to open an issue using the This page feedback button+form at the bottom of the English-US (en-us) topic, but I'll take a look at this and respond tomorrow morning.

Hello @GregTrevellick ... It's best to open an issue using the This page feedback button+form at the bottom of the English-US (en-us) topic, but I'll take a look at this and respond tomorrow morning.

Sure, no probs, I did wonder about doing that from the outset funnily enough, will do tomorrow 😃

Sure, no probs, I did wonder about doing that from the outset funnily enough, will do tomorrow 😃

We usually discuss a potentially more complicated changes to a topic before receiving a PR. Changes that go directly to a PR are typically just patch fixes, such as a misspelled word or an incorrect C# statement. That way for content changes that are more conceptual in nature, the dev doesn't end up doing work that we don't take and ultimately feel like they wasted time trying to help improve the docs. Fortunately in this case, the change is small.
I'll get back to you in the morning on this. ☕

We usually discuss a potentially more complicated changes to a topic before receiving a PR. Changes that go directly to a PR are typically just patch fixes, such as a misspelled word or an incorrect C# statement. That way for content changes that are more conceptual in nature, the dev doesn't end up doing work that we don't take and ultimately feel like they wasted time trying to help improve the docs. Fortunately in this case, the change is small.
I'll get back to you in the morning on this. ☕

I'm up. ☕ ... and the 🐈 let me sleep in to 5:30am for a change. Gee ... thanks! ... rotten 😼!
The language used in the <Authorizing> element is currently by-design because the rate limiting step for authorization isn't usually the authorization aspect (authenticated or not) ... that's really FAST 🏃. It's the authentication step for an unauthenticated user that takes long enough that showing something is worthwhile in most cases. It takes mere tiny fractions of a second to compute authz for an authenticated user in most cases. That's why it was written this way. Technically yes, they're being authorized, but Steve implies that most users are really waiting on authentication to occur. He's made the markup of the property be more specific for most users.
I'm not opposed to the change. The description of this property is ...

The content that will be displayed while asynchronous authorization is in progress.

Practically, it's usually going to display during authentication. However, it invites confusion in its present form.
The bullet point above this for "allows the app to specify custom content if" reads ...

Asynchronous authentication is in progress.

... so that covers authn for the scenario.
I searched the doc set, and this is the only place this property is shown/described. We don't maintain any sample apps that host a version of this component with this property set. Therefore, this is likely the only change that we need.
WRT ...

there are potentially other similar confusions

Those would have to be explicitly called out until I reach this topic for an overhaul on https://github.com/dotnet/AspNetCore.Docs/issues/19286. I'm working on those passes now, and I hope to reach this topic by mid-year.

I'm up. ☕ ... and the 🐈 let me sleep in to 5:30am for a change. Gee ... thanks! ... rotten 😼!
The language used in the <Authorizing> element is currently by-design because the rate limiting step for authorization isn't usually the authorization aspect (authenticated or not) ... that's really FAST 🏃. It's the authentication step for an unauthenticated user that takes long enough that showing something is worthwhile in most cases. It takes mere tiny fractions of a second to compute authz for an authenticated user in most cases. That's why it was written this way. Technically yes, they're being authorized, but Steve implies that most users are really waiting on authentication to occur. He's made the markup of the property be more specific for most users.
I'm not opposed to the change. The description of this property is ...

The content that will be displayed while asynchronous authorization is in progress.

Practically, it's usually going to display during authentication. However, it invites confusion in its present form.
The bullet point above this for "allows the app to specify custom content if" reads ...

Asynchronous authentication is in progress.

... so that covers authn for the scenario.
I searched the doc set, and this is the only place this property is shown/described. We don't maintain any sample apps that host a version of this component with this property set. Therefore, this is likely the only change that we need.
WRT ...

there are potentially other similar confusions

Those would have to be explicitly called out until I reach this topic for an overhaul on https://github.com/dotnet/AspNetCore.Docs/issues/19286. I'm working on those passes now, and I hope to reach this topic by mid-year.

Thanks Luke, just checking, is it still worthwhile me raising an issue? Happy to do so, but suspect already covered by the existing wider topic.

Thanks Luke, just checking, is it still worthwhile me raising an issue? Happy to do so, but suspect already covered by the existing wider topic.

still worthwhile me raising an issue

Only if you think that there are other potential changes that aren't patches.

still worthwhile me raising an issue

Only if you think that there are other potential changes that aren't patches.


Update try_from_into.rs

No idea if it's appropriate to do this, as it's my first time opening a pull request and I am quite new to the coding world. But I've been trying to figure out this rustling all weekend and I found some inspiration in your attempts. Hope you find this useful.

Thank you for the pull request. (And welcome to wonderful wacky world of writing code.)
As you can see in this repo rustlings-idiomatic-solutions has one or more solutions to each of the current rustlings exercises. If you have a novel or efficient solution that isn't already covered then create a new file (usually in the form of [exercise][tactic].rs i.e. solving the from_into.rs with match would be called from_into_match.rs - alternatively from_into[your_name].rs is an option.)
Pull requests are also welcome for actual errors, (or things that are no longer valid in stable Rust,) but the file that you seem to be patching is still a valid working solution.
So I'm going to bounce this one back to you. Feel free to create a new file in your fork with your solution, and I'll take a look at it in the next pull request.
Thanks again. (And welcome to the joys of Rust programming.)


Add support for Kubernetes v1.13.0-alpha.2

What this PR does / why we need it:
See https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.13.md#v1130-alpha2
TODO:

[x] Upload Windows binary

If applicable:

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

Kubernetes: add support for v1.13.0-alpha.2

/lgtm


store/chrome: re-enable headless chrome

The headless chrome command is segfaulting now. Travisci did an update to their env, but I'm not sure if that's the problem or not.

This job ran on our Trusty environment, which has been updated on Tuesday, December 12th, 2017. Read all about this on our blog and take note that you can add group: deprecated-2017Q4 in your .travis.yml file to use the previous image version.

https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch

We need to support cert9.db for chrome also. /cc #142


支持一下ip2region？

RT.233

have a try. https://github.com/zu1k/nali/releases/tag/0.3.6
NALI_DB_IP4=ip2region nali <IP_ADDRESS>


fixed another import mismatch for more recent wagtail versions

Hi,
this will fix another import mismatch.
As your PR https://github.com/infoportugal/wagtail-embedvideos/pull/64 is not included yet, you might be interested in adding this
Cheers

If you like, you're welcome to pass it upstream ;)

Awesome thanks. Not sure if that repo is active anymore so I have just been maintaining my own version unfortunately.


cli fails to build

npx shadcn-ui@latest init fails with Unexpected token {
Using Nextjs build process
~/project main ❯ npx shadcn-ui@latest init                    10s 13:42:51

npx: installed 198 in 12.828s
Unexpected token {
~/project main ❯                                              14s 13:43:26

Resolved.

how did you fix this error? I encountered same problem,

Fixed it already by running the command on external terminal instead of terminal inside VSCode.

getting same issue


Unable to use this package

HI all I am not able to use this component in the project. as whenever I run this component it throws errors. I am able to trace that there is no index.js file available in the package.
Here i am sharing the browser console log:
Error: (SystemJS) XHR error (404 Not Found) loading http://localhost:5555/node_modules/t-json-viewer/index.js
Error: XHR error (404 Not Found) loading http://localhost:5555/node_modules/t-json-viewer/index.js
at XMLHttpRequest.wrapFn [as _onreadystatechange] (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:889:29) []
at Zone.runTask (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:151:47) [ => ]
at XMLHttpRequest.ZoneTask.invoke (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:345:33) []
Error loading http://localhost:5555/node_modules/t-json-viewer/index.js as "t-json-viewer" from http://localhost:5555/app/dashboard/locations/locations.module.js
at XMLHttpRequest.wrapFn [as _onreadystatechange] (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:889:29) []
at Zone.runTask (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:151:47) [ => ]
at XMLHttpRequest.ZoneTask.invoke (http://localhost:5555/node_modules/zone.js/dist/zone.js?1487330922173:345:33) []
Error loading http://localhost:5555/node_modules/t-json-viewer/index.js as "t-json-viewer" from http://localhost:5555/app/dashboard/locations/locations.module.js "Report this error at https://github.com/mgechev/angular2-seed/issues"

Is this issue actual?

It is not working at my side. Let me know how can I help.

I created index.js file. Could you check on your side?

Hey, there!
I think I am having the same or a similar problem in getting this module to run. Specifically I'm getting this error in the browser's console:
Uncaught Error: Module build failed: Error: ENOENT: no such file or directory, open '/home/maninak/Desktop/NoMoTS-webapp/node_modules/t-json-viewer/index.js'

I'm developing an Ionic web app using the latest Ionic v3.4.2 which uses angular v4.1.3. I have dumped node modules and reinstalled, and have checked multiple times that I'm not doing something horribly wrong.
Let me know if I can be of any further help in resolving this.

I've developed v1.2.0. Could you test it?

Still getting a runtime error, although now it complains about the index.js.map missing, instead of index.js.
Tested against same development setup as above with package.json dependency changed as "t-json-viewer": "^1.2.0".
Full runtime error follows:
Module build failed: Error: ENOENT: no such file or directory, open '/home/maninak/Desktop/NoMoTS-webapp/node_modules/t-json-viewer/index.js.map'

You should probably have "sourceMap": true in your tsconfig.json file for your module.

It's strange. I've removed all configs from a package. All on your side.
Could you show your project or it's confidential?

Not at all, it's actually a new open source project of mine https://github.com/maninak/NoMoTS-webapp


Group runInSeparateProcess and preserveGlobalState

Description
Closes #6783
The relevant php-cs-fixer rule will be adjusted in coding-standard (https://github.com/CodeIgniter/coding-standard/commit/644b3edd1dc5ad21849c4aded4a3c6e39d0e2eaf)
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

This PR forgot include AutoloaderTest, See https://github.com/codeigniter4/CodeIgniter4/actions/runs/3355759616/jobs/5560276695

That must have been added in 4.3. The PR targeted develop.

Follow-up PR underway.


fix #43

Hi, here is my attempt on this .
Thanks for this great work!

Since @fitzgen was the one who responded to the question I'm tagging them for review on the content :)

Thanks a lot for the review ! I changed accordingly  .
If you have more suggestions , its more than welcome :)

Thank you @fitzgen  and @mgattozzi  :)

Thanks for doing this and closing the issue :)


val/loss=nan.0 when training with ddp (distributed data parallel)

Hello, I have access to a system that has 4 GPUs per node. I wanted to run on 8 gpus so I modified your script (see below).  It started without error and appeared to be training properly and I checked to see that all GPUs were being used and they were, but at the first evaluation I noticed that the loss and perplexity values for train and val were =nan.0
Do you have better suggestions on how to run on GPUs that are not on the same node?
What I changed:
Removed this line from
run_pretrain_caduceus.sh
trainer.devices=${NUM_DEVICES} \
Then changed the configuration file this way:
~caduceus/configs/trainer/default.yaml
target: pytorch_lightning.Trainer
#devices: 1
devices:

[0, 1, 2, 3]  # GPUs available on the first node
[0, 1, 2, 3]  # GPUs available on the second node

accelerator: ddp
#accelerator: gpu
accumulate_grad_batches: 1 # Gradient accumulation every n batches
max_epochs: 200
# accelerator: ddp # Automatically set if gpus > 1
gradient_clip_val: 0.0
log_every_n_steps: 10
limit_train_batches: 1.0   # train on full dataset, can be used to toggle quick run
limit_val_batches: 1.0     # validate on full dataset, can be used to toggle quick run
num_sanity_val_steps: 2    # default value: 2; override to 0 to skip sanity checking

At what step did you hit the NaN? I think the model is training at too high a LR for too long. You set max_epochs to 200 which is much higher than what we used. For example, at 10k training steps we don't even complete a full epoch. The learning rate scheduler is decided based on max number of epochs/steps so my guess is that your LR is too high for this long of training

I am getting the nan.0 in epoch 0, at the very first time that it does an evaluation on the val file
I did not make any change to the max_epochs. That is the default in the ~/caduceus/configs/trainer/default.yaml file.
The only change that I made to the run_pretrain_caduceus.sh file was to remove the line overriding the train.devices, so I believe that the learning rate is set in that file with
LR="8e-3"
optimizer.lr="${LR}"
I am currently setting up a new environment and cloning again from scratch, to see if perhaps I made some other error along the way...I will let you know how that goes.

Unfortunately, it did happen again with the clean install (and the changes listed above).  I did make one more change, since the batch size was too large and causing and OOM I changed
BATCH_SIZE=$(( 1048576 / (SEQLEN*4) ))
to reduce the batch size
I uploaded the log file so that you can take a look.
Uploading caduceus_ps_3413538.log…

You can keep the same effective / global batch size by increasing gradient accumulation steps. So you can have train.global_batch_size be 1024 but reduce the dataset.batch_size to be the largest that fits on your machine. Gradient accumulation should be computed automatically by the config file here
  accumulate_grad_batches: ${div_up:${train.global_batch_size}, ${eval:${trainer.devices} * ${dataset.batch_size} * ${trainer.num_nodes}}}

Thank you, Yair. I will try that.
Have you been successful running caduceus across multiple nodes using ddp?

I have not tried multi-node training

Don't worry. It trains so fast, multi node is probably not necessary.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/401 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit e3261a2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


TS should not allow assigning value with undefined union to non-nullable property when strictOptionalProperties

Bug Report
First, congrats to the new compiler switch!
I don't know if this is intentional since strict optional property semantics seems tricky. Related to #44421.
🔎 Search Terms
strict optional properties, assignability
🕗 Version & Regression Information
Nightly, with strictOptionalProperties on

I was unable to test this on prior versions because strictOptionalProperties is a new option

⏯ Playground Link
Playground link with relevant code
💻 Code
declare var a: {[x: string]: number | string }
declare var b: {a: number, b: string}
declare var c: {a: number, b?: string}
declare var d: {a: number, b: string | undefined }
declare var e: {a: number, b?: string | undefined }

a = b // ok
a = c // ok
a = d // error
a = e // expect error

🙁 Actual behavior
TS allow a = e where the property b might be undefined.
🙂 Expected behavior
TS should report error because of consistency?

@ahejlsberg I'm inclined to agree but let's discuss today


@ModelAttribute object is not mapped when the setters are not void

I have this controller:
@RestController
public class TestController {
    public Result find(@ModelAttribute SomeFilters filters) {
        ...
    }
}

If the POJO for the ModelAttribute has the setters like this (returning itself):
public class SomeFilters {
    private String param;

   public SomeFilters setParam(String param) { this.param = param; return this; }
   public SomeFilters getParam(String param) { this.param = param; }
}

It will not map the property param as a QueryParameter. The only way that works is if the setter  returns void:
public void setParam(String param) { this.param = param; }

Is this a known problem / limitation? I didn't find any reference about this.
Thanks!
Diego

That is by design. Have you looked at this section in the documentation?
Only properties that conform to the bean spec are supported.

Yes I did. About the bean spec (http://download.oracle.com/otndocs/jcp/7224-javabeans-1.01-fr-spec-oth-JSpec/), if I didn't misread it doesn't say anything about  the setters must return void.
If the Spring Framework understand the properties this way, wouldn't be better if Springfox do the same? This way if anyone who has a running spring application wants to add documentation to it, won't have the need to refactor the code to work.
Anyway, this is a suggestion. This API is awesome with or without this behavior!


add and expose driver/gui version

currently the driver does not have it's version fields filled out.
this makes it impossible to determine if the current install is out of date.
i think the following would be really helpful

add version information to the driver
add version information to the gui (currently the exe has set <IP_ADDRESS> regardless of version)
display both version numbers in the gui (maybe under "about" menu, pretty much standard practice)
the displayed driver version should be the one installed in the system, not the one of the rawaccel.sys file in the rawaccel folder

(information displayed by nirsoft's utility)

agreed, i'll get to this soon, and add better version mismatch handling to the gui.


add codm, fm radio, nubank, picpay, spay, sim toolkit and tachiyomi

rkbdi*k

thank you W**STxda I will merge this now


chore: organize deps with Poetry v1.2 groups

I've organized dependencies using the new dependency groups feature released with Poetry v1.2. Since Poetry v1.2 is required now anyway, I think it's nice to leverage this feature.
Thanks to dependency groups, dependencies can be defined in a more granular fashion and groups can be optional, so that it isn't necessary to always install all of them. Here's what you can do:
# Install for code dev
poetry install

# Install for code dev + docs
poetry install --with docs

# Install for docs only (without `poethepoet`)
poetry install --only docs

# Install for docs only (with `poethepoet`)
poetry install --only core,docs

# Install for runtime only
poetry install --only main

Also, docs dependencies aren't exposed as a runtime extra anymore, which was just a workaround for the missing optional dev dependencies feature.
WDYT?

Codecov Report

Merging #823 (81bc8bc) into master (bd766ba) will decrease coverage by 0.23%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #823      +/-   ##
==========================================
- Coverage   96.68%   96.45%   -0.24%
==========================================
  Files          41       41
  Lines        2959     2959
==========================================
- Hits         2861     2854       -7
- Misses         98      105       +7

Flag
Coverage Δ

unittests
96.45% <0.00%> (-0.24%)
:arrow_down:

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

Impacted Files
Coverage Δ

devtasks.py
0.00% <0.00%> (ø)

tests/test_tools.py
68.00% <0.00%> (-24.00%)
:arrow_down:

copier/cli.py
96.47% <0.00%> (-1.18%)
:arrow_down:

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

After some back and forth trying to get Read the Docs to install the docs dependencies using Poetry, it works now. It seems it's not possible to install Poetry using the official installer, which is the recommended approach, because then the installed packages are not installed in the virtual environment created and managed by Read the Docs. Unfortunately, Read the Docs' documentation on using Poetry is outdated and incorrect. When installing Poetry via pip, it works but is not recommended because Poetry's own dependencies are installed into the same virtual environment as those of the project. It works fine in most cases though.
This PR is ready for review now.


Update the user information in GUI

Connect userUpdate to MyDetailsEdit GUI

The checking will be when the edit screen will be modified and will contains more fields for update
@Shahar-Y please notify me when you add the following phoneNumber field,
and make sure that the new code doesn't effect your code 😄

thanks to @Shahar-Y update at the GUI screen I could finish this issue.


Remove onResize setState

This is extremely expensive. Every time the window resizes the entire app re-renders on every 'onresize' event. https://github.com/Jam3/generator-jam3/blob/master/templates/react/src/sections/App/index.js#L19

But there are some components and sections that will need to re-render anyway because they need a new windowWidth or Height.

Also, if sections aren't actually using windowWidth / windowHeight, theoretically they would not be re-rendered since there would be no change to the dom.

My problem is that this encourages people to use it and consequently, potentially, unnecessary re-renders happen. I only usually have a couple listeners in an app where window dims are needed. Juniors will use this all the time and it is crazy expensive.

Essentially every resize the section and all of the sections children will rerender. I would highly discourage this type of default behaviour. If your section needs this it should be added at the section level. they are connect route components and are in principle supposed to be isolated.

I don't see how this can't be accomplished with CSS at a section level. Not only that, some browsers can trigger resize event in weird situations like scroll bars showing or hiding.
I upvote this.

Although it may not cause rerenders wouldn't it cause additional evaluations as props have changed? Not sure how expensive that is. Any who I think it encourages bad practice. I would defer to css for presentational resizing and I don't think everyone knows when to use it for behaviour and when not to use it for presentation.

you are setting state on the root app component (on window resize!). if fed through props you will trigger the lifecycle for the sections and most likely the children. It will force a comparison (reconcilliation) even if the result is not inserted into the dom. or something like that.

It will cause a render call for sure, you can't escape that if you are setting state because it's the actual thing why setState exists, what might happen lately is that React's reconciliation algorithm compares virtual tree with actual DOM representation and sees that there's nothing to update, but all update cycle callbacks will get called, including the render function.

For sure it will go through a react evaluation, but this kinda seems like something that react is built to handle (evaluate updates to prevent unnecessary dom manipulation). I'm not against removing it, but I would be interesting in seeing how it affects performance (especially if no sections are using it). This has kinda been a design decision for a long time, back to bigwheel days, it would send the width and height to each section (mostly so sections don't attach their own listeners to things like resize and improperly clean them up).
Might be an idea to add it to the store so connected sections could still use it if they need to, although I'm not sure if the store is the right place for this kind of data.

A good compromise would be to debounce the resize event :)

You could have an action that dispatches on resize.
https://github.com/cape-io/redux-windowsize <- just an example but I still
think this is all a little dodgy.
My main problem is that encourages people to use it deeply nested in their
component tree forcing rerenders when it simply isn't necessary.
On Fri, Apr 7, 2017 at 5:57 PM, Nick Poisson<EMAIL_ADDRESS>wrote:

For sure it will go through a react evaluation, but this kinda seems like
something that react is built to handle (evaluate updates to prevent
unnecessary dom manipulation). I'm not against removing it, but I would be
interesting in seeing how it affects performance (especially if no sections
are using it). This has kinda been a design decision for a long time, back
to bigwheel days, it would send the width and height to each section
(mostly so sections don't attach their own listeners to things like resize
and improperly clean them up).
Might be an idea to add it to the store so connected sections could still
use it if they need to, although I'm not sure if the store is the right
place for this kind of data.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Jam3/generator-jam3/issues/276#issuecomment-292649795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm7y1NEWZ_TlcovgL0uAYdIXyBu2dQFks5rtqMvgaJpZM4M3Srl
.

Another reason behind passing the window size down would be gaining more control over the app. If, for some reason, you wanted to render your app in only a portion of the page, simply changing this prop would handle that.

mmmm. people can add it if they need it. juniors use this too much and it
forces rerenders in places they don't expect. I always remove it.
On Fri, Apr 7, 2017 at 6:07 PM, Nick Poisson<EMAIL_ADDRESS>wrote:

Another reason behind passing the window size down would be gaining more
control over the app. If, for some reason, you wanted to render your app in
only a portion of the page, simply changing this prop would handle that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Jam3/generator-jam3/issues/276#issuecomment-292652068,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm7y3F2smjFLCON2r3f2WMgFrP9v_JWks5rtqWbgaJpZM4M3Srl
.

I'm still thinking what this part of our logic is solving that can not be tackled by CSS 🤔

Is this module on your radar react-sizeme?
(Jeffrey found it btw)
Can independently configure refresh rate and throttle mode on components that care to know its own size, and move that responsibility out of the root component

Next steps: Debouncing and researching https://github.com/wnr/element-resize-detector


Two Sample Tests

Pull Request Test Coverage Report for Build 277

0 of 46 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-2.1%) to 93.147%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mgcpy/benchmarks/power_two_sample.py
0
46
0.0%

Files with Coverage Reduction
New Missed Lines
%

mgcpy/benchmarks/power_two_sample.py
1
0.0%

Totals

Change from base Build 275:
-2.1%

Covered Lines:
1332

Relevant Lines:
1430

💛  - Coveralls


Release

This is a test release for Azure Release Pipeline

Need to turn off branch rule in test to avoid CI Builds.


How to add a new accordion item?

Description
How to add a new accordion item? I have no clue...
edit: now I have; d&d from "Components" panel ... but in WP Gutenberg there is plus icon; on AEM is "Add components here" or sth like that; without such "helpers" it is not so intuitive to demystify it
WebSight CMS version
1.0.0
Steps To Reproduce

Edit homepage
Scroll to accordion component
Try to add an new item

Expected behavior
"Add components here" hint
Screenshots

Desktop

OS: macOS
Browser: Chrome
Version: 105

Additional context

Reported by @pun-ky in https://github.com/websight-io/starter/discussions/11

Howlite-related issues should be accepted only if are bugs. Howlite will be replaced with Bulma - new reference components library.


support oracle

oracle pagination is a little bit different
this is an example: https://github.com/oracle/node-oracledb/blob/master/examples/rowlimit.js#L64

I've been playing around with Oracle. It looks like version 12c is needed to support pagination, as LATERAL and OFFSET are not available in version 11g. Version 12c does not seem to have a free express edition, so my access to Oracle is limited as of right now. If I can get a version of 12c to develop against, I can add it in pretty easily.

I can help you with this. Please let me know how we can forward with this?

I am currently working on this. I'm blocked by this if someone would like to help me.

Oracle is now a supported dialect in v1.1.0-beta.1. Expect an un-handled edge case or two, as its a new addition to the beta version.

Tks for the great work

Thank You.


Support SSH for go get

Gitea version (or commit ref): 1.12.1 built with GNU Make 4.2.1, go1.14.4 : bindata, sqlite, sqlite_unlock_notify
Git version: 2.24.3
Operating system: Arch Linux
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
We have a private gitea repository containing a go module. When we want to go get git.company.com/organization/private, gitea returns only the HTTPS link of the repository, not the SSH one.
To reproduce, one can simply open a link in the browser: https://git.company.com/organization/private?go-get=1
and examine the returned HTML:
<!DOCTYPE html>
<html>
<head>
<meta name="go-import" content="git.company.com/organization/private git https://git.company.com/organization/private.git">
<meta name="go-source" content="git.company.com/organization/private _ https://git.company.com/organization/private/src/branch/master{/dir} https://git.company.com/organization/private/src/branch/master{/dir}/{file}#L{line}">
</head>
<body cz-shortcut-listen="true">
go get git.company.com/organization/private
</body>
</html>

Here are the relevant source code locations:
templates/base/head.tmpl:	<meta name="go-import" content="{{.GoGetImport}} git {{.CloneLink.HTTPS}}">
modules/context/repo.go:	ctx.PlainText(200, []byte(com.Expand(`<meta name="go-import" content="{GoGetImport} git {CloneLink}">`,
modules/context/context.go:		<meta name="go-import" content="{GoGetImport} git {CloneLink}">

One can see in these files/lines that only the HTTPS path is ever returned. We expected that this can be at least configured to either return the SSH or HTTPS one. When disabling HTTPS for the repo, the returned links still stayed the same.

I don't think go get support SSH protocol.

It does. We use it in production. The meta tag should look as following:
<meta name="go-import" content="git.company.com/organization/private git<EMAIL_ADDRESS>

It does. We use it in production. The meta tag should look as following:
<meta name="go-import" content="git.company.com/organization/private git<EMAIL_ADDRESS>

When a version control system supports multiple protocols, each is tried in turn when downloading. For example, a Git download tries https://, then git+ssh://.

https://golang.org/cmd/go/#hdr-Remote_import_paths

Interesting! Thanks for the information.

It's quite useful for private internal git modules :)

OK looking at: https://github.com/golang/go/blob/95e1ea4598175a3461f40d00ce47a51e5fa6e5ea/src/cmd/go/internal/get/discovery.go#L36-L64
I think we could even have a second go-import tag which would save yet another setting...

Actually looking on - I think that might not work:
https://github.com/golang/go/blob/8cb865c9197f0f383b0bde48e37faea7b7a2451d/src/cmd/go/internal/get/vcs.go#L815
https://github.com/golang/go/blob/8cb865c9197f0f383b0bde48e37faea7b7a2451d/src/cmd/go/internal/get/vcs.go#L979-982
Sigh.

OK I think this is going to need (yet) another setting. The ideal would be a global setting and a per repository setting.
Simply because every time we do this we're causing a change of schema - I think we need a generic settings system and I'm opening an issue for that.

Here is : https://github.com/go-gitea/gitea/blob/main/CODE_OF_CONDUCT.md
Before asking "Why don't you solve this", please ask: could you write some code to help the open-source projects?
Complaining doesn't help anything.  Being constructive and respectful

@wxiaoguang 你说的很对， 我来解决这个问题

I send a pull request for this;
补丁好不好不说， 反正我提供了

Awesome, thank you very much. I did a quick review, I think the PR is high quality.
Before approving, there are only a few nits (I can vote my approval, it needs at least 2 approvals to be merged, other maintainers will also review)


Head properties not updated on Pages

Using last Nuxt version 2.15.7.
The Pages configuration do not iverride the global configuration set in the nuxt.config.js file.
When loading the page, for a very short time, I can see the global title on the browser tab, then it is updated with the right Page title.
Browsing the page source, the title, description and all other meta information are the ones set in globally. When sharing the pages to a social media it displays the global information and never the ones set in the Pages.
I see you wrote in the documentation:

Setting your SEO options via the asyncData should NOT be done in Server-Side Rendering (SSR) mode. For SSR, you should use the Nuxt head method above.

Unfortunately, by setting the $seo using asyncData is the only way to get it right. So, why we shouldn't if it is the only way to have it working as expected?

@Torone to make sure I understand what you are experiencing, I have a few questions:

when loading the page initially, your global default title is set as the actual page title (no matter what). then after a few moments, your page specific title is updated as the current page title?
is that "global title" you are seeing set in your seo or the head opbject in your nuxt-config.js file?

Reason to "not set SEO via asyncData"
The reason for the documentation stating to NOT set the SEO in asyncData for SSR is that the titles will not be updates as you navigate between the different pages on the Nuxt site. In this case the title is only updates upon initial load of the site. And will not change when navigating to another page. But if you refresh the browser on that new page, the title is updated
Request you share your code?
Based on your message, it sounds like you are experiencing the opposite though. Can you share your head and seo settings from nuxt-.config.js (your entire file would work too) as well as the way you are setting the seo data on a specific page?

I am having same issues as well. The title of the page initially shows from the nuxt config and then gets overridden by the page head configuration, but the page source still keeps the title and description from the nuxt config, thus always showing the same title and description across all pages when I share links to social media sites.

@sdevkota how are you setting specific titles on the page? Is it via asyncData or the head function?
Can you share your seo snippet from your nuxt.config.js file? And the code you are using on a specific page you are experiencing the problem?

@nickfrosty I just updated my comment above with the code snippets. Sorry should've done it earlier. Not via asyncData  but head ;

@sdevkota in your home page code, you are returning a generic JSON object.
In order to use the nuxt-seo plugin, you need to return the $seo property. Like this example from the docs usage page
From inside the head method, you can either:

destructure the context head({ $seo }), build your SEO data, and then return $seo(JSON_data), or
use the context within the head method via this.$seo. which would require your to use return this.$seo(JSON_data)

Also, the way you are using a separate function (the one you have named  createSEOmeta) is not required since this nuxt-seo package performs the hid assignment automatically.

@nickfrosty I switched it to nuxt-seo and it is a great plugin. Same thing, I guess that might be because ssr:false, target:'static'?


Konnect entities: Consumer's group assingment

Problem statement
After #436 and #514 are implemented we can now implement assigning consumers to a group.
Proposed solution

Request declarative group assignment API

https://kongstrong.slack.com/archives/C03LRB400TC/p1724411291389629

Use Consumer's group field: https://github.com/Kong/kubernetes-configuration/blob/9ac1d3cf7906e01a6bf14979fef9418195b2053e/api/configuration/v1/kongconsumer_types.go#L56-L59 for assigned groups

Acceptance criteria

[x] KGO can assign Consumers to ConsumerGroups in Konnect based on the groups field

Marking as blocked as we still do not have the declarative ConsumerGroup membership assignment implemented in the Konnect API: https://konghq.atlassian.net/browse/KOKO-1952

We shouldn't expect a declarative API anytime soon and do the state tracking on our side.
This is therefore unblocked.


Can I limit uuid length?

example :
$uuid1 = Uuid::uuid1();
echo $uuid1->toString() . "\n"; // i.e. e4eaaaf2-d142-11e1-b3e4-080027620cdd
$uuid1 = Uuid::uuid1(7); // for length 7

Do you mean the length of the string returned by toString()?

UUIDs cannot be shortened. They are 128-bit unsigned integers that are represented in a defined hexadecimal format. If you’re looking for shorter, non-sequential IDs, check out the hashids/hashids package or pascaldevink/shortuuid.

Thanks a lot <3


Text size in messages output is too small: make it configurable

Is your feature request related to a problem? Please describe.
My eyesight isn't great and I can't make the text in the messages output bigger. As it stands it is tiny.
Describe the solution or feature you'd like
An ability to customise the text: typeface and size.
Describe alternatives you've considered
Switching back to SSMS (despite no dark theme). Coping into a text editor to read.
Additional context
The red color used for errors makes this worse. The lack of contrast makes it even harder to read

you can use the Results Grid: Font Size to adjust the font size of the font in the entire output area (grid and messages). Does this solve your issue?

Regrading the color of the errors @yualan @angdesign we might look at making these theme aware colors so they can be configured

@anthonydresser  Results Grid: Font Size does work (but hardly discoverable: searches for "error", "output", "message" don't find it).
A highly saturated red on a dark background does need improvement (I find it not great on a light background either, again lack of contrast makes reading very hard – I have a severe astigmatism: contrast is everything).

I think we can add messages to the description in the setting which should make it more discoverable.

The error message color needs to be theme aware.  I'm not sure Red on Black has enough contrast ratio to meet our Accessibility requirements.
Adding messages to the description should address the original issue discussed, though we may want different settings for messages then resultsgrid, similar to SSMS.

The Results Grid font family setting now shows up when searching for "Messages" so I'll close this out now.


HIVE-27069: Incorrect results with bucket map join

What changes were proposed in this pull request?
The changes will fix the issue [HIVE-27069]. The issue is present while using Tez only.
For Bucket Map Join we should use FIXED Reducer Trait as it has to map buckets from small table to buckets buckets of big table. Current code also does the same for BucketMapJoin. When join is applied on tables it takes SIMPLE_EDGE as it has to do the table scan so here based on this condition Reducer Trait is set. But when query contains a subquery instead of a table then it takes a CUSTOM_SIMPLE_EDGE as it can be dynamically bucketed on the join column. Actually it takes CUSTOM_SIMPLE_EDGE when it uses Dynamically Partitioned HashJoin but here it uses Bucket Join only so just added a check like when edge type is CUSTOM_SIMPLE_EDGE and its not a Dynamically Partitioned Hash Join then setting Reducer Trait as FIXED.
Actually while fixing HIVE-11605 this issue got introduced. Earlier without having any check they were setting the value.

Why are the changes needed?
To fix [HIVE-27069]

Does this PR introduce any user-facing change?
No

How was this patch tested?
Added .q file and tested with .q file.

@mdayakar
Could you please elaborate a bit the root cause of the issue and why/how does this patch fix it?

@mdayakar Could you please elaborate a bit the root cause of the issue and why/how does this patch fix it?

@kasakrisz Updated the description, please check

LGTM +1


Pendulum 2.0.2 compatibility

Does the minimal work required to get maya working with pendulum 2.0.2, and run the test suite clean on py2.7 and py3.6.
Possible area for improvement:

make better use of pendulum's Duration class for parsed duration strings, and not assume that everything passed back by pendulum is a DateTime
be more robust around MayaInterval parsing to cope with strings that have a duration as the starting component, as well as the ending component

Addresses issue #160

Thanks for this first step :tada:
Do you know of any semantic changes in pendulum 2.0 which would break mayas API?

I'm sorry, I don't -- my only knowledge of pendulum is through use of maya, and my use of Maya is quite casual; the fixes to get maya at least testing clean with pendulum 2.0.2 seemed pretty straightforward, but I didn't do more investigation than just that.

The list of 2.0.0 changes is here: https://github.com/sdispater/pendulum/releases/tag/2.0.0
The 2.0.2 changes are just bug fixes.

any updates on this one?

Unfortunately, not from my side. I'll find some time tomorrow to have a look at this!

I'm closing this PR in favor of #166 🎉


Fix for Galaxy server annotation

The list of public Galaxy servers was moved to the hub, this updates the annotation script to get the list from new location.
ping @erasche

Gracias!!!