[Refactor] refactor sql tester cases of query external file

Fixes #issue
Some sql-tester cases are unstable. Probably because many test cases are running simultaneouly, then maybe some staments are executing at the same time：

ossutil64 rm -rf oss://${oss_bucket}/test_orc_count_star_opt/array_data_only
sql-query

So maybe sometimes, there will be error like 'file not found'.
To fix this case, it's better to generate unique environment for each run of test cases.
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

@mergify backport branch-3.1


[YUNIKORN-171] Add example and document about how to run kubeflow with yunikorn

Add a tfjob example for yunikorn.

Codecov Report

Merging #122 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #122   +/-   ##
=======================================
  Coverage   54.71%   54.71%
=======================================
  Files          30       30
  Lines        2811     2811
=======================================
  Hits         1538     1538
  Misses       1215     1215
  Partials       58       58

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 68c9fb7...6f8c443. Read the comment docs.

Overall looks good.
If its possible, I would like to have a Readme or Application section in landing Read me doc about the running apps YuniKorn.
Like Spark, Flink, Kubeflow etc called out explicitly

Yeah, that's a good suggestion. I do think our doc currently is not very easy to follow. Maybe we should have a separate section for this. We need to org our doc better than what we have now.


workbox-window.update() swallows errors

Library Affected:
workbox-window 5.1.2
Browser & Platform:
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36"
Issue or Feature Request Description:
workbox-window.update() seems to swallow errors. For instance, if I am offline the catch block below is never executed, nor do I see any error messages in the console.
wb.update().then(function () {
   // Do stuff
})
.catch(function (error) {
  // Handle error.
});

Workbox.update() is a very thin wrapper on top of ServiceWorkerRegistration.update(), which explicitly kicks off the service worker update flow (as opposed to waiting for the next implicit update check).
There's nothing in the service worker update flow that involves raising an exception or rejecting a promise if there's a failure when making the request for the new service worker file.
I know that there's another issue open with some feature requests to make Workbox.update() more useful, and that may happen in a future release of Workbox. In the meantime, though, the behavior you're seeing here is either expected. It amounts to a feature request, rather than a bug in the current behavior.

There's nothing in the service worker update flow that involves raising an exception or rejecting a promise if there's a failure when making the request for the new service worker file.

You seem to be right @jeffposnick. The error I was seeing when offline in my vanilla sw code were due to failed importScripts in the service worker script.
I have added a fetch just before the call to update() to trigger an error if offline.
await fetch(scriptURL, {method: 'HEAD'});

Sorry to bother you.


Added Query for Enums

*What:
Added query feature for Enums
*Why:
So that users can query for Enums
*How:
By writing code

@goru97 I think you need to rebase this PR against the enums-feature branch since we didn't a rebase of that against master a few days ago, and merged 3 other PRs in.  We can work together to resolve the conflicts that you'll most likely have with the rebase when you have a chance.

closed in favor of #527.


nltk.pos_tag performance

NLTK's built-in POS tagger doesn't perform so well:
>>> text = word_tokenize("The quick brown fox jumps over the lazy dog")
>>> pos_tag(text)
[('The', 'DT'), ('quick', 'NN'), ('brown', 'NN'), ('fox', 'NN'), ('jumps', 'NNS'), ('over', 'IN'), ('the', 'DT'), ('lazy', 'NN'), ('dog', 'NN')]

We need a better built-in model.
cf. http://stackoverflow.com/questions/30821188/python-nltk-pos-tag-not-returning-the-correct-part-of-speech-tag

@stevenbird Can we get one or more new labels for issues that try to improve coverage, accuracy, robustness of existing modules? I'm thinking also about e.g., better trained models for the dependency parser and the NER module, and making the CCG parser probabilistic.

@stevenbird , I think the simplest to "reimplement" with top quality accuracy is actually honnibal's perception tagger.
Next, the simplest to implement with unknown accuracy is ngram taggers with backoff ngram taggers using existing tagger corpora in NLTK or redistributable model that one can build with LDC's corpora (something like Spaghetti tagger.
There's one hand-crafted tagger with unknown accuracy too in nltk.parse.malt. Other rule-based tagger to consider is from [CLIPS' pattern.en] (https://github.com/clips/pattern/blob/master/pattern/text/en/init.py#L169). The major caveats of pattern's tagger is the dependence on lexicon.

@alvations: thanks for those suggestions. It looks like Honnibal's tagger uses an MIT license. @syllog1sm is there any objection to including this tagger in NLTK?

Sure, go ahead. You might want my transition-based parser too, which is also under MIT I think.

@honnibal – great, thanks very much

Another example of bad behaviour: http://stackoverflow.com/questions/32571486/nltk-red-not-recognised-as-an-adjective

Resolved by #1122


Attribute recognition

@Tiago-Roxo  thanks for sharing the code base , can we modify the architecture to perform attribute recognition like age , clothings and accessories ie multi lablel attribute recoginition . Pls share your thoughts
Thanks in advance

Hello.
Sorry for the late response.
Yes, you can alter the architecture for that goal.
One of the required changes is, besides a new .pkl of datasets with all the intended information (ours only has gender info), is a change in the num_att variable (e.g., line 37 in train.py) to your number of attributes. This will alter the model (check line 91 in train.py), particularly in the classifier layer (models/base_block_meta.py, in the function starting in line 7).
Another thing that needs to be changed is the att_model variable (line 33 in train.py). It is currently "-1," but you need to adapt it since this variable affects, at least, the "batch_trainer" (in batch_engine.py, lines 29 and 39). Another change is the way accuracy is calculated. Currently, it is only considering one variable but with more attributes it will probably not work (tools/function.py, in line 93).
If you change all the variables mentioned in all the files where they are used, you should be on the right track to have the model for multi-label attribute recognition.


play icon needs a space lol.

https://github.com/aome510/spotify-player/blob/8ea51d4829c4e234c5fd95fdab333eee41d0cd64/examples/app.toml#L20

play/pause icon looks fine on my end. If it doesn't work for you, you can always configure the icons to add extra space.

on my end whenever you pause, it throws the whole title one space to the right. i thought it was because pause had a space after it.

on my end whenever you pause, it throws the whole title one space to the right. i thought it was because pause had a space after it.

My guess is that the pause character doesn’t render nicely on your terminal. You can try another character, e.g non-unicode character like = to ensure the character’s width is 1.
Will close this issue for now.


Snowflake & Motherduck partner identifier params

This PR adds query parameters to connection strings of Snowflake and Motherduck destinations to allow them to discover dlt users.
Ticket: https://github.com/dlt-hub/dlt/issues/1257
TODO

[ ] Update Snowflake and Motherduck client configuration to include configurable integration params,
[ ] Waiting for DuckDb about their partner and integration identifiers,
[x] Adjust tests,

Converting to draft. Will just define two separate fields one for Snowflake one for Motherduck.


np.meshgrid not supported by Numba

Hi,
I am using np.meshgrid function inside one of the custom transformation function that I have written using the ffcv.pipeline.operation class and it is giving the following error

numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Failed in nopython mode pipeline (step: nopython frontend)
Use of unsupported NumPy function 'numpy.meshgrid' or unsupported use of the function.

Hi! I think this is an issue better raised in Numba---it seems like there are workarounds for implementing compilable version of mesh grid, see e.g., https://stackoverflow.com/questions/70613681/numba-compatible-numpy-meshgrid.

I agree, we are not maintaining numba, we are just using it as a dependency.


Fix a few highlighting errors and remove two modes

Fixes a few highlighting bugs such as keyword lists not having spaces at
the end causing the last keyword of one line and the first keyword of
the next to be combined. Also fixed highlighting of iso in class
definitions and function heads without bodies in traits and interfaces.
This also removes the FUNCTION and CLASS modes until there is a more
clear benefit to using them. In a couple cases such as an interface
with multiple function heads without an => indicating a body they
broke the highlighting of the second function head e.g.
interface Iterator[A: A]
  fun has_next(): Bool
  fun next(): T?

Thanks for fixing those. Will try to do a release with the fixes today or tomorrow.


Allow RSA-PSS also in EVP_PKEY_assign() and EVP_PKEY_can_sign()

As discussed in https://github.com/openssl/openssl/issues/21813 further fixes for RSA-PSS keys.

This pull request is ready to merge


expose low level api

can you say why you want to expose the low level API?

Hi sorry, I accidentally made a pr to original repo instead of the fork. So you can close it if you want but if you are interested in the use case and why do I need it feel free to consider:
I want to build DAS protocol similar to what Avail does with their light client approach. In nutshell light client need to pick few cells from data blob (a grid of kzg.Blobs) in order to verify if data is available. Each cell is a tuple (value, proof). So published data block has to have a proof to every value. Light client can query these tuples and verify them agains KZG commitment.
Existing implementation allows to generate a proof agains a random value but not within the polynomial domain.
Also high level API calls have a bit of redundancy: results are serialised, and when they are passed into a next function they are deserialised. Not sure what are the benefits of serialising points and scalars all the time.

Hey no worries :)
What you want makes complete sense. I'll be working on a new implementation that exposes this behaviour in the coming weeks. The (slight) issue with the current implementation is that it produces one proof per point being opened, whereas a "Cell", atleast how it is defined in the ethereum specs, can contain 64 opening points.
For this, we can use a more efficient kzg proving scheme that allows one proof per 64 points without sacrificing much in terms of performance.

