To add in FAQ?

I would like to share my experience using the plugin.
I got a lot of calls calling my pagination while scrolling anywhere in the window.
I had this :

but it was calling a lot of pagerFunction(). Similar behaviour to current FAQ Why is ngInfiniteScroll triggering my expression on every single scroll event?.
InfiniteScroll seems to use the div offset top and height. As I use height: 100% I had to wrap in an additional div like this :

Maybe this can help others if put in FAQ.

@stefanofornari Could you create a jsfiddle instead, so I could fix it for you ?

Hi samuel,
thanks for your reply. I have tried, but I am not very familiar with it and
I could not find a way to make it to work (I mean to create something with
jquery, angular and nginfintescroll), sorry :( However, I worked around my
problem and now works. If you are interested in fixing the issue in
infinitescroll, maybe you can initiate a working jsfiddle and then I will
try to reproduce it?
thanks again,
Stefano
Ste
On Mon, Jan 5, 2015 at 10:28 AM, Samuel ROZE<EMAIL_ADDRESS>wrote:

@stefanofornari https://github.com/stefanofornari Could you create a
jsfiddle instead, so I could fix it for you ?
—
Reply to this email directly or view it on GitHub
https://github.com/sroze/ngInfiniteScroll/issues/51#issuecomment-68684710
.


Added Default Tools Pressure setting.

Added configuration to Settings Dialog
Circle, Line and Rectangle Tool pressure use the configured pressure instead of the constant 0.5

Should fix #212, #252 and #216

You are right. I'll change it as soon as possible.


DeepLabV1-WR38

Hi, author, I have reproduce the DeepLabV1-WR38 according to the reference you had pointed in the CLIMS issues(Hi, you can refer to this repo. Btw, welcome to star CLIMS:)), but the result have a huge gap with your paper. What is the problem on it? Any help is appreciate. Thank you for your great job.

Hi, you can try the following config in the config.py:
config_dict = {
		'EXP_NAME': 'qa_clims',
		'GPUS': 1,

		'DATA_NAME': 'VOCDataset',
		'DATA_YEAR': 2012,
		'DATA_AUG': True,
		'DATA_WORKERS': 4,
		'DATA_MEAN': [0.485, 0.456, 0.406],
		'DATA_STD': [0.229, 0.224, 0.225],
		'DATA_RANDOMCROP': 512,
		'DATA_RANDOMSCALE': [0.5, 2.0],
		'DATA_RANDOM_H': 15,
		'DATA_RANDOM_S': 15,
		'DATA_RANDOM_V': 15,
		'DATA_RANDOMFLIP': 0.5,
		'DATA_PSEUDO_GT': '/path/to/sem_seg',

		'MODEL_NAME': 'deeplabv1',
		'MODEL_BACKBONE': 'resnet38',
		'MODEL_BACKBONE_PRETRAIN': True,
		'MODEL_BACKBONE_DILATED': None,
		'MODEL_BACKBONE_MULTIGRID': None,
		'MODEL_BACKBONE_DEEPBASE': None,
		'MODEL_NUM_CLASSES': 21,
		'MODEL_FREEZEBN': False,
		'MODEL_SCALES': [0.5, 0.75],

		'TRAIN_LR': 0.0008,
		'TRAIN_MOMENTUM': 0.9,
		'TRAIN_WEIGHT_DECAY': 0.0005,
		'TRAIN_BN_MOM': 0.0003,
		'TRAIN_POWER': 0.9,
		'TRAIN_BATCHES': 6,
		'TRAIN_SHUFFLE': True,
		'TRAIN_MINEPOCH': 0,
		'TRAIN_ITERATION': 30000,
		'TRAIN_TBLOG': True,

		'TEST_PERIOD': 'test', # val / test
		'TEST_MODE': 'crf', # mode for test, infer/crf
		'TEST_MULTISCALE': [0.5, 1.0, 1.5, 2.0],
		'TEST_REDUCTION': 'mean',
		'TEST_FLIP': True,
		'NUM_WORKERS': 128,
		# 73.3105724144242
		'CRF': {
			'ITER_MAX': 10,
			'POS_W': 3,
			'POS_XY_STD': 1,
			'BI_W': 4,
			'BI_XY_STD': 67,
			'BI_RGB_STD': 3
		},
		'TEST_BATCHES': 1,
}

I have some questions about the config file, what are those params "MODEL_SCALES", "MODEL_BACKBONE_DILATED", "MODEL_BACKBONE_MULTIGRID", "MODEL_BACKBONE_DEEPBASE"? They are not present in the semantic-segmentation-codebase.
And the params for test and val in the config, the semantic-segmentation-codebase had not presented some of those. Any help is appreciated, thank you!

The main puzzling param is "TEST_REDUCTION", where use it in the semantic-segmentation-codebase. I have not found it in the codes, thank you!

Hi, sorry for the confusion.
The params MODEL_BACKBONE_DILATED, MODEL_BACKBONE_MULTIGRID, MODEL_BACKBONE_DEEPBASE is used by the generate_net() at train.py#L52. However, these params were not used by the deeplabv1.py, so ignore them.
For the param MODEL_SCALES, we apply multi-scale training from kazuto1011/deeplab-pytorch.
For the TEST_* params, we also apply the CRF options from kazuto1011/deeplab-pytorch, and some multi-processing code to speed up the process.
You can find our modified  code for training the DeepLabV1-WR38 model at this link

Thank you for your careful replies! The (DeepLabV1-WR38 model at this link)'s permissions have been set, could you authorize me to access it? thank you!

done

Thank you for your codes. I also have some questions about the deeplabv2 from your another great job CLIMS, I also can not reach the result in the QA-CLIMS paper by just using the V2 from the CLIMS, are there any change in the deeplabv2 for QA-CLIMS? Any help is appreciate, Thank you!

Hi, we use the same configuration as CLIMS in this file to train the deeplabv2, but change batch_size to 5.
Please check if the generated pseudo labels get the similar results as ours, which can be evaluated by step/eval_sem_seg.py.
Otherwise, make sure you have apply the CRF options on the generated predictions, just like https://github.com/CVI-SZU/CLIMS/blob/f9546d32ad9b4545577eebdc9e4d879aff3366d7/segmentation/deeplabv2/run_voc12_imagenet_pretrained.sh#L4

According to your description, the main difference is the BS. I also use the crf for post-process, but the segmentation result is poorer than yours about 0.4~.
And, I use your coco-codes for training coco-step, I got the problem in this train_qa_clims.py#194, the exception is "IndexError: invalid index of a 0-dim tensor. Use tensor.item() in Python or tensor.item<T>() in C++ to convert a 0-dim tensor to a number", did you had encountered this exception before?
I also want to know your server config for coco, I use 2GPU that 48G per-GPU, I got the CUDA out of memory problem.
Any help is very appreciate, thank you!

Hi, I have pushed a new version of step_coco/train_qa_clims.py, it may fix the IndexError you mentioned.
We use 4 x 32G memory GPUs to train the coco model.

Thank, I also wnat to know your coco miou in evaluation step for 10000 images. And the V2's config for the coco step. Thank you again for your great job.

And how long have you spend for training coco dataset with deeplabv2? thank!

We got ～0.424 in evaluating 10000 images, and the final miou is ～0.421.
We train deeplabv2 with batch size 10 for 100000 steps, other configurations are the same as voc.
I don't really remember the exact amount of time spent on training, it might take you more than 20 hours to train deeplabV2, and when you do the crf operation, it takes a lot more time.

Thank you for your patient reply and your great jobs.

And I also want to confirm how many time did you spent in the mask_sem_seg_labels  step when you generated the 82081 masks for the deeplabV2.
Did you mean using the 82021 images to train deeplabV2 and you spent more than 20 hours? Is there just your one program in your server? Is there any approximate time how long did you spent? Thank you very much!

Hi, author. I have some problem in VOC Test dataset. I found that there are a huge gap between val and test. Are there any different config between val and test?

Any help is very appreciate!

Sorry for the late reply.
I'm sorry I can't find the exact time spent on these steps.
make_sem_seg_labels for all coco images may takes much time, you can change the n_process_per_gpu value in step_coco/make_sem_seg_labels.py#L76 to speed up.
We use the same trained model for evaluation on the val and test sets.

Hi, sorry for the confusion.
The params MODEL_BACKBONE_DILATED, MODEL_BACKBONE_MULTIGRID, MODEL_BACKBONE_DEEPBASE is used by the generate_net() at train.py#L52. However, these params were not used by the deeplabv1.py, so ignore them.
For the param MODEL_SCALES, we apply multi-scale training from kazuto1011/deeplab-pytorch.
For the TEST_* params, we also apply the CRF options from kazuto1011/deeplab-pytorch, and some multi-processing code to speed up the process.
You can find our modified code for training the DeepLabV1-WR38 model at this link

The (DeepLabV1-WR38 model at this link)'s permissions have been set, could you authorize me to access it? thank you! Besides, i want to know whether you have tried trainning DeepLabV1-WR38 model on COCO dataset? Thanks!


Defend public headers against inclusion of Windows.h

... which defines some nasty function-like macros min and max when _NOMINMAX isn't defined. We prevent expansion as a function-like macro by inserting some token(s) between min/max and the following (. Most commonly that means wrapping the entire qualified-name in () a la (std::min)(x, y), but an explicit template argument list (std::min<int>(x, y)) works as well.
EDIT: To be perfectly clear, I'm not suggesting introduction of an explicit template argument list as a good way to fix this issue so much as pointing out that existing occurrences with an explicit template argument list - there are a couple in the repo - don't need any additional fix.

@CaseyCarter, https://github.com/CaseyCarter/azure-sdk-for-cpp/pull/1

Ugh, I've done something terrible to this branch revising history while resolving a merge conflict. I'll fix and force push momentarily.

There we go: I reset to the prior commit and rebased on master. Apologies for resetting incremental review: what's here is much the same as before except that macro_guard.cpp moved from test into test/ut for the SDKs that made that change on master.

@CaseyCarter Change looks good. Our team owns the KeyVault portion and has signed off.
Please submit

I don't have merge rights:

Not that I mind, but someone else will have to push the big red button.

@CaseyCarter, if you join the same orgs that I have on my profile, you should be able to merge, would you like to do that? I think it makes sense. Otherwise, I can merge your PR.

