Is there a way to launch jobs within specific nodes? Or even to launch single core job on each node within a multi-node allocation?

To give an example: Lets say I have 2 nodes (node1 and node2) allocated with 128 cores each. At the end I want a job such that it runs on 1 core within node1 and 1 core within node2 specifically. Is this even possible within QCG-pilot?

Hi Satish,
There is currently no way to tell QCG-PilotJob to start a job on a specific node or core. If you can explain a bit more about why you want to do this, maybe we can find another way of solving it, or get a clear set of requirements worked out for a new feature?
There's some related discussion in https://github.com/psnc-qcg/QCG-PilotJob/issues/65. I solved it by skipping the QCG-PJ front-end and using the back-end directly, but this is a bit of a special case in that I use QCG-PJ as a library, and I don't need the workflow engine at all. So that may not work for you.

Hi Satish,
As Lourens mentioned this is currently not possible. Some workaround is to specify a task with resource requirements numCores=128, numNodes=1 with the model=default - the QCG-PilotJob should allocate entire node for your task, but run a single process. The downside is that no other task can use this node until the first one finishes.

Actually, reading the question again, could it be that you want to run an MPI job across two nodes, with one MPI process on each node? (And perhaps OpenMP or another threading solution within each process and node?)

Hi @pkopta and @LourensVeen ,
Thank you for both your replies. I will tell you what I am currently working on, but the feature I ask is applicable to many other instances, such as when I want 2 MPI jobs running on different nodes and do not want them to run on the same node even by chance.
@LourensVeen the scenario that you specify is possible to control within MPI itself I think either by using a rankfile or by specifying OpenMP threads via --map-by ppr:Tasks_Per_Node:node:pe=ncores .
What I am trying to do is work on an embarrassingly parallel work flow with many python jobs (lets call these jobs A1, A2, ...) which run along with a master python process that hosts a shared memory (lets call this job B) on each node. Each of these A1, A2 ... write a part on the shared memory hosted by B, therefore B runs until A1, A2 ... on that particular node are not completed. Since this is shared memory, I need job B to run on 1 cpu on each node.