@kevaundray can you point me to this documentation that actually might be my case as well.

@kevaundray can you point me to this documentation, that actually might be my case as well.

Yep sure, it should all be in this document: https://github.com/ethereum/consensus-specs/blob/master/specs/_features/eip7594/polynomial-commitments-sampling.md#compute_cells_and_kzg_proofs

Going to close this as we have started to add the above functionality into the library


Remove extra closing div tag

There's an extra unnecessary </div> tag here that isn't valid.

Thanks!


no music just crackles

I'm having no music and its an OGG file i tried to fix it anyway i could think of please HELP

you're the first one to have this bug so it might be just your file, just download it again or convert it to ogg again in a software like audacity.

Hey! I also had this issue. In my case I was able to fix it by selecting another audio output device in the Windows Control Panel.


Error: tuner_command_channel: Tuner closed connection

Describe the issue:
When I run the nni experiment, the webui gets stuck after a while, and the running and subsequent trials stop. I check the log file, and the contents of each log file are as follows. In 'dispatcher.log', it shows that 'AttributeError: module 'numpy' has no attribute 'float'.'. I would like to know how to solve this problem, thanks!
Environment:

NNI version: 2.10.1
Training service (local|remote|pai|aml|etc): local
Client OS: Ubuntu
Python version: 3.10.10
PyTorch/TensorFlow version: PyTorch 1.13.1
Is conda/virtualenv/venv used?: conda
Is running in Docker?: No
numpy: 1.24.3

Configuration:
experimentName: xxx

searchSpace:
  batch_size:
    _type: choice
    _value: [128]
  xxx.....

trialCommand: python main.py
trialCodeDirectory: .
trialGpuNumber: 1
trialConcurrency: 4
maxExperimentDuration: 100h
maxTrialNumber: 1000

tuner:
  name: TPE  # or SMAC
  classArgs:
    optimize_mode: maximize

assessor:
  name: Curvefitting
  classArgs:
    epoch_num: xx
    start_step: xx
    threshold: xx
    gap: xx

trainingService:
  platform: local
  useActiveGpu: True
  maxTrialNumberPerGpu: 1
  gpuIndices: [4, 5, 6, 7]

Log message:

nnimanager.log:

[2023-06-09 12:57:11] INFO (main) Start NNI manager
[2023-06-09 12:57:11] INFO (NNIDataStore) Datastore initialization done
[2023-06-09 12:57:11] INFO (RestServer) Starting REST server at port 8080, URL prefix: "/"
[2023-06-09 12:57:11] WARNING (NNITensorboardManager) Tensorboard may not installed, if you want to use tensorboard, please check if tensorboard installed.
[2023-06-09 12:57:11] INFO (RestServer) REST server started.
[2023-06-09 12:57:12] INFO (NNIManager) Starting experiment: qa7ydetw
[2023-06-09 12:57:12] INFO (NNIManager) Setup training service...
[2023-06-09 12:57:12] INFO (LocalTrainingService) Construct local machine training service.
[2023-06-09 12:57:12] INFO (NNIManager) Setup tuner...
[2023-06-09 12:57:12] INFO (NNIManager) Change NNIManager status from: INITIALIZED to: RUNNING
[2023-06-09 12:57:13] INFO (NNIManager) Add event listeners
[2023-06-09 12:57:13] INFO (LocalTrainingService) Run local machine training service.
[2023-06-09 12:57:13] INFO (NNIManager) NNIManager received command from dispatcher: ID,
[2023-06-09 12:57:13] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 0, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.5687418247198174, "pe_dropout": 0.3795992922324143, "attn_dropout": 0.31940210733313745, "gru_dropout": 0.7501120836764036, "head_dropout": 0.9413345527713036, "label_smoothing": 0.2971732637510747, "pool": 0}, "parameter_index": 0}
[2023-06-09 12:57:13] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 1, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.6106341933273577, "pe_dropout": 0.362797822930322, "attn_dropout": 0.3928725106416544, "gru_dropout": 0.3227819485793446, "head_dropout": 0.872189272426159, "label_smoothing": 0.350726674354764, "pool": 0}, "parameter_index": 0}
[2023-06-09 12:57:13] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 2, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.5297279262160532, "pe_dropout": 0.40210539352497937, "attn_dropout": 0.368406504769002, "gru_dropout": 0.3530454310598614, "head_dropout": 0.8271236612115623, "label_smoothing": 0.2640100599154913, "pool": 0}, "parameter_index": 0}
[2023-06-09 12:57:13] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 3, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.6816049034866344, "pe_dropout": 0.36311316138448635, "attn_dropout": 0.3026207961686919, "gru_dropout": 0.703280384754806, "head_dropout": 0.8660018580114488, "label_smoothing": 0.1821250821626217, "pool": 0}, "parameter_index": 0}
[2023-06-09 12:57:18] INFO (NNIManager) submitTrialJob: form: {
  sequenceId: 0,
  hyperParameters: {
    value: '{"parameter_id": 0, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.5687418247198174, "pe_dropout": 0.3795992922324143, "attn_dropout": 0.31940210733313745, "gru_dropout": 0.7501120836764036, "head_dropout": 0.9413345527713036, "label_smoothing": 0.2971732637510747, "pool": 0}, "parameter_index": 0}',
    index: 0
  },
  placementConstraint: { type: 'None', gpus: [] }
}
[2023-06-09 12:57:18] INFO (NNIManager) submitTrialJob: form: {
  sequenceId: 1,
  hyperParameters: {
    value: '{"parameter_id": 1, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.6106341933273577, "pe_dropout": 0.362797822930322, "attn_dropout": 0.3928725106416544, "gru_dropout": 0.3227819485793446, "head_dropout": 0.872189272426159, "label_smoothing": 0.350726674354764, "pool": 0}, "parameter_index": 0}',
    index: 0
  },
  placementConstraint: { type: 'None', gpus: [] }
}
[2023-06-09 12:57:18] INFO (NNIManager) submitTrialJob: form: {
  sequenceId: 2,
  hyperParameters: {
    value: '{"parameter_id": 2, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.5297279262160532, "pe_dropout": 0.40210539352497937, "attn_dropout": 0.368406504769002, "gru_dropout": 0.3530454310598614, "head_dropout": 0.8271236612115623, "label_smoothing": 0.2640100599154913, "pool": 0}, "parameter_index": 0}',
    index: 0
  },
  placementConstraint: { type: 'None', gpus: [] }
}
[2023-06-09 12:57:18] INFO (NNIManager) submitTrialJob: form: {
  sequenceId: 3,
  hyperParameters: {
    value: '{"parameter_id": 3, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 512, "ffn_dropout": 0.6816049034866344, "pe_dropout": 0.36311316138448635, "attn_dropout": 0.3026207961686919, "gru_dropout": 0.703280384754806, "head_dropout": 0.8660018580114488, "label_smoothing": 0.1821250821626217, "pool": 0}, "parameter_index": 0}',
    index: 0
  },
  placementConstraint: { type: 'None', gpus: [] }
}
[2023-06-09 12:57:23] INFO (NNIManager) Trial job wGF5H status changed from WAITING to RUNNING
[2023-06-09 12:57:23] INFO (NNIManager) Trial job l1qUb status changed from WAITING to RUNNING
[2023-06-09 12:57:23] INFO (NNIManager) Trial job TpSLZ status changed from WAITING to RUNNING
[2023-06-09 12:57:23] INFO (NNIManager) Trial job vJ6Yb status changed from WAITING to RUNNING
[2023-06-09 14:08:37] INFO (NNIManager) Trial job vJ6Yb status changed from RUNNING to SUCCEEDED
[2023-06-09 14:08:37] INFO (NNIManager) NNIManager received command from dispatcher: TR, {"parameter_id": 4, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 1024, "ffn_dropout": 0.5147415801616881, "pe_dropout": 0.3754598540657963, "attn_dropout": 0.28474165110165683, "gru_dropout": 0.6126774117630752, "head_dropout": 0.904972479249912, "label_smoothing": 0.32764941826042104, "pool": 0}, "parameter_index": 0}
[2023-06-09 14:08:42] INFO (NNIManager) Trial job l1qUb status changed from RUNNING to SUCCEEDED
[2023-06-09 14:08:42] INFO (NNIManager) submitTrialJob: form: {
  sequenceId: 4,
  hyperParameters: {
    value: '{"parameter_id": 4, "parameter_source": "algorithm", "parameters": {"batch_size": 128, "lr": 0.01, "momentum": 0.9, "n_heads": 64, "n_layers": 1, "d_ff": 1024, "ffn_dropout": 0.5147415801616881, "pe_dropout": 0.3754598540657963, "attn_dropout": 0.28474165110165683, "gru_dropout": 0.6126774117630752, "head_dropout": 0.904972479249912, "label_smoothing": 0.32764941826042104, "pool": 0}, "parameter_index": 0}',
    index: 0
  },
  placementConstraint: { type: 'None', gpus: [] }
}
[2023-06-09 14:08:44] ERROR (tuner_command_channel.WebSocketChannel) Error: Error: tuner_command_channel: Tuner closed connection
    at WebSocket.handleWsClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:83:26)
    at WebSocket.emit (node:events:538:35)
    at WebSocket.emitClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:246:10)
    at Socket.socketOnClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:1127:15)
    at Socket.emit (node:events:526:28)
    at TCP.<anonymous> (node:net:687:12)

