How to train unregular box?

Hi, my data set labels are unregular, where to modify the data preprocessing code?
The format of the label is like this:

You can try to register your own data following detectron2's official documentation here: https://detectron2.readthedocs.io/en/latest/tutorials/datasets.html

@rentainhe thank you for your reply, does data augmentation need to be modified?

@rentainhe thank you for your reply, does data augmentation need to be modified?

Yes, we use detectron2's default data augmentation, but it only works on the normal box, you should double-check this in detectron2's source code.

@rentainhe thank you for your reply, does data augmentation need to be modified?

Yes, we use detectron2's default data augmentation, but it only works on the normal box, you should double-check this in detectron2's source code.

thanks, I got it

@rentainhe thank you for your reply, does data augmentation need to be modified?

Yes, we use detectron2's default data augmentation, but it only works on the normal box, you should double-check this in detectron2's source code.

thanks, I got it

You're welcome, detectron2's documentation has detailed tutorial on how to register your own dataset and augmentations, it may be helpful


todo_widget: Add button to hide completed tasks.

todo: improve button appearance.
Testing plan:
GIFs or screenshots:

Let's say "Hide completed tasks."  And then can we take the "wip" out of the title?

Code LGTM to me now.

The visuals still need work here; ideally we'd not spend a whole line on this toggle.  Could we figure out a pair of icons for hidden/revealed (maybe some of the eye icons) and just have a toggle button represented by that icon with a tooltip explaining what it means?

Updated the toggle to be a button with eye and eye-slash icons, see gif bellow:


(Feature) #1545 Optimize lodash imports