Do we need to make similar fixes to the source cpp files as well?
https://github.com/Azure/azure-sdk-for-cpp/blob/50efbdb4c08ed57e7eedd1bd571dc377d3455c0a/sdk/core/azure-core/src/http/curl/curl.cpp#L690
https://github.com/Azure/azure-sdk-for-cpp/blob/bf347d24c24d8a46d0013e2b4a34197c424ecff2/sdk/core/azure-core/src/http/body_stream.cpp#L76
https://github.com/Azure/azure-sdk-for-cpp/blob/249327a3fa8002a8e25804cd6ebe139cb8612cd3/sdk/storage/azure-storage-blobs/src/blob_client.cpp#L212

Do we need to make similar fixes to the source cpp files as well?
https://github.com/Azure/azure-sdk-for-cpp/blob/50efbdb4c08ed57e7eedd1bd571dc377d3455c0a/sdk/core/azure-core/src/http/curl/curl.cpp#L690
https://github.com/Azure/azure-sdk-for-cpp/blob/bf347d24c24d8a46d0013e2b4a34197c424ecff2/sdk/core/azure-core/src/http/body_stream.cpp#L76
https://github.com/Azure/azure-sdk-for-cpp/blob/249327a3fa8002a8e25804cd6ebe139cb8612cd3/sdk/storage/azure-storage-blobs/src/blob_client.cpp#L212

Nope: we control source files, and can simply avoid including <Windows.h> and/or using problem identifiers and/or build with _NOMINMAX defined if we like. The problem only exists for headers which - thanks to textual inclusion - can be affected by headers a user includes before ours. (Modules can't get here soon enough!)


TCP zero window on Hi-load

Hi, when we user code on hi-load server(above 500 users and 50 CPS) Asterisk 18 is down:
AMI Manager freezes on  command asterisk -rx "manager show connected".
What happens : AmiClient read messages from TCP stack on line 232 (master branch on 28/02/2022).
this.readBuffer = this.readBuffer.Append(bytes.Slice(0, nrBytes));
Then we try to find in Byte readBuffer TerminatorBytes. If we found it, then we pasre one line. If readBuffer contains several lines, we continiue parse other line.
At this time(when thread parse lines) in TCP buffer (TCP Window) we receive a lot of messages, which not receiving by ami client(because we parsing previous fragment of buffer).
Then we get issue : TCP zero window. This is mean, that receive from TCP buffer is very slowly.

Possible solution : use separate thread, which will be receive messages from TCP buffer into ConcurrentQueue and another thread, which will be get messages from queue and parse lines

@syvorotnevds have you made any further investigation regarding this problem, as I am experiencing the same behaviour?

@alexforster I have a fix regarding this issue, can you please create a branch for it?


[develop 2.0] allow configuration of pretty-printing swagger.json

It is only a few bytes more to pretty-print a swagger spec:
https://github.com/swagger-api/swagger-ui/issues/746

you can now configure via web.xml:
    <init-param>
      <param-name>swagger.pretty.print</param-name>
      <param-value>true</param-value>
    </init-param>

or via BeanConfig:
config.setPrettyPrint(true)

:+1:
What's the default value though?

Thanks for asking--default is off (compact)


Somehow it is conflicting with save.

delay.sendTextAsVoice(user, @theannounce)

  def sendTextAsVoice (user, announce)
    begin
      userphone = "+1#{user.phone_number}"

      # put credentials here
      @account_sid = '**********************************************'
      @auth_token = '**********************************************'

      # set up a client to talk to the Twilio REST API
      @client = Twilio::REST::Client.new(@account_sid, @auth_token)

      builturl = "https://'**********************************************''**********************************************'"

      # make a new outgoing call
      @call = @client.account.calls.create(
        :from => '+19999999999',
        :to => userphone,
        :url => builturl
      )
      rescue StandardError => failedWith
        # Set error variables
        Deliveryerror.new(:objecttype => 1, :deliverytype => 1, :objectid => announce.id, :errormessage => failedWith, :user_id => user.id).save

      end
  end

This call is from a model called Usernotes and I am creating an instance of Deliveryerror. The call + save above works on rails console and when not in a delayed job. I know the call goes into 'recue' but it is never saving a Deliveryerror entry to the db.
Env
Rails 3.1
Lion Server
Ruby 1.9.2
PostgreSQL
[edit] Title misspelling

Solved it by using Deliveryerror.create as opposed to Deliveryerror.new. Still not sure why one did and the other one did not work.


grill help doesn't provide any help text

blake@LAPTOP-ASBN7T4S:~/workspace/the-gorge$ grill help
🔥 Grill warming up..
🔥 Ready. Version: <<IP_ADDRESS>-jenkins-WurstSetup-123>
Use one of the following commands: HELP, INSTALL, REMOVE, GENERATE, TEST, BUILD

No, that is what the help command displays. https://github.com/wurstscript/WurstSetup/blob/4c136f8532c977d819dafb0e15705cea4ae1f27c/src/main/kotlin/file/SetupApp.kt#L59

@Frotty what an awful help message. You should be ashamed of yourself


reduce dependence on Github Enterprise

might be useful to add rationale for this here: https://github.com/alphagov/gds-tech/blob/gh-pages/source-code.md
@alexmuller working on this, reduced number of repos on GHE to c. 180 from 300 so far. some conversations with non-GOV.UK teams still need to happen though.

costing and business model for moving away are being worked by Isobel


Multiple DBC read to same database object

Tries to read multiple non conflicting DBC files into the same database object.
Guess this should be possible?
`dbfiles = ["file1.dbc", "file2.dbc"]
db = cantools.db.load_file(dbfiles[0])
for file in dbfiles[1:]:
db.add_dbc_file(file)`

Forgot to actually say whats happening.. get some decode error:
Traceback (most recent call last):
File "proto.py", line 256, in load_configuration
db.add_dbc_file(file)
File "/home/dennis/.local/lib/python3.6/site-packages/cantools/db/database.py", line 106, in add_dbc_file
self.add_dbc(fin)
File "/home/dennis/.local/lib/python3.6/site-packages/cantools/db/database.py", line 94, in add_dbc
self.add_dbc_string(fp.read())
File "/usr/lib/python3.6/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa1 in position 2452: invalid start byte
Worth mentioning is that each file works to load separately if I dont use the db.add_dbc_file() function

Try with the newst version of cantools: sudo pip3 install -U cantools

Just did and I then got some errors in the dbc file it didn't like, after removing those it seams to work ok.
The things it didn't like in the database was signals that was not connected yet so it was connected to a dummy message VECTOR__INDEPENDENT_SIG_MSG that dosen't have a size.
cantools.database.errors.Error: The signal <my_signalname> does not fit in message VECTOR__INDEPENDENT_SIG_MSG
Thank you for an awesome library!

You can give strict=False to load_file() to skip various checks, among the the size check. If you are lucky your original DBC-files does not have to be modified at all.
I'm glad you like the library =)


Release memoryStore locks before filter/apply

Rework memoryStore so that filters and apply run
on a cloned list of containers after the lock has
been released. This avoids possible deadlocks when
these filter/apply callbacks take locks for a
container.
Fixes #22732
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

Don't we still only have pointers to the containers? Should this be a copy of each container, or is the issue with the collection itself?

@cpuguy83 The problem is that the memoryStore lock is being held when the callbacks run and need container locks. On attach, the situation is opposite where container lock is already held and memoryStore lock is needed.

Nice @tonistiigi ; this will help with some of the issues I have been looking at lately around lock contention. Specific to @cpuguy83's Q, the lock on the memoryStore is to protect iteration over it from modification via add/remove. Making a copy of the list resolves that problem. Container locks still exist to protect container metadata and already have appropriate protections via the container lock, so no extra work needs to be done here.

This could be a good use case for https://github.com/hashicorp/go-immutable-radix. Each change to the tree results in a new tree root, but all nodes except the parents of the changed node are shared by the new tree and the old tree. By using atomic pointer swaps to update the tree root, it's a good way to do cheap copy-on-write. This is how https://github.com/hashicorp/go-memdb works.

This was your only failure:
02:45:51 ----------------------------------------------------------------------
02:45:51 FAIL: docker_cli_help_test.go:15: TestHelpTextVerify.pN52_github_com_docker_docker_integration_cli.DockerSuite
02:45:51
02:45:51 docker_cli_help_test.go:137:
02:45:51     c.Fatal(err)
02:45:51 ... Error: Should not have a blank line on ["logs"]
02:45:51

LGTM

LGTM


Parameter in RL-PVC

Nice work on the implementation of PVC algorithms.
In the PMB paper (PETPVC: a toolbox for performing partial volume correction techniques in positron emission tomography), formula (8), the alpha parameter is the step-size. What is the exact value used in the algorithm in the tool? Can I change it?
Thanks.

Formula 8 refers to RVC rather than RL. The default step size is 1.5. You can modify this by passing the -a or --alpha switch. If incorportating the VanCittertPVCImageFilter into your own code, then you set it via the SetAlpha method.


Export the ability to create the joint_config_space as a function

The ConfigurationSpace can be a source of randomness and unfortunatly only provides a seed(...) functionality to update it. I don't trust this for re-use across multiple benchmark runs. If there was a function that created the config space with a given, that would be very helpful.
https://github.com/automl/jahs_bench_201/blob/c1e92dd92a0c4906575c4e3e4ee9e7420efca5f1/jahs_bench/lib/core/configspace.py#L4

Hi, I'm sorry for the late response. I just realized that I'm not getting automatic notifications for these issues. Thank you for the suggestion, I think that's a valid point!


Autosave

User Story
As an applicant,
I want my responses to save automatically while I am on a page
so that I don't lose progress while working on something.
Research & Design
https://github.com/bcgov/cas-cif/pull/164
https://github.com/bcgov/cas-ciip-portal/pull/933
Acceptance Criteria

[ ] Given that a user is on any page with inputs
when they make a change to an input
then their responses are automatically saved

Hey team! Please add your planning poker estimate with ZenHub @AntBush @marcellmueller @wenzowski

@marcellmueller can you please estimate this ticket today?

For reference: https://ant.design/components/notification/

@zoeyli-46

are we keeping the autosave messages sticky, or
will it be fixed together with the rest of the text?

@elliottSlee would you mind explaining (for not-a-dev) what does 'sticky' means please :)