dispatcher.log:

[2023-06-09 20:57:12] INFO (nni.tuner.tpe/MainThread) Using random seed 829346290
[2023-06-09 20:57:12] INFO (curvefitting_Assessor/MainThread) Successfully initials the curvefitting assessor
[2023-06-09 20:57:12] INFO (nni.runtime.msg_dispatcher_base/MainThread) Dispatcher started
[2023-06-09 22:08:37] INFO (curvefitting_Assessor/Thread-2 (command_queue_worker)) Updated completed best performance, trial job id: vJ6Yb
[2023-06-09 22:08:38] INFO (curvefitting_Assessor/Thread-2 (command_queue_worker)) List of effective model: ['vap', 'pow3', 'linear', 'logx_linear', 'dr_hill_zero_background', 'log_power', 'pow4', 'mmf', 'exp4', 'weibull', 'janoschek']
[2023-06-09 22:08:38] ERROR (curvefitting_Assessor/Thread-2 (command_queue_worker)) unrecognize exception in curvefitting_assessor module 'numpy' has no attribute 'float'.
`np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
    https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
Traceback (most recent call last):
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefitting_assessor.py", line 120, in assess_trial
    predict_y = curvemodel.predict(scalar_trial_history)
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/model_factory.py", line 326, in predict
    self.mcmc_sampling()
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/model_factory.py", line 290, in mcmc_sampling
    init_weight = np.ones((self.effective_model_num), dtype=np.float) / self.effective_model_num
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/numpy/__init__.py", line 305, in __getattr__
    raise AttributeError(__former_attrs__[attr])
AttributeError: module 'numpy' has no attribute 'float'.
`np.float` was a deprecated alias for the builtin `float`. To avoid this error in existing code, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
    https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
[2023-06-09 22:08:38] ERROR (nni.runtime.msg_dispatcher_base/Thread-2 (command_queue_worker)) Result of Assessor.assess_trial must be an object of AssessResult, not <class 'NoneType'>
Traceback (most recent call last):
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/runtime/msg_dispatcher_base.py", line 108, in command_queue_worker
    self.process_command(command, data)
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/runtime/msg_dispatcher_base.py", line 154, in process_command
    command_handlers[command](data)
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/runtime/msg_dispatcher.py", line 149, in handle_report_metric_data
    self._handle_intermediate_metric_data(data)
  File "/home/sunze/miniconda3/lib/python3.10/site-packages/nni/runtime/msg_dispatcher.py", line 234, in _handle_intermediate_metric_data
    raise RuntimeError(msg % type(result))
RuntimeError: Result of Assessor.assess_trial must be an object of AssessResult, not <class 'NoneType'>
[2023-06-09 22:08:42] INFO (nni.runtime.msg_dispatcher_base/MainThread) Dispatcher exiting...
[2023-06-09 22:08:44] INFO (nni.runtime.msg_dispatcher_base/MainThread) Dispatcher terminiated

nnictl stdout:

--------------------------------------------------------------------------------
Experiment qa7ydetw start: 2023-06-09 20:57:11.300714
--------------------------------------------------------------------------------

nnictl stderr:

--------------------------------------------------------------------------------
Experiment qa7ydetw start: 2023-06-09 20:57:11.300714
--------------------------------------------------------------------------------
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:56: RuntimeWarning: overflow encountered in power
  return c - a * x**(-alpha)
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:56: RuntimeWarning: overflow encountered in multiply
  return c - a * x**(-alpha)
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:124: RuntimeWarning: invalid value encountered in scalar power
  return (theta * x**eta) / (kappa**eta + x**eta)
/home/sunze/miniconda3/lib/python3.10/site-packages/scipy/optimize/_minpack_py.py:906: OptimizeWarning: Covariance of the parameters could not be estimated
  warnings.warn('Covariance of the parameters could not be estimated',
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:171: RuntimeWarning: invalid value encountered in power
  return c - (a*x+b)**-alpha
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:196: RuntimeWarning: invalid value encountered in power
  return alpha - (alpha - beta) / (1. + (kappa * x)**delta)
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:220: RuntimeWarning: overflow encountered in exp
  return c - np.exp(-a*(x**alpha)+b)
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:242: RuntimeWarning: divide by zero encountered in divide
  return c - a / np.log(x)
/home/sunze/miniconda3/lib/python3.10/site-packages/nni/algorithms/hpo/curvefitting_assessor/curvefunctions.py:242: RuntimeWarning: divide by zero encountered in scalar divide
  return c - a / np.log(x)
node:events:504
      throw er; // Unhandled 'error' event
      ^

Error: tuner_command_channel: Tuner closed connection
    at WebSocket.handleWsClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:83:26)
    at WebSocket.emit (node:events:538:35)
    at WebSocket.emitClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:246:10)
    at Socket.socketOnClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:1127:15)
    at Socket.emit (node:events:526:28)
    at TCP.<anonymous> (node:net:687:12)
Emitted 'error' event at:
    at WebSocketChannelImpl.handleError (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:135:22)
    at WebSocket.handleWsClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:83:14)
    at WebSocket.emit (node:events:538:35)
    [... lines matching original stack trace ...]
    at TCP.<anonymous> (node:net:687:12)
Thrown at:
    at handleWsClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:83:26)
    at emit (node:events:538:35)
    at emitClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:246:10)
    at socketOnClose (/home/sunze/miniconda3/lib/python3.10/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:1127:15)
    at emit (node:events:526:28)
    at node:net:687:12

How to reproduce it?:

So could you try nni v3.0rc1 to test it? @sunze992

I tried this version, but ran into another problem: webui wouldn't start. I found out that glibc version is 2.27. It seems that glibc version is too low for webui to start. glibc is the underlying library of Ubuntu system, so I can't upgrade it easily to avoid all kinds of system problems. So now I have this new problem, do you know how to solve it? Thanks!

Seems that you indeed need an updated version for Ubuntu

I've encountered the same issue while using v3.0rc1 on Ubuntu 22.04. It seems like the curve fitting assessor requires a version of numpy that is 1.1 or earlier?


minimal profile produces a lot of warnings (-Wunused-function)

Description

Type: Bug

Bug
mbed-client-cli version
b97cbfb3db70058ed66579b7496200f851d386a2
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:368:25: warning: ‘cmd_history_save’ declared ‘static’ but never defined [-Wunused-function]
 static void             cmd_history_save(int16_t index);
                         ^~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:369:25: warning: ‘cmd_history_get’ declared ‘static’ but never defined [-Wunused-function]
 static void             cmd_history_get(uint16_t index);
                         ^~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:370:25: warning: ‘cmd_history_clean_overflow’ declared ‘static’ but never defined [-Wunused-function]
 static void             cmd_history_clean_overflow(void);
                         ^~~~~~~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:371:25: warning: ‘cmd_history_clean’ declared ‘static’ but never defined [-Wunused-function]
 static void             cmd_history_clean(void);
                         ^~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:372:25: warning: ‘cmd_history_find’ declared ‘static’ but never defined [-Wunused-function]
 static cmd_history_t   *cmd_history_find(int16_t index);
                         ^~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:387:25: warning: ‘goto_end_of_history’ declared ‘static’ but never defined [-Wunused-function]
 static void             goto_end_of_history(void);
                         ^~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:388:25: warning: ‘goto_beginning_of_history’ declared ‘static’ but never defined [-Wunused-function]
 static void             goto_beginning_of_history(void);
                         ^~~~~~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1872:13: warning: ‘cmd_variable_print_all’ defined but not used [-Wunused-function]
 static void cmd_variable_print_all(void)
             ^~~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1820:24: warning: ‘variable_find’ defined but not used [-Wunused-function]
 static cmd_variable_t *variable_find(char *variable)
                        ^~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1796:21: warning: ‘alias_find_n’ defined but not used [-Wunused-function]
 static cmd_alias_t *alias_find_n(char *alias, int aliaslength, int n)
                     ^~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1774:21: warning: ‘alias_find’ defined but not used [-Wunused-function]
 static cmd_alias_t *alias_find(const char *alias)
                     ^~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1648:13: warning: ‘cmd_replace_variables’ defined but not used [-Wunused-function]
 static void cmd_replace_variables(char *input)
             ^~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1626:13: warning: ‘replace_variable’ defined but not used [-Wunused-function]
 static void replace_variable(char *str, cmd_variable_t *variable_ptr)
             ^~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1615:13: warning: ‘cmd_replace_alias’ defined but not used [-Wunused-function]
 static void cmd_replace_alias(char *input)
             ^~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1559:13: warning: ‘cmd_clear_last_word’ defined but not used [-Wunused-function]
 static void cmd_clear_last_word()
             ^~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1547:13: warning: ‘cmd_move_cursor_to_next_space’ defined but not used [-Wunused-function]
 static void cmd_move_cursor_to_next_space(void)
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1533:13: warning: ‘cmd_move_cursor_to_last_space’ defined but not used [-Wunused-function]
 static void cmd_move_cursor_to_last_space(void)
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1507:6: warning: ‘cmd_tab_lookup’ defined but not used [-Wunused-function]
 bool cmd_tab_lookup(void)
      ^~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1184:13: warning: ‘cmd_arrow_left’ defined but not used [-Wunused-function]
 static void cmd_arrow_left()
             ^~~~~~~~~~~~~~
/home/teetak01/devel/mbed-client-testapp/mbed-client-cli/source/ns_cmdline.c:1163:13: warning: ‘cmd_arrow_right’ defined but not used [-Wunused-function]
 static void cmd_arrow_right()

Originally I decided to use #ifdef and linker combination to reduce foot print of the library. #ifdef reduce calls that is not needed for selected configuration and linker do rest of reduction jobs (require some optimization flag, like -O1). Reason for this was that number of #ifdef start growing and makes harder to read the code. It is true that -Wunused-function causes ~20 errors because of unused function, but using -Wno-unused-function silents those errors.
Questions:

Does current approach works for all compilers we use ?
Which compiler option is default in mbed-os (-Wunused-function or -Wnounused-function) ?
Is there some optimization enabled by default ? (-O1)
How mbed-os implementation generally does this thing ? (only #ifdef's or rely on linker functionality to drop unused functions)
Should we encapsulate also "unused functions" with #ifdef even it makes code less readable ?

@seppo @kjbracey-arm please check this out..

This warning is on by default in most compilers - seems you're doing something which really does tend to provoke it.
We tend to use ifdefs where this arises in Mbed OS, but it doesn't occur that often. Normally stuff that isn't used is not marked static, which is what prompts the complaint.
I think marking the functions static inline should shut that warning up in all compilers, with no downside that I can see if it's called exactly once. Or you could stop them being static.
It's possible the MBED_UNUSED attribute in mbed_toolchain.h might work, but it's only documented for use on parameters.

most of those functions that causes compiler warning are called only once so inline is just fine for them. It also seems to work as expected so I'll create PR with inline.

seems that ARM compiler was not happy with inline:
[Error] ns_cmdline.c@1740,0:  #1059-D: an entity with internal linkage cannot be referenced within an inline function with external linkage

Hmm have to re-think how to fix this.

It's possible the MBED_UNUSED attribute in mbed_toolchain.h might work, but it's only documented for use on parameters.

Would not like to use mbed-os specific attributes since library is generic and used with other OS's as well...

They should have been set static inline, not just inline.   They're still private to that C file, right?

seems that static inline does not silent these warnings:
../../source/ns_cmdline.c:388:39: error: unused function 'goto_beginning_of_history' [-Werror,-Wunused-function]
static inline void                    goto_beginning_of_history(void);

Okay, that's a bit weird. It must be distinguishing between headers and C files, because it wouldn't complain if there was an unused "static inline" in a header.

How about sticking pragma(s) at the top of the file to silence the warnings? When the code isn't wrong, and any change would make it worse, I'd rather shut the compiler up:
#pragma GCC diagnostic ignored "-Wunused-function"

will work for Clang (ARMC6) and GCC. IAR

that's fine for me also. Does anyone have an objection?
@SeppoTakalo @teetak01


Event not sent

Hi there.
I'm sorry if this is vague but unfortunately I don't have much time to spend on this at this stage.
Anyway, I swapped my SingleLiveEvent class taken from the one on the google repo for yours since I needed the same functionality but with multiple observers.
All I did is a direct copy paste into the SingleLiveEvent class with your code in, and the very first event I use in the class ( it's on the main activity to decie whther to go to the login screen or Home ) never fired at all, so the app just hangs there.
I've left the exact same code as from SingleLiveEvent, only swapped out the code in the class, and it doesn't work.
I don't know if there's something obvious I'm missing...

Thank you for your feedback.
I added some tests here to check your claim, but they work as expected! Would you provide a test case? Thanks.

Close due to inactivity.


Don't show 'OK' button when autoOK is enabled.

^

I'm not sure we want this. Could you explain?

@oliviertassinari If you notice the date-picker with AutoOk enabled the OK button is not displayed and the same is expected in the time-picker as well.

If you notice the date-picker with AutoOk enabled the OK button is not displayed

That's right. I think that it should be displayed for the DatePicker. Let's say the autoOk property is true and that I just want to change the year. I need the OK button to be there. It's kind of the same with the TimePicker.
What do you think?

With autoOK enabled it makes no sense to have the OK button.
If your usecase is to change the year/time then don't set the autoOK attribute.

I have a second concern with this change. Let's say we have a TimePicker with the autoOK option and that the user pick a time and now he just want to change the hour. Without the ok button, he has to reselect the minutes.

don't set the autoOK attribute

Is this your answer to this issue ?

With the below layout with auto ok, the user can meet your requirement?

Yes. But let's ask @shaurya947 what he think.

@hemanth @oliviertassinari personally, I would never have a picker without the OK button.
Perhaps we need to change DatePicker to also display the OK button even when autoOK is enabled?

What's the purpose of autoOK then?

What's the purpose of autoOK then?

Good question, the description in the could be improved. As far as I know this option is useful when the user pick a date / time and you want to save the last step : click on OK.

Yes, if that is the case, then it make sense not to show the OK button as it's already in date-picker ?

Yes, It does. However, right know, there is some edge cases where you need this ok button event those the autoOK is set.

@hemanth @oliviertassinari if you look at the pickers in the Material Design spec, all of them have the "OK" button. It seems like the autoOK prop is just something we added as a convenience to save the user one click.
If anything, it confuses developers and potentially leads to a non-uniform user experience. I'm all for deprecating autoOk prop and removing it in v0.14.0. Thoughts?

When there are multiple date picker autoOK save few clicks, that's why I was happy about it.

Looking at the thread, it seems everyone agrees the OK button should remain, even when autoOk is set. I'm closing for now, but we can revisit if there's a compelling case to reconsider.

:+1:


fix: correct jsdoc

using correct jsdoc will allow us to have easier to maintain.

Gah! Sorry I missed this PR. Yes, you're very right. I saw you do this on your YAML PR.
I think I accidentally stomped this PR with https://github.com/nodejs-loaders/nodejs-loaders/pull/57 though: I think merging this will only create a conflict there (I think it already covers the great updates you've made here).

we can close this one in favor of your


PureBasic: Add ".pbf" and ".pbp" Extensions

Add PureBasic's .pbf and .pbp file extensions:

.pbf to "PureBasic" setcion
.pbp to "XML" setcion

*.pbf files are "form files" created with PureBasic IDE's integrated Form Designer. Form files' contents are just PureBasic sourcecode:
http://www.purebasic.com/documentation/reference/ide_form.html
*.pbp files are PureBasic project files, created by the PureBasic IDE. They are just XML files:
http://www.purebasic.com/documentation/reference/ide_projects.html
http://www.purebasic.com/documentation/reference/ide_tools.html

Please have a look at the guidelines to add support for a new extension to Linguist. In particular, you'll need to link to a GitHub search result page showing in-the-wild usage, for each extension.

Ok, I've created an example project in "samples" that provides sample files for both ".pbp" (XML) and  ".pbf" (PureBasic code) files.
I'm not sure about the search results links requirement, the guidelines are quite terse about it. The best I've managed is this:
https://github.com/search?q=extension%3Apbf+extension%3Apbp+fork%3Atrue+label%3Apurebasic+NOT+nothack&type=Code&utf8=✓
... but search result include some false positives for .pbp extension (some "*.PBP" binary files), even though I specified in  advanced search to filter with a "purebasic" label (which, by the way, probably reduces drastically the result findings).

First off, thanks for the contribution. I've taken a quick look at the general structure of .pbf files that I can find on GitHub that aren't binary files and they all seem to share a common use of the word event With this in mind, I created a search for this extension using this keyword and found very few results: https://github.com/search?utf8=✓&q=extension%3Apbf+Event+NOT+nothack&type=Code
I performed a similar search for pbp, which is much easier as it's XML and also got very few results: https://github.com/search?utf8=✓&q=extension%3Apbp+xml+NOT+nothack&type=Code
As per our contributing guidelines, we really need each extension individually to be used in hundreds of repositories. Neither extension meets this requirement. Accordingly, we can't accept this PR at this stage and I've labeled this PR accordingly.
Additionally, the failures in this PR are legit failures that need to be addressed.
The two .cfg files should probably also be removed from this PR as they look more like editor configuration files than files written in PureBasic.

As per our contributing guidelines, we really need each extension individually to be used in hundreds of repositories. Neither extension meets this requirement.

I understand your point, but as far as the *.pbf extension goes, it's just an alternative extension to the default *.pb extensions (which is already registered with Linguist). The *.pb being the base extension, the others are just alternative conventions, where *.pbi simply indicates that it's an "include" file (that doesn't do anything by itself), and the f in *.pbf indicates that is a "form" file (ie: autogenerated by the IDE's form manager).
Conventions aside, they are just plain PureBasic syntax files, using the same syntax.
PureBasic is a bit of a niche language, add to that that the *.pbf extension is not commonly used in many projects, than chances are that currently GitHub won't be hosting enough search results as required in the specifications you pointed out.
I'd like though to make a point of the fact that PureBasic is a 20 years old language (started out in 1998, and underwent major updates). It originally run on Amiga (the Amiga version being open source now), and currently runs on Windows, Linux and macOS. Maybe the sheer fact that it has been around for 20 years could be taken into account in this case.
https://en.wikipedia.org/wiki/PureBasic
As said, I'm only trying to register on Linguist variations of what is an already present extension — I've provided links to the official documentation in support of that.

The two .cfg files should probably also be removed from this PR as they look more like editor configuration files than files written in PureBasic.

Correct; I just added them for the sake of completness  — basically, I've put in this PR all the manual settings that I usually put in the .gitattribures file of a PureBasic project. Usually, in my Linguist settings I configure the *.cgf and *.pbp extensions as auto-generated.

I understand your point, but as far as the *.pbf extension goes, it's just an alternative extension to the default *.pb extensions (which is already registered with Linguist).

They may be, but we require all extensions meet these requirements, regardless of how popular the language or another extension of that language is.

I understand. What should we do then, should I close the pull request?
Can I then safely delete my PR branch and/or my fork of Linguist?

It's entirely up to you. You can keep the PR open and check up on the popularity over time, but then you can't delete your fork. Or close the PR, delete your fork and keep an eye on the popularity and when things become more popular open a new PR.

Closing in favor of #4219. We'll monitor the popularity of the extensions there.
If you have improved search queries compared to those I used in #4219, please post them here and I'll update #4219.


[Bug] Invalid file generated in Python client

Describe the Bug
An invalid file is being generated, with an empty method.
Information to Reproduce
CLI Version
v0.16.25
Generator Version
0.7.2
Custom Config
I don't think it's custom, but here it is in full
default-group: local
groups:
  local:
    generators:
      - name: fernapi/fern-python-sdk
        version: 0.7.2
        output:
          location: local-file-system
          path: ../generated/sdk/python

Fern Definition
The minimal fern definition required to reproduce the bug.
Unknown
Actual Python SDK
The buggy Python SDK that is produced:
# This file was auto-generated by Fern from our API Definition.

import enum
import typing

T_Result = typing.TypeVar("T_Result")
class OauthScope(str, enum.Enum):
    def visit(self) -> T_Result:
# missing anything in the method body

Expected Python SDK
Honestly not sure. API seems to work fine if I just put pass in there.
# This file was auto-generated by Fern from our API Definition.

import enum
import typing

T_Result = typing.TypeVar("T_Result")

class OauthScope(str, enum.Enum):
    def visit(self) -> T_Result:
        pass

Additional Context
I tried tracking this down, but I don't actually see anything about this in the fern .definition of the API. I'm attaching the full swagger.json. This isn't super urgent, and I don't know if it happens with other openapi specs, but if it does then getting this fixed will make onboarding easier for new folks, as they can run fern and then black/ruff/whatever linting they have set up and the linters won't complain. Also this could be an issue with the spec itself, I'm not sure, but if that's the case maybe fern can let me know what's missing like it did with the other spec issues :)
swagger.json

@Daniel-Vetter-Coverwhale, could you try this on the latest version of the python generator - 0.11.10? There have been a large number of changes since this version!
https://github.com/fern-api/fern/blob/main/generators/python/sdk/CHANGELOG.md

Hey sorry this took me a long time to get back to, my apologies!
I upgraded fern itself to 0.19.24
❯ fern --version
(node:15843) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
0.19.24

and the python generator to 0.8.0
      - name: fernapi/fern-python-sdk
        version: 0.8.0
        output:
          location: local-file-system
          path: ../generated/

but now I'm getting
❯ fern generate --local
(node:15980) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[api]: POST /v1/tenants/{tenantUniqueName}/geofence is marked with x-fern-ignore. Skipping.
[api]: Found 3 errors and 4 warnings. Run fern check --warnings to print out the warnings.
[api]: eventAccess.yml -> service -> endpoints -> getVideoPlayUrl -> examples[0] -> path-parameters
       Example is missing required path parameter "tenantUniqueName"
[api]: eventAccess.yml -> service -> endpoints -> getVideoPlayUrl -> examples[0] -> path-parameters
       Example is missing required path parameter "videoIds"
[api]: eventAccess.yml -> service -> endpoints -> getVideoPlayUrl -> examples[0] -> response
       Expected example to be an object. Example is: undefined

which looks like it's complaining about something in the IR? That op (getVideoPlayUrl) doesn't seem to have any examples, so it makes sense that they would be missing, but doesn't necessarily make sense that that matters.
Sorry again for the late response! I'm using fern with a few other api specs, and it works much better for those. This weird spec might be useful though, since I have encountered many poorly written specs out there in the wild. I appreciate you guys and fern, thanks again!

@Daniel-Vetter-Coverwhale would you be able to share an updated API spec?

@Daniel-Vetter-Coverwhale given you're no longer with the Coverwhale team, I'm going to close this out and can re-engage if others run into the same issue down the line.


routeable address discovery and specification of internet routeable interface

well, it's done, all addresses using explicit addresses. But actually the listeners should be :00000

Need to find the concrete active addresses for automatic addresses as described above also, adding new variables to store them and a setting to make them automatically discover that can be turned off if manual is preferred. The discovery enables routing across all interfaces with a multicast zone, including zerotier and VPNs and hypervisors.

simplest and dumbest solution is to loop through the given IP addresses and drop out on the first one that succeeds, since it doesn't happen often a simple solution is probably enough.


Implement a logger instead of print statements

Change all print statements to use Logger from OSLog.

[ ] Each package should have it's own log category
[ ] The logger's subsystem should be the product bundle identifier. If you need a default value use dev.cctplus.peakfit
[ ] The logger should live in the utilities package
[ ] The logger should be callable using PFLogger()
[ ] This PR should be labeled as a chore

Resources:

Modern logging with OSLog by Donny Wals

I would like to this issue.

@rajhraval it's all yours!

Just have some doubts:

Each package should have it's own log category

So it should be called like PFLogger.error(package: .design, error) Denoting it is an error from Design Package?

The logger should live in the utilities package

But if all packages import the Utilities package isn't it bad? That you are importing a single package too many times in different packages?

PFLogger.error(package: .design, error) I've tried doing stuff like this before, but I end up loosing functionality from the Logger in OSLog. I more so imagined it working like this:
// Error example
PFLogger.log(.design).error("message here")
// Debug example
PFLogger.log(.dataStorage).info("Saved a new exercise: \(exercise.name, privacy: .public)")

the .log function takes in a category that is whatever package it's being called from or even more specific category added later (like maybe one for a service) and returns a properly configured Logger with . The .error() is the Logger's built in error. This allows us to utilize the message capability to mark values as private if needed.
I should have probably put more of this in the issue description, so I'm sorry about that.

But if all packages import the Utilities package isn't it bad?

There shouldn't be an issue. This project uses a modularized code base and that's exactly what this does. If you have any docs or articles saying otherwise, then I'd love to read them.
Hopefully that helps answer some questions

Oh, like this. I have raised a PR with my kind of implementation not added the statements, does it align?

@rajhraval i'm gonna look at the PR after work today. Sorry for the delay.


Unit tests using OverlayRef fails with Error: 1 timer(s) still in the queue.

All my component unit tests that are exercising Material components that make use of OverlayRef, like mat-select throw an error when my unit test destroys the test fixture due to a setTimeout(500) in OverlayRef.detachBackdrop:
https://github.com/angular/material2/blob/5321ab3cc4104369ea756857210c724f6c028cea/src/cdk/overlay/overlay-ref.ts#L436
It would be really awesome if OverlayRef.ngOnDestory this timeout would be cleared with clearTimeout(timeoutId).
Currently the only workarounds is to call tick(500) at the end of my unit tests. I don't like this because it artificially delays all my unit tests.

It does get cleared (see https://github.com/angular/material2/blob/5321ab3cc4104369ea756857210c724f6c028cea/src/cdk/overlay/overlay-ref.ts#L416), however that callback depends on a transitionend event being fired on the backdrop which won't happen on its own during a unit test.

Closing since this behavior is unlikely to change.

Explicitly calling fixture.destroy() at the end of unit tests causes the overlay-ref to close the backdrop, but it schedules a new task in zonejs: https://github.com/angular/material2/blob/5321ab3cc4104369ea756857210c724f6c028cea/src/cdk/overlay/overlay-ref.ts#L436
To workaround this issue I have been able to do the following at the end of each test:
  fixture.destroy();
  flush();

By calling flush() the Scheduler of the FakeAsyncTestZoneSpec has it's non-periodic tasks flushed, leaving no tasks in the scheduler's queue.


Error upgrading from 0.6.0 to 0.6.1

Hi, While upgrading from 0.6.0 to 0.6.1 , I am getting below error:-
level=error ts=2021-10-12T05:05:31.770Z caller=runner.go:50 msg="aborting startup due to error" err="migration error: Error while trying to migrate DB: Error encountered during migration: error executing migration script: name versions/dev/0.5.2-dev/1-downsampling.sql, err ERROR: UPDATE requires a WHERE clause (SQLSTATE 21000)"
I tried the workaround mentioned above , but the ALTER query is breaking:-
ERROR:  column "table_schema" of relation "metric" does not exist
Database version - PostgreSQL 13
Thanks
Originally posted by @rinshadka in https://github.com/timescale/promscale/issues/755#issuecomment-940678655

@rinshadka could you check the schema version with select version from prom_schema_migrations;?

Hi, Please see the results respectively,
 version
---------
 0.5.1
(1 row)

\dx
                                       List of installed extensions
    Name     |  Version  |   Schema   |                            Description
-------------+-----------+------------+-------------------------------------------------------------------
 plpgsql     | 1.0       | pg_catalog | PL/pgSQL procedural language
 promscale   | 0.1.2     | _prom_ext  | Promscale support functions
 timescaledb | 2.3.0-dev | public     | Enables scalable inserts and complex queries for time-series data
(3 rows)

Thanks

Does the problem also occur when going from 0.5.1 -> 0.6.1 directly?

The issue is now resolved once I upgraded to v0.6.2, Thank you.


Fix handling content type and raw input

Related issue: https://github.com/liyasthomas/postwoman/issues/597
Scope of work:

Enable raw input toggle only for application/x-www-form-urlencoded and force true in other cases;
Fix default body (raw) for each content type;

Hey @leomp12,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 3aa376e0-685d-11ea-9beb-cb7d09b98ed8


@selection-change Range index is relevant to current line, not entire content

Version
@vueup/vue-quill version 1.2
Describe the bug
When using the @selection-change event, the returned value's range property's index property is always relevant to the line the cursor is on, instead of the entire content.
Expected behavior
As per the Quill API documentation, the index property of the selection range should provide the index of the cursor position with respect to the entire content of the Quill editor, not the index within the current line.
Example
Let's say my Quill editor had the following contents:
A dog,
a cat,
and a mouse

If I placed my cursor before the letter "m" in line 3, the index would be 5 (for some reason, position 0 is returned as -1).  The index should not be 5, it should be like 20.

Here's an example of how it SHOULD work:
https://codepen.io/cpascariu/pen/NWWLmQO (I didn't make this)


[Forwardport 2.9] integration test suite: unbreak f-string

Forwardport of https://github.com/rancher/rancher/pull/43580

ping @bmdepesa


Errors map key could honour FieldTagName setting

If FieldTagName is set in the Config option, the validation errors map's key should maybe be made up of field names from the tag specified.
Assuming I used
...
FieldTagName = "json",
...

The following struct
type myStruct struct {
    SubStruct struct {
        MyField string `json:"my_field"`
    } `json:"sub_struct"`,
}

could create a map key like
sub_struct.my_field

Instead of
SubStruct.MyField

Thanks @byrnedo will add a boolean option to the config for this after the holidays

UPDATE: after some review will be adding another field on each FieldError for this as don't want to confuse StructPartial and StructExcept methods which use the key to determine which fields are to be included/excluded.

@byrnedo I have completed the changes please check it out and let me know if it works for you.

Hi, I'll have a look soon, bit busy at the minute, thanks for doing this!
On 6 January 2016 at 15:51, Dean Karn<EMAIL_ADDRESS>wrote:

@byrnedo https://github.com/byrnedo I have completed the changes please
check it out and let me know if it works for you.
—
Reply to this email directly or view it on GitHub
https://github.com/go-playground/validator/issues/227#issuecomment-169343636
.

np just let me know when you can

any word @byrnedo ?

Will take a look today, sorry for the delay
On 18 January 2016 at 14:29, Dean Karn<EMAIL_ADDRESS>wrote:

any word @byrnedo https://github.com/byrnedo ?
—
Reply to this email directly or view it on GitHub
https://github.com/go-playground/validator/issues/227#issuecomment-172527348
.

Looks good Dean, that works for me!
On 18 January 2016 at 14:33, Donal Byrne<EMAIL_ADDRESS>wrote:

Will take a look today, sorry for the delay
On 18 January 2016 at 14:29, Dean Karn<EMAIL_ADDRESS>wrote:

any word @byrnedo https://github.com/byrnedo ?
—
Reply to this email directly or view it on GitHub
https://github.com/go-playground/validator/issues/227#issuecomment-172527348
.

Perfect


Read Me doesn't cover the beer's description variable name.

At one point we defined it as beer_description and another as description. We should probably document which it is.

Hmm... where is this @benlachman? https://github.com/AthensWorks/OBWapp-API/blob/master/README.md

/beers endpoint

Fixed in fd3dfc31481719f7a835919d39d9b2f5b75dd595


I cannot install CaptainHook composer plugin

Hello,
I'm trying to install Captainhook and the plugin via composer, and it gives me an error.
composer require --dev captainhook/plugin-composer
Using version ^5.1 for captainhook/plugin-composer
...
Package operations: 1 install, 0 updates, 0 removals
  - Installing captainhook/plugin-composer (5.1.0): Loading from cache
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.
Writing lock file
Generating optimized autoload files
ocramius/package-versions: Generating version class...
ocramius/package-versions: ...done generating version class
CaptainHook Composer Plugin

  The "-g" option does not exist.

configure [-c|--configuration [CONFIGURATION]] [-e|--extend] [-f|--force] [-a|--advanced] [--bootstrap [BOOTSTRAP]]

Installation failed, reverting ./composer.json to its original content.

In ComposerPlugin.php line 203:

  Shiver me timbers! CaptainHook could not install yer git hooks! (invalid-exit-code)

I see there's a -g option used in ComposerPlugin.php that seems to not exist in captainhook (or I don't find it).
By the way, I'm using these versions:
Composer 1.9.3 2020-02-04 12:58:49
PHP 7.3.14 (cli) (built: Jan 21 2020 09:59:50) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.14, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.3.14, Copyright (c) 1999-2018, by Zend Technologies
    with Xdebug v2.9.2, Copyright (c) 2002-2020, by Derick Rethans

I see it works well if I require plugin-composer as ^4.0, but as soon as I update it to ^5.0 or ^5.1, it fails.

The -g option error should be fixed in version 5.1.1
The container-interop/container-interop dependency is not because of captainhook it seems like a dependency on your end ;)

Yes, container-interop is another issue not related to captainhook, don't worry about that. The main problem was that -g option. I have just installed 5.1.1 and I can confirm that now it works, thank you!

Nice thanks for the feedback :)


 Could you make that change?

Looks great. Thanks @Joeperdefloep . I see this is your first contribution to xarray. Welcome!


[PE-D][Tester B] Filter for Recurring Tasks not Listing the Weekly Tasks

Tasks 2 and 4 are tagged weekly

Entered this command

but nothing is showing :(. May want to look into that!

Labels: severity.High type.FunctionalityBug
original: butteredyakiimo/ped#11

Need to specify Recur Tag is different from normal tag.


Blank spaces break markdown table

Summary
Blank spaces in certain places of Markdown tables cause them not to render at all
Note: There was a very similar issue reported in the past. But in this issue blank spaces in other places will cause the same behavior to occur
Environment Information

Device Name:
OS Version: iOS 12
Mattermost App Version: 1.14 .0 (Build 158)
Mattermost Server Version: 5.5.0

Steps to reproduce

In the mobile app, create the following tables:
a. (With extra spaces at the end of each line)

| Header 1 | Header 2 |
| :--: | :--: |
| r1c1 | r1c2 |
| r2c1 | r2c2 |
| r3c1 | r3c2 |

b. (With an extra space before the second : )
| Header 1 | Header 2 |
| :--: | :-- : |
| r1c1 | r1c2 |
| r2c1 | r2c2 |
| r3c1 | r3c2 |

View it on Mobile app & Webapp

Expected behavior
Tables should render on mobile properly, as they already to on the webapp
Observed behavior
Table markdown appears in plaintext on the mobile app

Possible fixes
Changes may need to be made on the markdown parser used by the mobile app to ensure whitespace gets ignored in the right parts

Thanks for the report, opened a ticket here: https://mattermost.atlassian.net/browse/MM-13516.

Closing this as this has been fixed for v1.18 release,


unable to assign "Owner" built-in role?

When I try to assign the Owner built-in role I get the message "The role definition" (id of Owner Role) "is restricted for registration".  Is it not possible to delegate with Owner role?

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

ID: 85dc331a-0f34-f9a2-43d9-8ab7e0e635c6
Version Independent ID: 96c07c81-f84c-f47b-659c-b3d055aefb03
Content: Onboard a customer to Azure delegated resource management - Azure Lighthouse
Content Source: articles/lighthouse/how-to/onboard-customer.md
Service: lighthouse
GitHub Login: @JnHs
Microsoft Alias: jenhayes

Ignore comment above - I've just found https://docs.microsoft.com/en-gb/azure/lighthouse/concepts/tenants-users-roles which states that Owner role is not supported - any idea when it might be (if ever)?

@rich-davies Thanks for your comment! We will review and provide an update as appropriate.

@rich-davies This is the UserVoice / feedback forum page for Azure Lighthouse related feedback and here I could see that your ask is the top ask from other partners as well and it is on our list to be addressed for the roadmap. Please upvote it and other features that are of interest. We would announce and/or update the referred document once it is addressed.

@rich-davies At this point it appears that there's no edits or updates needed for the referred Azure documentation so closing this issue for now. If there are further questions regarding this matter or feedback on the documentation, please do let us know and we will gladly continue the discussion.


Team

Is your feature request related to a problem? Please describe.
create a team part where we represent our team.
First, make ad design according to the given design.
Data for team member will be provided soon
Additional context

I can do this.

Sure @JINDAL-JJ

One more thing @JINDAL-JJ  There is a hover feature shown in the

below photo.
so there we want twitter , Github and Linkedin icon


Improve RHV provider field names and tooltips

The host name/IP, user name, and password are for the RHV Manager (upstream: Engine). You may want to add that to the field names or as a tooltip to the fields.
The CA certificate field has a tooltip that is not very helpful because the RHV CA certificate location is documented in the RHV Administration Guide. Suggest you change the tooltip to: "The CA certificate is the /etc/pki/ovirt-engine/apache-ca.pem file on the Manager machine."

@apinnick I attached a PR for this, not sure I got it exactly right, but please review when you find time. I couldn't tag you as reviewer on the PR for some reason.. Thanks!

@seanforyou23
I made a few comments about following UI and our style conventions on your PR. Other than those issues, LGTM.

@apinnick would you mind opening a BZ for this?


Unresolved string: "You sent ${amount} LBC"

Version Found
lbry.tv 2020-06-24
Bug
Sent LBC to someone and got this:

There's also one on the "large account history" string on app startup (splash file).

There's also one on the "large account history" string on app startup (splash file).

This one? https://github.com/lbryio/lbry-desktop/pull/4440

Close

The change in redux has been incorperated.
The "large account history" issue has been fixed.


[flutter_tools] attempt to not copy partial dill file

Description
Fixes https://github.com/flutter/flutter/issues/58109
If the tool is expecting the frontend_server to output a new file, don't attempt to copy the dill when exiting. This does not distinguish between full/incremental dills to simplify the implementation.

Trying to reproduce this problem is time-consuming as there are not guaranteed steps to get expected failure unfortunately.
Also I'm not sure whether race between frontend server and copying is what causes zero-filled cached.dill files. I wonder whether there is a race when IDE tells flutter daemon to shut down which initiates the copying of app.dill into cached.dill, and flutter daemon force to exit/exiting before copying finished. I basically tried to artificially add tail 100mb of 1..16 sequence into the app.dill file during serialization and then see if it gets across into cached.dill file intact. I saw that if I run and stop flutter app from Android Studio, then rather frequently I get zeros instead of 1..16 sequence in the end of the file.

We could remove copying from the shutdown stage since that seems risky (and Android Studio behavior is unlikely to change). If we copy the first compilation we'll still get a decent dill for initiailization.

Closing in favor of https://github.com/flutter/flutter/pull/58188


Remove binary files and download them in CI process instead

I found that the binary files are included in the source release, which should not

Should we put the version at the beginning of the file? I think we will need to upgrade one day or another.


supercell-wx: init at 0.4.4

Description of changes
Adds Supercell Wx at version 0.4.4.
Supercell Wx is a free, open source application to visualize live and archive NEXRAD Level 2 and Level 3 data, and severe weather alerts. It displays continuously updating weather data on top of a responsive map, providing the capability to monitor weather events using reflectivity, velocity, and other products. Extended functionality, including weather reports and lightning data can be added using placefiles.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Build fails on x64 Linux. Note that ofborg (and my build) are done by first merging the PR on current master. To reproduce the failure you need to rebase your branch on master.
FAILED: scwx-qt/CMakeFiles/scwx-qt.dir/source/scwx/qt/external/stb_image.cpp.o
/nix/store/xj72byimwa4w92f9vlrg921qdprr01vl-gcc-wrapper-14-20241116/bin/g++ -DBOOST_CONTAINER_DYN_LINK -DBOOST_CONTAINER_NO_LIB -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DBOOST_JSON_DYN_LINK -DBOOST_JSON_NO_LIB -DBOOST_TIMER_DYN_LINK ->
In file included from /build/source/scwx-qt/source/scwx/qt/external/stb_image.cpp:14:
/build/source/external/stb/stb_image.h: In function 'int stbi__parse_png_file(stbi__png*, int, int)':
/build/source/external/stb/stb_image.h:5166:56: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
 5166 |                   for (k = 0; k < s->img_n; ++k) tc[k] = (stbi_uc)(stbi__get16be(s) & 255) * stbi__depth_scale_table[z->depth]; // non 8-bit images will be larger
      |                                                  ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/build/source/external/stb/stb_image.h:5082:25: note: at offset 3 into destination object 'tc' of size 3
 5082 |    stbi_uc has_trans=0, tc[3]={0};
      |                         ^~
cc1plus: all warnings being treated as errors


Partially initialized module error when running python examples

After cloning the repository, I run the configure.sh script and then when I try and run the stanford_bunny example I receive the following error:
ImportError: cannot import name 'PrintLogo' from partially initialized module 'QuESo_Application' (most likely due to a circular import) (/path/to/QuESo/queso/QuESo_Application.py)

Hi @drtloudon,
this sounds like that the LD_LIBRARY_PATH is not set properly. Can you confirm that it is set to the /libs folder within your QuESo directory. Also please check if the compilation was successful and the /libs folder was actually created. It should contain two files:

libQuESo_ApplicationCore.so
QuESo_Application.cpython-**-x86_64-linux-gnu

You can check the LD_LIBRARY_PATH  with echo $LD_LIBRARY_PATH.
I hope this helps.
Best,
Manuel

Thanks for the response. I did have LD_LIBRARY_PATH set, but my libs folder contains the the libQuESo_ApplicationCore.so and QuESo_ApplicationNone, not QuESo_Application.cpython-**-x86_64-linux-gnu. The only thing that looks odd in the output of "bash configure.sh" is:
lto-wrapper: warning: using serial compilation of 16 LTRANS jobs
Not really sure what I'm doing wrong. Thanks for your help.

I figured it out. I had set both ./QuESo and ./QuESo/queso in the PYTHONPATH. Getting rid of the latter fixed the problem. Thanks.

Does QuESo provide quadrature points for both volume integrals and surface integrals? I didn't see anything in your wiki about surface integrals. Thanks.

By that I mean integration points used to impose essential boundary condition's. In case, you define one or several boundary conditions in QuESoSettings.py, see e.g.: example, you can do the following. Note that each condition is initially defined by an standalone STL, as shown in the cantilever example.
# Project imports
from QuESo_PythonApplication.PyQuESo import PyQuESo

def main():
    pyqueso = PyQuESo("QuESoSettings.json")
    pyqueso.Run()

    for condition in pyqueso.GetConditions():
        settings = condition.GetSettings()
        # Settings stores all information you specified in QuESoSettings.json
        condition_id = settings.GetInt("condition_id")

        # Each condition input triangle mesh is split into segments that obey the element boundaries of the backgorund mesh
        for condition_segment in condition.GetSegments():
            triangle_mesh_segment = condition_segment.GetTriangleMesh()
            num_triangles = triangle_mesh_segment.NumOfTriangles()
            for tri_id in range(num_triangles):
                integration_method = 0 # The higher, the more integration points are used per triangle
                # Please note that the following points are in physical space
                global_points = triangle_mesh_segment.GetIntegrationPointsGlobal(tri_id, integration_method)

if __name__ == "__main__":
    main()

PS: I still work at a couple of things. Once they are done, I'll add all features to the wiki.

This is exactly what I needed. Thanks so much.


TextFormField: tapping on character count focuses the input field

Steps to Reproduce

Create a sample screen with a TextFormField
Add a value to maxLength parameter let's say 100, you will now see the character length text as 0/100.
When you tap on this counter text, the text field focuses, which is weird.

Expected results:
The text field should only focus when you tap inside the text field
Actual results:
Text field focuses itself on tapping the maxLength text
The whole green area shown in the screenshot focuses the text field on tapping.

I tried creating my own counterBuilder and adding an empty tap to it as a workaround, it worked but only for the that widget area I created. The space on the right hand side of that text, just below the text field still focuses the field on tapping.

Code sample

Logs

Thanks for the report @wal33d006
I think it is WAI.  Using below code sample:
body: Center(
        child: TextField(
          maxLength: 100,
          decoration: InputDecoration(
            border: OutlineInputBorder(),
          ),

        )
      ),

Since maxLength is part of the TextField and TextFormField widgets, any interaction with any of the properties of these 2 fields makes an impact to the input. For example, when the textfield is focussed and we start inputing, the maxLength value changes, so the other way round is true too.
You may check with any native app and see if the behavior is same or not.

Thanks for the report @wal33d006 I think it is WAI. Using below code sample:
body: Center(
        child: TextField(
          maxLength: 100,
          decoration: InputDecoration(
            border: OutlineInputBorder(),
          ),

        )
      ),

Since maxLength is part of the TextField and TextFormField widgets, any interaction with any of the properties of these 2 fields makes an impact to the input. For example, when the textfield is focussed and we start inputing, the maxLength value changes, so the other way round is true too.
You may check with any native app and see if the behavior is same or not.

That's correct. But by design and UX, it shouldn't be like that. As a user, they would not expect to tap somewhere out of the text field and get a keyboard popping up. The focusing should strictly remain restricted to the actual visible part of the insides of the text field (which I think should not be a problem to fix).

they would not expect to tap somewhere out of the text field and get a keyboard popping up

Ideally, a user if they see a textfield, would most probably tap inside it to make it active and the chances of them tapping on something like maxLength section are far less, that's my personal opinion.

You may check with any native app and see if the behavior is same or not.

Did you get a chance to look at it ? If native behaves same way, then it makes more sense that Flutter also matches native, but if the behavior is different (ie, on native this doesn't occur, but in Flutter does), then it would probably makes sense to match it with native.

I figured out a hacky way of doing it by wrapping the counterBuilder widget in a Row, and wrapping the child in an Expanded, and then wrapping the whole Row in a GestureDetector and applying behavior: HitTestBehavior.opaque
Thanks for the responses @darshankawar


Publish 04/06/2021, 3:30 PM

Docs Build status updates of commit 1be2d3e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md
:bulb:Suggestion
View (sharepoint-ps)
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOGeoStorageQuota.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md

Line 2, Column 1: [Suggestion-audience-missing] Missing required attribute: 'audience'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

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


Fixes to use lfs_filebd on windows platforms

There are two issues, when using the file-based block device emulation
on Windows Platforms:

There is no fsync implementation available. This needs to be mapped
to a Windows-specific FlushFileBuffers system call.
The block device file needs to be opened as binary file (O_BINARY)
The corresponding flag is not required for Linux.

Hi @m8ddin, thanks for thePR.
A request, could these be changed to explicit ifdef statements?
#ifdef _WIN32
bd->fd = open(path, O_RDWR | O_CREAT | O_BINARY, 0666);
#else
bd->fd = open(path, O_RDWR | O_CREAT, 0666);
#endif

This would just help future work to know what exact idiosyncrasies are required for each platform.

I also want to highlight that we can't easily test these platform specific changes in CI, so future regressions are possible. This unfortunately may break in the future without warning.

Hi @geky !
Thanks for reviewing the PR so quickly! Of course, I can add explicit ifdefs. Will add another commit today.

Hi @m8ddin, thanks for the update.
Sorry, I meant that each platform specific function should be an ifdef, both the O_BINARY and FlushFileBuffers, instead of aliasing fsync. Consider what would happen if Windows adds fsync in the future (or more likely fsync is provided by mingw or some other toolchain on Windows).
#ifdef _WIN32
int err = FlushFileBuffers((HANDLE)_get_osfhandle(bd->fd)) ? 0 : -1;
#else
int err = fsync(bd->fd);
#endif

Makes sense :+1:

Thanks for this! I will bring this in next minor release, which shouldn't be too far away.


Commercial Use

Hello! I'd like to clarify the availability of this tool for use in commercial applications. I see it's licensed under MIT terms, but I'm not sure if the algorithms used are encumbered by intellectual rights patents, as they appear to be derived from research done by Shazam. Any insight here will be greatly appreciated!
Ps. Really excellent work on this project; it's been a really educational tool for me and was easy to get started with.

I can’t give legal advice, but my implementation is based on the ideas in
Avery Wang’s paper.
DAn.
On Tue, Apr 23, 2019 at 12:53 Jay Weeks<EMAIL_ADDRESS>wrote:

Hello! I'd like to clarify the availability of this tool for use in
commercial applications. I see it's licensed under MIT terms, but I'm not
sure if the algorithms used are encumbered by intellectual rights patents,
as they appear to be derived from research done by Shazam. Any insight here
will be greatly appreciated!
Ps. Really excellent work on this project; it's been a really educational
tool for me and was easy to get started with.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dpwe/audfprint/issues/60, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEGZUO3YFKN2KIHT53V4TLPR45JRANCNFSM4HH3VJRA
.


CXF-7130 Maven plugin to invoke SOAP service

I needed a Maven plugin that would allow me to invoke SOAP service as a part of Maven lifecycle so I implemented one, and I'm hoping that you can include it in CXF.
The plugin has the functionality of calling SOAP service given a WSDL, port, service, operation, request body and optional SOAP headers. Additionally Maven project properties can be set from the response using XPath expressions and additional XPath expression can be used to determine if the request needs to be repeated.
This is a minimal implementation that I needed for my use-case, hope you find it useful and that it can be incorporated in CXF.
This is a new pull request, I squashed the commits to make it a bit easier to follow.

Had a discussion with @ffang and decided that this was not a good fit for CXF. Thanks for the consideration!


PIL or Pillow is not listed in setup.py to run

Why isn't PIL or Pillow listed in the install_requires field in setup.py? As far as I can tell, you need it to run this so it should be listed for completeness.

hiya, this library is being deprecated - we have a similar library that works with Python3 and modern linux computers. please check out this guide for more info
https://learn.adafruit.com/monochrome-oled-breakouts/python-wiring