Description
Configure lodash-webpack-plugin for dev and pro webpack.config file. Change the way of methods import from lodash libarary to match the optimize convention. Fix the test with terms of use web view.
About #1545
How Has This Been Tested?
The app should work fine as before, without crashes and very specific issues.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request ( for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

Conflicts resolved

@sirpy conflicts resolved

please resolve build errors
in SignupState _get is used (which was removed by this PR, now we're importing { get })

please resolve build errors
in SignupState _get is used (which was removed by this PR, now we're importing { get })

Right, there one variable wasn't renamed - fixed in a new commit.


AWS: Increase HttpPutResponseHopLimit to 3 for EC2 instances

What this PR does / why we need it:
The latest Ubuntu 22.04 images have IMDSv2 enabled as a default. By default, the limit of hops of PUT requests to metadata service is 2. The instance metadata service is not reachable from the container network in case if further hops are required.
We came across this issue while working with Cilium as CNI. The issue has been documented here.
Although, the issue mentions a workaround to make it work with Cilium. Fixing it just for a single component is not ideal since a tool like machine-controller shouldn't judge how the underlying network or programs hosted on the machines provisioned by it are configured. Hence, we went with a more generic fix for this, i.e. to set the HTTP PUT response hop limit to 3. This ensures a much wider compatibility.
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?

/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

AWS: Increase HttpPutResponseHopLimit to 3 for EC2 instances

Documentation:

NONE

/hold
Looks like we don't run AWS tests by default in MC, let me quickly check this

/test pull-machine-controller-e2e-aws
/hold cancel

/cherrypick release/v1.59

/cherrypick release/v1.58

/cherrypick release/v1.57

@ahmedwaleedmalik, hello
We encountered the same issue when retrieving the session token from the instance metadata. We are also using Cilium as the cluster CNI (no issues were observed with Flannel).
Therefore, we are also considering increasing the hop limit to 3. What potential drawbacks or concerns should we be aware of when increasing it?"


Programming Languages - "R" Complete Resources

IMPORTANT: When creating your Pull Request, please use the following format for the title: Category - Resource Name & Section
PR Title samples:

Web development - CSS Portal & Tools
Web development - Leetcode & Challenges

Closes #372
Description:
Hey @jfmartinz I have added all resources for R Programming Language
./Programming Languages
       /R
         / readme.md

Please take a look and do let me know,
Hope it helps. (also pls do not forget to add labels)
Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[x] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[x] I followed the prescribed PR title template. (Check this if you're adding a resource)

@jfmartinz Please add gssoc and level badges

I always forgot. haha, thanks

@jfmartinz Please assign this PR to me.


Update foundation.topbar.js

Fixed an issue created by the intial-scroll of Google Chrome.
Description of the issue and the solution:
If you scroll down your foundation-website and use the sticky-tobbar and then you reload the page on Google Chrome, Chrome will directly jump to your last scroll position.
Because start_offset has the default value of 0, the script won't toggle the sticky and fixed classes. So I've set the default value of start_offset to false (still 0 in JS arithmetics) and on the initialization of the script, it searches for the current offset of the topbar and sets it to the start_offset variable, if the start_offset equals to false.

Thanks for the PR! Since this is for Foundation 5, it needs to be pointed to the V5 branch in this repo. Are you able to resubmit there so we can test and merge?

Closing based on last comment.  Please resubmit against V5.


Resources generalisation in knit

files is a list for uploading, and should include any zipped python env. Things
ending in .zip will be treated as archives with a name like the filename minus the
.zip. Existing resources in hdfs can also be passed (no upload).
environment (set of key/values) is passed as a dictionary.
for now, dask launch command is simply derived from the environment passed, as
before.

Meantime:
changed application and client kill to atexit.

Notes:

needs careful documentation
atexit method works in absolutely getting rid of hanging processes and applications, but often causes error messaging in the console at shutdown. This is presumably because everything it torn down at the same time; I don't know how to avoid it.

Fixes #100

@jcrist - is this how it's done? I'm not experienced with weakref.

I stuck with the class attribute and method as, in my mind, this is better for possible subclassing - not that I expect much of that.


IZPACK-1466: Non-canonical paths do not work in exists condition

Imagine you have property e.g. property INSTALL_PATH set to C:/test and a file test.txt exists in C: root.
When you use exists condition it is not able to create a canonical path if you set it like this
<condition type="exists" id="DoesNotWork">
  <file>${INSTALL_PATH}/../test.txt</file>
</condition>

it is evaluated as false.
When you set it like
<condition type="exists" id="Works">
  <file>C:/test.txt</file>
</condition>

it is true.

Solved for the following conditions:

contains
empty
exists


Automatic removal of orphan nodes

Completes work from https://github.com/celestiaorg/smt/pull/24 :

[x]  implement the actual removing of orphans
[x]  more extensive testing (update/delete operations, tree with multiple entries)

Thanks for continuing this work and this PR!
Changing the leaf value (https://github.com/celestiaorg/smt/pull/36/commits/341c9985ac9bf4b32561c6f9ba94f71c545789af) seems to a breaking change. Is this necessary to implementing orphan removal, and why? There already shouldn't be any ambiguity about which key a leaf is for, as it's already prefixed in the leaf's value.

@musalbas sorry, my commit message wasn't very clear. The problem only arises when deleting a leaf with a duplicate value - there's no way to know if a value is still referenced by another leaf. Another solution would be some kind of reference count.

@roysc The implementation storing the hash of the value for the leaf value is an implementation detail. It's in no way required. You could instead store values in the separate map hash(key) -> value, as in https://github.com/celestiaorg/smt/issues/14#issuecomment-762895582. Breaking the commitment specification is simply not a viable workaround to an implementation detail.
I suggest you start by refactoring as per #14, then pruning will follow readily.

@adlerjohn my apologies for not respecting the commitment spec. Using key -> value is a simple change; but if this mapping is stored in the same DB, would there be any concern about malicious users intentionally storing a plain key that collides with an existing tree hash? Or are you suggesting using a separate DB instance for this?
And could you clarify what you mean by modifying the current test suite? Are you referring only to the changes in the commitment spec, or changes in the LazyLedger/Celestia core? I haven't modified any existing tests here.

Or are you suggesting using a separate DB instance for this?

Yes, the suggestion is a separate KV store just for values. There's no inherent reason to put both values and nodes in the map KV store.

And could you clarify what you mean by modifying the current test suite? Are you referring only to the changes in the commitment spec

Yes, to clarify I mean that the commitment as specified here must be the same before and after any PR dealing with implementation details.

I'm not able to reopen this PR, new one: https://github.com/celestiaorg/smt/pull/37


do you support to evaluate rwkv?

I try to run
python main.py --device cuda --no_cache --model hf-causal-experimental --model_args pretrained=/RWKV-4-Raven-7B-v12-Eng98%-Other2%-20230521-ctx8192.pth,trust_remote_code=True,use_accelerate=True --tasks truthfulqa_mc --num_fewshot 0
to evaluate RWKV, but fail with errors:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 64: invalid start byte
and
OSError: It looks like the config file at
'/data/leaderboard/weights/BlinkDL/RWKV-4-Raven-7B-v12-Eng98%-Other2%-20230521-ctx8192.pth' is not a valid JSON file.

Hi! We do support RWKV via Huggingface's implementation, but only the models that are converted to Huggingface's format.
For example, I'm able to run https://huggingface.co/RWKV/rwkv-raven-7b without issue, but it seems like you're trying to pass a specific .pth file, which isn't supported by default. To evaluate this model, either you'll need to integrate it into your own LM subclass or you'll need to convert it to Huggingface's format, which I believe can be done via this script: https://github.com/huggingface/transformers/blob/main/src/transformers/models/rwkv/convert_rwkv_checkpoint_to_hf.py


Add Client.apply_many() and Client.delete_many() for batch resource operations

This PR proposes some helpers to address a problem with handling batches of resources.  I'm not married to the API, etc., and am happy to adjust and flesh out anything that is missing (for example, create_many()?), but I'm mainly curious atm whether this feature would be appreciated in lightkube or if I should finish it as a separate helper I keep elsewhere.
Working with a batch of resources has an order of operations challenge.  For example, this valid YAML contains both a ClusterRoleBinding and the ClusterRole/ServiceAccount it references:
kind: ClusterRoleBinding
roleRef:
  kind: ClusterRole
  name: example-cluster-role-binding
subjects:
- kind: ServiceAccount
  name: example-service-account
...
---
kind: ClusterRole
metadata:
  name: example-cluster-role
...
---
kind: ServiceAccount
metadata:
  name: example-service-account

If users loop over the yaml and create the objects, they will get errors because the ClusterRoleBinding is created before the items it uses.  Tools like kubectl or kapp handle this for the user.
This PR is a proposal to similarly automate this issue with lightkube by adding Client.apply_many() and Client.delete_many() helpers.  They both accept iterables of resources and, before executing on them, order them in a safer order by kind.  afaict this is sufficient to avoid any conflicts, but I'm flexible if there's something missing.

Did you find the corresponding logic in kubectl source code? Is it just based on resource names like in your implementation or something else?
In general I would like to keep this library sufficiently low level and easy to learn. So I would prefer to avoid new methods that can be created with few lines of code. The key component of your PR is the sorting function and that is something we could include as it's non trivial and can be used for creating more high level functionalities.
So something like
from lightkube import sort_objects

for obj in sort_objects(objs, by='kind-rank'):    # better name and signature TBD
    client.apply(obj)

for obj in sort_objects(objs, by='kind-rank', reverse=True):
    namespace = obj.metadata.namespace if isinstance(obj, NamespacedResource) else None
    client.delete(obj, name=obj.metadata.name, namespace= namespace)

We can also support other types of object sorting in the future.

That makes sense to me - keeping this to a sorting helper works.  In my opinion having a _many version of the create/apply/delete would be helpful without complicating the package too much (their names will be intuitive, which I think helps) but I can see your point as well.
I made a mistake in the original post - as far as I can tell, kubectl does not reorder objects before applying.  I don't see any ordering in the source, and after testing it explicitly just now I think I have just been lucky in the past and always applied YAML that was already in a safe order.  The tool kapp does reorder objects before applying, and their kind-rank is similar or the same to what is here.

Sorry, between business trips and covid I dropped the ball on this.  I'll put a workable solution together next week

I have reverted the previous changes and added a sort_objects like you mentioned.  What do you think?  I wasn't sure where this function should live - it currently is in client.py, but it feels a bit out of place.  Would appreciate suggestions or any requested changes - thanks!

Thanks a lot, changes are merged.


Known data issues with dungeoncog

Since we're not actively developing dungeoncog, I'm going to keep this one ticket as a place to report dungeoncog data issues instead of having many open tickets that we're not actively planning on addressing, but do want to be aware of

Shura 1 wrong def
→ I also suspect several floors of Shura 1 display higher DEF than in realit. F8 Arondight typically doesn't have 1b DEF.
Originally #1393

→ Shura 1 Menoa Floor (20 & 21)

All Menoas are displayed twice (F20 has 2 spawns instead of 1, F21 has 10 instead of 5)
All Menoas are displayed with high 2b DEF when in reality they either don't have it, or only a little amount.

Originally #1392

SR3 spawns seem to have their execute counters off. I'm not sure where they're pulling 7 turns from, rather than 14, or why it thinks it's looping over those 7 turns.

Originally #1309

SR1 Perseus shows his skyfall as [:blind: for None]. Is that supposed to be [:blind: for 1 Turn]?
Originally #1306

Dungeon Invades are showing up on both floor 1 & the actual floor
Originally #1298

Moves aren't always shown in order of priority, which is a little difficult to figure out. For example, Thoth on F12 shows his revive below his regular attack.

Originally #1310

While (hit AND color change) abilities show the color change part, (color change, THEN hit) are missing the color change. Things like the F2 golems in SR3 do the former as part of their normal moves, but every floor until F13 should be doing the latter in their turn 15 execute. Also, the former is shown as (Self:arrow_right: random :orb_fire::orb_water::orb_wood::orb_light::orb_dark:)(:single_hit::102,000) but should probably be reversed. The damage is done as the previous color!

Originally #1308

Cond: X% chance lines are common enough to probably get their own representation. #1312
Maybe prefix the move with [50%:game_die:] or similar, rather than having a separate line?
[9:18 PM]Siveran:With all this combined, an example spawn:
Enemy:Super Red Carbuncle | Spawn:1/5 | Floor:1/15 | Page: 1/1
HP:2,500,000,000 ATK:75,500 DEF:2,500,000,000 TURN:1 COLOR:R/x
(Passive)(:resolve:50%)
(Preemptive)(:skill_bound: for 15)
Condition: when 1 enemies remain, once:
(:enrage:900% for 999))
Condition: turns 1-14:
(:multi_hit::75,500)
Condition: when 1 enemies remain:
(Self:arrow_right: random :orb_fire::orb_water::orb_wood::orb_light::orb_dark:) + (:multi_hit::2,642,500)
(:single_hit::6,040,000)(Self:arrow_right: random :orb_fire::orb_water::orb_wood::orb_light::orb_dark:)

(color would be done through an emoji)
Originally #1312

Skill bind show as :res_bind: :skill_bound:, which is a bit confusing. Just :skill_bound: would be fine.
Originally #1303


OpenSSL does not have any of the ciphers that Microsoft Outlook uses

I installed the required libeay32.dll and libssl32.dll that LispWorks requires to receive emails as an SMTP with CTX and SSL. I don't understand secure socket layer very well because I don't program at a low enough level.
I start up my server program. Then from Outlook, I send a test email on server (port) 25 to localhost. My server program receives the connection. But on the HELO stage gives this error:
SSL failure in #<COMM:SOCKET-STREAM 220F362F>:
error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher
I think that error means that OpenSSL cannot do even one of the many ciphers that Outlook can do.
Would be nice if someone can prove me wrong so I can get on with my program. But if I am not wrong, then I am right. And seems that OpenSSL would want to support writing email servers that can interface with the ubiquitous Microsoft Outlook client.
I'm running Windows 10 64-bit, Outlook 2016 64-bit, and Lispworks 32-bit. LispWorks can use C language generated DLLs through its "Foreign Language Interface" (foreign language meaning C and not Lisp).
Let me know what you need from me to analyze. I hope I can supply whatever you ask.

This is almost definitely a configuration mismatch; OpenSSL supports almost every cipher, but some of them are not enabled by default, for example, because they are no longer considered secure.  What version of OpenSSL did you install?  Can you list the available ciphers in your server?  Can you figure it to use anythting other than DEFAULT? Can you get a packet trace?

I really appreciate your taking interest. The main problem has got to be my own ignorance.
I downloaded Win32OpenSSL-1_0_2k.exe and Win32OpenSSL_Light-1_0_2k.exe
from https://slproweb.com/products/Win32OpenSSL.html . So, my version is 1.0.2k.
Each is an installation program. The Light is for users and the other for developers. I don't really know which I need because I'm not sure what developer means. Maybe when programming at a high level, the user version is fine. The developer did not seem to give me a more detailed error message.
Running either installation programs was not enough to make my program run. But copying two of the resulting DLLs (libeay32.dll and libssl32.dll) into the same directory as LispWorks.exe (actual executable is "lispworks-7-0-0x86-win32.exe") got me past the first error. The first error said something like "cannot not finding libssl32.dll". I moved these DLL files into the "Windows\System32" directory. That also works.
So, now I get the current error I mentioned in my first post of "no shared cipher".
After I posted, I ran into the ebook "OpenSSL Cookbook" and the program in the OpenSSL installation "OpenSSL.exe". I'm making a wild guess that my server's list of ciphers has to do with PEM files. And just like my server could not find the libssl32.dll and the libeay32.dll, it can't find any PEM. And the reason it cannot find any shared cipher is because it doesn't have even one cipher. And it doesn't have even one cipher because it doesn't have even one PEM file.
I don't know whether what I'm thinking and typing here makes any sense. But maybe my next step is to read the OpenSSL Cookbook to learn how to use OpenSSL.exe and for what OpenSSL.exe can be used. It might make PEM or other files. Maybe it configures something for me.
In LispWorks COMM package, I think so much is done for me that I'm a lot in the dark about what's going on underneath. I don't see a function to list the available ciphers. And my not seeing could be because I don't know what it's called in LispWorks or because I don't know where to look for such a function.
Maybe you can tell me whether my thinking makes sense about how the Server doesn't find any PEM files, therefore doesn't have any ciphers. Or is there no connection between PEM's and ciphers?
And I am interested whether you think I might be helped along by my reading OpenSSL Cookbook and learning how to use OpenSSL.exe and for what to use it.
Am I on a good track? Or can you point me to something more likely to help?

Each is an installation program. The Light is for users and the other for developers. I don't really know which I need because I'm not sure what developer means. Maybe when programming at a high level, the user version is fine. The developer did not seem to give me a more detailed error message.

The page doesn't really explain it, but my guess is the developer version include debug symbols.

After I posted, I ran into the ebook "OpenSSL Cookbook" and the program in the OpenSSL installation "OpenSSL.exe". I'm making a wild guess that my server's list of ciphers has to do with PEM files. And just like my server could not find the libssl32.dll and the libeay32.dll, it can't find any PEM. And the reason it cannot find any shared cipher is because it doesn't have even one cipher. And it doesn't have even one cipher because it doesn't have even one PEM file.

To run a server you need to have a Certificate and an associated private key (typically stored in PEM files). "openssl.exe" will help you to create those things. Without those things you will not have any ciphers available, which is probably why you are getting the error message. Reading the cookbook would be a very good start - I recommend it. The cookbook is an extract from a larger book on SSL/TLS in general (not OpenSSL specific) which would give you an excellent grounding in the subject if you are after a more detailed understanding. I recommend this book too:
https://www.feistyduck.com/books/bulletproof-ssl-and-tls/

Thank you for the encouragement and the tip.

Please re-open the issue is needed.


Entry storage test cases

Adds test cases for DatabaseInterface, EntryRepository and EntryFactory. I implemented the mocks myself instead of using a framework because I wanted to implement some simple control structures therefore making the output of the mocked method dependent on the input.
I'm merging it to this branch instead of the master branch because I rebased from this branch in order to copy the folder structure and your configuration inside the CMakeLists.txt.

I found the same page while looking for a documentation on the mocking feature of Google's testing library, however, I wasn't completely sure then how I would implement if-else structures. I just had a look at it again and I thought I get it now, so I just tried it. This is what I did: EXPECT_CALL(abstractDbMock, executeSql("SELECT * FROM passwords WHERE EntryId = \"1\";").Times(1).WillOnce(Return(std::make_pair(nonEmptyEntrySet, ""))); and this is the error I got: Unterminated function-like macro invocation. Of course nonEmptyEntrySet is a local variable I initialized above the EXPECT_CALL invocation and I also included the call to MOCK_METHOD inside the AbstractSqlDatabaseMock declaration, which looks like this: MOCK_METHOD((std::pair<std::set<DDD::Entities::Entry>, std::string>), executeSql, (const std::string& statement), (const, override));
Honestly I think for now the manually implemented mocks will do. I agree that we don't have an assurance on whether the function is really called which would be neat, however, I feel like the mocks produced by gMock are relatively strict which I would like to avoid so that there is more freedom on the implementation side.
So is it ok for you if we just use the manual mocks instead of gmock?


multi-currency and multi-language are not working in production

I can't seem to get NexSJ to work with multi-currency and multi-language are not working on production. For some reason nextJS is blocking calls to location API so multi-currency and multi-language. see video
https://www.dropbox.com/s/4jtn3juqh4vfluk/locale test.mkv?dl=0
any help is appreciated

Hey there! Thank you for your contribution. We have decided to take Next.js Commerce in a new direction and will be closing out current PRs and issues due to this change. Please see this PR for more details: #966


Event doesn't show up in either index

This request didn't show up in either the good or bad index:
stm=1471355603353&e=se&se_ca=compare&se_ac=deals_popup_impression&se_la=v2&se_pr=%2B_1_210_EUR&tv=js-2.6.2&tna=cloudfront&aid=localhost&p=web&tz=Europe%2FBerlin&lang=en-US&cs=UTF-8&res=453x654&cd=24&cookie=1&eid=22e32d8b-97cb-49e1-abd3-3d35b85275ad&dtm=1471355603266&vp=453x653&ds=453x653&vid=1&sid=2c418c3b-204e-4f6a-b89f-7cd74720e3e7&duid=ecb6d0a6-2889-4e02-b026-5bb2e979ab67&fp=1984288169&url=http%3A%2F%2Flocalhost%3A3000%2Ftravel-search%2Fresults%2F1718387152%2Fbus%3Flocale%3Dfr%26v%3Ddp%3Av2&cx=eyJzY2hlbWEiOiJpZ2x1OmNvbS5zbm93cGxvd2FuYWx5dGljcy5zbm93cGxvdy9jb250ZXh0cy9qc29uc2NoZW1hLzEtMC0wIiwiZGF0YSI6W3sic2NoZW1hIjoiaWdsdTpjb20uc25vd3Bsb3dhbmFseXRpY3Muc25vd3Bsb3cvd2ViX3BhZ2UvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiaWQiOiJhNTczZmNjNS01OTYwLTQxMTAtYjA3OC03YzYwZDc0NjA3NzYifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc2VhcmNoX2NvbnRleHQvanNvbnNjaGVtYS8yLTAtMCIsImRhdGEiOnsic2VhcmNoX2lkIjoiMTcxODM4NzE1MiJ9fSx7InNjaGVtYSI6ImlnbHU6Y29tLmdvZXVyby9zdWJzZXNzaW9uX2NvbnRleHQvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsic3Vic2Vzc2lvbl9pZCI6IjAxZGY2MWJjLWVhMTktNGIyNC1hYTlhLWFkYjc2ODI2MGQxNyJ9fSx7InNjaGVtYSI6ImlnbHU6Y29tLmdvZXVyby9wYWdlX3R5cGVfY29udGV4dC9qc29uc2NoZW1hLzEtMC0wIiwiZGF0YSI6eyJwYWdlX3R5cGUiOiJzZWFyY2hfb3V0Ym91bmQifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc3lzdGVtX3ZlcnNpb25zX2NvbnRleHQvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiY2xpZW50IjoibW9iaWxlLXdlYiIsImJhY2tlbmQiOiIiLCJjbGllbnRfdmVyc2lvbiI6IjEuMi4yMi1yMS1TTkFQU0hPVCIsImJhY2tlbmRfdmVyc2lvbiI6IiIsInRyYW5zbGF0aW9uX3ZlcnNpb24iOiIxLjIuMjUiLCJiYWNrZW5kX3NlcnZlciI6IiIsImNsaWVudF9lbnZpcm9ubWVudCI6ImRldmVsb3BtZW50IiwiYmFja2VuZF9lbnZpcm9ubWVudCI6IiIsIm90aGVyX2NvbXBvbmVudHMiOiIifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc2VhcmNoX3BhcmFtZXRlcnNfY29udGV4dC9qc29uc2NoZW1hLzEtMC00IiwiZGF0YSI6eyJhZHVsdHMiOjEsImFycml2YWxfcG9zaXRpb25faWQiOjM3Njk0NiwiY2hpbGRyZW4iOjAsImRlcGFydHVyZV9kYXRlIjoiMjAxNi0wOS0wNFQwMDowMDowMCswMjowMCIsImRlcGFydHVyZV9wb3NpdGlvbl9pZCI6Mzc2MjE3LCJpbmZhbnRzIjowLCJyZXR1cm5fZGF0ZSI6IiIsInJvdW5kX3RyaXAiOjB9fSx7InNjaGVtYSI6ImlnbHU6b3JnLnczL1BlcmZvcm1hbmNlVGltaW5nL2pzb25zY2hlbWEvMS0wLTAiLCJkYXRhIjp7Im5hdmlnYXRpb25TdGFydCI6MTQ3MTM1NTU5OTk1MiwidW5sb2FkRXZlbnRTdGFydCI6MTQ3MTM1NTYwMDAxNywidW5sb2FkRXZlbnRFbmQiOjE0NzEzNTU2MDAwMTcsInJlZGlyZWN0U3RhcnQiOjAsInJlZGlyZWN0RW5kIjowLCJmZXRjaFN0YXJ0IjoxNDcxMzU1NTk5OTUzLCJkb21haW5Mb29rdXBTdGFydCI6MTQ3MTM1NTU5OTk3MywiZG9tYWluTG9va3VwRW5kIjoxNDcxMzU1NTk5OTczLCJjb25uZWN0U3RhcnQiOjE0NzEzNTU1OTk5NzMsImNvbm5lY3RFbmQiOjE0NzEzNTU1OTk5NzMsInNlY3VyZUNvbm5lY3Rpb25TdGFydCI6MCwicmVxdWVzdFN0YXJ0IjoxNDcxMzU1NTk5OTczLCJyZXNwb25zZVN0YXJ0IjoxNDcxMzU1NjAwMDEzLCJyZXNwb25zZUVuZCI6MTQ3MTM1NTYwMDAxOSwiZG9tTG9hZGluZyI6MTQ3MTM1NTYwMDA0MiwiZG9tSW50ZXJhY3RpdmUiOjE0NzEzNTU2MDAyMzEsImRvbUNvbnRlbnRMb2FkZWRFdmVudFN0YXJ0IjoxNDcxMzU1NjAwMjMxLCJkb21Db250ZW50TG9hZGVkRXZlbnRFbmQiOjE0NzEzNTU2MDAyMzMsImRvbUNvbXBsZXRlIjoxNDcxMzU1NjAyNDE4LCJsb2FkRXZlbnRTdGFydCI6MTQ3MTM1NTYwMjQxOCwibG9hZEV2ZW50RW5kIjoxNDcxMzU1NjAyNDMxLCJjaHJvbWVGaXJzdFBhaW50IjoxNDcxMzU1NjAwNDI0fX1dfQ

Can you provide any steps to recreate this?

@jbeemster - can we just curl the request that @bogaert has provided into a snowplow-mini instance?
Christophe tested this event repeatedly with one of our client's snowplow-mini instances. It would be worth testing whether the event fails to show up in another...

So this is really weird. I tried sending the data through to another snowplow-mini instance and it went through fine, using curl:
curl 'http://{{ snowplow mini ip address }}:8080/i?stm=1471355603353&e=se&se_ca=compare&se_ac=deals_popup_impression&se_la=v2&se_pr=%2B_1_210_EUR&tv=js-2.6.2&tna=cloudfront&aid=localhost&p=web&tz=Europe%2FBerlin&lang=en-US&cs=UTF-8&res=453x654&cd=24&cookie=1&eid=22e32d8b-97cb-49e1-abd3-3d35b85275ad&dtm=1471355603266&vp=453x653&ds=453x653&vid=1&sid=2c418c3b-204e-4f6a-b89f-7cd74720e3e7&duid=ecb6d0a6-2889-4e02-b026-5bb2e979ab67&fp=1984288169&url=http%3A%2F%2Flocalhost%3A3000%2Ftravel-search%2Fresults%2F1718387152%2Fbus%3Flocale%3Dfr%26v%3Ddp%3Av2&cx=eyJzY2hlbWEiOiJpZ2x1OmNvbS5zbm93cGxvd2FuYWx5dGljcy5zbm93cGxvdy9jb250ZXh0cy9qc29uc2NoZW1hLzEtMC0wIiwiZGF0YSI6W3sic2NoZW1hIjoiaWdsdTpjb20uc25vd3Bsb3dhbmFseXRpY3Muc25vd3Bsb3cvd2ViX3BhZ2UvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiaWQiOiJhNTczZmNjNS01OTYwLTQxMTAtYjA3OC03YzYwZDc0NjA3NzYifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc2VhcmNoX2NvbnRleHQvanNvbnNjaGVtYS8yLTAtMCIsImRhdGEiOnsic2VhcmNoX2lkIjoiMTcxODM4NzE1MiJ9fSx7InNjaGVtYSI6ImlnbHU6Y29tLmdvZXVyby9zdWJzZXNzaW9uX2NvbnRleHQvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsic3Vic2Vzc2lvbl9pZCI6IjAxZGY2MWJjLWVhMTktNGIyNC1hYTlhLWFkYjc2ODI2MGQxNyJ9fSx7InNjaGVtYSI6ImlnbHU6Y29tLmdvZXVyby9wYWdlX3R5cGVfY29udGV4dC9qc29uc2NoZW1hLzEtMC0wIiwiZGF0YSI6eyJwYWdlX3R5cGUiOiJzZWFyY2hfb3V0Ym91bmQifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc3lzdGVtX3ZlcnNpb25zX2NvbnRleHQvanNvbnNjaGVtYS8xLTAtMCIsImRhdGEiOnsiY2xpZW50IjoibW9iaWxlLXdlYiIsImJhY2tlbmQiOiIiLCJjbGllbnRfdmVyc2lvbiI6IjEuMi4yMi1yMS1TTkFQU0hPVCIsImJhY2tlbmRfdmVyc2lvbiI6IiIsInRyYW5zbGF0aW9uX3ZlcnNpb24iOiIxLjIuMjUiLCJiYWNrZW5kX3NlcnZlciI6IiIsImNsaWVudF9lbnZpcm9ubWVudCI6ImRldmVsb3BtZW50IiwiYmFja2VuZF9lbnZpcm9ubWVudCI6IiIsIm90aGVyX2NvbXBvbmVudHMiOiIifX0seyJzY2hlbWEiOiJpZ2x1OmNvbS5nb2V1cm8vc2VhcmNoX3BhcmFtZXRlcnNfY29udGV4dC9qc29uc2NoZW1hLzEtMC00IiwiZGF0YSI6eyJhZHVsdHMiOjEsImFycml2YWxfcG9zaXRpb25faWQiOjM3Njk0NiwiY2hpbGRyZW4iOjAsImRlcGFydHVyZV9kYXRlIjoiMjAxNi0wOS0wNFQwMDowMDowMCswMjowMCIsImRlcGFydHVyZV9wb3NpdGlvbl9pZCI6Mzc2MjE3LCJpbmZhbnRzIjowLCJyZXR1cm5fZGF0ZSI6IiIsInJvdW5kX3RyaXAiOjB9fSx7InNjaGVtYSI6ImlnbHU6b3JnLnczL1BlcmZvcm1hbmNlVGltaW5nL2pzb25zY2hlbWEvMS0wLTAiLCJkYXRhIjp7Im5hdmlnYXRpb25TdGFydCI6MTQ3MTM1NTU5OTk1MiwidW5sb2FkRXZlbnRTdGFydCI6MTQ3MTM1NTYwMDAxNywidW5sb2FkRXZlbnRFbmQiOjE0NzEzNTU2MDAwMTcsInJlZGlyZWN0U3RhcnQiOjAsInJlZGlyZWN0RW5kIjowLCJmZXRjaFN0YXJ0IjoxNDcxMzU1NTk5OTUzLCJkb21haW5Mb29rdXBTdGFydCI6MTQ3MTM1NTU5OTk3MywiZG9tYWluTG9va3VwRW5kIjoxNDcxMzU1NTk5OTczLCJjb25uZWN0U3RhcnQiOjE0NzEzNTU1OTk5NzMsImNvbm5lY3RFbmQiOjE0NzEzNTU1OTk5NzMsInNlY3VyZUNvbm5lY3Rpb25TdGFydCI6MCwicmVxdWVzdFN0YXJ0IjoxNDcxMzU1NTk5OTczLCJyZXNwb25zZVN0YXJ0IjoxNDcxMzU1NjAwMDEzLCJyZXNwb25zZUVuZCI6MTQ3MTM1NTYwMDAxOSwiZG9tTG9hZGluZyI6MTQ3MTM1NTYwMDA0MiwiZG9tSW50ZXJhY3RpdmUiOjE0NzEzNTU2MDAyMzEsImRvbUNvbnRlbnRMb2FkZWRFdmVudFN0YXJ0IjoxNDcxMzU1NjAwMjMxLCJkb21Db250ZW50TG9hZGVkRXZlbnRFbmQiOjE0NzEzNTU2MDAyMzMsImRvbUNvbXBsZXRlIjoxNDcxMzU1NjAyNDE4LCJsb2FkRXZlbnRTdGFydCI6MTQ3MTM1NTYwMjQxOCwibG9hZEV2ZW50RW5kIjoxNDcxMzU1NjAyNDMxLCJjaHJvbWVGaXJzdFBhaW50IjoxNDcxMzU1NjAwNDI0fX1dfQ'

It ended up in bad because none of the schemas could be found but that is OK.
I then retried it with the client's snowplow-mini instance and it didn't go through.
Not sure what the best next steps for debugging are?

I tried as well to my own snowplow-mini and it ended up in bad.  Could it be that the event was already sent and it is simply being marked as a duplicate on subsequent submissions?

Is that something Snowplow Mini does? We tried sending in a whole range events. All showed up up in either good or bad within 5 seconds, but each time we sent this particular combination, a certain structured event plus several contexts, nothing showed up. Each time we tried, it was also with a different event ID - so it was never a duplicate.
Let's close if we can't replicate.

It is something that Elasticsearch does.
Does removing the contexts let it work?
Does eliminating certain contexts let it work?

Yes to both questions.

Also, all payloads validate against their schema.

Is there then a particular context that when added broke it?

We didn't have time to test all permutations - so not sure.

Push back @BenFradet ?

I think this has to do with schema updates breaking the Elasticsearch index mapping.  Incompatible type additions are likely causing it to silently swallow events in this case.
What I mean by this is large mutative changes in a schema without bumping versions.
Perhaps a fix is to add a mapping reset button?

I think you're right - I think it's patching of existing schemas. Let's push back and keep considering what to do here...

Mini has been renewed since then and this issue has become obsolete.


[iOS] Update information to how install ios-deploy correctly

Update information to how install ios-deploy tools correctly via Homebrew.

Platforms affected
iOS
Motivation and Context

Update information to how install ios-deploy tools correctly via Homebrew.
Description

Testing

Checklist

[x] I've run the tests to see all new and existing tests pass
[x] I added automated test coverage as appropriate for this change
[x] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[x] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[x] I've updated the documentation if necessary

As soon as travis is finish running, I'll merge :)

Tests passed! :tada: Thank you for your contribution @mosabab


We can't join the room and high latency

nostrnests are very popular for Bitcoin community in Thailand now (Community for the Lonely)
But using it has problems
I've identified two significant issues with nostrnests that need attention: room access and high latency
Room Access Issue:
Users encounter difficulties joining rooms, preventing them from participating effectively
The problem persists across different browsers, such as Firefox and Microsoft Edge, Opera
High Latency:
Latency during conversations is unacceptably high, ranging from 2-20 seconds
This delay impedes smooth communication, causing inconvenience for users


Update editorWidget.background color

Fixes #57136
This makes the editor/suggest widget background color the same as the quick pick background color. This also helps the list selection color stand out more.

Before
After

I just pushed a commit to update the light bg color as well. Our theme already overwrites this in the light theme defaults so it's just making that the default in the color registry.
FYI @jrieken, this also applies to the breadcrumbs picker as breadcrumbPicker.background inherits from editorWidget.background:

Before
After

@rebornix ping


Fix a typo in the Connector documentation

Thanks!

Thanks, that was bothering way more than it should be :laughing:


Unable to get PDFJS global object

Hello All,
I guess I am facing issue while accessing PDFJS global object. From alert I have added I can see upto altert 3 I am getting , following alert is not showing up. Please help to resolve this issue. Code is attached for your reference.
Regards
SB
helloworld64.txt

Hi All,
Further info, I was trying to test this by simply converting that .txt extension to .html and was opening that .html in web browser

With PDF.js version 2.0, the global PDFJS object has been removed. Hence this issue, as filed, is no longer valid.
Also, when reporting an issue with a custom deployment of PDF.js, as outlined in https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md, you need to provide access to a complete (and runnable) example since just code snippets aren't helpful.


Command line option for skipping part of the script

During debugging, I often don't need to do a checkout of dependencies (um, ukca, ...), or run the configurator again. I typically comment out these calls then.
It would be convenient if we had a command line option(s) to:

skip any git/svn/fcm checkout
configurator (ok, I wrote: "and maybe even file find" - that's stupid, file_find fills the artefact store :) )

Additional suggestion: maybe the directories in which some dependencies are checked out could get a 'version' number. E.g. instead of checking out to science/jules, we would check out to science/jules-29007. This way we could handle this much better:
if the directory already exists, don't clone. If a directory with a different version exists, we could:

abort with a warning (leaving it to the user to remove it) or
even remove it (though one could argue about potential risks if a script recursively deletes files - any bug could seriously affect a user)
Maybe automatically ignore this directory in Fab (with a specific user warning)?


Build Failed on Xcode8.3.3 , macOS 10.13, cocos2d-x 3.16

Env: Xcode8.3.3 , macOS 10.13, cocos2d-x 3.16
this is the step, I did

use cocos command make out IOS library
copy libs
fllow this

$ git clone https://github.com/chukong/programmers-guide-samples.git
$ cd programmers-guide-samples/cpp
$ open proj.ios_mac/Programmers\ Guide.xcodeproj/

run on Xcode, failed

It seems like much framework find failed, for many of them is RED clolor
will you test this demo using cocos2d-x v3.16 on Xcode8.3.3 ?

I can test this today
On Mon, Oct 16, 2017 at 5:38 AM, drelaptop<EMAIL_ADDRESS>wrote:

Env: Xcode8.3.3 , macOS 10.13, cocos2d-x 3.16
this is the step, I did

use cocos command make out IOS library
copy libs
fllow this

$ git clone https://github.com/chukong/programmers-guide-samples.git
$ cd programmers-guide-samples/cpp
$ open proj.ios_mac/Programmers\ Guide.xcodeproj/

run on Xcode, failed

It seems like much framework find failed, for many of them is RED clolor
will you test this demo using cocos2d-x v3.16 on Xcode8.3.3 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chukong/programmers-guide-samples/issues/32, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHJQrnrc8YzmFQENGiGoojTZFBlW314fks5ssyP6gaJpZM4P6V-P
.

--
Community Evangelist
Cocos2d-x
Like us on Facebook!: https://www.facebook.com/cocos2dx/
Follow us on Twitter: https://twitter.com/cocos2dx
Our Blog: http://blog.cocos2d-x.org/
Our Programmers Guide: http://cocos2d-x.org/programmersguide/
Our Forums: http://discuss.cocos2d-x.org/
I am: @slackmoehrle

So there are issues. I have most of them worked out except this:
Undefined symbols for architecture x86_64:
  "_CTFramesetterCreateWithAttributedString", referenced from:
      _calculateShrinkedSizeForString(NSAttributedString**, objc_object*, CGSize, bool, int&) in libcocos2d iOS.a(CCDevice-ios.o)
  "_CTFramesetterSuggestFrameSizeWithConstraints", referenced from:
      _calculateShrinkedSizeForString(NSAttributedString**, objc_object*, CGSize, bool, int&) in libcocos2d iOS.a(CCDevice-ios.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

BTW. These samples need some updating. We were goin go automate the building process better and make each chapter run-able.

ok, I fixed this. Not it builds and runs, but I noticed I still have hard coded paths in a few places in the build settings. I can work on making this generic.

BTW, I am doing this in branch v3.16.

@drelaptop were you able to get this to build at least? I know it looks funny and needs to be fixed. I can put this on my list.

@slackmoehrle I will try it today, and then get the result

Build Failed on Xcode8.3.3 , macOS 10.13 Again

build error cocos2d.h file not found
much library not found, for example

SDKs/MacOSX10.12.sdk/usr/lib/libcurl.dylib

I can't find this file in my PC, but find libcurl.4.tbd tbd format file!
3.  I didn't find SDKs/MacOSX10.12.sdk/.. , should I download that SDK?

BTW, I build on branch v3.16, code at least

Sorry. Are you using v3.16 branch and getting this error? Did you change your include paths?

yes, I get the error on v3.16 branch. I didn't change anything, should I change include paths? how

Build Success on Xcode8.3.3 , macOS 10.13, Using v3.16
Solve Error Steps:

modify library paths one by one
change include paths, follow Creating And Using Prebuilt Libraries chapter
modify Linking paths
remove x86_64 on config Valid Architecture to fix error like

missing required architecture x86_64 in file...
Undefined symbols for architecture x86_64:

Just add the right frameworks, no need to remove x86_64 at all.
On Tue, Oct 24, 2017 at 3:46 AM, drelaptop<EMAIL_ADDRESS>wrote:

Build Success on Xcode8.3.3 , macOS 10.13, Using v3.16
Solve Error Steps:

modify library paths one by one
change include paths, follow Creating And Using Prebuilt Libraries
chapter
modify Linking paths
remove x86_64 on config Valid Architecture to fix error like

missing required architecture x86_64 in file...
Undefined symbols for architecture x86_64:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chukong/programmers-guide-samples/issues/32#issuecomment-338903938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHJQrjcABmV0XkjIf4CW2cIigW4er0G_ks5svZXcgaJpZM4P6V-P
.

--
Community Evangelist
Cocos2d-x
Like us on Facebook!: https://www.facebook.com/cocos2dx/
Follow us on Twitter: https://twitter.com/cocos2dx
Our Blog: http://blog.cocos2d-x.org/
Our Programmers Guide: http://cocos2d-x.org/programmersguide/
Our Forums: http://discuss.cocos2d-x.org/
I am: @slackmoehrle

how to find which is wrong, and add right frameworks
▶ lipo -info libcocos2d\ iOS.a
Architectures in the fat file: libcocos2d iOS.a are: i386 armv7

mean libcocos2d iOS.a didn't support x86_64 or not?

You must not have build the libraries the same way I did or something because I have this:
$ lipo -info libcocos2d\ iOS.a
Architectures in the fat file: libcocos2d iOS.a are: i386 armv7 x86_64 arm64

Command I used is cocos gen-libs -c -p ios -m debug, something else need to do?

@drelaptop would you like me to fix this to run in XCode 8, 9 and Android Studio?

@slackmoehrle oh! I hope so, but I think it's not a urgent things, and I prefer you finish the unfinished 4 items of docs first.

@drelaptop agreed. I just didn't want to lose track of this. I think I may re-write this a bit too at the same time. I will get this fixed in a few weeks. I a writing a Cocos Creator demo that is more important. I will write the docs too.


Add BlackList DEVEX-164

Added a black list so that login URLs and other sensitive URLs are ignored.
Fixed some module import omissions.

Result of Integration 1
Duration: 12 minutes and 11 seconds
Result: All 224 tests passed, but please fix 2 warnings.
Test Coverage: 63%

Result of Integration 3
Duration: 12 minutes and 17 seconds
Result: Build failed 2 tests out of 224

Result of Integration 4
Duration: 10 minutes and 40 seconds
Result: All 224 tests passed, but please fix 2 warnings.
Test Coverage: 63%


Revert "Mvtec 3d"

Reverts openvinotoolkit/anomalib#907 due to the failed tests.

@alexriedel1 I've merged your PR, but reverted it now since the tests are failing. Will you be able to check why the tests are failing?

@alexriedel1 I've merged your PR, but reverted it now since the tests are failing. Will you be able to check why the tests are failing?

Yes sure, will have a look into it today

@alexriedel1 I've merged your PR, but reverted it now since the tests are failing. Will you be able to check why the tests are failing?

Yes sure, will have a look into it today

Great, thanks a lot!


[MINOR] More image replay test cases

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ahuang98 I still saw lots of test failures, and when I checked them locally I actually was able to reproduce the below failures.  Can you take a look to see if you also agree these fail locally and then, assuming you agree, investigate as to why?
testTopicDualWriteDelta()
testTopicDualWriteSnapshot()
testControllerFailover()

Latest test run has 14 "new failing" which are all timeout related/unrelated - https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-14206/17/tests

Is there a downside to having deleteTopic in ZkTopicMigrationClient not delete configs? Otherwise changing the logging level seems okay to me.

@mimaison tagging you again just in case you have time to take a look
@mumrah I've added the logging change in the meantime - are we okay merging in the next week if we don't get a response?

@mimaison the PR was originally meant to introduce additional test changes, I believe @mumrah renamed it after I added the migration fix. I'll move the tests out and apply your suggestions, thanks!

@mimaison @mumrah I moved unrelated test changes over to https://github.com/apache/kafka/pull/15373. The latest commit 1c1eb7d addresses the comments left here (mostly imports)

There's quite a few failures related to ZkMigration in the last CI run: https://ci-builds.apache.org/job/Kafka/job/kafka-pr/job/PR-14206/22/testReport/

Thanks @mimaison, looks like this is because I split out the TopicsImageTest changes into a separate PR. The migration tests depend on the DELTA1_RECORDS defined there so I moved over changes from TopicsImageTest as well.

@mimaison could you help merge this if this looks good to you? :)


v3.3.0 release (fixes #4310)

Preparing the 3.3.0 release.
Release checklist below was copied from https://github.com/microsoft/LightGBM/pull/4169.
Release checklist:

[x] Update VERSION.txt number.
[x] Update version in Appveyor config file.
[x] Update version in configure file of R-package: /gha run r-configure.
[x] Run R valgrind checks after all PRs are merged: /gha run r-valgrind.
[x] Run R Solaris checks after all PRs are merged: /gha run r-solaris.
[ ] Push commit with v* tag to trigger GitHubRelease action at Azure Pipelines.
[ ] Convert automatic GitHub release from Draft to normal one.
[ ] Update stable tag at GitHub.
[ ] Trigger RTD build for new tag.
[ ] Upload release to PyPI.
[ ] Upload release to CRAN.
[ ] Update cran-comments.md when new release is accepted on CRAN.
[ ] Upload release to NuGet.
[ ] Update version and hash in Homebrew formula.

Necessary PRs and other Changes
I don't believe any additional PRs remain (we had been tracking this all along in #4310).

[x] Add @shiyu1994 as maintainer in R-package/DESCRIPTION

/gha run r-configure

/gha run r-valgrind

/gha run r-solaris

I'd like to point out that there's at least one blocker left for a potential CRAN release: https://github.com/microsoft/LightGBM/issues/4598

I'd like to point out that there's at least one blocker left for a potential CRAN release: #4598

@david-cortes we are not treating that as a blocker in releasing to CRAN. The code that issue describes has been in every previous LightGBM submission to CRAN and has not been flagged as problematic.
It would be great to address it at some point but I don't favor delaying this release until that issue is picked up.

I'd like to point out that there's at least one blocker left for a potential CRAN release: #4598

@david-cortes we are not treating that as a blocker in releasing to CRAN. The code that issue describes has been in every previous LightGBM submission to CRAN and has not been flagged as problematic.
It would be great to address it at some point but I don't favor delaying this release until that issue is picked up.

But that's because it was only accessible from tests that were skipped. As those tests are now unskipped, they'd either have to be set to skipped again, or the issue addressed, otherwise it might randomly fail their tests (particularly solaris).

But that's because it was only accessible from tests that were skipped

This is not a correct statement. LGBM_DatasetCreateFromCSC_R is invoked dozens of times across many of the R package's tests, since the agaricus datasets used for testing are sparse matrices. Any test calling lgb.Dataset() or lgb.train() or lgb.cv() on a dataset built from that data will end up using LGBM_DatasetCreateFromCSC_R.
https://github.com/microsoft/LightGBM/blob/a77260f03eb735923125024b0f36df9f63a6e0f3/R-package/tests/testthat/test_basic.R#L10
library(lightgbm)
data(agaricus.train, package = "lightgbm")
class(agaricus.train$data)

[1] "dgCMatrix"
attr(,"package")
[1] "Matrix"

https://github.com/microsoft/LightGBM/blob/a77260f03eb735923125024b0f36df9f63a6e0f3/R-package/R/lgb.Dataset.R#L263-L269

@shiyu1994 are you ok with releasing the current state of this branch as 3.3.0? I'd like your approval before we merge this and start pushing to package managers.

Sure. I'm ok with this.

Thanks all!
Before we merge... @StrikerRUS did you want https://github.com/microsoft/LightGBM/pull/4637 to make it into 3.3.0? If so we'll need to merge latest master here.

I'd like to ask to not merge new large PRs with major features for one or two weeks after releasing v3.3.0. This will ease the process of creating v3.3.1 hotfix release if that will be needed in case of some critical bugs in v3.3.0 we might get reports about.

/gha run r-solaris

/gha run r-solaris

Ok, Solaris tests passed! Thanks for your patience, everyone.
I'm going to merge this and start the work on the remaining checklist items.

GitHub release for 3.3.0 has been published: https://github.com/microsoft/LightGBM/releases/tag/v3.3.0
and tag v3.3.0 has been pushed: https://github.com/microsoft/LightGBM/tags
here's the Azure Pipelines build triggered by the new tag: https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=11089&view=results

The jobs at Azure Pipelines completed successfully. Just submitted to CRAN!

I did the renaming we talked about in https://github.com/microsoft/LightGBM/pull/4169#issuecomment-818311840 like so:
wget \
    https://github.com/microsoft/LightGBM/releases/download/v3.3.0/lightgbm-3.3.0-r-cran.tar.gz \
    -O lightgbm_3.3.0.tar.gz

@shiyu1994 please check your email. You should get an automated email from CRAN asking you to confirm this submission.

Great, thank you!

Source distribution of the R package is now available on CRAN.
https://cran.r-project.org/web/packages/lightgbm/index.html
We'll have to check https://cran.r-project.org/web/checks/check_results_lightgbm.html to see how the automated checks there go. Hoping they succeed!!

@david-cortes Thank you very much!


Broken Link Fix

https://github.com/Ngugisenior/sql-mysteries/pull/1/commits/131778acdbb677d0583298143a4c782892352694

Thank you!


[incubator/cassandra] Replaces '_' with '-' in keyspace name when constructing a CronJob name

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Keyspaces can be assigned a name containing '_' chars but CronJobs cannot. So if a keyspace name is set to 'some_keyspace_name' then the cronjob name will contain '_' which is not allowed.
This PR contains a very small fix that transforms '_' to '-' when building the name for a CronJob.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md

/ok-to-test

/lgtm
Nice catch @anbarium and thanks for your contribution!


fix(grid): incorrect x and y passed to onStop

This was caused by onStop erroneously recalculating coordinates,
which is not necessary / should not happen in the real world, as mouseup
and touchend should not pass clientX and clientY values meaningfully
different than the last corresponding move event. In fact, they are already
ignored by <Draggable>.
For this reason, we can simply trust the lastX and lastY in onDragStop,
and pass those back.
Fixes #413, bokuweb/react-rnd#453

@nicholaschiang could you verify this works for you - simply pin react-draggable to this git branch in your package.json resolutions?
"react-draggable"<EMAIL_ADDRESS>

Just added it @STRML and it looks like the issue is still there:

You'll notice how the draggable keeps jumping a couple of pixels after dropping (there are some other unrelated issues shown in that GIF too... feel free to ignore them until I finish debugging on my end).

@STRML I also created a little repro of the same (or, at least, a similar) problem I was having when dynamically resizing the grid snap and RND size.
https://codesandbox.io/s/white-water-xrqp2?file=/src/index.js
You'll notice in that repro that the RND keeps jumping around and doesn't snap correctly to the resized grid (even though we're using the { x: data.lastX, y: data.lastY } workaround proposed in #413):

Ideally, the X position should always be a multiple of the RND's width (displayed on the parent) and the Y position should always be a multiple of the RND's height (also displayed on the parent).

Any idea on on a timeline for this? @STRML

@nicholaschiang could you verify this works for you - simply pin react-draggable to this git branch in your package.json resolutions?
"react-draggable"<EMAIL_ADDRESS>

The repository does not exist at this link anymore.
Also, when trying to checkout include that branch in this repo as an npm dependency, the source code for this not repo is not included in ./node-modules because the package.json in react-grid-layout/react-draggable does not include lib in the  [files](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#files) field, or have./build committed to that branch.


Resolves #1752, ThreeTenBP is now included via 'implementation'.

The only problem I see with this, is that using api allows consuming apps to see the classes that are used and returned by this library. E.g. in the callback or with methods like selectedDate(): LocalDate. If we remove that api reference, then consuming apps have to explicitly add the dependency to ThreetenBP if they don't already have it.

Well, but that would only cost a line in the docs, but actually, users of the library are not able to use e.g. the ThreeTenABP library.
In my case, I need this lib, since the standard ThreeTenBP library causes an error 'No time-zone data files registered' on devices loading the time-zones of the ThreeTenBP lib too slow. ThreeTenABP provides another loading mechanims, which prevents this error.

Right - maybe ThreeTenABP should be used here instead because of those reasons

Well, sounds appropriate, since this is an android library.

Alternatively, we could use Calendar and not require an external dependency 😄

Okay!


How to use variable in Regex?

This is my code and i wanted to parsed a dynamic string from an array unfortunately it gave an error saying Type Error: pattern.pattern.exec is not a function. I believe im doing it wrong becaue i dont know how to use a variable on regex string
                  {this.state.data.map(names => (
                    <ParsedText
                      parse={[
                        { pattern: names, style: { color: '#ff0000' } }
                      ]}
                    >
                      some long texts here........
                    </ParsedText>
                  ))}

map function returns a new array. Are you sure you want to return an array of ParsedText?

If anybody is still wondering, you can use variables by using RegExp
myVariable = 'styleThisWord'

...
pattern: new RegExp(myVariable)
...


link error by vs2022 LNK2019

When I build vsgExample/ui/vsgimgui_example, I got the error
error: vsgImGui.lib(implot.obj) : error LNK2019: 无法解析的外部符号 "unsigned int __cdecl ImGui::GetColorU32(unsigned int)" (?GetColorU32@ImGui@@YAII@Z)，函数 "bool __cdecl ImPlot::ShowLegendEntries(struct ImPlotItemGroup &,struct ImRect const &,bool,struct ImVec2 const &,struct ImVec2 const &,bool,struct ImDrawList &)" (?ShowLegendEntries@ImPlot@@YA_NAEAUImPlotItemGroup@@AEBUImRect@@_NAEBUImVec2@@32AEAUImDrawList@@@Z) 中引用了该符号
build\windows\x64\release\imgui.exe : fatal error LNK1120: 1 个无法解析的外部命令

Platform：win10 vs2022
vsgImGui commit 0bbb45a68ba6b699b8f418a585f45363be1540c1 tag v0.3.0
vsgExample commit 9d3ae99f4362d271d3a16e3f4ad50a627ada6667  tag v1.1.4
vsg commit 967e6327790c8553e806023de03c0b11ec192db4 tag v1.1.4

I haven't seen this issue myself under Linux or Windows, and others have been using vsgImGui under Windows fine so I don't know why you've had issues while others haven't,
I've pulled in the latest ImGui v1.90.8 today and tagged a vsgImGui-0.4.0 release for this.  Could you try updating to v-0.4.0 or vsgImGui master to see if the issue is fixed.

when use the cmake command with the arg ‘-A x64’，got the error.
cmake -G "Visual Studio 17 2022" -A x64

When not use the arg '-A x64', it pass the link.
cmake -G "Visual Studio 17 2022"

I think the problem has been solved.

Use cmake -G "Visual Studio 17 2022"  to generate vs project, then build the vsgimgui project, and install it.
Rebuild vsgimgui_example, no link error now.


Proposal: How to use Type system to force use of decorated errors

First off: thanks for a really great library and hope this is the right place for this.
Within the confines of my particular application I'd really like to make sure that ALL errors have been decorated with a stack trace. I feel like the best way to do this would be with the type system, perhaps:
func MyRecordCreationFunction(some args...) (record, errors.ErrorWithStack) {
   record, err := orm.CreateObj("...")
   if err != nil {
     return nil, errors.WithStack(err)
   }

   err = record.hydrate()
   if err != nil {
     return nil, err // <- fails to compile, type error does not implement method StackTrace() ...
   }

   return record, nil
}

Unfortunately this is quite challenging with the types that this package decides to export right now. Is there another way to achieve this? Or is this worthy of a PR?
Thanks for your time.

Is the problem that record.Hydrate() returns error, not a type that exports
Stack trace?
On Sat, 11 Feb 2017, 07:01 John Barker<EMAIL_ADDRESS>wrote:

First off: thanks for a really great library and hope this is the right
place for this.
Within the confines of my particular application I'd really like to make
sure that ALL errors have been decorated with a stack trace. I feel
like the best way to do this would be with the type system, perhaps:
func MyRecordCreationFunction(some args...) (record, errors.ErrorWithStack) {
record, err := orm.CreateObj("...")
if err != nil {
return nil, errors.WithStack(err)
}
err = record.hydrate()
if err != nil {
return nil, err // <- fails to compile, type error does not implement method StackTrace() ...
}
return record, nil
}
Unfortunately this is quite challenging with the types that this package
decides to export right now. Is there another way to achieve this? Or is
this worthy of a PR?
Thanks for your time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pkg/errors/issues/103, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAcA1LbEhCLIVHLesncZD19PIzNzuPbks5rbMH_gaJpZM4L9yzk
.

@davecheney that's right, my app is made up of code I've written - where I can always use this library and other libraries like sqlx where I have to wrap things.

I'm not quite sure what you want to change in the errors package, the code
you showed worked fine wrt errors.WithStack.
On Sat, 11 Feb 2017, 09:44 John Barker<EMAIL_ADDRESS>wrote:

@davecheney https://github.com/davecheney that's right, my app is made
up of code I've written - where I can always use this library and other
libraries like sqlx where I have to wrap things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pkg/errors/issues/103#issuecomment-279087268, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAzQSGbeLW2GLARCtJ4nC4T-eSFIBks5rbOhjgaJpZM4L9yzk
.

Ahh, that's the point - excuse my edit. I want it to fail! I want to reject any error that hasn't captured a stack trace.

Any news on did? Did you find a solution?
I would love to use the type system to assure me that my program returns decorated errors all over.

I guess that it could suffice to define something like this in my code:
type ErrorCauser interface {
    Error() string
    Cause() error
}

Then function signatures can look like:
func doThing() errorCauser

I have implemented the best solution that I could think of in a new package:

https://github.com/aviau/errors

Feel free to comment. It is mostly compatible with pkg/errors.

Closing, if you want this use https://github.com/aviau/errors !


dragstart 为啥没有

dragstart 为啥没有

https://caniuse.com/#feat=dragndrop ?

having dragstart find something would be helpful. if appropriate https://caniuse.com/#feat=dragndrop.

Available at https://caniuse.com/#feat=mdn-api_document_dragstart_event


Fixed tagging NPEs - includes new ContentLayers layer widgets, IME focus policy adjustment (Resolves #1397)

Fixed tagging NPEs - includes new ContentLayers layer widgets, IME focus policy adjustment (Resolves #1397)
The tangible goal of this PR is to fix issues found with the tagging system in the Example app. Before this PR, the tagging examples were producing NPEs on every character the user entered.
To fix the tagging experience, a few changes were made:
Content Layers
Despite my best attempts to hack the Flutter build order, every time the user inserted a new character into a tag, it would trigger a build timing problem where the caret overlay would try to inspect the document layout before the document layout was run.
I was unable to further hack the Flutter build order to resolve this. At this point, I had to bring some level of new responsibility to the widgets that are displayed as layers.
As of this PR, any widget that's provided as a layer in ContentLayers must be a subclass of ContentLayerWidget. I've created a few options to facilitate different use-cases:

ContentLayerProxyWidget - Let's users display regular widgets that don't care about the content layout. This is essentially an escape hatch for when you don't care about any of the rest of this.
ContentLayerStatelessWidget - A stateless widget that wants to base its widget tree on the content layout render object.
ContentLayerStatefulWidget - A stateful widget that wants to base its widget tree on the content layout render object.

IME and Focus
User tag and action tag demos display a popover, where the user can press up/down to select a tag. As a result, the popover needs to hold primary focus, meaning SuperEditor has non-primary focus. Previously, we were automatically closing the IME when SuperEditor loses primary focus. This focus policy breaks expected behavior because the user can't type anything once the popover appears. Therefore, this PR changes the default focus policy so that SuperEditor keeps the IME open as long as it has focus, even if it's not primary focus.
Also related to focus is Mac OS selectors. When SuperEditor moves to non-primary focus, and some other part of the UI takes primary focus, like a popover, Flutter jumps in and responds to certain keys, like arrow keys. For example, Flutter tries to move focus to other widgets when the user presses arrow keys. We don't want this. We want arrow keys to either move selection in the popover, or move the caret in SuperEditor. To prevent Flutter from taking over, when SuperEditor has non-primary focus, we no longer ignore the key press on Mac. Instead, we respond to all key presses on Mac when SuperEditor has non-primary focus so that we can block Flutter from doing things we don't want.

CC @miguelcmedeiros @Jethro87 @jmatth - This PR will break any custom content layers/document layers. The fix should be pretty straightforward - it requires using a custom version of stateless and/or stateful widgets. Within those widgets you can include traditional widget trees.
There are also some minor focus policy changes that could conceivably impact you.


Support specifying annotations for devworkspace pods in the DWOC

What does this PR do?
Provides config.workspace.podAnnotations field for DWOC to specify annotations for the devworkspace pods
What issues does this PR fix or reference?
https://github.com/devfile/devworkspace-operator/issues/1270
Is it tested? How?

Deploy DWO by using this catalog source and installing DWO from OperatorHub:

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: devworkspace-operator-catalog
  namespace: openshift-marketplace
spec:
  sourceType: grpc
  image: quay.io/dkwon17/devworkspace-operator-index:annotations-dwoc
  publisher: Red Hat
  displayName: DevWorkspace Operator Catalog
  updateStrategy:
    registryPoll:
      interval: 5m

Update the devworkspace-operator-config DWOC by adding an annotation:

config:
  workspace:
    podAnnotations:
      test-annotation: test

Create a workspace:

oc apply -f ./samples/plain.yaml -n openshift-operators

Once the workspace pod is created, check the pod annotations and verify that test-annoation: test exists:

metadata:
  annotations:
    test-annotation: test
    ...

PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Tested on Minikube and works as expected :+1:

@dkwon17 I haven't debugged this to verify, but I think the CI is failing because we're now creating a workspace pod that has an empty map[string]string of annotations, which gets converted into nil when the object is created on the cluster. As a result, the SyncObjectWithCluster's diff function for pods is probably seeing that the pod on the cluster has nil annotations, when it expects it to be an empty map[string]string of annotations. This would be why we're seeing printed diffs in the CI logs:
    	... // 2 ignored fields
    	Spec: v1.DeploymentSpec{
    		Replicas: &1,
    		Selector: &{MatchLabels: {"controller.devfile.io/devworkspace_id": "workspace05b48af9f4d14dd4"}},
    		Template: v1.PodTemplateSpec{
    			ObjectMeta: v1.ObjectMeta{
    				... // 9 identical fields
    				DeletionGracePeriodSeconds: nil,
    				Labels:                     {"controller.devfile.io/creator": "", "controller.devfile.io/devworkspace_id": "workspace05b48af9f4d14dd4", "controller.devfile.io/devworkspace_name": "test-devworkspace"},
  - 				Annotations:                map[string]string{},
  + 				Annotations:                nil,
    				OwnerReferences:            nil,
    				Finalizers:                 nil,
    				ManagedFields:              nil,
    			},

I think this function would be worth checking to see how it's behaving. Looking at its implementation, it doesn't seem like this would cause the diff to conclude that the cluster and spec objects are different, but maybe something subtle is going on.

Thanks for the feedback, I updated the PR, I learned that before, it was this check always caused the operator to try updating the deployment:
https://github.com/devfile/devworkspace-operator/blob/b49427cecf4ba036a7587be4e7319b4dfec42dcf/pkg/provision/sync/diff.go#L58

I've squashed some commits and reviewed: https://github.com/devfile/devworkspace-operator/pull/1267

I've squashed some commits and reviewed: #1267

Thank you :)
Sorry, I should have specified earlier, but it's probably worth updating the commit titles (and maybe descriptions) just to clarify a bit more what these commits change.
For example, b7ccba1 (#1271) could be titled as: "Add config.workspace.podAnnotations field to DWOC".
2bfdcd4 (#1271) could be titled as "Add pod annotations from DWOC & podAdditions to devworkspace pod" and the description could include "Fix #1270" to link the original issue to the commit.
Also.. I just had a second thought about a detail in this PR so please hold off on merging.


Hide create swift project button by default

Adding our own button to the welcome page by default is a tragedy of the commons issue. I'd like to keep the button available, but hide it behind a setting that the user can enable if they really want it.

Other language extensions add buttons to the welcome page eg Java. Can we keep the option but default it to true.

Yeah, we can keep it true for now. I'm just concerned that the more extensions that add to this the more bloated it's going to become. At least people can disable it if they don't want it this way.


How to reset input?

First of all well done for the great work!
I'm wondering if there is an easy way to reset the input after a value has been chosen?
I've tried the following but it doesn't seem to be working:
<input auto-complete
      [(ngModel)]="myElement"
      [source]="elements"
      (valueChanged)="handleElement($event)"/>

export class ElementComponent {
  elements: Element[];
  myElement: Element;

  handleElement(element: Element): void {
    this.myElement = element = null;
  }
}

My bad, I was just making a mistake while resetting, the correct code was this:
this.myElement = new Element();


.Send delay not delaying

I've been experimenting with your message queue a bit.
I've been really impressed with it overall, but I can't get the worker.send delay to actually delay the message.
For my test I was attempting to send the received message after a 60 second delay.
 worker.on( "message", function( msg, next ){
    worker.send(msg, 60);`
    next()`
  });`

However the message is processed immediately.    Am I missing something?

I will have a look at it and check it next week.

After a short look into the code I can provide a quick workaround.
Just add an empty function to .send( msg, 60, function(){} ).
I will fix the argument dispatch next week, to make the callback in combination with the delay optional.

Yep that does indeed fix the delay.
Thank you.


Makes GENX opt in

Closes Issue #263

Addresses Issue #262

It got removed by accident some how when I was messing around with the header files. Sorry 🤷♂


No warning given for duplicate fields

do_not_use.pdf
When this PDF with normalized field names is run through the weaver, there are 4 fields that contain duplicates. See https://github.com/SuffolkLITLab/FormFyxer/issues/10.
There's no warning given for the duplicates, although the field type is detected as None.

Several things have changes since this issue:

the issue with the given PDF was that it had radio buttons; with #754, it's not an issue anymore, and doesn't give you duplicate fields anymore
Gavel (i.e. Documate) doesn't let you give things duplicate names; it'll automatically add a 1 or 2 at the end, which is neat (if we do ever get to help them with their tool, it'd be cool to make ours automatically the __1 or __2 that the Weaver expects.
This might seem weird, but duplicate fields just work now? I tested in Firefox, Chrome, Evince, and Acrobat, and they all behave slightly differently when editing (some will change all of the fields to the newly edited val, others will only update one), but they all display the PDF from docassemble correctly. I'm sure there was a specific reason we avoided duplicate names, but do we remember what specifically it was? Like, did it break docassemble or Acrobat, or was it just subpar behavior?  I tested with
do_not_use_actual.pdf, which has three undefined_ah fields. The Weaver and docassemble seem to handle them well now.

Can confirm this doesn't seem to be a problem anymore. Going to close this stale issue.


display balance in wallet page

Title: [Persona name] should (not) be able to [action]
Currently:
[What happens now in the regression]
Expected:
[What the correct behavior should be]
STEPS TO REPRODUCE:
[If needed, add steps to reproduce]
REFERENCE:
[Link or attach screenshot(s) to story if relevant]
Possible fixes:
(If you can, link to the line of code that might be responsible for the problem)
Related issues

Related Merge Requests

/label ~bug

related to
https://github.com/particle4dev/dicoapp-e/issues/6


Support new option to force all groups to be returned per segment

Currently per-segment results from an aggregation are trimmed to Max(5000, <query limit> * 5). This can result in incorrect results when these partial results are combined by the broker, most obviously where the ordering of groups is opposite the value being used to do the ordering.
For example, assume a table with two fields, studentId and testScore. If there are multiple test scores per student, and rows for the same student can be stored in two different segments, and there are more than 5000 unique student ids in each segment, then this query is problematic:
SELECT studentId, min(testScore) AS lowScore
  FROM testResultsTable
  GROUP BY studentId
  ORDER BY lowScore DESC
  LIMIT 10

If Student1 has a single row with a testScore of 0 in segment A, and that isn't one of the highest 5000 group results from that segment (likely), then it doesn't get returned to the broker. If Student1 also has a single row with testScore of 100 in segment B, and this is one of the top 5000 results from this segment (likely), then it will be returned to the broker.
So now when the broker recreates the combined aggregation results for Student1, it appears that the low score is 100, and it gets returned as one of the top 10 results...which isn't correct.
In this situation, the only way to get accurate results is to return ALL of the groups from each segment, so that the broker can calculate correct results. You can force this by using a very high limit, but (a) you'd need to know the max cardinality of of groups for any segment that participates in the query, and (b) the broker is doing a lot of wasted work in generating a very large result that will mostly be ignored.
@Jackie-Jiang has suggested supporting a new option (e.g. OPTION(noGroupTrim=true)) which would force all groups to be returned to the broker.

I see various GroupByUtils.getTableCapacity() methods that calculate the result trim size, but some of them only take a limit (without query context).
And I see existing options that seem related:
        public static final String ENABLE_SEGMENT_TRIM = "enableSegmentTrim";
        public static final String MIN_SEGMENT_TRIM_SIZE = "minSegmentTrimSize";

Though the way these are used isn't obvious to me.

OK, I see a recent issue - https://github.com/apache/pinot/pull/7052. Hoping @Jackie-Jiang can explain whether what we discussed is just an extension to this, or something very different.

@Jackie-Jiang clarified - PR #7052 was for segment-level trimming, versus server-level trimming.

Looks like the only change needed would be in GroupByUtils.getTableCapacity(QueryContext queryContext), to use the new options to return a different trim value. Though maybe rename to something like getServerGroupTrimSize(), and use a different call (getBrokerGroupTrimSize()?) that's used by GroupByDataTableReducer.getIndexedTable()

PR #7241 handles this - so closing the issue. Support is via OPTION(minServerGroupTrimSize=<value>); if you use -1 for the time size, trimming is disabled.


Flatten HAL and move common content to crate root

~WiP: I published this PR in parallel to #424 for review purposes. Preferably #424 is going to be merged in first; thus, samd{1,2}1 modules will be absent and HAL structure will become much cleaner.~
#424 is already in.

Incorporate common/mod.rs into lib.rs
Create a shim implementation of common module inside of lib.rs for backward compatibility
Removed common/mod.rs
Moved common/* to crate root

Long term goals note:

Get rid of the shim as soon as API breakage is acceptable (BSCs + examples are reworked)
Make other implementation-leaking modules (thumbv6m, thumbv7em) private

@jessebraham, should we move forward with this?


Тестируем обновление ченджлога

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.49%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6677

Relevant Lines:
7511

💛  - Coveralls


Trim base64 padding

One way to fix #18
Length seems to be calculated correctly this way

@namaggarwal any thoughts on my solution?


RUNC troubleshooting documentation request

Add troubleshooting documentation for RUNC issues on helm install.
Suggested solution

Locate the path where the runc binary in your cluster using which runc for instance
Set the following environment variable when running the helm install command --set nodeAgent.env[0].name=<RUNC_PATH>,nodeAgent.env[0].value=/run/runc

we are probably moving this section into a different repository since it will be more appropriate


Sketch Artboard no longer working

I can drag images to Skala Preview; however, I can't use Command + P to preview artboards from sketch anymore. It gets stuck on a black 1x1 square (see screenshot).
I'm using the latest version, 207, and macOS High Sierra 10.13.2.

Still not working

@nigharsh Were you experiencing the same issue as the OP?
If so, the log output described in the troubleshooting section would be helpful. Otherwise please provide some specifics of how you're using the plugin.


Relationship Criteria Fields: Field ResponseStatus does not exist on the child object.

Hi Andy,
I am having problems creating a rollup of the SurveyInvitation object to a custom object, TASKRAY__Project__c. I am trying to get the number of completed surveys on a project.
I get the following error messages when I try to save my rollup:

Relationship Criteria Fields: Field ResponseStatus does not exist on the child object.
Relationship Criteria: Relationship Criteria 'ResponseStatus = 'Completed'' is not valid, see SOQL documentation http://www.salesforce.com/us/developer/docs/soql_sosl/Content/sforce_api_calls_soql_select_conditionexpression.htm, error is 'No such column 'ResponseStatus' on entity 'SurveyInvitation'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.'

However, I can run the following SOQL on workbench without any issues:
SELECT Id,Project__c,ResponseStatus,Survey_Name__c FROM SurveyInvitation where ResponseStatus = 'Completed'

Thank you for your help!
Kris

Andy... anything that can be done in regards to this?
Thanks!
Kris

@kryan0618 it looks like this field came with v44 and I think DLRS is only up to v42. The API version of the classes will need to be updated to support this field.
CC @afawcett

I have opened a new issue #831 that will resolve this hopefully in the next release. For now you could create a custom formula field that mirrors the missing field and roll that up instead. Or you could go with the unmanaged version of DLRS and update the API numbers yourself, but that could cause you some longer term maintenance issues.

Good workaround @JimBTek . WIll close this issue as its indeed resolve by the API upgrade issue you raised. 👍


Revert "Deploy cesiumjs.org branch to cesiumjs.org"

Reverts AnalyticalGraphicsInc/cesium#6530

@ggetz, thanks for the pull request! Maintainers, we have a signed CLA from @ggetz, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks, once this finishes, I'll verify deploys are working as expected again and then merge.

Thanks, looks like deploys are going to the correct place again.  Everyone will need to merge master into their branches (CC @lilleyse @bagnell )


Huge number of SMSs for backup

Hi. Thanx for this app. Vs.: 1.5.10, phone: LG G3.
I used it about 6 months ago, but somehow it did not continue. I reinstalled it, and then did a backup. I thought only the last six months would be dealt with, but it backed up over 4300 SMSs. Huh? I do not even have that many on my phone. And my phone has a 500 message limit. And afterwards, the SMS folder at Gmail only increased by about 100 messages. So where did they all go?
Confused.
Thanx for any info!
Aharon Naiman

I also observed a higher amount of messages being backed up or restored than messages in my IMAP folder. My guess (!) is: since SMS are limited to 160 characters, longer message are send as 2 or more messages. Today's phones do this transparent to the users and SMS Backup+ saves them as one e-mail, but during restore and backup they are counted message by message. But again: It's just an assumption.

@Woi that's very likely the case

@jberkel What comes to my mind is either count Multi-SMS as one message, so that the numbers match. Or just be transparent to the user with something like "Saving X messages to Z emails."or "Saving X SMS and Y Multi-SMS (Concatenated SMS, Long SMS) to Z emails"


[ QUESTION ] There is any alternative to persiste state like HydratedBloc?

You can use the HydratedMixin, check on the docs here.


encoded-compare: false positive of YAMLEq

https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/integration/repo_test.go#L905

@viceice fixed, expected in the next patch release of golangci-lint.
thanks!

thanks 🙏


remove notebook files for modules 0-5

Moved .ipynb files to the content folder.

Looks good; merging.


Removed aztro from resources and Readme

This PR deprecates the Aztro API by removing it from the public-apis repo's resources and updating the Readme to reflect its removal.
No additional changes.

Thank you!


Redirect invalid in https://accounts.google.com/o/oauth2/auth

Using gdrive 2.1.1, trying to run command "./gdrive-linux-386 about", the parameter argument in &redirect_uri=urn:ietf:wg:oauth:2.0:oob is invalid.
See https://developers.google.com/identity/protocols/oauth2/resources/oob-migration?hl=en
Thanks

same!

same!

same issue 400 error code from google.

same!

https://github.com/prasmussen/gdrive/issues/645#issuecomment-1261333851
Try that. works.


Add ability to pause state seeking

In a breaking-glass scenario, a user should be able to explicitly pause a state seeking. The instance is placed to an explicit "paused" state until it's unblocked.
An extension of this is to have a reconciliation policy that dictates how reconciliation process should be handled in the case of errors.

Another policy candidate is to "stop after n tries". There's also a proposal of "skipping getting current state" but that needs further discussion.


Folia support

Adds support for Paper's multithreading Folia project.
Code has been tested with Paper 1.21.1 and Folia 1.21.1

I don't know what is Folio.
So you should explain the Folio to me. I have issues about is Native Spigot works with that code?

@adabugra Could i request to take the jar which supports Folia?


Extra data, localizations, search functions

Closes #1 and addresses #2 . Library I think is finished now.
I'm at over 4.3 million lines of code contributed to this, the binaries can get as large as 413M, and scc calls this a 185 million dollar project with docs. Emoji was a mistake.

@richardanaya If everything looks good can you publish the new version to crates.io?


Cannot find module package.json

Seems like there's an issue with<EMAIL_ADDRESS>I can't reproduce it on 0.3.1. I went ahead and created an issue on that repo: https://github.com/ember-cli/babel-plugin-filter-imports/issues/19
Might be worth checking out. Thanks

This is my fault for not having updated the configuration. I usually test ember-attacher on my side projects, but forgot to run in prod mode, which hid this error. Really sorry about that! I'll mull this over a bit to see if I can prevent something similar from happening in the future.
For now I'm digging into a fix

Thanks! I didn’t know where the problem was because I looked into configuration and it seemed to be fine. Let me know what you find!


Implement shift+XOR instructions for amd64 native backend.

This PR relies on #105 - please hold off on review till the former is ready.
This adds support for a few more instructions that are frequently used in math heavy computations (the kind that benefits greatly from AOT compilation).

Codecov Report

Merging #109 into master will decrease coverage by 2.94%.
The diff coverage is 65.12%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
- Coverage    68.9%   65.96%   -2.95%
==========================================
  Files          33       40       +7
  Lines        3345     3916     +571
==========================================
+ Hits         2305     2583     +278
- Misses        783     1067     +284
- Partials      257      266       +9

Impacted Files
Coverage Δ

wasm/operators/op.go
75% <0%> (ø)
:arrow_up:

exec/internal/compile/compile.go
0% <0%> (ø)

exec/internal/compile/scanner.go
0% <0%> (ø)

exec/internal/compile/native_exec.go
100% <100%> (ø)

exec/func.go
76% <100%> (+0.48%)
:arrow_up:

exec/native_compile_nogae.go
100% <100%> (ø)

exec/native_compile.go
65.9% <65.9%> (ø)

exec/vm.go
85.01% <71.42%> (-1.76%)
:arrow_down:

exec/internal/compile/amd64.go
79.75% <79.75%> (ø)

exec/internal/compile/allocator.go
81.81% <81.81%> (ø)

... and 7 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a76146c...54ca604. Read the comment docs.

Rewritten into #115.


Passing the appWaitDurationParam to appium-adb startApp method

This is required for appium/appium#780

👍

Thanks for this! This is great!
One final piece to the puzzle is to add the capability to the list here.

Published in<EMAIL_ADDRESS>


Support different file formats for config

Thank you for your hard work!
I have a question about supported config file format. Will it be possible to use format other than java properties format (yml etc)?

Konf is a similar configuration library, which supports YAML and many other formats (JSON/HOCON/XML/TOML/etc). Give it a try.

@uchuhimo thank, I will try it. My colleague is already your library

You can write an implementation of the Configuration interface to read configuration from other sources.  On our project, for example, we have implementations that read from environment variables configured in CloudFoundry YAML manifests, from JSON objects, etc.


Github empty status

Hey, everyone😉
Recently, I've found one thing that's kinda annoying.
So that, I wanna propose a new feature, although it can be a fix or something.
As for me, it'll be a nice idea to disable expanding that small status container while hovering if status is empty at all.
To see an example, you can enter my profile by following the link below:
https://github.com/Krausso
Thanks for your attention!
Have a nice day!

I don't know what you're referring to, please include a screenshot. I don't see anything expanding on your profile or my profile

Good morning:) I mean this container with an electron emoji.
Now it's hovered(expanded)

And now it's not

I see it now. This might be doable by dropping the margin added on hover and readding it on .user-status-message-wrapper > div, which only exists when the text exists


[Mongoose Traveller 2e] Remove id's from tabs

Removed id's from tabs and replaced with action button/sheetworker method.
Changes / Comments
The use of id's for tabs in this sheet has been raised as a problem in the forums twice in the last six months that I have seen.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

The use of ID is explicitly discourage in the documentation. It even has it's own Section due to how large impact it has: https://wiki.roll20.net/BCS#Only_Use_Classes.2C_not_IDs
The Character Sheet documentation is updated continuously, so I recommend to check it frequently.
The radio input based solution would have otherwise been fine if the IDs are removed, but switching to the button-based solution is a smart move anyway.


NO-JIRA: chore: remove Konflux pipelines from main-rhtap

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main-rhtap@72492fc). Learn more about missing BASE report.

Additional details and impacted files

@@              Coverage Diff              @@
##             main-rhtap     #769   +/-   ##
=============================================
  Coverage              ?   57.95%
=============================================
  Files                 ?       53
  Lines                 ?     4215
  Branches              ?        0
=============================================
  Hits                  ?     2443
  Misses                ?     1531
  Partials              ?      241

/lgtm


API for content filter, unit testing fixed and added documentation fo…

I have added the Content Filtering API of OpenAI (Moderations) and documentation for this API. Also there are some issues in unit testing so fixed them too.
#15
@orhanerday not being able to add reviewers for this

LGTM! Thanks @bashar94

You are welcome @orhanerday


[test] Modernize GREASY Tests

Codecov Report

Merging #2144 (92252d8) into master (152d697) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2144      +/-   ##
==========================================
+ Coverage   85.97%   86.00%   +0.03%
==========================================
  Files          53       53
  Lines        9362     9368       +6
==========================================
+ Hits         8049     8057       +8
+ Misses       1313     1311       -2

Impacted Files
Coverage Δ

reframe/frontend/autodetect.py
60.90% <0.00%> (+3.42%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 152d697...92252d8. Read the comment docs.


client requirements should include starlette

#694 and #650 added starlette status constants to the client, but starlette never made it into the client requirements causing an import error if you only install tiled[client].
I believe it should be in both [client] and [minimal-client].
A broader question as this has happened before: could we add a CI test that installs the package with just [minimal-client] or [client] and verifies (to first order) that the package imports, and ideally that a basic client function test passes, maybe against the public test server?  This would likely have to be its own GHA/non-pytest script since afaik there is no environment control at the pytest level.

Good call @pbeaucage! :+1: for a test with client and minimal-client deps only.


next-pylint azure-core / corehttp

resolves https://github.com/Azure/azure-sdk-for-python/issues/34166
resolves https://github.com/Azure/azure-sdk-for-python/issues/34169

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-core

/check-enforcer override
ai - ci pipeline is failing on main so overriding on this PR.


python311Packages.panel: 0.14.3 -> 0.14.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.panel is: A high level dashboarding library for python visualization libraries
meta.homepage for python311Packages.panel is: https://github.com/holoviz/panel
meta.changelog for python311Packages.panel is: https://github.com/holoviz/panel/releases/tag/v0.14.4
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.14.4 with grep in /nix/store/gc8shzy21q8pqhlp8j8h7242mr1c921k-python3.11-panel-0.14.4
found 0.14.4 in filename of file in /nix/store/gc8shzy21q8pqhlp8j8h7242mr1c921k-python3.11-panel-0.14.4

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

11 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.datashader
python310Packages.holoviews
python310Packages.hvplot
python310Packages.intake
python310Packages.nbsmoke
python310Packages.panel
python311Packages.holoviews
python311Packages.hvplot
python311Packages.intake
python311Packages.nbsmoke
python311Packages.panel

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gc8shzy21q8pqhlp8j8h7242mr1c921k-python3.11-panel-0.14.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.panel https://github.com/r-ryantm/nixpkgs/archive/aaf828279a666eb481abfa90e1e3988ee2e3565f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gc8shzy21q8pqhlp8j8h7242mr1c921k-python3.11-panel-0.14.4
ls -la /nix/store/gc8shzy21q8pqhlp8j8h7242mr1c921k-python3.11-panel-0.14.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

python310Packages.datashader

10 packages built:

python310Packages.holoviews
python310Packages.hvplot
python310Packages.intake
python310Packages.nbsmoke
python310Packages.panel
python311Packages.holoviews
python311Packages.hvplot
python311Packages.intake
python311Packages.nbsmoke
python311Packages.panel

Maintainer pings
cc @costrouc for testing.

Result of nixpkgs-review pr 231220 run on x86_64-linux 1

2 packages failed to build:

python310Packages.datashader
python310Packages.datashader.dist

20 packages built:

python310Packages.holoviews
python310Packages.holoviews.dist
python310Packages.hvplot
python310Packages.hvplot.dist
python310Packages.intake
python310Packages.intake.dist
python310Packages.nbsmoke
python310Packages.nbsmoke.dist
python310Packages.panel
python310Packages.panel.dist
python311Packages.holoviews
python311Packages.holoviews.dist
python311Packages.hvplot
python311Packages.hvplot.dist
python311Packages.intake
python311Packages.intake.dist
python311Packages.nbsmoke
python311Packages.nbsmoke.dist
python311Packages.panel
python311Packages.panel.dist