sticky means that it follows the same position on the page wherever you scroll. I.e. autosave message is always in the top right corner of your screen no matter how far down the page you scroll.
We have decided that it will not be "sticky" and it will be fixed. So the autosave message is in the top right corner of the page and if you scroll down you won't be able to see the message anymore.

The date/time display do not seem to comply with the BC Gov IM/IT standards. We should probably use a 24h clock and a 3-character month abbreviation.

hmm I'm not seeing the autosave messages in the top right

Works now!


Select Radio Button failures

Originally submitted to Google Code by bryan.oakley on 15 Mar 2010

I'm getting the following error with SelectRadioButton:
ERROR: Invalid xpath [2]: //input[@type='radio' and
@name='models['selectedState']'and (@value='true' or @id='true')]
Notice how the word "and" is immediately after the single quote.
Also, the code fails to take into consideration that the name might have a
single quote in it.
And finally, if I understand the generated xpath correctly, it is not
possible to select a radiobutton that has a value of 'false' since the
xpath includes the clause "and (@value='true' or @id='true')"

Originally submitted to Google Code by bryan.oakley on 15 Mar 2010

Uh, never mind that last paragraph. I understand now that I think about it four five
seconds...(slaps forehead)

Originally submitted to Google Code by Andreas.EbbertKarroum on 23 Apr 2010

This issue was closed by revision 00f0a188a1.

Originally submitted to Google Code by @pekkaklarck on 24 Apr 2010

We use 'Done' status instead of 'Fixed'. Unfortunately there doesn't seem
to be option to configure the state used when issues are closed by commit
messages.


Is it possible to disable overdragg?

To prevent from being dragger under DragLinearLayout edges.

It would be possible to do by modifying the logic inside DragLinearLayout's onDrag() method.
Pull requests are welcome :smile:

If anyone reads this in future, i managed to get this working. It's by NO MEANS perfect but just about gets the job done for now.
In the "onTouchEvent" -> "ACTION_MOVE"
simply place this at the bottom:
if(lastEventY >= (getHeight() - (draggedItem.height / 2)) || lastEventY <= ((draggedItem.height / 2))){
    return false;
}


Incorrect processing of VideoRecorder.Start(Sys)

Run VideoRecorder.Start(Sys)
Get errors:
`---------------------------
TestComplete
'undefined' is null or not an object
Microsoft JScript runtime error
script.sj  Line: 98  Column: 4.
Plug-in: VideoRecorder 1.0 by SmartBear Software
Location: c:\program files (x86)\smartbear\testcomplete 12\Bin\Extensions\ScriptExtensions\RecordVideo.tcx
OK   Help

TestComplete
JavaScript runtime error.
Error: 0x80020101
Error location:
Unit: "TestProject210\TestProject210\Script\Unit1"
Line: 25 Column: 17.
OK
---------------------------`

Now, all the types except "string" will be detected and recording will be with Normal quality

I'm agree that it'll be good to have such option, but for Help button, not for VideoQuality parameter:
https://github.com/AlexanderGubarev/RecordVideo-TestComplete-extension/issues/10


Option to only use performance cores when automatically determining core count

Describe the issue
I tried out the latest UTM version using an existing qcow and vhdx windows 10 ARM image, and Windows 10 runs qualitatively much slower (less responsive, more GUI tearing), than another compiled version of QEMU.
UTM running Windows 10 arm:

Standalone Qemu running exact same image:

My goal is for UTM to be just as fast or faster than standalone Qemu. The launch options when I run qemu by itself are:
launchwin.sh.txt
Configuration
Version 2.0.28 (28)
*MacOS 11.3.1 (20E241)

Apple Silicon

Comparing to QEMU compiled using these directions:
https://forums.macrumors.com/threads/success-virtualize-windows-10-for-arm-on-m1-with-alexander-grafs-qemu-hypervisor-patch.2272354/
Debug log
debug.log
Upload VM
config.plist.txt

I did a quick test of setting UTM to max cores of 4, and this seems to bring it to parity with my other qemu version. So perhaps there's some issue with using all cores and hypervisor framework?

@iRonJ I think the issue is that Windows doesn’t understand the difference between the performance cores and the efficiency cores and may have scheduled tasks non-optimally. So forcing it to a lower core count solved it. I’ll consider adding an option to use only the performance core count instead of the total core count.

Here's the plan: a new global setting "Ignore efficiency cores when determining core count". Manually setting a core count for a VM will still override the automatic count.

Just a follow up to do this, but i noticed also that playing a youtube video works perfectly fine in my standalone qemu, but there's horrible video artifacts when running through UTM. Any thoughts on what could cause this?

It may be related to #2569


Assignment Optimal Transport Entropic Maps

Work done as part of M2 Data Sciences IPP.
Topic chosen. Add a tutorial/features to the OTT toolbox.
Entropic Maps.

Done by Nils Reynaud.


Fix Floating Base Orientation

The euler order in computing the orientation of the floating base seems to be incorrect.

See here

This should be solved, right?. Problem was given by the external state estimator


fix(TDI-39008) : change leadKey column to the correct value

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-39008
What is the new behavior?
change leadKey column to the correct value
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[X] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[X] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


build: postgres integration tests

Awesome! Shall I try and add this to GHA? Or should we put that into a Good First Issue?


@wip; [OREE-1874] add stage to opportunity contextual params

OREE-1874

Add support for additional opportunity parameter - stage

@palootcenas-outreach
I'm sorry but I were not able to utilize jest.useFakeTimers('modern') in any way to run tests
no matter what I tried, there was discrepancy between CI and local timezones
I've tried tried this for an hour, but not to waste any more time I opted for a different solution

@sheff3rd It's fine if it works in CI.


Reduced the gradient button shadow hover and default size

Reduced both hover and default size by 2px.

Issue:

Please run npm run compile to apply the change to the css file according to CONTRIBUTING.md.

Hi should i also check in the generated CSS file ? I had ran npm run compile locally but didn't check it in.

@TomWBush checked in the sbuttons.css file.

Great work thank you!
@all-contributors please add @abid1998 for code


need serializers for bloomfilter, CMS, etc....

everyone will want to store these.
Probably a bufferable is the way to go.

Going to close this in favor of a larger #119 initiative. Totally agree here.


Add support for deployment to GKE

This PR restructures the repository and adds code/config to support deployment of the Autoscaler to Kubernetes (GKE) as well as to Google Cloud Functions, fixing #67. As well as this, #71 and #62 are additionally fixed as a result of changes to the service account provisioning/permissions within the Terraform code.
Because this PR is large and touches a significant proportion of the codebase, thorough testing before merging is recommended -- we can set aside some time for this if helpful.

Thanks for the PR!
I've started working through it, but you are right it is a big one.  One thing we'll need to update are the GitHub Actions to run unit tests. I think the change is simply to update the working directories.

I fixed the markdownlinter findings and modified the paths for the unit tests -- will check the results next time the workflows run (currently waiting for approval). Thanks!

Did a quick run through of the per-project Cloud Functions deployment.  Looks like the working directory exports in the READMEs need to be updated.  Here is an example from the per-project README, export AUTOSCALER_DIR="$(pwd)/autoscaler/terraform/per-project".

[ ] terraform/cloud-functions/distributed/README.md
[ ] terraform/cloud-functions/per-project/README.md

@davidcueva , this change is looking good.  Given the size and scope would you also be able to do a quick review?

Closing to recreate from new master branch following #75.


Index Glitch in GdalRaster with Very Large Rasters

I was using the GDAL extension to pull in specific values from a 14GB tiff file with the GetValues method and ran into a minor casting glitch in GdalRaster.cs which can be corrected with a few brackets.
Problem Code: Under GetValuesT, lines 174-177 (version 2.0):
                foreach (long index in indices)
                {
                       int row = (int)index / NumColumnsInFile;
                       int col = (int)index % NumColumnsInFile;
When pulling values from a very large raster, the raster indices can get large, unsurprisingly as 'index' is typed as a long.  When employing the GetValues method this index is converted to an integer prior to determining the row, column coordinates.  If that index value exceeds the maxvalue for an Int32 an incorrect value is returned.  (For my indices range (1.3x10^10), this resulted in negative row, col values and an exception from GDAL).
I corrected this behaviour by wrapping the calc in brackets prior to casting and recompiling:
int row = (int)(index / NumColumnsInFile);
int col = (int)(index % NumColumnsInFile);
Hope that helps someone down the line.  Love DotSpatial, glad to see the project growing.
Pete

Pete, thanks for reporting! I've pushed corrected changes into master branch.


HNC: detect group automatically where possible

 Issue by adrianludwin
Tuesday Jan 05, 2021 at 19:46 GMT
Originally opened as https://github.com/kubernetes-sigs/multi-tenancy/issues/1336

See https://groups.google.com/g/kubernetes-wg-multitenancy/c/g3B9_faG-iY. We insist that users include the API group of any non-core resource, but K8s includes a way to map from unscoped to fully scoped names automatically (I assume only if there isn't a conflict, but I'm not sure).
It would be cool if the --group field could (safely) be made optional, either in the CLI or in server-side.

 Comment by adrianludwin
Tuesday Jan 05, 2021 at 19:46 GMT

/help-wanted

 Comment by smarterclayton
Tuesday Jan 05, 2021 at 21:57 GMT

Ungrouped names are “first one registered wins” which is mostly to preserve backward compatibility (as we went from ungrouped to grouped).  It can certainly be optional from a client, but any user automating should specify them or risk being broken randomly later.  I don’t think kubectl documents all the gotchas the way it should, but it can at least serve as a guide.

 Comment by adrianludwin
Tuesday Jan 05, 2021 at 22:04 GMT

Thanks @smarterclayton - I hadn't known that history. I had a mutating admission webhook in mind for the server-side so whatever decision we made was preserved immediately, but on reflection I think that client-side is definitely the way to go as you say, possibly with a warning message.

 Comment by fejta-bot
Monday Apr 05, 2021 at 22:12 GMT

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

 Comment by yiqigao217
Wednesday May 05, 2021 at 18:29 GMT

/remove-lifecycle stale


[Feature]: Request to Add Visibility of Component Feature in Tree List 👁

Contact Details
<EMAIL_ADDRESS>Feature
Dear Theta Development Team,
I hope this message finds you well. I am an active user of your application and have been using it for quite some time now. I am writing to you today with a feature request that I believe would greatly enhance the usability and efficiency of the app.
The feature I would like to propose is the addition of a visibility control for components in the tree list. Currently, when modifying a component, it becomes challenging if there is an element above it that is visible to me. This often leads to difficulties in editing and adjusting the desired component effectively.
By introducing a feature that allows users to make specific components invisible while building the app, we would have greater flexibility and ease of use during the development process. This visibility control would enable us to focus solely on the component we are currently working on, without being distracted or hindered by other visible elements in the tree list.
Here are some potential benefits of implementing this feature:
Enhanced productivity: Users will be able to concentrate on the components they are modifying without interference from other visible elements. This will result in faster development and a more efficient workflow.
Improved accuracy: By having the ability to hide specific components temporarily, developers can ensure that changes and adjustments are made precisely to the desired component, reducing the risk of unintended modifications.
Simplified debugging: When troubleshooting or identifying issues within the app, being able to hide certain components can make it easier to isolate and diagnose problems, saving time and effort during the debugging process.
I believe that the addition of this visibility control feature would be a valuable enhancement to your app, benefiting both novice and experienced users. It would provide an intuitive and user-friendly experience while maintaining a high level of flexibility in the development workflow.
Thank you for considering my feature request. I appreciate the hard work and dedication your team puts into improving the application. I look forward to seeing how this suggestion could potentially improve the overall development experience for users like me.
If you require any further clarification or have any questions regarding this feature request, please feel free to reach out to me. I would be more than happy to provide additional details and discuss this idea further.
Once again, thank you for your attention and consideration.
Sincerely,
ARyan
Additional context

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Thanks ARyan!
We will introduce it soon. In the meantime, you can change the visibility properties of the right bar.

Thanks @ghostyARYAN


Custom 404 page does not work in example

Hm.. does not work locally for me
Seems to work on the deployed version - https://kind-lichterman-5edcb4.netlify.app/es/asdasdad

Needed to click no the button


Related datasets/collections (t-shirt)

Depends on collections feature

Closing, as this was a placeholder card for grant forecasting purposes.


:hammer: Fixed spacing issues with SecretsConfig

Hi @naoki0719, I found there was an issue in spacing parameter setup in SecretsConfig class, I have fixed it and it's just a one liner change, Please do merge it and publish the new version ASAP if possible.

@naoki0719 I am also facing the same issue it will be really helpful if you can merge this PR on priroity.

Thanks @naoki0719 for merging the PR, Do you have a plan to release the new version with this fix?

@DhavalRKansara
We just released it and it will appear on pub.dev soon.
The version is 9.0.2.

@DhavalRKansara We just released it and it will appear on pub.dev soon. The version is 9.0.2.

Thanks @naoki0719


Dynamic loading

Is it possible to use a event listener for the scroll event in order to use dynamic loading?
I tried to use it like this:
listView.addEventListener('scroll', function(){
Titanium.API.info('scrolling...');
});
The event never gets fired.
Am I doing anything wrong?
Thank you!

with listview you can use setMarker({sectionIndex:5, itemIndex:10}); and "marker" event, but I'm not sure that it will work with TiCollectionView
lets ask author :)