Hi Satish,
Yes, I was thinking that you could do that with mpirun, that's why I asked :). QCG-PJ lets you specify additional mpirun options, so I thought that that could work. But it's not what you're doing, so maybe not the best solution.
When a QCG-PilotJob job is ready to run (i.e. you've submitted it and any dependencies have finished), then QCG-PJ will look at what resources it requires and what it has available, and try to find some free resources to run it on. If it finds a suitable set of free resources, the job is started, and those resources are marked as occupied. They will then be unavailable to other jobs until the present job finishes.
So, one thing that will definitely not work is to submit A and B as separate jobs to QCG-PJ, because they need to share resources. In that sense, your problem is similar to mine as explained in #65. This is a fundamental issue: QCG-PJ assumes that jobs form a Directed Acyclic Graph-based workflow, and that each job is basically a function that can be run independently of all other jobs. The only dependencies it supports are of the task-A-must-finish-before-task-B-can-start variety. We have tasks that communicate with each other while they are running, and this is something that QCG-PJ doesn't understand.
Would it be possible to create a script that starts one instance of B and as many instances of A as you have cores? Then you could ask QCG-PJ to run that script (or as many copies of it as you have nodes) using Piotr's settings above, and it should work. One of my users has done something similar in the past, launching a MUSCLE3 simulation on each node using QCG-PJ, and then using MUSCLE3 to coordinate as many instances of a submodel as there were cores available within the node. MUSCLE3 now has QCG-PJ integrated so this is no longer needed, but it did work.

@LourensVeen and @pkopta ,
I got this to work using SLURM script outside of QCG pilot. I am initiating a shared memory instance using a python job outside. The shared memory instance survives even after the end of the first python call. Then executing the QCG-pilot job with jobs filling this shared memory and again unlinking the shared memory with the python job again after all jobs from QCG are done.
#!/bin/bash
#SBATCH --job-name=qcgpilotjob-ex
#SBATCH --nodes=2
#SBATCH --time=00:10:00
#SBATCH --exclusive
#SBATCH --partition=thin

# NOTE: Change number of nodes at all places including the srun statements at the bottom if changed at the top.

module load 2020
module load Python/3.8.2-GCCcore-9.3.0
module load QCG-PilotJob/0.12.3-foss-2020a

# Change this path to where ever EnergyPlus is installed
export PATH=/home/$(whoami)/.local/easybuild/Centos8/2020/software/EnergyPlus/9.4.0-GCC-9.3.0:$PATH

# Running 1 task per node for initiating shared memory and finally unlinking it as well.
srun --ntasks-per-node=1 --nodes=2 python3 initiate_shared_memory.py
python3 qcg_pilot_energyplus.py
srun --ntasks-per-node=1 --nodes=2 python3 shared_memory_unlink.py


mwc-random < <IP_ADDRESS> needs an upper bound of primitive < 0.6

Can an upper bound of primitive < 0.6 be added retroactively to mwc-random versions < <IP_ADDRESS> to prevent problems like this:
Building mwc-random-<IP_ADDRESS>...
Preprocessing library mwc-random-<IP_ADDRESS>...
[1 of 3] Compiling System.Random.MWC ( System/Random/MWC.hs, dist/dist-sandbox-a6a612b9/build/System/Random/MWC.o )

System/Random/MWC.hs:440:3:
Configuring network-uri-<IP_ADDRESS>...
    Could not deduce (Control.Monad.Primitive.PrimBase m)
      arising from a use of ‘unsafePrimToIO’
    from the context (PrimMonad m)
      bound by the type signature for
                 withSystemRandom :: PrimMonad m =>
                                     (Gen (PrimState m) -> m a) -> IO a
      at System/Random/MWC.hs:431:21-69
Building nats-1...
    Possible fix:
      add (Control.Monad.Primitive.PrimBase m) to the context of
        the type signature for
          withSystemRandom :: PrimMonad m =>
                              (Gen (PrimState m) -> m a) -> IO a
    In the expression: unsafePrimToIO

I've added upper bound for al mwc-random releases starting from <IP_ADDRESS> I hope that's enough.
P.S. hackage needs feature for bulk update of package constraints

Thanks!


Merge from main to live for WAM updates

Merging to live branch with approval from @dcaro.  Suggestions in this PR can be found in https://github.com/MicrosoftDocs/azure-docs-cli/pull/4319 which will publish to live later today or tomorrow, May 22.


Update scodec-bits to 1.1.27

Updates org.scodec:scodec-bits from 1.1.20 to 1.1.27.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scodec", artifactId = "scodec-bits" } ]

labels: library-update, semver-patch

Superseded by #126.


Decouple StatementExecutor and SQLExecutor

For #3691.

Pull Request Test Coverage Report for Build 11019

131 of 152 (86.18%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 57.602%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/sharding/execute/sql/execute/SQLExecutor.java
0
1
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/execute/JDBCExecuteEngine.java
1
2
50.0%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/statement/ShardingPreparedStatement.java
15
18
83.33%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/executor/StatementExecutor.java
43
47
91.49%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/executor/PreparedStatementExecutor.java
36
42
85.71%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/statement/ShardingStatement.java
10
16
62.5%

Totals

Change from base Build 11015:
0.01%

Covered Lines:
11839

Relevant Lines:
20553

💛  - Coveralls


Closes other menus in the NavBar before opening one of them

Fixes #265

Hi @mikewheaton, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Looks awesome, please merge in.


skip serializing ArrayMetadata fields if None

This PR adds a serialize_if macro to the fields of ArrayMetadata struct. This should prevent crs or edges from being serialized if they are empty. Closes https://github.com/geoarrow/geoarrow-r/issues/34

I'm not sure if this will actually fix it because it'll still add the key in the arrow metadata with a value of {} @paleolimbot

@kylebarron could you point me to where the metadata gets serialized? I'm happy to give it a shot. I've gotten dirtier in serde than I care to admit and may have an idea or two (or none).

https://github.com/geoarrow/geoarrow-rs/blob/eb94df3d998801be3c55128b4535fc9f58652b66/src/array/point/array.rs#L127-L130
Probably best to add an is_empty(&self) -> bool method on the ArrayMetadata and then switch that to
if !self.metadata.is_empty() {
        metadata.insert(
            "ARROW:extension:metadata".to_string(),
            serde_json::to_string(self.metadata.as_ref()).unwrap(),
        );
}

(note there's one file for each array type)
Though I've also been debating how to DRY the implementation there with the one here on GeoDataType:
https://github.com/geoarrow/geoarrow-rs/blob/eb94df3d998801be3c55128b4535fc9f58652b66/src/datatypes.rs#L298-L307

Either way there should probably be tests? (Probably outside the scope of this PR if there weren't any to begin with)

Yes there should and no there are not currently 🙃 f

Should be fixed in https://github.com/geoarrow/geoarrow-rs/pull/498 with a couple tests


Migrate to NATS JetStream

Includes changes needed to run a new NATS JetStream image across amd64, s390x and arm64 platforms.

We may need to update the github build actions due to the new messaging URIs, because the build of the jetstream branch works fine locally.


Add Health Endpoint

Health endpoints are used for monitoring applications. Currently, there is no such endpoint in this application.
Create one!
See: https://github.com/eclipse/microprofile-health

done by 30cbda67b5c35717e117ba91ba2e3310a9475bb2


XCode 12 Archive Fails

Related issues #86 #119.
Since this is blocking us, we're going to open a CSM ticket in parallel to reporting here.
Reproduction

With fresh app, follow Iterable docs to setup library

Expected

Dev builds work, archive works

Actual

Dev build works, archive fails with Use of undeclared identifier 'IterableAPI'.

Troubleshooting steps taken

[x]  Have @import IterableSDK; at the top of AppDelegate.m
[x] Added blank swift bridging header
[x] Play with different Library Search Paths per this comment
[x] Set Always Embed Swift Standard Libraries to no

Env

App boilerplate created with ignite cli v6.5
XCode v12.4
React Native 0.64
Cocoapods 1.10.1

At Michael's (CSM) request, here is our AppDelegate.m.

We finally figured this out. There were two issues going on:

The original error posted here was due to my error, you can see in the listed AppDelegate.m that I had inadvertently nested @import IterableSDK; inside the flipper #ifdef statement. This was quickly identified by Iterable CSM for corrected.

We hit new errors exactly as listed in #86. For whatever reason, the setting that required config to edit was not in our application target, but in our project configuration. Once we realized the documentation was leading us to look at the incorrect place, we were finally able to archive the build. Attaching screenshot since it's XCode.

Hi jehartzog,
The troubleshooting steps are complete, but it not work for me.
I added "$(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME)" and "$(inherited)" to Library Search Paths, but it didn’t work. (It’s worth noting that it was originally empty here)

@1280103995 I don't have much for you. After removing the $(TOOLCHAIN_DIR)/usr/lib/swift-5.0/$(PLATFORM_NAME) entry, we actually had to add it back when we added the iterable message extension to enable rich iOS pushes. Already spent way too much time trying to configure swift-5.0 vs not, and still not sure exactly where we ended up.

I read the first point carefully and after adjusting the import position, it worked. Cheers!


Wrap form in FormContext

What is this?
At its base, this PR separates the internal state of Form.jsx into its own component and exposes it as a context to any of its children or grandchildren.
What are the benefits?

Performance: the properties doesn't need to be passed to the EditBlocks anymore, so each edit block won't re-render when other blocks are changed.
It enables intra-form communication (via the form global state) for edit widgets. Blocks are being passed properties={formData} but widgets don't have that
It enables form state mutation from any of the form components

What can we do with it?
I have multiple uses and it enables some advanced scenarios. For example:

Inter-widgets communication. I have a widget where I can set "ElasticSearch Hostname" and the next widget is a dropdown with a list with the indexes on that ES Server. That means that the second widget needs to be able to read the values from the first widget (so that it knows which server to query for index values). I've used a similar idea in the volto-searchkit prototype.
"Batch" editing of blocks. Right now the on*Block  methods don't use promises, so it's not easily possible to ensure order of execution or state integrity, so I'm forced to wrap mutation calls in setTimeout, which seems to ensure a sort of "synchronicity" in multiple setState calls. See this as a counter-example of the workarounds that are needed.

Is this a breaking change?
Not really. I haven't removed yet the properties being passed to EditBlock, but I'd like to do that. Removing it would improve the performance of the edit form, as blocks wouldn't have to re-render when one of them is changed (unless they specifically watch the context formData). I've changed all the Volto blocks that needed any change, so that we are prepared to remove that passed properties parameter. I don't know if there's any other blocks "out there" that depend on the "properties" passed to them.
All of this is quite cleanly implemented and the advanced behavior is "opt-in". Child components need to use useFormStateContext() or static contextType = FormStateContext to get access to the ancestor form's internal state/setState.
My intention is to further build, as next PRs::

promisify the form state change
wrap the other form implementation (ModalForm, InlineForm) in the FormStateContext provider
Explain all this in documentation

As a teaser, what this PR enables: proper transformation of copy/paste to Volto blocks for rich text content (via volto-slate).


Add wait logic before initiating deployment to Python applications

Due to short/lack of sufficient wait time in the client, the necessary app settings are updated by VSCode before deployment but do not get enough time to propagate to all instances of the application.

VS Code updates deployment related app settings before deployment, but a lot of time the app settings are not propagated before the deployment leading to an inconsistent behavior.
For example: For python apps on Linux, Vs Code removes WEBSITE_RUN_FROM_PACKAGE app setting before deployment. If this setting is not propagated before deployment, then post deployment function app will show "no triggers found" when the setting is propagated.
Solution:

Add a loop after updating app settings to make sure the settings are propagated like done by DevOps and GitHub action: https://github.com/Azure/functions-action/blob/d2580abdb32d42249f37bd6ec7a6fc7acd82bc30/src/publishers/zipDeploy.ts#L144-L179
Add a wait time for at least 1 minute (might have to increase to 2 minutes).


out of memory

LDAP is too big，so when i dump it。 it's out of memory
[] Connecting to host...
[] Binding to host
[+] Bind OK
[*] Starting domain dump
MemoryError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\xxxxxx\AppData\Local\Programs\Python\Python37-32\lib\site-packages\ldap3\utils\asn1.py", line 121, in decode_sequence
ber_len, ber_value_offset = compute_ber_size(get_bytes(message[start: start + 10]))
MemoryError
During handling of the above exception, another exception occurred:
MemoryError
During handling of the above exception, another exception occurred:
MemoryError
During handling of the above exception, another exception occurred:
MemoryError
During handling of the above exception, another exception occurred:
MemoryError
During handling of the above exception, another exception occurred:
MemoryError

This is a know issue, see #10


Changed elm-package.json to be compatible with elm 0.15. Bumped version to 1.1.0.

The code itself is already compatible, but elm-package.json needed elm-lang/core upgraded to 2.0 and an extra line for elm-version 0.15.
I thought this warranted bumping the version to 1.1.0. Let me know what you think.

Thanks so much for doing this.

No problem. Thanks for writing such a useful package!

Just published to the elm package listing.
As a heads up, I set the version back to 1.0.3, because the elm package tool complained that I shouldn't bump the minor version when there are no API changes. In hindsight, I agree.
Thanks, elm package.

OK, that makes sense. I wasn't sure.


Deploy powerboosting on develop( not staging) ENV

We dont want to merge #600 for now, so we deploy it in develop ENV then frontend can use that until we get ready to merge it on staging

@MoeNick I and @mohammadranjbarz decided to deploy Power Boosting feature on develop env impact-graph and don't make the staging env dirty.
The server will be accessible at https://dev.serve.giveth.io/

@MohammadPCh
we deployed power boosting feature on develop ENV (https://dev.serve.giveth.io)
Now you can use below queries/mutaions

Set power boosting for single project
https://github.com/Giveth/impact-graph/blob/28725b924353e588eb5217ef8df1732f93223259/test/graphqlQueries.ts#L1365-L1379

Set power boosting for multiple projects
https://github.com/Giveth/impact-graph/blob/28725b924353e588eb5217ef8df1732f93223259/test/graphqlQueries.ts#L1380-L1394

Get list of power boosting of users and projects

https://github.com/Giveth/impact-graph/blob/28725b924353e588eb5217ef8df1732f93223259/test/graphqlQueries.ts#L1395-L1423
And for see how you can call them you can see our test cases to get more insights:
https://github.com/Giveth/impact-graph/blob/f_16_power_boosting/src/resolvers/powerBoostingResolver.test.ts


Setctty set but Ctty not valid in child

Setctty set but Ctty not valid in child

There is nothing I can do with so little information.
I would suggest StackOverflow.

Sorry, I just made a mistake.


Feature: Implement X so users can do Y (REPLACE THIS)

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
In the Equalizer section with the Sliders, there is an option in Advanced, that you can use some Color shades to control the EQ.  The sit on top of whatever visualization is playing and makes it difficult to see the viziualization, once you are done manipulating them.  It would be nice, if there was a way to turn them on and off.  See example of what I mean below, its outlined by a horrible red line of my own creation ;)

User flow & interface:
A very small icon about the size, of the Eye icon used to minimize the section, in the same shade and wavy pattern would help, if you click it once, it goes grey and turns it off, if clicked again, it turns lightly colored and turns it on again.

 If there is no room, in the front interface, then a checkup box when you click the EQ Gear Menu would also work.

Thanks!

This has now been implemented in the latest UI update in the Expert EQ settings, we discussed it on Discord :) Please next time the Title of the issue need to be replaced from the Template. Closing this issue.


Problem with train my datasets.

Hi Yao Yao.
Thank you, MVSNet code.
But I have problem with my dataset.
Your Train.py Require depth_map, cam.txt.
So, Doesn't Above file created in post-processing ?
How, Why this file getting to Train.py ?
How use my dataset in your MVSNet train, When I have only jpg file.

If you want to train on your own data then you need to prepare [reference_image, source_images, reference_camera, source_cameras, reference_gt_depthmap].
To integrate into the current pipeline, I think the easiest way is to generate a training sample list (like gen_dtu_resized_path() in preprocess script) on your own data, and change the image input size and depth sample number correspondingly.

Thanks !


Documentation regarding template should be improved.

The template that is shown does not work if simply copied verbatim.
Firstly, you should mention that bootstrap.css should be loaded, though that should be obvious.
Secondlt, please mention that font awesome is needed for the icons on the date picker to appear correctly.  I found that it does not show the clock icon correctly on the date and time picker when you use the latest version 5 of font awesome from the cdn.  It's best to stick to version 4.7, which is what is used in the tempus dominus demo pages. Maybe that fiel should be part of form.media.
And finally, unless you put the form inside a container, and a column (or more likely a container, row and column),  tempus-dominus will pause on an exception: "datetimepicker component should be placed within a relative positioned container".
I have incorporated all of the above in the attached file.
template.txt

Thank you again, @ianastewart - this has been updated with some code comments.
It'll go out with today's release.


Installing UE Plugin Panics

Describe the bug
When installing Apparatus ECS plugin on UE4, I get this immediately after the download starts:
thread 'Download Pool' panicked at 'called `Result::unwrap()` on an `Err` value: Message { msg: "u128 is not supported", location: None }', src/ui/widgets/download_manager/mod.rs:536:64
To Reproduce
Steps to reproduce the behavior:

Install Apparatus plugin

Expected behavior
Installs plugin properly
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Linux 5.10.84-1-MANJARO #1 SMP PREEMPT Wed Dec 8 09:50:30 UTC 2021 x86_64 GNU/Linux
Additional context
This is the output with full backtrace:
$ RUST_BACKTRACE=full /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=epic_asset_manager --file-forwarding io.github.achetagames.epic_asset_manager
thread 'Download Pool' panicked at 'called `Result::unwrap()` on an `Err` value: Message { msg: "u128 is not supported", location: None }', src/ui/widgets/download_manager/mod.rs:536:64
stack backtrace:
   0:     0x55e57feb517c - <unknown>
   1:     0x55e57fedd21c - <unknown>
   2:     0x55e57feadfd5 - <unknown>
   3:     0x55e57feb7160 - <unknown>
   4:     0x55e57feb6d17 - <unknown>
   5:     0x55e57feb7814 - <unknown>
   6:     0x55e57feb72f0 - <unknown>
   7:     0x55e57feb5644 - <unknown>
   8:     0x55e57feb7259 - <unknown>
   9:     0x55e57f5f8831 - <unknown>
  10:     0x55e57f5f8923 - <unknown>
  11:     0x55e57f6ad603 - <unknown>
  12:     0x55e57f968f31 - <unknown>
  13:     0x55e57f96acff - <unknown>
  14:     0x55e57febe7e3 - <unknown>
  15:     0x7f586424e3ba - <unknown>
  16:     0x7f5864027b03 - clone
  17:                0x0 - <unknown>

Published a new release on flathub, you should get the update soon, this does not exactly fix the issue, but the json manifest is not crucial for anything right now so it can be skipped in case of an issue like this. Though it is strange it happens, I can get any plugin to download just fine. Sadly I do not have access to that particular asset as it is kind of costly, but this should be a general fix for the issue you reported.

Thanks for making a release so quickly, but it seems to still panic, but in a different place now:
thread 'main' panicked at 'failed to upgrade `obj` (if you don't want to panic, use @default-return)', src/ui/widgets/download_manager/download_item.rs:241:13
stack backtrace:
   0:     0x564206b1a25c - <unknown>
   1:     0x564206b41e7c - <unknown>
   2:     0x564206b126c5 - <unknown>
   3:     0x564206b1c2a0 - <unknown>
   4:     0x564206b1be55 - <unknown>
   5:     0x564206b1c954 - <unknown>
   6:     0x56420626fe55 - <unknown>
   7:     0x56420626d746 - <unknown>
   8:     0x56420623b0c1 - <unknown>
   9:     0x564206363c9f - <unknown>
  10:     0x7f1e287443a8 - <unknown>
  11:     0x7f1e287436d1 - g_main_context_dispatch
  12:     0x7f1e28743bb8 - <unknown>
  13:     0x7f1e28743c83 - g_main_context_iteration
  14:     0x7f1e28976c45 - g_application_run
  15:     0x5642063515ee - <unknown>
  16:     0x5642063b6f02 - <unknown>
  17:     0x56420626f1c3 - <unknown>
  18:     0x5642062a7249 - <unknown>
  19:     0x564206b19f3b - <unknown>
  20:     0x5642063b7302 - <unknown>
  21:     0x7f1e2802eb90 - __libc_start_main
  22:     0x564206261e5e - <unknown>
  23:                0x0 - <unknown>

There is something funny going on on your side. Can you download other assets/plugins? I can "fix" this one as well but it would not make much sense as it would stop showing any download progress if this is allowed to gracefully fail(though it should probably do so anyway as hard GUI crash is not desirable).


Handle Animated layout (dynamic, hided by Keyboard)

Hello there,
the library works well for basic usecase. However, here, I got a FlatList where row are basically containing (vertically aligned) a  and a . And I added at the bottom of these two an Animated View which appear when the content filled in the TextInput is not what I'm expecting. Like an error layout.

Problem is that KeyboardAwareScrollView is not expecting that I guess. And the Animated View is hide by the keyboard, because the keyboard is just below the <TextInput/>
How can I handle the case that when the animated error layout show up, to add an extra padding to not hide it ?

Here is my setup :

<KeyboardAwareScrollView>
          <FlatList
                   getItemLayout={(data, index) => ({ length: 90, index })}
                   contentContainerStyle={{ flexShrink: 2 }}
                   keyboardShouldPersistTaps='always'
                   bounces={false}
                   data={_data}
                   renderItem={({ item }) =>
                   <View style{{ column }}>
                           <SomeContentWithTextInputInside />
                           {shouldDisplay ? <AnAnimatedView style={{zIndex:9999}}/> : null}
                   </View>
                   }
             />
</KeyboardAwareScrollView>

Thanks for the help.

Hello, I succeed to handle it quite nicely (well the workaround works well I mean...).
I just wrapped my conditional rendering Animated View as follow :
<View style={{ height: this.state.extraHeight ? 60 : 0 }}>
        <AnAnimatedView style={{zIndex:9999}}/>
</View>

And I just added a check which, when my condition is verified, setState({extraHeight : true}) with a  setTimeout(() to set it back to false 3 seconds later.
And in the <KeyboardAwareScrollView> don't forget to add a onContentSizeChange={() => this.scroll.scrollToEnd()} using the innerRef ref, so that it scrolled to the end by adding the temporary extra height then go back to normal.


Browser Fingerprinting Document

What feedback can we give to Nick Doty around the fingerprinting guide he is putting together int he privacy interest group? https://w3c.github.io/fingerprinting-guidance/

Discussed in NYC; @mnot to start.

Discussed in SF; scheduled for 5-20

Discussed 5-20 we may run a special session in Berlin on this.

Discussed in Boston.

@mnot is happy with the revised version. @slightlyoff needs to feed back as well.

I have some concerns:

the recent TAG Finding on Unsactioned Tracking appears to be more actionable regarding how we might guide spec/feature designers in specific areas like storage mechanisms
Best Practice #1 in this document seems to guide in an ambiguous way. What's "unnecessary"? Who decides?
Best Practice #3 and #6 seems like the strongest, most actionable advice.
Reducing available entropy and storage (BP's 4, 5, 7) seem as though they're either deeply confused or are unsupportable as general principles. We discussed this in the Unsanctioned Tracking finding and these points appear to be incompatible with that finding.
Perhaps BP #8 might have some relationship to @mikewest's new work on Clear Site Data?: https://w3c.github.io/webappsec/specs/clear-site-data/

IG note published in November:
https://www.w3.org/TR/2015/NOTE-fingerprinting-guidance-20151124/
This feedback doesn't appear to have been addressed.

/cc @npdoty (esp. regarding previous comment)

Hey all (/me waves at @npdoty):
It looks like the Draft NOTE doesn't include changes based on the comments we left in Sept. Eager to have a conversation about those and come to some consensus.
Perhaps we can schedule some time on an upcoming call to discuss?
/cc @torgo and @plinss re: scheduling

@torgo to contact @npdoty to schedule a call

Have done & will schedule for a future call.

Thanks for the note. I tried to do a pass to address TAG feedback earlier, but I think I was responding to a different list than what is described by @slightlyoff above. (Also, I may have been guilty of focusing on addressing the issues I best knew how to address.) Happy to talk more, and thanks @torgo for scheduling.

Hi @npdoty – have put this on our agenda for next week (2-feb).

https://pad.w3ctag.org/p/03-02-2016-minutes.md

https://github.com/w3c/fingerprinting-guidance/issues/5 not yet resolved... @npdoty can you update on the status?

Edits made this month attempt to address the naming issue (w3c/fingerprinting-guidance#5) and add several examples, which I noted during our February call might address concerns or at least elucidate where we disagree. @slightlyoff, you might look at those now and see if that helps, or at least, I'm at the point where I'll need more info from you to understand your concerns. (The minutes from the February call might also explain my position and what I don't understand.)
On the challenge of explaining how specifications should handle the trade-off, would it help to combine Best Practices 1 and 2 and note that, when trying to balance functionality with additional fingerprinting surface, a key consideration is especially to avoid increases in the passive surface?

We are reviewing today in the TAG f2f.

Hey Nick,
Thanks for bringing this up.
We're happy to see the name change. Thanks for doing that!
Regarding the definitions of fingerprinting types ("Passive", "Active", and "Cookie-like"): the name "Cookie-like" is a bit tough. The second sentence in "Passive" seems to imply that cookie storage is handled by "Passive". Is "Cookie-like" a superset of "Passive"? If not, should "Cookie-like" be called "Supercookie"?
At a higher level, I'm struggling with how to consider using this document with engineers on my team who want to do the right thing. I.e., if someone came to me and asked me to review a spec, I'm not sure that handing them this document would clarify anything for them about how to design their feature.
This might be because the document lacks examples? For instance, in "Best Practice 1" it'd be great to understand how a specific design(s) might be changed to be better. What's the razor for "unnecessary"? What sort of changes shouldn't be undertaken because they would be too costly or defeat a feature?
Consider the hypothetical conversation with an engineer who wants review:

Their API includes some method which stores some data in a persistent way
In a review, I'd ask them something along the lines of "so, what control does the user have over setting and clearing this?". Normally that implies integration with cache/data clearing UI. If something is settable but not clearable (by design), I'd flag it for the privacy team to review (this is your "Cookie-like" bucket). That higher level of invasiveness is something we don't want in the platform and the TAG finding on unsanctioned tracking is now the "Big Stick" that I (and others) can use to prevent such features from being added.
Assuming a feature can be reworked to put things under positive user control, I'm not sure where I'd apply Best Practices 7 and 8 in the review. Lets say the question is "access to local fonts". This is a capability that would be behind a permission prompt. What's the actionable guidance from this document for a designer of such a feature? Would it be to not add it? Language to possibly include in the prompt? Guidance on ambient usage indicators to let users know when these sorts of features are being accessed? Discussion of how to enable/disable them from iframes and sub-documents (vs. top-level documents)? Re-designing the feature to consult a service with a list of known fonts? Some way to remove uncommon fonts (again, perhaps via bloom filter from a service) to reduce the capacity for fingerprinting? Or is the permission prompt "enough"?

Cataloging those sorts of mitigations and the decision tree (with examples) might be a good way to help make this document more actionable.
In general the TAG is supportive of this work and we'd like to see a version of this valuable effort move forward. Thanks again for persisting through our sporadic feedback.
Regards

One other thought about the active / passive / cookie-like split in section 3.  It seems that perhaps being cookie-like is orthogonal to active vs. passive (e.g., cookies are cookie-like and passive, while indexed db is cookie-like and active).  If that's the intent, maybe it should be clearer that cookie-like isn't mutually exclusive with active and passive.
I also wonder two other things:  whether cookie-like features actually should be considered part of "fingerprinting" (as stated in section 1), and whether supercookies that aren't clearable should be part of the cookie-like category or should instead just be considered bugs (in spec or implementation) of a more severe category.

Discussed at the TAG f2f in Boston. https://pad.w3ctag.org/p/2017-02-08-minutes.md
@wseltzer said: This is sitting with PiNG. Nick is deep in his PhD, so this is unlikely to have changed since your last review. I will make sure PiNG pings TAG when it's ready for another review.


'li' tags are treated as no content tags when empty

'li' tags are treated as tags with no content, such as 'img', 'br' etc.
XHTML standard defines a list of tags with no content, described here: https://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116 under "A.2. Elements that can never have content".
Correct examples:
Nokogiri::HTML('

').to_s

in the output, the
 tag remains:

Nokogiri::HTML('
').to_s

in the output, the
 tag converts into

, as 'p' tags should have content
Nokogiri::HTML('').to_s

int the output, the  remains single img tag, as img tags have no content
Problematic examples:
Nokogiri::HTML('

').to_s

in the output, the

 converts into
, which should not happen
Nokogiri::HTML('
').to_s

in the output, the
 remains a single no-content tag, although 'li' should have content.
Reproduced on the last version:
# Nokogiri (1.10.2)
    ---
    warnings: []
    nokogiri: 1.10.2
    ruby:
      version: 2.5.0
      platform: x86_64-darwin16
      description: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin16]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/Users/username/.rvm/gems/ruby-2.5.0/gems/nokogiri-1.10.2/ports/x86_64-apple-darwin16.7.0/libxml2/2.9.9"
      libxslt_path: "/Users/username/.rvm/gems/ruby-2.5.0/gems/nokogiri-1.10.2/ports/x86_64-apple-darwin16.7.0/libxslt/1.1.33"
      libxml2_patches:
      - 0001-Revert-Do-not-URI-escape-in-server-side-includes.patch
      - 0002-Remove-script-macro-support.patch
      - 0003-Update-entities-to-remove-handling-of-ssi.patch
      libxslt_patches: []
      compiled: 2.9.9
      loaded: 2.9.9

Hi! Thanks for asking these questions about the parser's behavior. Unfortunately, Nokogiri inherits parsing and serialization behavior from the underlying libraries (in your case this is libxml v2.9.9) and as a result there's not much that Nokogiri can easily do to change that behavior.
I will point out, though, that XHTML is a different spec than HTML 4.0 and the HTML 4.0 spec says that the LI end tag may be omitted:
https://www.w3.org/TR/1998/REC-html40-19980424/struct/lists.html#edef-LI
which leads me to conclude (in the absence of a deeper investigation) that libxml2's behavior is not incorrect here.
I hope this helps?

Thank you very much for your answer! It did clarified the situation for me.


Support for events

Add support for events

Re-opening as this was not closed in #8 since that one closed #3 instead.


CMS_DIR Constant when no CMS ;)

When adding Moderno to a framework only site/app SiteConfigEditFormExtension results in:
[Notice] Use of undefined constant CMS_DIR - assumed 'CMS_DIR'
        if (defined('CMS_DIR')) {
            Requirements::javascript(CMS_DIR . '/javascript/CMSMain.EditForm.js');
        }

Fixes this.

Dang it all... will fix.  :P

No problem,  Thank you for moderno btw and will you be bootstrapping it for 4.0.0???

Might be... I need to find some time to play around with the SS4 alpha first.


floating label rtl fix

Add RTL support to Floating labels
Short description of what this resolves:
RTL support for floating labels
Changes proposed in this pull request:

added a scss code which set transform-origin to right for RTL direction on html.

Ionic Version: 2.x / 3.x

Thank you for creating a pull request for RTL, its great to see more people helping on that.
As this is your first contribution, please read the "creating a pull request" guide, and commit message style under it.
This is a great change, but it is missing all-platforms support.
There is also .label-ios[floating] and .label-wp[floating] that need to be addressed.

@manucorporat @brandyscarney This looks done. Can you merge?

I'm creating another pr which contains this too.
So I'm closing this.

In theory, PRs should be "Small, independent, complete contributions" such that it is preferable to have 2 different PRs rather than 1 PR with 2 features.
If your new PR fixes more labels, than it should be 1 PR, otherwise 2.
If you are interested in learning more -

Read: http://dl.acm.org/citation.cfm?id=2594458
Or view it presented: https://www.youtube.com/watch?v=48TjLDUf-B4

@AmitMY So I should open this and make some new other PR for my other changes? sorry I'm new to this.

@sijav No problem :)
Yes, imo, and the theory suggest, that is better if you open it and create a new PR for any other feature.
I really recommend that video, it explains a lot about open source PRs and the review process

Yes, Thanks a lot,

This looks great! Thank you @sijav for the PR, and @AmitMY for doing a great job reviewing and providing feedback. 🙂 :tada:


[BUG] Inconsistent focus management

I am loving lity so far in the first few days of using it. The focus on accessibility is what led me to you! I believe this is a bug and not expected behavior. Happy to be wrong :)
To Reproduce

Open any lightbox instance
Hit ESC

- OR -

Open any lightbox instance
Click in black "background" area to close lightbox

Current Behavior
Focus is returned to document root.
Example: After closing lightbox, hitting TAB once goes to the first-in-source "Skip to Content" link.
Expected Behavior
Focus is returned to last-focused element (usually the lightbox-triggering link element).
Using the "X" close button via keyboard and mouse exhibits this behavior already, leading me to expect the same result from all methods of closing the lightbox.
I'm not familiar enough with the library yet to be able to suggest a fix.

Hi,
thanks for the report. I've released a fix in v2.1.1.

Awesome. I should be able to update and test fixes today or tomorrow. Will report back if anything is still of. Thanks for such a quick response!

Quick tests look good!


Truncated MIT license text

The word "permission" is missing
See https://github.com/Succo/wkttoorb/pull/1 for another example.
There could be more repos of yours subject to the same issue?

See also https://github.com/Succo/countrymoji/blob/master/License.txt

At some time in the future, this is going to prevent the doc from being visible on pkg.go.dev.

At some time in the future, this is going to prevent the doc from being visible on pkg.go.dev.

Patched thanks

The word "permission" is still missing at the current master: https://github.com/Succo/emoji/blob/f96f5c4523387c5758d05f5bc2f954ecea8d2a03/License.txt.

Indeed, but I belive it is now corrected https://github.com/Succo/emoji/blob/master/License.txt


⚠ GitLab Server has degraded performance

In 940647d, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 11502 ms

Resolved: GitLab Server performance has improved in 609b9d2.


FatalErrorException

runnning:
php artisan generate:migration create_users_table
i got:
[Symfony\Component\Debug\Exception\FatalErrorException]
Method Pingpong\Generators\Stub::__toString() must not throw an exception
but running php artisan make:migration create_users_table
ok

I've fixed this issue via this commit https://github.com/pingpong-labs/sky/commit/5705abf37c42462b636ec86ab1c7b82c204c1161. And will pushed to this repository soon. Thanks!

thank you
can you tell me how you debug,
I can't finf throw problem with regular exception...
Il 08/07/2015 06:40, Gravitano ha scritto:

I've fixed this issue via this commit pingpong-labs/sky@5705abf
https://github.com/pingpong-labs/sky/commit/5705abf37c42462b636ec86ab1c7b82c204c1161.
And will pushed to this repository soon. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/pingpong-labs/generators/issues/3#issuecomment-119428961.

Just basic debugging. If using artisan, you can add -v option to see the error trace is something went wrong.


Enable logging of the Elliptic Curve used to communicate with the client

This PR adds the ability of logging the SSL Elliptic Curve used by Trafficserver to communicate with the client when using an ECDHE cipher.

I'm not too sure who requested 8.0.x backport and whether we should backport this to 8.0.x, but if we do, we need #5992 as well.

My vote would be to not back port this to 8.0.x. It's a new feature, and that's not supposed to be a candidate for a patch release.


feat: use design theme as default theme

Types

[x] 🎉 New Features

Background or solution
ChangeLog
use design theme as default theme

promptCache.ts 文件中的调用:if (!isCacheEnable()) {


SqlServer raise WKB is not valid format.

This issue was imported from CodePlex
mese79 wrote 2012-06-11 at 02:05
Hi
When i tried to create a new sqlserver DbGeometry from multipolygon IFeature WKB, i'v got error like 'WKB is not valid format', but WKT works with no error for the same IFeature.

//feature type is polygon and geometry type is multipolygon.
var geom = DbGeometry.FromBinary(ifeature.BasicGeometry.toBinary(), srid); //raises error
var geom = DbGeometry.FromText(ifeature.BasicGeometry.toString(), srid); //works
mudnug wrote 2012-06-12 at 20:23
Would you like to provide the WKT for this feature?
jocull wrote 2015-04-15 at 17:25
This is happening to me as well. Here's the WKT (UTM)

@mogikanin Do you know how to test this? Seems we'd need a sqlserver DBGeometry object to test if the results can be read.

Should be resolved as it seems to be the same issue as #475.


Orchestrator/LUIS: Disambiguation trigger should behave similarly

Related to issue Component#1015.
This ticket tracks the investigation and Composer related changes to have the OnChooseIntent trigger behave similarly for Orchestrator and LUIS.
There were a couple of proposed solutions in the above issue, we will investigate and see which is feasible for R14.

Status: design

Closing as not planned as LUIS is on the deprecation path


Where should I update dataset setting and path

How should I update dataset setting and path? Which configuration file should I edit?
dataset_type = "NuScenesDataset"
n_sweeps = 10
data_root = "/data/Datasets/nuScenes"
db_info_path="/data/Datasets/nuScenes/dbinfos_train.pkl"
train_anno = "/data/Datasets/nuScenes/infos_train_10sweeps_withvelo.pkl"
val_anno = "/data/Datasets/nuScenes/infos_val_10sweeps_withvelo.pkl"
Thank you very much!

https://github.com/poodarchu/Det3D/blob/master/det3d/datasets/dataset_factory.py


Sign container images

Implement container image signing using cosign in build-images workflows. Leveraging image signing gives users confidence that the container images they got from the container registry were the trusted code that the maintainer built and published.
Fixes: #19282
Signed-off-by: Sandipan Panda<EMAIL_ADDRESS>
Sign container images with cosign

CI run to test signing container image using cosign in https://github.com/cilium/cilium/actions/runs/3228306057/jobs/5284228087

The purpose of the other two PRs is to test container image signing and SBOM generation by implementing the features first in build-images-ci.yaml and then opening a PR from a branch inside the Cilium repository to run the GH workflow with the changes. After the testing is successful, these features can be implemented in the build-images workflows as per the discussions with my mentors. As there are two separate issues for container image signing and SBOM generation, I thought it might be better to make separate PRs to implement those features. Adding everything into a single PR would require a lot of changes while opening a PR from a branch inside the Cilium repository to run the GH workflow with the changes.

cc @qmonnet. While re-requesting review from @nbusseneau, review request from @qmonnet was automatically removed.

Example of a failure after merge: https://github.com/cilium/cilium/actions/runs/3298535923/jobs/5440783983
Not sure what changed between previous tests and the merge, we'll have to double check.

Example of a failure after merge: https://github.com/cilium/cilium/actions/runs/3298535923/jobs/5440783983
Not sure what changed between previous tests and the merge, we'll have to double check.

@nbusseneau thanks to @aanm for catching it, we have to add if: ${{ github.event_name != 'pull_request_target' }} for # master branch pushes and if: ${{ github.event_name == 'pull_request_target' }}for # PR updates in the - name: Sign CI Images steps in build-images-ci.yaml

Additionally, we have to add if: ${{ github.event_name != 'pull_request_target' }} for # master branch pushes and if: ${{ github.event_name == 'pull_request_target' }}for # PR updates in the - name: Sign CI Images steps in build-images-ci.yaml

Update: Implemented the feature to sign Cilium images using cosign with the required changes addressed.


Reverted to old downloads method. Removed unnecessary code. fixed log…

…ic to jump to agents menu after exit command

Fix for #899


feature_contact-form

changed contact from .md to .njk and added from to page as submissions weren't pushing to netlify

👷 Deploy Preview for darling-cascaron-57e64e processing.

Name
Link

🔨 Latest commit
70f2b9d045af6bc68ee0ce6b9d726ec7d240c53a

🔍 Latest deploy log
https://app.netlify.com/sites/darling-cascaron-57e64e/deploys/6656486fd98b390008ee4bb4


Limit the size and age of the ZIP-401 rejected transaction ID list

Motivation
ZIP-401 limits the number of transactions in the rejected list, and the age of the entries in that list.
This Ticket Depends On
RecentlyEvicted:

[ ] #2780

[x] #2778
[x] #2779

[x] #2440

Specification
The checked items are covered by other tickets.

EvictTransaction MUST do the following:

[x] Select a random transaction to evict, with probability in direct proportion to eviction weight.
[x] Add the txid and the current time to RecentlyEvicted,

[ ] dropping the oldest entry in RecentlyEvicted if necessary to keep it to at most eviction_memory_entries entries.

[x] Remove [the randomly selected transaction] from the mempool.

[ ] Nodes SHOULD remove transactions from RecentlyEvicted that were evicted more than mempoolevictionmemoryminutes minutes ago. This MAY be done periodically, and/or just before RecentlyEvicted is accessed when receiving a transaction.

https://zips.z.cash/zip-0401#specification
Design
The ZIP-401 reject list must be implemented as a new list in MempoolStorage. This avoids bugs that confuse different rejection rules.
Since this time is only used by the local node, it should be monotonic (strictly increasing):
https://docs.rs/tokio/1.11.0/tokio/time/struct.Instant.html
If we use an IndexMap<transaction::Hash, Instant>, we can efficiently evict transaction IDs by using IndexMap::pop, until we reach a transaction that's below the eviction limit:
https://docs.rs/indexmap/1.7.0/indexmap/map/struct.IndexMap.html#order

Are we already doing this? It was in the list of mempool tasks but did not have an issue number assigned

This is part of #2744:

Rejected set is recommended capped at 40K, we should check if everything we currently put in the rejected set maps to what ZIP-401 considers part of that 40K.

This is part of #2744:

Rejected set is recommended capped at 40K, we should check if everything we currently put in the rejected set maps to what ZIP-401 considers part of that 40K.

#2744 is a very large ticket, so I'm splitting it up into sub-tickets.

Hey team! Please add your planning poker estimate with ZenHub @conradoplg @dconnolly @jvff @oxarbitrage @upbqdn

If we use an IndexMap<transaction::Hash, Instant>, we can efficiently evict transaction IDs by using IndexMap::pop, until we reach a transaction that's below the eviction limit: https://docs.rs/indexmap/1.7.0/indexmap/map/struct.IndexMap.html#order

I think that doesn't work because pop removes the last inserted item (newest) and we need to remove starting from the first (oldest). We can remove the first item with shift_remove but it's O(n).
I've searched a bit and couldn't find any library that would solve that, so I think the solution is to have another list (VecDeque) with (Hash, Instant) tuples. What do you think @teor2345 ?

Yeah, I think you're right.
Here's one way we could implement this

ordered_entries: VecDeque<(transaction::Hash, Instant)> - reject list entries in insertion order, allows duplicate Hashes
'unique_entries: HashMap<transaction::Hash, Instant>` - unique reject list entries and their most recent insertion times

Here's how we could implement the operations:
Add or update the age of an entry - O(1):
- push onto the back of ordered_entries
- insert or replace in unique_entries
Remove the oldest entries when they have expired - O(expired):

search from the front of ordered_entries for the first time that hasn't expired
drain the expired entries from ordered_entries

also remove the ID from unique_entries if the times are equal

Remove the oldest entry when the list is too long - O(1):

remove the excess entry from the front of ordered_entries
remove the ID from unique_entries if the times are equal


Make conversion nil safe in case of empty annotations

Description

We didn't handle the Annotations map safely during conversion, which can cause a panic.
How can this be tested?

Deploy a v1beta2 DynaKube, with no-annotation and metadataEnrichment.Enabled = true. (or any new field that would be converted from an annotation)

Codecov Report
Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 58.77%. Comparing base (290c4da) to head (d94db37).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3254      +/-   ##
==========================================
- Coverage   58.78%   58.77%   -0.02%
==========================================
  Files         325      325
  Lines       18149    18153       +4
==========================================
  Hits        10669    10669
- Misses       6283     6285       +2
- Partials     1197     1199       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Updating freshness

@mimig1

@ryancrawcour You can close this PR. You updated the date last week (10/20, see live article) and closed the related TFS item last week. If you were getting pings, it was probably because the PR was only accepted yesterday.


Selecting score elements is off

To select a score element I have to find an invisible location at the bottom right of what I want to select.

The above is only for the first note, in fact. Further notes cannot be selected at all.


[Release] Publish all 2.0.0 images to docker hub

Description
No response
Use case
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

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


Switch default for useDefineForClassFields in ESNext

Since this targets 3.7.1, I'm going to close this bug. When class fields reaches stage 4, I'll do the final two steps.

Originally posted by @sandersn in https://github.com/microsoft/TypeScript/issues/27644#issuecomment-542299230

useDefineForClassFields should be switched to true when targeting ESNext.

Class fields aren't stage 4 yet. Moving to 3.9.

This isn't mentioned in the RC notes for 3.9- has it been bumped to a later version?

Don't think this was done in 3.9 - @sandersn?

No, class fields still aren't at stage 4. For 4.0, I did make https://github.com/microsoft/TypeScript/pull/37894, which makes suspicious accessor/property override patterns an error everywhere. Together with the included codefix, that finishes off all the planned work for #27644 except this issue.

FYI, we plan to switch the equivalent Babel option to true by default in Babel 8.

FYI, we plan to switch the equivalent Babel option to true by default in Babel 8.

See also https://github.com/microsoft/TypeScript/issues/41788, which will be fixed by this.

See also https://github.com/microsoft/TypeScript/issues/41788, which will be fixed by this.

Hey everyone, sorry, I know I shouldn't ask questions on issues (where should I ask them?) but I was wondering one thing.
Is there a way to configure TS so that uninitialised variables use declare implicitly?
That way this code
class SomeClass {
  private prop1 = 'default';
  private prop2?: string
}

would emit:
class SomeClass {
  constructor() {
    this.prop1 = 'default';
  }
}

without me having to add declare to all my uninitialised properties

@guilhermesimoes this is a perfect question for Stack Overflow since it results in a yes/no answer that is recorded for the future and can be updated if needed.

#41788 changed default for useDefineForClassFields which broke my code and took me more than 1 hour to find the reason.
It's ok to introduce break changes and it's easy to revert to the old behavior too. The problem is that the release note said nothing about this.
If it's expected, please note it somewhere. Thanks.

This has shipped in TypeScript 4.3.1‑rc, so it probably should’ve been kept in the TypeScript 4.3.1 milestone.

Just ran into this as a bug. Was using target: ESNEXT and using class properties to define types for classes. I had defined a property on the prototype as an optimization, and when trying to do an upgrade of TypeScript started noticing that the property was overwritten to be undefined. Really would appreciate this kind of change appear in the release notes.
Alternatively, if there were a way to define the types of class properties without buying into the whole TC39 class properties spec, that would be fantastic.

Alternatively, if there were a way to define the types of class properties without buying into the whole TC39 class properties spec, that would be fantastic.

You can write declare before the property name.

@nicolo-ribaudo
I consider declare and most modifiers to be a little too noisy, but yeah that’s what I’m doing. Thanks for the tip!

@brainkim

One potential option would be to allow us to define properties via sibling interface:
interface Point {
	x: number;
	y: number;
}

class Point {
	constructor() {
		this.x = 0;
		// the absence of this line should cause an error
		// this.y = 0;
	}
}

You can do that already.
It’s used in the @types/node package: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/d8e2ccd84ce78d70e48863e874653e2d8f9b75ae/types/node/events.d.ts#L21-L22

@ExE-Boss
But you’re losing the strict property initialization checks right?

Class fields moved to stage 4 in the April 2021 meeting, slated for publication in ES2022.

For reference, this was fixed by PR https://github.com/microsoft/TypeScript/pull/42663 and released in TypeScript 4.3.


push_to_git_remote doesn't escape branch names

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
push_to_git_remote seems to not be escaping parameters
The git command is constructed as follows
        command = [
          ‘git’,
          ‘push’,
          params[:remote],
          “#{local_branch}:#{remote_branch}”
        ]

I believe that the branch names should be escaped as follows
“'#{local_branch}':'#{remote_branch}'”
The issue being that pushing a branch named release-1.0.0(1) to the git remote fails with
bash: syntax error near unexpected token ('`
Complete output when running fastlane, including the stack trace and command used

[INSERT OUTPUT HERE]

Environment

🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.13.6

Ruby
2.2.5

Bundler?
false

Git
git version 2.17.1 (Apple Git-112)

Installation Source
~/.rvm/gems/ruby-2.2.5/bin/fastlane

Host
Mac OS X 10.13.6 (17G65)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.2.5/lib

OpenSSL Version
OpenSSL 1.0.2e 3 Dec 2015

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.0

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
fastlane gems

Gem
Version
Update-Status

fastlane
2.104.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.14.6

slack-notifier
2.3.2

atomos
0.1.3

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.6.0

rouge
2.0.7

xcpretty
0.3.0

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

commander-fastlane
4.4.6

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

mime-types-data
3.2016.0521

mime-types
3.1

httpclient
2.8.3

google-api-client
0.21.2

emoji_regex
0.1.1

faraday
0.15.2

json
2.1.0

highline
1.7.10

excon
0.62.0

CFPropertyList
3.0.0

plist
3.4.0

unf
0.1.4

domain_name
0.5.20180417

faraday_middleware
0.12.2

fastimage
2.1.3

terminal-table
1.8.0

unicode-display_width
1.3.3

dotenv
2.4.0

generated on: 2018-09-19

@akmarinov I have a PR for this if you want to test it out, point to my branch. 👍


chore: fix doc

Please reference any Issue related to this Pull Request. Example: Fixes #1.
See
here
for tips on good Pull Request description.

@googlebot I signed it!


Addition of Linear Search in Searching Algos.

@pankaj-bind
I am going to add the Linear Search Algorithm in the Searching Algorithms.
With the proper Objective and Explaination, with proper code in C.
Please Assign this to me.

You can start

@pankaj-bind please add lebels of gssoc

@pankaj-bind i have already added the Linear Search Folder and you also have merged that along with DFS, but this issue is still opened.

I would like to work on this .Please assign to me.


[Feature] Shortcuts to UEXcorp websites URLs from Configuration Tab

https://github.com/Hybris95/UEX-Trader/issues/132


[UIE-128] Move truncateInteger out of libs/utils

https://broadworkbench.atlassian.net/browse/UIE-128
Continuing to break up libs/utils....
truncateInteger is used in one place. Thus, it doesn't need to be in libs/utils. This PR moves it into workspace-data/Data.

https://broadworkbench.atlassian.net/browse/UIE-128
Continuing to break up libs/utils....
truncateInteger is used in one place. Thus, it doesn't need to be in libs/utils. This PR moves it into workspace-data/Data.

But what if someone else wants to use it someday?!?

But what if someone else wants to use it someday?!?

I think it's specialized enough that that's unlikely. There's a more general number formatter (Intl.NumberFormat) built into the browser.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#digit_options


Initialize devcontainer

The container image includes .NET 6.0 and Node JS (v18, the current LTS).
Reason for creating as a draft PR:

[x] ~Scripts in the package.json rely on windows specifics (npm run clean and npm run generate-toc)~
[x] ~The PR introduces hackiness related to forcing the container to use bash shell~
[x] Need to confirm it works on Windows

~As a minimum to get the devcontainer working properly, I needed to manually update the generate-toc script in ./package.json:~
https://github.com/ryanspain/sample-docfx-with-live-reload/blob/aa726f2e82fd4e7b892d337253cab189628a4b18/package.json#L13
~to replace it with:~
"generate-toc": "DocFxTocGenerator -d docs -o docs -s -r"

then I ran the following commands:

~npm install~ (now run automatically when the devcontainer starts up)
~npm run setup~ (now run automatically when the devcontainer starts up)
npm run build
npm run preview


Implement stream constructor version 2 (error support, new syntax)

There is a new basic type stream<T,E>, which represents a sequence that may be constructed lazily and is iterable a sequence of values of type T with error type E; stream is short for stream<T,never>.
var x = new stream<xml,error>(foo);

stream<xml,error> x = new(foo);

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/21524 ...


Fixing download-edge script in ARM devices

donwload-edge script fails on ARM devices on a race condition between extracting the edge.zip and deleting the file. This PR fixes the issue allowing it to finish the extract before deleting.

Do you happen to know why this is ARM devices specifically?  Also could you link the relevant issues this fixes?  Like will we need to do anything with default browser paths or was this the main issue behind ARM devices?

I think is has to do with computing power.  It is probably taking more time to the unzipper to complete which fails the deletion (or viceversa), this is not related to the extension not working on the ARM devices, I have not gotten there yet as I got blocked by this one first. Here is a screenshot of the error:


Wrong elevation is returned in 3D view in groundAlt example

It is returning around -10,000 meters for certain areas in the United States.

Like Google Earth, it gets more precise as you zoom in.  We plan to improve this.  See https://groups.google.com/forum/#!topic/cesium-dev/piux2QQqo3k


Add promote operation during meld action

Promote would allow a player to automatically meld (and optionally execute) a card of lesser or equal value in their forecast when a card is melded.
The promotion would also trigger visible echo effects of the promoted color.
The user would need an option to skip the promotion even if they were eligible and the ability to select their card (possibly using a private viewing window).

I just added the new states to the diagram. Time to implement this!

Ah I didn't account for how we sometimes will be digging before we promote. This graph is going to get messy...

don't forget about the city searching interaction (returning cards that don't match symbols)
If you are redrawing the diagram, you might want to consider how endorsing will work.

Yeah that's a great idea. I'll consider the city searching interaction at the same time.
Endorsing won't touch the exact same part of the graph (since it doesn't involve melding) so I'll worry about that later.

I finished updating the state diagram:


[Bug] I would like to add a loader

Describe the bug
currently it shows loading..instead of that I would like to implement a better loader animation
To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

can I work on this?

can I work on this?

I realised that I was having network issues. loader is there


tags support

added tags support  but for one  tag at the time  it will crawl all the posts and look for all the tags and generate the paths accordingly with pagination

zod repo has a pr that will add array uniqueness checks see
HorizontalCard is only used by the blog for now so idk if tag_url is even required
added aliases for both components and layouts

@brahimABD98 Hi, do you have a screenshot of this?

@hmenorjr Oh this means you can filter posts using one tag  at a time (you can't filter using multiple tags at once ) but you can add multiple tags to each post  and they have to be unique
screenshot :

@manuelernestog all good to go

@brahimABD98 Awesome, thanks. I was thinking of how to add a tag in the HorizontalCard since it's in a some sort of for-loop. I just got back to development for my website. So yeah, thanks. Like this template for SEO and simplicity. thanks again.


Checkbox on Delete-Node dialog regarding deleting animations

Initial version to fix #3562.
This is a minimal fix. Mainly to get feedback for a proper one.
It is therefore also not cleaned up or squashed, with lots of comments in the code regarding issues that showed up. I welcome any feedback on all those comments.
This fix simply adds a checkbox to the "Delete Node" confirmation dialog. The checkbox directly reflects, and changes, the editor setting "editors/animation/autorename_animation_tracks", as this controls if animation tracks that refer to a node are deleted.
This is suboptimal, I would say - for one autorename is not autoremove. But see below for more.

The actual deleting of animation tracks is done with the function duo of fill_path_renames and perform_node_renames.
They actually perform 4 different functions:

Renaming animation tracks when the corresponding nodes are renamed or reparented
Deleting animation tracks when nodes are deleted
Rewriting nodepaths in exported script properties when renamed/reparented
Deleting (setting to null) nodepaths in exported script properties when nodes are deleted

The editor setting mentioned above seems to only be meant to affect 1 and 2 (even though it's called "autorename"). If I parsed the code correctly, it does actually affect 3 and 4 potentially, and I think this might also involve a bug that could explain a crash mentioned in this issue #26144 but I haven't fully tested that yet.
My main question is: what is the desired behavior? Should there be two separate editor settings for rename and remove? Should the checkbox be a separate setting that only affects the current node-deletion rather than directly changing the editor-wide setting?
(Also I would ideally like to add more info the the dialog, as in how many tracks (and script properties) will be affected, and disable the checkbox if there would not be any effect. But that would need a lot more code changes.)

Superseded by #58598.


Broken reference links in "Advanced (Windows Presentation Foundation)" guide

The majority of reference links in the Advanced (Windows Presentation Foundation) guide have been broken for over a year.
For a specific example, reference links on Input (WPF) page lead to missing URLs such as https://docs.microsoft.com/en-us/dotnet/api/system.windows.uielement:

We’re investigating this issue right now. It should be related to the work we’re doing for #4789

We found the root cause, which was unrelated to the work being done for #4789, and the problem is now fixed. The issue only started this morning. Thanks for letting us know, @fragmer.


Add num_replicas and num_partitions to ModuleOp

Request description
The statically know values  num_replicas and num_partitions, being provided by HLOModuleConfig, helps to find the size of each process group to be employed in parallel execution. Currently these values are not exposed in StableHLO.
Having these values in StableHLO will enable

type inference of CollectiveOps. For example, using  num_replicas and num_partitions we can determine shard_count using GetSubgroupSize. With that we can say: dim(result, all_gather_dim) = shard_count * dim(operand, all_gather_dim).

Populate empty replica_groups ref

Originated in https://github.com/openxla/stablehlo/pull/503#discussion_r1032732950 and
https://github.com/openxla/stablehlo/pull/503#discussion_r1032839388

JAX has just added mhlo.num_replicas and mhlo.num_partitions to their lowering: https://github.com/google/jax/pull/15586. It's great to know that this information is available during lowering :tada:


Build the test bootstrapper app as netcoreapp3.1 instead of netcoreapp2.0

I'm not sure what the intentions are for the bootstrapper app now that the github actions are running the tests directly, but:
I'm getting build warnings (visible in the appveyor build as well) about the bootstrapper app being built as .NET Core 2.0, when the test assembly that it depends on is now built as .NET Core 3.1 and .NET 4.6, so - try fixing that by retargetting it at 3.1 to match.
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

Actually, looks like the appveyor CI is failing to run the tests altogether as is?
Invalid : C:/projects/sharpziplib/test/ICSharpCode.SharpZipLib.TestBootstrapper/bin/Debug/netcoreapp2/ICSharpCode.SharpZipLib.Tests.dll
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
  ----> Could not load file or assembly 'System.ValueTuple, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


Feat/tdp 2048 better jdbc error handling

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)

What is the current behavior? (You can also link to an open issue here)
When user supply a wrong SQL query, the API returns an "unexpected exception"
What is the new behavior?
When user supply a wrong SQL query, the API returns a more detailed message from JDBC
Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information:
There might be other changes needed in JDBC component where SQL syntax errors are not caught separately.

Pull request test result: success :star:


Increment version for cosmos releases

Increment package version after release of com.azure azure-cosmos

/check-enforcer override