No, the "marker" event isn't implemented yet.

@mpociot Kannst du das Scroll Event vielleicht hinzufügen? Das wäre echt Klasse.

So I took a look at it again.
I was wrong , the "marker" event is implemented :)
Use it, as you would with a regular listView.
collectionView.addEventListener("marker", function(e){
    // Load more entries and set a new marker...
});
collectionView.setMarker({sectionIndex:0,itemIndex: 10 });


re-train non default wms layers

add support to re-train for non default wms layers
cc @ingalls

I've removed retrain support from master as it was model specific and we'd like to continue to focus on building a model agnostic inference engine. This is now even more so the case with the launch of our initial PyTorch support.
Moving forward we'll implement webhooks which will allow launching a docker image to do arbitrary docker retraining.


[WIP] add all-your-base

I'll will be working on this exercise.

How is it going?

Good! I'll commit my first working solution soon, so we can discuss about it. I'm sure it can be improved.

Great. I look forward to seeing it.
It's OK to post a work-in-progress too.

I think it's ready for review. :)

Looking good. Did you manually create the test file or did you write a generator to generate it from the x-common all-your-base.json file?

I manually created the test file from the json file. I also (forgot to say this) decided on the special cases as I thought made more sense. Basically I took the approach of "what would happen if writing this in a calculator". I that way, for example, entering [0, 0] is valid and the same as [0] (and, in turn, 0 in any base is 0). Hope this makes sense...

Looks good, :heart: It's certainly in a good enough state to merge in as it is, but it would be even better if you're able to address some of the points I've raised. (And also feel free to disagree if you don't think they'd be an improvement.)
I've not looked too closely at your example solution, that's what the Exercism site is for :).

I also decided on the special cases as I thought made more sense

You should create a pull request to add them to the all-your-base.json file in https://github.com/exercism/x-common
Sometime in the future, someone will create a generator to generate the test file based on the common json file, and this might cause your cases to be lost.

I think it's ready for another review. If it's good I'll rebase and squash to leave just one commit. Sorry for all the time it took me to finally finish this!

Looks good to me :+1:

I think it's ready to merge. I've rebased and squashed all commits into one. Let me know if I am missing something. :)

Looks good :+1: I'll wait and see if @kotp has any comments, otherwise I'll merge it in over the weekend.

Nothing so far, but I think I can review this later this evening.

Ok. If you're happy you can merge it in.

Thanks for all your work on this @sebarmano :heart:


Vagrant 1.8.4 crashes when vagrant-omnibus is used with winrm

The bug has already been reported in vagrant repo: https://github.com/mitchellh/vagrant/issues/7459
Here is the stacktrace: https://gist.github.com/olivierlemasle/a173b1077e784c224b3c345317479ee7
Similar issue has already been fixed in vagrant-hostmanager: https://github.com/devopsgroup-io/vagrant-hostmanager/issues/198

Updated PR: https://github.com/olivierlemasle/vagrant-omnibus/pull/1

Fixed by #135


Improve camera movement

Either make sure the camera follow_system is running after the player movement system, or add a tweening for the camera movement, so that it lags behind in a way that looks more like it's intended ^^

The camera entity could be placed as child on the player, so that the transform would be automatilly applied by the engine


Equivalent of ionViewCanGoBack

Are you requesting a feature, reporting a bug or ask a question?
Asking a question
What is the current behavior?
The only available lifecycle events available are for if the user leaves the page by either popping or pushing a new one. I'd like a lifecycle event for just the former to check if the user decides to leave mid form instead of checking even when the form is accomplished and the user proceeds to the next page.
What is the expected behavior?
An available lifecycle event for just checking if the user is popping a page (going back through the navigation stack).
Specify your

browser: Chrome
browser version: 61.0.3163.100 (Official Build) (64-bit)
surveyjs platform (angular or react or jquery or knockout or vue): Angular
surveyjs version:

@juleslui I am not sure, if I understood you correctly. Do you need this?
survey.onCurrentPageChanged event
and Page.visibleIndex property
It will allow you to find out, if a user go to the next page or back.
Thank you,
Andrew

Thank you so much for your reply, good sir, but this was my bad. I posted this on the wrong repository.
I'll be closing this now.
Sorry for the confusion.


glassmorphism ui added

dark mode

light mode
ui refined
pls merge it @heysagnik with hacktoberfest tag

Ok but add glassmorphism UI for buttons and video preview too.
I am creating a beta repo Can you please create a PR again with this current changes , I will merge it their , oK?


How to use GPU?

How does this use GPU? I see the GPU utility is 0%.

Hi Yash, maybe you tried it already, but if not, you should try uncommenting the following line:
# tensorflow-gpu==1.14.0  # GPU version of TensorFlow.
and commenting out the first line of requirements.txt before installing the requirements with pip.
Does this help?

I am using Tensorflow 1.15 where temsorflow is tensorflow-gpu by default.
But I saw 0% GPU utilization in the training step.

Did you solve this problem?
I saw 0% GPU utilization, too.

This was pretty much my fault, as the code utilizes GPU by default.
I had a poorly configured tensorflow setup that could not use GPUs. I swiched to Nvidia's Tensorflow-1 19.12 NGC container, which come preconfigured for GPU .


[SPARK-9177][SQL] Reuse of calendar object in WeekOfYear

https://issues.apache.org/jira/browse/SPARK-9177
@rxin Are we sure that this is thread safe? @chenghao-intel explained in another PR that every partition (if I remember correctly) uses one expression instance. This instance isn't used by multiple threads, is it? If not, we are fine.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Expression states are not shared across threads, so this should be OK.

@tarekauel the other patch for more powerful codegen is now merged.

Jenkins, test this please.

@rxin Jenkins still doesn't like me

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #1116 has started for   PR 7516 at commit 0c1313a.

I triggered it finally. Meantime, if you have time, do you want to pick up some other issues here? https://issues.apache.org/jira/browse/SPARK-8829

Test build #37809 has started for   PR 7516 at commit 0c1313a.

Sure. I am going to solve some of them.

Test build #37809 has finished for   PR 7516 at commit 0c1313a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #1116 has finished for   PR 7516 at commit 0c1313a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM

Thanks - I've merged this.


Log telemetry events into separate log file and the output channels for logs

At present, there is no way for a user to know what telemetry events are being logged in VS Code other than searching the code base for telemetryService.publicLog. Event after doing so, its never clear what data is exactly being sent. In order to be transparent, we need to have a dedicated place where the user can see all the telemetry events being logged along with the data being sent.
The output channels for the logs from various processes (main, shared, renderer) can also benefit from the inclusion of the telemetry events (albeit with common data removed to reduce noise) as this will help the development/debugging process.

Here is my proposal:
When the log level is set to trace

All telemetry events with all data is logged to a new dedicated file telemetry.log. This file will live in the same place as other log files.
The telemetry events for the shared, main and renderer processes will appear in the respective log files and output channels with reduced content (event name + data without noise from common data)

When the vscode is opened via the cli using the --verbose flag,

The telemetry events from the cli process will be included in the cli.log file (this is the existing file that has logs from the cli process)
The telemetry events from the main process will be included in the main.log file (this is the existing file that has logs from the main process)

Note: This does not include telemetry events sent from extensions.

Re-opening to investigate logging telemetry events from extensions that use our vscode-extension-telemetry module to send telemetry

Finally. :)


Thermal Printer package issue

Describe the bug
when i try to use any thermal printer package this buffer issue come out,
Uncaught Error: Dynamic require of "buffer" is not supported , when i try to install react-thermal-printer/electron-pos-printer
To Reproduce
Install any thermal printer package like electron-pos-printer

I also tried to use 16.20.1 node version and latest version of node 18.17 but still have that error.

Hello, thank you for using Retron template!
I don't know much about the electron-pos-printer module, but I've seen a lot of installation issues registered as GitHub Issues.
Can you determine if this module is working properly in the latest electron environment?
Also, here are some speculative causes:

Retron is optimized for ESM and you may need to use import instead of require.
some modules should be run in the Main process instead of running in the Renderer process.

If you're still experiencing issues, I'd like you to share a simple Electron project that I can reproduce.
Regards,

hi, thank you for your response,
I also try some of thermal printer package and still have error in "Dynamic require", and in my code i didnt use require, the issue came from node modules. im almost 80% of my project but im looking forward to find out how to fix the "Dynamic require"


63 Refined UI (a lot)

Refined UI
Closes #63 #70 #36 (kinda)

Made NavTwo fixed, this should solve the issues with scrolling in various pages.
Some modifications to NavOne styles.
Made new route groups for /modify & /reports (hence, new URLs as well).
Fixed role-based views in NavTwo for /settings.
Made skeletal /reports to WAYY prettier /reports.

Would like to add further refining, but will do that on a different branch.. :)
Dashboard (try spotting the changes 🗿):

Report:
No Data:

With Data:
[add when there is data]
Settings:

So much I still wanna do ;-;

Report with data


fix(cache): fix dedup error of meta-cache

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)

Should we wrap this logic in LruCache?

Should we encapsulate this logic in LruCache?

For example, moka will automatically retry if the future aborts.
                        // Somebody else (a future containing `get_with`/`try_get_with`)
                        // has been aborted.
                        WaiterValue::EnclosingFutureAborted => {
                            retries += 1;
                            panic_if_retry_exhausted_for_aborting(retries, MAX_RETRIES);
                            // Retry from the beginning.
                            continue;
                        }

Should we encapsulate this logic in LruCache?

For example, moka will automatically retry if the future aborts.
                        // Somebody else (a future containing `get_with`/`try_get_with`)
                        // has been aborted.
                        WaiterValue::EnclosingFutureAborted => {
                            retries += 1;
                            panic_if_retry_exhausted_for_aborting(retries, MAX_RETRIES);
                            // Retry from the beginning.
                            continue;
                        }

Good point. It is better to put the logic in the implementation of lookup_with_request_dedup.

Should we encapsulate this logic in LruCache?

Done


messageForwardInfo class documentation is wrong

the messageForwardInfo documentation and all its child pages (messageForwardOrigin,  messageForwardOriginChannel, messageForwardOriginHiddenUser, and messageForwardOriginUser.) are wrong: it says I should receive something like
"forward_info":{
    "origin": {
        "@type":"messageForwardedFromUser",
        "sender_user_id":0
    },
    "date":0,
    "forwarded_from_chat_id":0,
    "forwarded_from_message_id":0,
}

while I receive a different organized json
"forward_info":{
    "@type":"messageForwardedFromUser",
    "date":0,
    "forwarded_from_chat_id":0,
    "forwarded_from_message_id":0,
    "sender_user_id":0
}

It isn't wrong. On-site documentation is for the latest public version TDLib 1.4.0 and you are using some older version. See Change log for the full list of changes.

oh, thank you. I forgot to check for TDLib updates!


Google Sign-in sample: Use GoogleSignInClient

This PR uses the GoogleSignInClient instead of GoogleApiClient.
Also, use the already available com.google.android.gms.common.SignInButton instead of custom one.
Updated target and compile SDK version to 29.
Moreover, some dependencies were not needed.

Please notice that I've removed the mUserIdToken since we are not requesting it as part of the sign in options.

Btw, would you like me to also update to version 2.5.0 of wearable libraries?

Sounds good to me on mUserIdToken. Rest looks good.
Yeah, might as well update this sample to 2.5.0. I can merge pull request after you do that.
Thanks again!!! :)

No problem. Libraries updated


Initial Action/CI

Added Unit Test and Build action
Added badges on the Readme

 Initial Action/CI

This PR can now be merged to main branch. Continuation to another new PR once refractoring is done. Which it needs to fix on issues found from running job Unit Testing action within flutter analyze command. The same continuation to another new PR for the actual Test script to test.


Java gen: Fixing Codacy warnings, fixing acronym handling

Current coverage is 78.89% (diff: 92.59%)

Merging #534 into master will decrease coverage by 0.02%

@@             master       #534   diff @@
==========================================
  Files           248        248
  Lines          9094       9085     -9
  Methods           0          0
  Messages          0          0
  Branches       1185       1186     +1
==========================================
- Hits           7177       7168     -9
+ Misses         1608       1604     -4
- Partials        309        313     +4

Powered by Codecov. Last update 363e8f4...a11d9f7

I needed to make one small tweak - I want to use upper acronyms for mock grpc classes, so that the naming correlates better.


Should not include model binaries in the repository.

@hideya
Currently it seems that the repository contains model binaries(example/tensorflow_js_simple/public). This is undesirable. When model data exceeding 200 MB is kept committed, git becomes very heavy.
Model data is included in the release. Please change the usage so that model data is downloaded separately. If you need to fixture the model data version, you can explicitly specify the release tag version.
When change of usage is confirmed, I delete the binary data by going back to the history.
Sorry to trouble you, but thank you.

Good point!  Thanks for the comment.  I've fixed the issue in PR https://github.com/maru-labo/doodle/pull/18
Please go ahead and remove the binary data from the commit history.
Sorry for the trouble...

@hideya
Thank you for your response! I deleted the binary by tracing the history.
This was a very dangerous operation. Please fork the repository again.

Thank you. Glad that you have done it before  the hands on.  Appreciate it!


SingleChildScrollView(GridView(CustomScrollView())) strange scrollbar artefact

Steps to Reproduce
CustomScrollView in grid children on flutter web

Execute flutter run on the code sample
scrolling one grid item, scroll also others scrollbars..

Expected results:
ScrollBars shouldn't synchronize
Actual results:
ScrollBars are synchronized

Code sample

GridView.builder(itemBuilder: (_,__) => CustomScrollView(slivers:[...]));

Logs

no errors in log

Analyzing l2k.io...
No issues found! (ran in 2.3s)

[✓] Flutter (Channel stable, 3.7.10, on macOS 13.2.1 22D68 darwin-arm64, locale en-FR)
    • Flutter version 3.7.10 on channel stable at /Users/renanyoy/code/sdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4b12645012 (3 days ago), 2023-04-03 17:46:48 -0700
    • Engine revision ec975089ac
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/renanyoy/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.77.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (3 available)
    • IPhone14.renan (mobile) • 00008120-0009582C2100C01E • ios            • iOS 16.3.1 20D67
    • macOS (desktop)         • macos                     • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)            • chrome                    • web-javascript • Google Chrome 111.0.5563.146
    ! Device<PHONE_NUMBER>67 is not authorized.
      You might need to check your device for an authorization dialog.

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

https://user-images.githubusercontent.com/259671/230569710-1f43098a-8241-4e88-a352-39aa7b90a21e.mp4

From your demo video, it looks like the issue is coming with Scrollbar rather than the list inside GridView since I see the 2nd list didn't move.
In order to address the issue properly, please provide a completed and minimal reproducible code sample so that we may verify this.
I built a simple minimal sample here and don't see the issue (perhaps I haven't added a Scrollbar but I'm not sure about your case). You may continue using it to represent your case.

Sample code
import 'package:flutter/material.dart';

void main() {
  runApp(const MaterialApp(home: MyApp()));
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: GridView.builder(
          itemBuilder: (_, __) => CustomScrollView(
            slivers: [
              SliverFixedExtentList(
                itemExtent: 50.0,
                delegate: SliverChildBuilderDelegate(
                  (BuildContext context, int index) {
                    return Container(
                      alignment: Alignment.center,
                      color: Colors.lightBlue[100 * (index % 9)],
                      child: Text('List Item $index'),
                    );
                  },
                ),
              ),
            ],
          ),
          gridDelegate: const SliverGridDelegateWithFixedCrossAxisCount(
            crossAxisCount: 2,
          ),
        ),
      ),
    );
  }
}

https://user-images.githubusercontent.com/104349824/230595881-87c03c31-fe6d-4d42-998d-83a074820739.mov

As far as I can see, it seems it is caused by the implementation. When removing Scrollbar widget on your lastest sample code above, I see it works well with its Scrollbar, and the scrolling behavior is not conflicted between lists (compared to your origin video).
https://user-images.githubusercontent.com/104349824/231150086-8c3b3866-9a5a-41d7-b0df-4a4dcbfe0de9.mov
Please try removing Scrollbar widget and confirm if it's solved on your end.

I don't have any scrollbar widget in my code

https://user-images.githubusercontent.com/259671/231204190-12f7128c-8ba9-4e19-ba6c-d807697bcadf.mp4

It seems there is a conflict between controllers that I see they don't exist on your sample code. I would suggest you attach the corresponding controller for scroll views to see if it can solve your case.

I tried that on my app,it didn't worked, same for keys, that's why I opened an issue here..

Hi. I see it already worked as my demo at https://github.com/flutter/flutter/issues/124379#issuecomment-1503168499. Can you share the reason why you need to put SingleChildScrollView outside GridView, it seems redundant and make the layout more complicated.
Also, as the problem is going differently from the original description (and sample code), this will be difficult for anyone to deal with next steps. If you still want to continue using SingleChildScrollView for this case, please leave a comment describing the problem (Description of the problem, actual/expected result and final sample code) or file a new issue would be appreciated. Thank you!

it's a complex web site with the with the main scroll view managed and at a different level than the page contents..
I opened a new issue #124770

Thanks for filing a new issue. I will close this issue in favor of a new one at https://github.com/flutter/flutter/issues/124770.


add ATTESTATION kind as material type

In some cases, we might want to add additional attestations as pieces of evidence. This could help with storing externally generated attestations, or connecting different workflows in your organization.
To do so, we could add an ATTESTATION material type that will

get uploaded to the CAS
we'll validate that's a valid DSSE envelope.
we need to make sure that if we take an attestation from chainloop CLI and add it here as a material, it's still the same digest.
NOTE: before ingesting this attestation type in the index, we might want to check that it is an existing attestation in your org. This is to make sure that nodes in the graph still represent attestations that have been generated with a run. Just some food for thought, I am not sure if we need this kind of optimization at this point, let's discuss it.

I took a look at the digest matching.
We need to be careful, since the output of `wf run describe --id ... --output attestation does not match the sha256 of the attestation. This is because it's pretty printed.
For example
the generated output doesn't match the requested digest, it should

the downloaded version does though

To make it match, what you need to do is to make the output single line
chainloop wf run describe --digest sha256:8b7c3bea8b640744762e7959a5f221a755fe28a8671d6ea9ff29ffa7625a3958 -o attestation | jq -c -r |  tr -d '\n' | sha256sum
8b7c3bea8b640744762e7959a5f221a755fe28a8671d6ea9ff29ffa7625a3958  -

So my suggestion would be to make sure we marshal the provided attestation in the client in such a way that fits the way we do it in the backend.
We have a method that does that already but it's in the context of the controlplane.
https://github.com/chainloop-dev/chainloop/blob/7b1e79263dd68653a0a4010dec57235670f0d0a4/app/controlplane/internal/biz/attestation.go#L63
I'd move that method to the parent internal/attestation package, and use it from controlplane and CLI, to format the provided attestation, what do you think?

Thanks for your analysis. Yes, this is certainly a problem that could be mitigated by creating the payload from the CLI using the same approach as the backend. Not a final solution, though. I'll perform the changes you suggest and submit a PR.


404.html does not include information about the site being created by scully

🐞 Bug report
Description
We have certain pages that require authentication and therefore wish not to prerender them.
I am using 'ignored' router plugin on those pages and our CDN returns 404.html when trying to open them and it gets rendered on the client side by angular correctly, but an issue arises when you first open site on such page which is not prerendered and then you try navigating to a page that was prerendered using Angular navigation, in this case window['ScullyIO']='generated' is missing and TransferStateService does not fetch data.json but instead does the requests to our CMS which should not happen.
Navigating to non-prerendered pages from a prerendered page does not cause any issues and everything works correctly
so I think that 404.html should contain window['ScullyIO']='generated' to make sure that TransferStateService behaves consistently regardless of which page users enters the site at.
🔬 Minimal Reproduction
Generate any angular application with scully and check contents of 404.html
💻Your Environment
Angular Version:

Angular CLI: 13.0.2
Node: 14.18.1
Package Manager: npm 7.24.0
OS: win32 x64

Angular: 13.0.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... localize, material, platform-browser
... platform-browser-dynamic, router, service-worker
... youtube-player

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1300.2
@angular-devkit/build-angular   13.0.2
@angular-devkit/core            12.2.10
@angular-devkit/schematics      12.2.10
@angular/cli                    13.0.2
@schematics/angular             13.0.2
rxjs                            7.4.0
typescript                      4.4.4

Scully Version:

"@scullyio/ng-lib": "^2.0.2",
"@scullyio/scully": "^2.0.3",

@BlindDespair do you have a sample site we can look at?

@aaronfrost do you mean a repo or just a url to a deployed site. Sadly I do not have a sample site which demonstrates this deployed anywhere although we do have 1 production site with this. Although I pretty much summed it up in the description, generating any app with scully will produce 404.html and that should contain the info about it being pre-rendered by scully just like any page.html


Support to handle Subscriber add code in HSS

Support to handle Subscriber add code in HSS. If any config is missing then request for sending new config

test container

retest this please

retest this please


add refactoring: string concatenation to template literals

Fixes #18267
@ajafff have a look

My inclination here is that concat -> template is a good refactor, but it's not clear to me why you'd want the reverse direction.
@DanielRosenwasser thoughts?

@typescript-bot pack this

Okay now @typescript-bot pack this

Hey @bigaru, I spoke with Ryan and at this time we think convert to template expression is clearly useful from users. On the other hand, we didn't have consensus that users wanted to go the other way. I've removed those bits and pushed up a commit to remove that functionality. In the future, we'll be able to revert ad0f0064cedffa5d6041733023f917fb93f46bf0 if we change our minds.

Nit-pick: At the moment, this refactoring seems to be called “Convert to template string”. The more correct name would be “Convert to template literal”.


Failing test as of 2017-09-22

Before working on a PR on this project, I tried to run the test suite to have confidence that my changes won't be regressing anything. I noticed that several examples do not pass anymore, often for trivial reasons like expecting "http://json-ld.org/test-suite/..." and getting "https://json-ld.org/test-suite/..." as shown below.
Would it be possible to update the specs so that they pass?
Here is what I did:
git clone https://github.com/ruby-rdf/json-ld.git
git checkout 2.1.5
edit Gemfile to add `gem "rake"` in the development group
bundle install --path .bundle
bundle exec rake spec

The spec take a long time, and many fail with errors like this one:
       Expected: [
         {
           "@id": "http://example.com/queen",
           "http://example.com/vocab/label": [
             {
               "@value": "The Queen"
             }
           ],
           "http://example.com/vocab/index": [
             {
               "@value": "No"
             },
             {
               "@value": "indexes"
             },
             {
               "@id": "http://json-ld.org/test-suite/tests/asTheValueIsntAnObject"
             }
           ]
         }
       ]
       Actual  : [
         {
           "@id": "http://example.com/queen",
           "http://example.com/vocab/index": [
             {
               "@value": "No"
             },
             {
               "@value": "indexes"
             },
             {
               "@id": "https://json-ld.org/test-suite/tests/asTheValueIsntAnObject"
             }
           ],
           "http://example.com/vocab/label": [
             {
               "@value": "The Queen"
             }
           ]
         }
       ]

On the whole test suite, I have like 35 failed tests as of 2017-09-22.

I typically run with a aymlink to the tests. Which is likely masking this problem. PRs to both the gem and the test suite welcome.

Hello @gkellogg ,
I found out that most of the test failures I reported in this issue are due to changes in the jdon-ld suite, which seems to be used as integration test of the ruby json-ld gem.
For example, the following error:
  3) JSON::LD test suite Compaction compact-0062-in.jsonld: @type: @vocab and relative IRIs
     Failure/Error: expect(result).to produce(expected, logger)

       Expected: {
         "@context": {
           "term": {
             "@id": "http://example.org/term",
             "@type": "@vocab"
           }
         },
         "term": "http://json-ld.org/test-suite/tests/not-a-term-thus-a-relative-IRI"
       }
       Actual  : {
         "@context": {
           "term": {
             "@id": "http://example.org/term",
             "@type": "@vocab"
           }
         },
         "term": "https://json-ld.org/test-suite/tests/not-a-term-thus-a-relative-IRI"
       }

Is explained by the renaming of 'http://json-ld.org/...' URLs to 'https://json-ld.org/...', renaming which was done last July in https://github.com/json-ld/tests/commit/d56f51a90660dec3edeb90c048af9c9140df2306
Another test failure I found is this one:
  2) JSON::LD test suite Compaction compact-0045-in.jsonld: @id value uses relative IRI, not term
     Failure/Error: expect(result).to produce(expected, logger)

       Expected: {
         "@context": {
           "term": "http://example.com/terms-are-not-considered-in-id",
           "compact-iris": "http://example.com/compact-iris#",
           "property": "http://example.com/property",
           "@vocab": "http://example.org/vocab-is-not-considered-for-id"
         },
         "@id": "term",
         "property": [
           {
             "@id": "compact-iris:are-considered",
             "property": "@id supports the following values: relative, absolute, and compact IRIs"
           },
           {
             "@id": "../parent-node",
             "property": "relative IRIs get resolved against the document's base IRI"
           }
         ]
       }
       Actual  : {
         "@context": {
           "term": "http://example.com/terms-are-not-considered-in-id",
           "compact-iris": "http://example.com/compact-iris#",
           "property": "http://example.com/property",
           "@vocab": "http://example.org/vocab-is-not-considered-for-id"
         },
         "@id": "http://json-ld.org/test-suite/tests/term",
         "property": [
           {
             "@id": "compact-iris:are-considered",
             "property": "@id supports the following values: relative, absolute, and compact IRIs"
           },
           {
             "@id": "http://json-ld.org/test-suite/parent-node",
             "property": "relative IRIs get resolved against the document's base IRI"
           }
         ]
       }

Where the @id value seems to be using a full URI such as http://json-ld.org/test-suite/parent-node instead of a relative one like ../parent-node; this failed example like the next one "4) JSON::LD test suite Compaction compact-0066-in.jsonld: Relative IRIs" look like regresssion to me.
I wish I had the skills to fix the test suite before doing my performance optimization PR but this would take me a long time, so I'm going to test my PR against the "fast" tests (those which are not skipped when ENV['CI'] is set).

I’ll go through the test suite when I can.

After updates to both the implementation and the test suite, these should all pass now.


COOP is not a defense against network timing attack.

Network timing attack works even if there is a COOP in HTTP response, since it measures how much time it takes for the server to create a response.
I fixed the defense table in network timing attack page.
The table was correct previously but it was somehow modified in #92 , so this PR is just a rollback.

For Cross-window Timing Attacks COOP can make it harder to leak data since the opener gets closed on a complete navigation which then requires a new popup/user activation to leak more data.
I think for this attack to be useful it needs be combined with a popunder.

Thank you for the clarification!
It makes sense now that COOP complicates the attack by preventing the opener from reusing the window.
While it's not a perfect defense, I understand what the table says better.
Thanks a lot!

The table is meant to guide about what defenses can be deployed to mitigate the risks. Almost any protection for xs-leaks isn't perfect since there are always edge cases or alternative techniques to leak the same information.
COOP is meant to limit most of the leaks to one bit of information per user interaction.


Fix NavigationAgent3D debug path duplicated points

Fixes duplicated points in NavigationAgent3D debug path.
The debug was using the line array for the path points by mistake, duplicating the points.
The point render is now disabled as well when point size is zero.
Adjusts the property ranges to the same as 2D in https://github.com/godotengine/godot/pull/74800

Thanks!

Cherry-picked for 4.0.1.


CMIP6 interface mixes Amon and Omon

Developing xarray version of the global_mean.py I found out that the current filenames expansion i.e. _expand_filename() does not make any difference between Amon and Omon variables, so that if both are available both are loaded and averaged together. This occurs specifically for historical EC-Earth3 on mafalda when computing net_sfc, which requires snow (prsn) which is available for both Amon and Omon, but other potential situation like this are possible.
CDO does not complaint since it just do global average, but xarray crashes so that I spotted the issue.
This has to be solved in the main branch: a possible workaround currently used in the xarray branch is to prepend an A and O to the filename definition in the interface_CMIP6.yml as done here below:
filetype:
  atm2d:
    filename: '{var}_A{frequency}_{model}_{expname}_{ensemble}_{grid}_{year1}01-{year2}12.nc'
    dir: '{ensemble}/{frequency}/{var}/{grid}/{version}'
    component: cmoratm
  atm3d:
    filename: '{var}_A{frequency}_{model}_{expname}_{ensemble}_{grid}_{year1}01-{year2}12.nc'
    dir: '{ensemble}/{frequency}/{var}/{grid}/{version}'
    component: cmoratm
  oce2d:
    filename: '{var}_O{frequency}_{model}_{expname}_{ensemble}_{grid}_{year1}01-{year2}12.nc'
    dir: '{ensemble}/{frequency}/{var}/{grid}/{version}'
    component: cmoroce
  ice:
    filename: '{var}_{frequency}_{model}_{expname}_{ensemble}_{grid}_{year1}01-{year2}12.nc'
    dir: '{ensemble}/{frequency}/{var}/{grid}/{version}'
    component: cmoroce

It is not clean but solves all the issues so far.

This is currently included in the main, could be closed


Resolved issue serializing deleted keys to the server after call to Clear()

Regardless of if SerializedRawData found and removed the key, mark the key as deleted to handle when Clear() is called, which clears all SerializedRawData immediately, so then keys never really get deleted at the server.

@welegan Can you confirm if this satisfies your intent between the logic in RedisSessionStateItemCollection.Clear() which also clears the SerializedRawData collection too; and the RedisSessionStateItemCollection.GetChangedObjectsEnumerator() called during RedisSessionStateStoreProvider.SerializeToRedis ?


Feat/bump rollups node to 1.0.1

Looks like we have a problem with the CI when NOT USING the localnode mode.


xpcError: connection interrupted when receiving data

Hello I am trying to send data via my android app, using the android method bluetoothGatt.writeCharacteristic(characteristic); and on the blendo side, I get the error soon after:
$ xpcError: connection interrupted
what information do I need to post here to troubleshoot this issue?
OS: Mac 10.10.3
Node: v4.2.6
***** ble.js
bleno.on('stateChange', function(state) {
    // state = unknown | resetting | unsupported | unauthorized | poweredOff | poweredOn
    console.log('on -> stateChange: ' + state);

    if(state === 'poweredOn') {
      console.log('startAdvertising');
      bleno.startAdvertising(config.name, config.serviceUuid);
      if(callback) {
        callback(null);
      }
    }
    else {
      console.log('stopAdvertising');
      bleno.stopAdvertising();
      if(callback) {
        callback(null);
      }
    }
  });

***** characteristic.js
var BlenoCharacteristic = bleno.Characteristic;

var Characteristic = function() {
  Characteristic.super_.call(this, {
    uuid: config.characteristic.uuid,
    properties: config.characteristic.properties,
    value: config.characteristic.value,
    descriptors: [
      new bleno.Descriptor({
        uuid: config.descriptor.uuid,
        value: config.descriptor.value
      })
    ]
  });

  this._value = new Buffer(0);
  this._updateValueCallback = null;
};
util.inherits(Characteristic, BlenoCharacteristic);

***** config.js
config.name = 'App';
config.serviceUuid = ['fff0'];
config.characteristic = {
  uuid: 'fff1',
  properties: ['read', 'write'],
  value: 'App characteristic value'
};

config.descriptor = {
  uuid: 'fff2',
  value: 'App descriptor value'
};

I also have same issue with the android app you have recommended in the README, any thoughts?

I figured it out, for anyone having this problem make sure the Characteristic value is null

@jareddlc this is good to know, I'll re-open this and prevent adding of characteristics with value that are non-read only.

I've made a change to prevent characteristics with value that are non-read only in https://github.com/sandeepmistry/bleno/commit/3a1ffa9c50b0e546ca2170706c0ef0c9148f87a5.

👍


added submodule, removed existing files

Everyone please make sure this works before we merge. I am also unsure why this isn't auto-merging, I'll look into that.

I don't think it likes merging software deletions? Anyways I'll merge manually after everyone makes sure this works.

Those conflicts are because they are conflicts. Your PR is a few commits behind master, critically behind the bump to tock master commit:
[-bash] Tue 30 May 11:27 [[master] /Volumes/code/lab11/signpost]
$ git log master...origin/software-submodule
commit e9e8a6e0264de8784a935d6b3743eb632cdc6f2a (origin/software-submodule)
Author: Joshua Adkuins<EMAIL_ADDRESS>Date:   Mon May 29 18:53:32 2017 -0700

    added submodule, removed existing files

commit 55b73cdb8e69174db781e88887405cc8037017c5 (HEAD -> master, origin/master, origin/HEAD)
Author: Joshua Adkuins<EMAIL_ADDRESS>Date:   Mon May 29 14:41:36 2017 -0700

    moved travis files to software for the impending split

commit 5f1fd73293474ecff81bf0b482ea6a91c1f47fda
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 17:27:32 2017 -0400

    use vpath for app subdirectories

    @brghena I think this should address your issue from 9a35bbd

commit 0e94087d392443eb137b11228e824a2197d9224a
Merge: b182df2 ab77c88
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 17:05:45 2017 -0400

    Merge pull request #61 from lab11/bump_tock_master

    Bump tock to latest master

commit ab77c88c0c49ef4c5f700e061430c851f7a5d67d (origin/bump_tock_master)
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 16:23:21 2017 -0400

    Bump tock to latest master

      - Update apps for merged ltd294x driver
      - Update boards for new build system

    Everything compile-tested.
    Print energy app verified on controller/debug_backplane

Thank makes more sense. Luckily sigmpost-software is not behind. I'll fix
after take off
On May 30, 2017 09:30, "Pat Pannuto"<EMAIL_ADDRESS>wrote:

Those conflicts are because they are conflicts. Your PR is a few commits
behind master, critically behind the bump to tock master commit:
[-bash] Tue 30 May 11:27 [[master] /Volumes/code/lab11/signpost]
$ git log master...origin/software-submodule
commit e9e8a6e0264de8784a935d6b3743eb632cdc6f2a (origin/software-submodule)
Author: Joshua Adkuins<EMAIL_ADDRESS>Date:   Mon May 29 18:53:32 2017 -0700
added submodule, removed existing files

commit 55b73cdb8e69174db781e88887405cc8037017c5 (HEAD -> master, origin/master, origin/HEAD)
Author: Joshua Adkuins<EMAIL_ADDRESS>Date:   Mon May 29 14:41:36 2017 -0700
moved travis files to software for the impending split

commit 5f1fd73293474ecff81bf0b482ea6a91c1f47fda
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 17:27:32 2017 -0400
use vpath for app subdirectories

@brghena I think this should address your issue from 9a35bbd

commit 0e94087d392443eb137b11228e824a2197d9224a
Merge: b182df2 ab77c88
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 17:05:45 2017 -0400
Merge pull request #61 from lab11/bump_tock_master

Bump tock to latest master

commit ab77c88c0c49ef4c5f700e061430c851f7a5d67d (origin/bump_tock_master)
Author: Pat Pannuto<EMAIL_ADDRESS>Date:   Mon May 29 16:23:21 2017 -0400
Bump tock to latest master

  - Update apps for merged ltd294x driver
  - Update boards for new build system

Everything compile-tested.
Print energy app verified on controller/debug_backplane

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lab11/signpost/pull/63#issuecomment-304916229, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGIJUAU6WTMW6a8z-sFaOeqQKK0KZlg4ks5r_DX4gaJpZM4Npv6D
.

Okay it's easiest to delete this one and try again


Fix the integration of TFLite models with multiple signatures and quantization

System information

TensorFlow version (you are using): tf-nightly
Are you willing to contribute it (Yes/No): No, this has a broader impact in the TFLite conversion & quantization API design.

Describe the feature and the current behavior/state.
TensorFlow 2.7 is finally adding support for multiple signatures in TFLite models as described here. However, this new support is lacking proper integration with model quantization in general, and with int8 quantization in particular.
Currently, full integer quantization is achieved by selecting a specific set of selected ops in TFLiteConverter, as described here. This also allows selecting the dtype of inputs and outputs through the inference_input_type and inference_output_type attributes, which can be float for automatic quantization/dequantization, or accept/produce quantized values directly.
However, when providing multiple signatures this quantization still applies only to one of them. In particular, I found that when using TFLiteConverter.from_concrete_functions, the quantized one is not even the first one provided in the list of signatures, but the first one alphabetically by its function name. This is certainly not a good design.
Furthermore, the function selected for quantization is limited to take a single input, which is the one inference_input_type applies to. I haven't checked if the same happens with outputs, but I wouldn't be surprised if it does.
Will this change the current api? How?
The API needs to undergo a redesign or provide new APIs to be coherent with support for multiple signatures. In particular:

Whether to apply quantization, and which kind of quantization and its settings, is something that should be decided at signature level instead of model level. Function names should be irrelevant to this.

Quantization should not be limited to single input functions. Rather, it should be possible to quantize or dequantize any desired set of inputs or outputs in any signature. Since indicating this per argument (and especially for outputs) might become quite cumbersome, the simplest approach might be to provide a way to easily quantize and dequantize values at will within the signatures themselves. This might require providing representative samples for all quantized signatures (except if using quantization-aware training, in which case the model should already have quantization ranges to use).

Bonus for extra points: allow a signature to produce quantized outputs that will be used as inputs in another signature. Or to say in another way, allow using the same set of quantization parameters for different quantized/dequantized values across signatures. For example, imagine an autoencoder where the encoder quantizes only its outputs for storage (not its calculation or weights), and a decoder takes already quantized inputs and works using int8 quantization.

Who will benefit with this feature?
Anyone using TFLite model conversion with multiple signatures, or even just one if quantizing a function that takes more than a single quantized argument.
Any Other info.
Partially tangential to this, I've noticed that the quantization parameters used by quantization-aware training do not seem to quite match the ones produced when producing TFLite models. This might be a potential source of issues as models are trained for a quantization different to what's applied later in practice. Maybe TFLite quantization should enforce keeping the quanization parameters of any annotated layers using fake quantization? If so, representative input data should not be needed in this case.

Hi @jvishnuvardhan ! Could you please look at this feature request!


Setting cookie attributes in $cookieStore

As a response to issues: #1786,#950,#1918,#1320
This PR enables setting a cookie's path and expires attributes using the $cookieStore service.
$cookies was not changed, since it's API is too strict, I could find no way to implement it without causing breaking changes, or using some terrible hacks.
I would suggest adding a new service to the module to support more advanced features (such as Json $watch expression, which should be more useful then binding the $cookies object directly), but this would probably require a bit of research regarding use cases.
Some things to note regarding the implementation:

urlroot (karma property) was added to all unit tests - to facilitate testing of different cookie path
Backward incompatible change (bad fixing a bad behaviour):
delete cookie now deletes cookies set with a path other then / (or baseHref)
that is before the fix, if you had a cookie set on path /karma (if it was added by the server for instance),
you would be able to see it, but deleting it will fail silently (and will not delete)
delete cookie now deletes duplicate cookies with the same name (if they have different paths)
Due to the fact that no browser allows inspecting the Path and Expiration date of a cookie, I chose to add a private _setCookie function inside the $browser module
which I override in unit tests. Not the most elegent solution, but the only other way to check Expiration is to mock the document object and change how document.cookie works, and that would have taken me too long for very little benefit.

Design decisions:

to change the path and/or expiration date of a cookie, you can pass an options object as the third argument to cookies(name,value)
the options object can override Path and Expires when adding a value, all other options variables are ignored (but are allowed, I.E. no validation is made).
You can pass either path, expires,none or both.
the path option is checked to be a string and be partial to window.location, otherwise, the default path is used. (warning is logged)
the expires option is checked to be a Date and in the future, otherwise no expiration is set. (warning is logged)
at the moment no support for non-Date expires is supported (for instance such as maxAge, or a number to indicate number of millesconds for cookie to last)
you can now delete a cookie on a specific path by calling cookie(name,undefined,options), with options containing path
only the $cookieStore service will support putting cookies with different path/expiration (as well as deleting certain paths.
this is to support backward compatability with $cookies.

Notes:
if the value passed to browser.cookies is not a String, it fails silently.
This is my first time contributing here (and on a Major open source project), I hope this can be incorporated.
I'm more than happy to make changes if something is wrong, so please let me know.

:+1:
I really think that using routing in your SPA, without the possibility to define that all cookies will have the same path is problematic and even error prone!

@altryne  - does https://github.com/angular/angular.js/pull/10530 solve the problem for you?

@petebacondarwin hey, I'm not sure how to try this out, but what I don't see there is a global config, so I can set up my default params like path , expiry and domain once

@altryne  - can you comment on that PR so that @shahata can ensure that he covers your use case?

@petebacondarwin now looking at it again, this was indeed supported!
An options parameter was added to $cookieStore.put() which supports passing path, domain, expires and secure parameters.
thanx!
hope this will land sometime soon

The new cookies implementation landed, this can be closed

:clap:


May be issue with bower package - missing files

dist/inputmask/bindings and dist/inputmask/dependencyLibs directories are both empty when installing bower package.

@amosfolz ,
Aw, I will include the files for the next release.

How do I specify a wildcard for the dist folder and subfolders?
"ignore": [
"/*",
"!dist//*",
],


Facing issue with Ansible playbook

I am getting error as attached :-

@enggnehaverma please include all the information that's requested when filing a bug, then we'll be able to take a closer look.
That screenshot above just shows apt errors, there's no hint of LXD anywhere in there. It's unclear if you're running this inside a container or not and I don't think any of us have any Ansible experience at all.
Not knowing anything about the environment, LXD versions, configuration, ... makes it impossible for us to do anything with this bug report.
Closing for now.


Can't enable Hot reload nor Debug react native app on Device.

Hello I just created an app using the react-native-cli and when it come to running this app on my phone it fetch a pre-bundle file. If I clicked Debug Js Remotely i got this error:
.
I build the App with Xcode & using the cli with:
react-native run-ios --udid & its seems that it founded my computer local IP address. Also accessing this address from my phone work so its not a firewall issue...

Additional Information

RN: 0.34.1
Platform: IOS 10.1
OS: macOs Sierra 10.12.

hey @frnk94, if you are working with simulator then you should have to chorme browser essential in your devices I don't have complete idea on ios, but you can use the command to enable the console debugging in your terminal when you are using hot reloading:
react-native log-ios
you can read the docs https://facebook.github.io/react-native/docs/debugging.html

@Anuj-786 Simulator work fine! It fetch the bundle from localhost:8081 and the hot reload is enable, but when it come to working on an actual device its always fetching from pre-bundle file so if i make any change to the code i need to rebuild and relaunch the app every time. It make it hard to debug things also the debugger give me an error. I can't really use the simulator since im using the camera inside the app and the simulator fail to simulate camera.

I just updated macOs and it now working not sure what was the issue...

Great !


video and audio disabled when 3rd person enters the room

No description provided.

hi, any solution to this, please?
I'm facing the same problem.

@bsobbe @Yerachmiel-Wand  I have same issue, are you able to fix the 3rd person enters room ? mute video mute sound, as soon as 1 person leave all back?

The solution was to change the ingress IP. We were using one that was
unreachable. Look at the client logs when the third person joins the room
and you will see jitsi moving from p2p to jitsi videobridge. That's where
it failed because it wasn't able to reach jvb.
On Wed, Nov 27, 2024 at 9:59 AM HP @.***> wrote:

@bsobbe https://github.com/bsobbe @Yerachmiel-Wand
https://github.com/Yerachmiel-Wand I have same issue, are you able to
fix the 3rd person enters room ? mute video mute sound, as soon as 1 person
leave all back?
—
Reply to this email directly, view it on GitHub
https://github.com/element-hq/jitsi-helm/issues/78#issuecomment-2503164299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ6IQ4ABSN2FCF7UDB4EC432CV3WNAVCNFSM6AAAAABSJGF3LOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBTGE3DIMRZHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
[image: Icon Description automatically generated]
Yerachmiel Feltzman
Backend Engineer
Mobile: +972 54 652-2363


"Learn Ruby the Hard Way" link fixed.

https://github.com/bento-io/collection/pull/196#issue-42897711


Hdnhdbsjxnvbd

git clone https://github.com/byrdboss/github-slideshow.git

git clone https://github.com/byrdboss/github-slideshow.git


[Feature Request] Collaboration tidy5e-sheet

My players and I use your loot sheet npc5e module for all of my merchants, the party pack, and chests in dungeons. One of the grips I get from my players is that their sheets look completely different from the loot sheets. I was wondering if you and sdenec would want to work together on using some of the tidysheet features that have been a hit like expanding item cards from the sheet and the clean aesthetic.
I added a similar request to tidy5e-sheet.
https://github.com/sdenec/tidy5e-sheet/issues/279

Maybe we can ping  @sdenec about this?
I would be absolutely in favor of collaborating on this.
Tidy sheet is awesome looking.
Current version of the lootsheet however is already closer to the look of the tidy sheet at least.


Flyway can't calculate the checksum of a large SQL script

Which version and edition of Flyway are you using?
6.0.2
If this is not the latest version, can you reproduce the issue with the latest one as well?
Yes
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
Oracle 12.1
Which operating system are you using?
Windows
What did you do?
I exported my database using SQL Developer, creating a SQL file ~32MB in size which I used as an effective baseline. When I tried to run flyway info, I got the following error:
Unable to calculate checksum for V001.001__BaselineScript.sql: Input length = 1
: Running flyway info failed: "C:\Program Files\flyway\flyway.cmd" exited with code 1
Flyway Enterprise Edition (unlimited schemas) 6.0.2 by Redgate
Database: jdbc:oracle:thin:@//localhost:1521/db (Oracle 12.1)

ERROR: Unable to calculate checksum for V001.001__BaselineScript.sql: Input length = 1

What did you expect to see?
I expected to see a standard flyway info response. The SQL script is valid and can be run in SQL Developer. When I tried to do something similar but on a much smaller database it all worked which suggests the size of the file is causing the problem.
What did you see instead?
See error as described above

The problem isn't the size - I can get the checksum of a 150MB file happily. I suspect it is an encoding issue. If you can forward us the file (have Slacked you privately) then I'll try to reproduce...

It would be helpful to know what flyway.encoding is set to in config, if anything, and what encoding the offending file is before we proceed?

OK, having gone down a bit of a rabbit hole the solution is to validate the file encoding and then flyway repair if necessary.  Flyway 5.2.4 was much more forgiving but that brings other problems into play.

Wanted to add a bit to this discussion. Had this exact problem yesterday, ERROR: Unable to calculate checksum of

@rscero  saved hours of my life, Cheers to you!

The problem seems to be that by default, flyway is expecting a UTF-8  text encoding. I hit this problem using files generated by SCA that used UTF-16 little-endian. You can specify the encoding in the config file ...
Encoding of SQL migrations (default: UTF-8). Caution: changing the encoding after migrations have been run
will invalidate the calculated checksums and require a flyway repair.
flyway.encoding=
... or you can specify the encoding of your migration files using the -encoding parameter.
I chose the 'cowards way out' and  converted the existing files to UTF-8!

The problem seems to be that by default, flyway is expecting a UTF-8  text encoding. I hit this problem using files generated by SCA that used UTF-16 little-endian. You can specify the encoding in the config file ...
Encoding of SQL migrations (default: UTF-8). Caution: changing the encoding after migrations have been run
will invalidate the calculated checksums and require a flyway repair.
flyway.encoding=
... or you can specify the encoding of your migration files using the -encoding parameter.
I chose the 'cowards way out' and  converted the existing files to UTF-8!

@rscero  saved my time. The same issue here. Was caused by specific polish chars like "ł, ó" etc. which somehow (perhaps through someones changing file encoding) changed into "�" marks. After moving them into original polish characters - migration went smoothly.


Crowdsale fails tests

when i run truffle test on the crowdsale contract
i receive
Error: VM Exception while processing transaction: invalid opcode

Solved

For the record, this was probably caused by lack of funds in testrpc. You should be running npm test which loads enough funds.

Yes that was exactly the case @frangio thanks for your reply


Internal: upgrade Prettier to 2.5.1

Checked, but no associated packages need upgrading as well

I'm tired of fighting stupid Prettier, abandoning this for now since it doesn't really matter