Channels: your quick start guide

Rebase develop branch -- new file, index, urls-en.txt and mkdocs.yml
rebase develop branch - article and place holders
rebase develop branch - icons
fixing the text
fixing general channel info
rebase develop branch -- 287 rebase and update topic branch
287 review and changes
287 final review -- ready for publication

Hey @Fabiomorais87 and @jorge-campo, I'm barging in uninvited with a few wording suggestions! That's what I noticed as someone who's just read this article for the very first time, so maybe these will help simplify things a bit.

'When you join a community, you automatically have access to these channels'
'get'?
'This area shows the channel name and permissions'
'You can see the channel name and permissions here'?
'From this area, you can select more options :mobile-more-options: to access additional channel information, like channel members, permissions or notifications.'
'such as'? I feel that 'like' is too informal for documentation.
'The #general channel exists by default when you [create a community][create-a-status-community].'
'appears' or 'is created'?
As a community administrator, you can use the following tips to make this channel more helpful:
'here's how you can make this channel more helpful'?
[Set permissions][configure-channel-permissions] to restrict who can post in #general.
'Set up'?

Thanks, @shamisem -- I will add your suggestions and merge the content.

Waiting for the screenshots to update and publish the topic.


Update the method for determining kernel language

The previous algorithm for getNotebookType() was based on getting the kernel spec out of the current notebook. This is a problem when format is triggered by, for example, jupyterlab-autosave-on-focus-change, immediately after notebook creation. In that case, the language is determined to be null and errors arise.
Now the onSave() handler waits for the sessionContext to be ready, then getNotebookType() gets the same kernel spec info from the session rather than the loaded notebook.

I was pursuing some additional changes around languages for both the notebook and editor formatters, but realized it was a lot to contribute without even asking.
@krassowski @ryantam626 Would you welcome larger code changes? In particular, I added some type definitions, extracted some repeated code, and replaced the hard-coded MIME-type map with the CodeMirror MIME service.


Fix day tabs's font

Idea Description
Reference images and links
app

design

https://www.figma.com/file/NcSMs6dMsD88d4wOY0g3rK/DroidKaigi-2022-Conference-App?node-id=0%3A1

I'd like to try this issue. 🙋🏼

Thanks! Assinged


KIM should stop processing any action on Gardener shoot after configured timeout

Description
All operations processed by the KIM service in the Runtime CR controller reconciliation loop should be interrupted after the configured timeout period has elapsed. Each runtime operation kind (provisioning / deprovisioning / upgrade) should have its own duration timeout defined.
If an operation times out:

The Runtime CR should be marked as "Failed" state
A specific condition should be added, indicating which operation has timed out

AC:

[ ] KIM deployment should be configured with three time-out values for each runtime operation type  (provisioning / deprovisioning / upgrade)
[ ] Runtime operations should be interrupted after when timeout period has passed
[ ] RuntimeCR Status should be set correctly when an operation has timed out

Relates to:
#193
Recovery
If the timeout during Update function occurs - user (KEB) can fix broken configuration that has timeout by manually deleting annotation in the Runtime instance:
kyma-project.io/runtime-operation-started:
In such a case Runtime reconciler will Patch Gardner shoot with fixed configuration and will start next upgrade cycle. If the operation succeedes on Gardener side the Runtime CR status will be switched in Ready state.

Output examples:
Provisioning timeout
 status:
    conditions:
    - lastTransitionTime: "2024-08-08T11:17:23Z"
      message: Shoot creation timeout
      reason: ShootCreationTimeout
      status: "False"
      type: Provisioned
    state: Failed

Question: update scenario. First update - KEB changes machineType, KIM do the proper changes in the shoot but a timeout occurs. KIM set the status failed. Then, let's say - one day after, KEB is sending another update (for example  an autoscaler max change). Should KEB do something with the annotation mentioned above?

Decided to descope this feature as it could cause side-effects we don't want to cope with.


Add version

Add a version to the library, output using ./synful -v or ./synful -version

Completed in PR #146


fix(MdSidenavLayout): Remove deprecated @View

@View was removed in beta.11
https://github.com/angular/angular/commit/f9fb72fb0e9bcbda7aeebbf8321ce5d70d78ecee

LGTM

I encountered this issue due to using a version after beta.10. I'm pulling the files into my project via NPM. Do you publish a nightly build to NPM, or do I need to wait for a new material2 release (or manually update from this repo)?

@gxclarke we don't have a night / per-commit snapshot set up yet; for now I'd recommend waiting until the alpha.2 release.

Is it possible to publish an alpha.1.1 to make the lib compatible with the versions >= beta.11?
I understand that this is part of the alpha game but it will be pretty cool :)


chore: add

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add chart annotations to help UI show CPU & memory requirements vs. actual remaining requirements when project monitoring installed

When a user installs project monitoring, show a banner that compares the required CPU and memory with actual remaining CPU and memory in the project resource quota.

This feature already exists for the monitoring chart. The result is a warning banner that shows in the UI:

After discussion with Geet and Arvind, I realized my above comment is wrong - this won't work exactly the same as it will for monitoring. There are two differences:

While the UI code for determining the warnings for monitoring is on the chart install page, the UI code for determining the warnings for project monitoring will need to be on the create/edit form for a ProjectHelmChart resource.
While the UI takes the monitoring annotations from the Helm chart data itself, the annotations for project monitoring resource requirements would come from a different source (something other than the Prometheus Federator chart itself). It sounds like the exact source is TBD.

To determine available resource capacity, the Rancher UI will probably have to check the remaining resources of the cluster as a whole because the system project is not expected to have a project resource quota.
There is an unanswered question of exactly how the Rancher UI will calculate how much CPU/memory is available.  Will it subtract all the reserved CPU/memory from the total CPU/memory in the cluster to get the remainder, or will it only subtract the amount of CPU/memory that was actually used? If the latter is true, the UI could allow too many project monitors to get deployed.
We should take into account the fact that the user deploying the ProjectHelmChart resource may only have permission to see CPU/memory usage in their own project.

Note for whomever takes this. This can be tackled along with whatever rewrite we do regarding resource quotas and monitoring.

@samjustus and @MKlimuszka -- I don't see any PRs for this work or anything, so I am moving it into the next v2.9-next1 milestone.

Upon triage with your team, if this does point back to being purely UI, then transfer it to rancher/dashboard and we can reassess but annotations would be needed from backend.


wallet_remove_contact_account - not persistent across client restarts

Detailed at
https://bitsharestalk.org/index.php?topic=12740.msg167693;topicseen#msg167693
There are two issues it appears:

When I've created a local contact account using a public key,  if the public key belongs to a registered account, it appears the client 'resolves' the key to the registered account name and I can no longer reference the local contact using the name I originally used as the contact name. (this may be true only for account registered before the BTSX to BTS transition)

I cannot remove the contact - it appears as though wallet_remove_contact_account does not save the removal to the users wallet - the removed contact re-appears on restart

Superseded by: #1401


Change parsing exceptions from CompilationException to ParsingException

We added a ParsingException class, but there is still a mix of ParsingException and CompilationException errors raised in parsing. We should standardize exceptions encountered in parsing on ParsingException.

@gshank  Hi, Can I help you with that issue ? I think it might be "good first issue".  If I am wrong do you see any issue on which I can help you ?


Newest update.

I downloaded the newest Alpha build. Tried to load it and it would get stuck on Building Terrain.  So I did a test, I created a new instance and Downloaded the newest Alpha and Lib, same thing! So I reverted to the old Lib and it crashed.. Something in the Files are failing To finish rendering.

I am on Discord if you have a fue minutes.... Will be on for about 2 more hrs Where did you send your TS in a PM

resolved?

Should be, no longer occurs after the fix it seems

Turns out I made another screw up while trying to remove special cases for Earth/sun..  Was basically trying to get sol (null) to set sol (null) then do something with sol (still null) causing the crash


⚠ Samsung has degraded performance

In f652903, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2123 ms

Resolved: Samsung performance has improved in 43b2b10.


Added Spell Scorched Character Sheet Files

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: < Spell Scorched >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: < Dynamic Games > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: < Dynamic Defense Systems > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] This sheet has been made on behalf of, or by, the game's publisher.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: < https://www.drivethrurpg.com/product/384179/Spell-Scorched-Core-Rulebook   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

I'm looking right at the sheet.json file. Am I missing something else?

Sheet.json

Hi @PeteNutButter your file extension is .JSON, can you correct it to .json, please?
Thanks!

Arg capslock strikes again. It should all be fixed now!

Hey @PeteNutButter ,
This is looking good, but one more small issue - it seems like your files use CR-LF line endings. Sheets in this repo are required to use LF line endings for the sake of avoiding automatic conflicts.  You should be able to set this up once in your editor of choice, to where it will use LF by default for future sheet updates.
Once you've got that set, this should be good to go.
Thanks!

Thanks, I think I've corrected the issue now.

Hey @PeteNutButter ,
Looks like capitalization's got you again here - css is correct, with proper line endings, but you've added a new SpellScorchedsheet.html (leaving the old SpellScorchedSheet.html), and a new Sheet.json (as opposed to the existing sheet.json)

oh facepalm
OK, fixed that!


[suggestion] WSV snapshot

Feature request
It is in the scope of this ticket to add a way for Iroha to serialize and deserialize wsv.
We can do this:

periodically with a configurable dumping period
we can implement another endpoint in Torii to force dumping of wsv to the disk.

Once restarted, the node will read the wsv from the disk and reapply any excess transactions from the block store on top of it. The node will try reading a serialized wsv only if it is started with a specific flag, otherwise not
We can also make the network exchange the wsv when started similarly to what we do with broadcasting genesis block. IMO this would require more work and development time for too small gains
Motivation
We need a way to restart Iroha without it having to reapply all transactions from the block store to get to the current WSV. This is a highly requested feature because it takes 3hrs to restart Iroha for Orillion team
Who can help?
@appetrosyan @mversic

I vaguely remember this discussed as a possible Kura init mode, where we periodically store snapshots of WSV in blockstore and restart by applying only txns that happened after the snapshot.
I'd say that makes the most sense to me.

you are referring to this discussion

I didn't think taking a wsv snapshot should be mixed with Kura init modes

I would recommend adding a SIGUSR1 handler too, since this is what most programs would do anyway.

Environment: mac m1
iroha2 commit: ee60fc82
setup: on system
step for reproduce:

./scripts/test_env.sh setup
-kill -2 ${pid}
./scripts/test_env.sh setup`

console output
`

BLOCK_COUNT=
echo -1
-1
'[' '' = 1 ']'
echo 'Sleeping 1 sec...'
Sleeping 1 sec...
sleep 1
for i in $(seq 1 $1)
echo 'Waiting for genesis block to be created, attempt 16/20'
Waiting for genesis block to be created, attempt 16/20
++ curl --fail -X GET http://<IP_ADDRESS>:8180/status/blocks
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (7) Failed to connect to <IP_ADDRESS> port 8180 after 4 ms: Couldn't connect to server
`

logs by peers was attached
WSV_SNAPSHOT_3651.txt


Various license updates

Updating per instructions here https://www.apache.org/legal/src-headers.html

Unit tests have been timing out today.  Not sure why...

Thanks @Shanedell

My only concern is that these changes are preparation for assignment to Apache, but don't record our own license and copyright (pre-assignment). Do you think that is important?
For instance, I thought this change would list us as the copyright holders, and there would be some subsequent commit during "assignment". But nothing like that is mentioned in the referenced instructions.

I think you are right. Will adjust.

The snippets file is json... does it get noted in the notices file

Im going to merge this so some other work can progress, we can adjust further if needed in separate PR


Enhancement shim datapath

Adding a batch of optimizations for the shim layer

Use static arrays instead of custom hashtable and hashset
Hint to the compiler likely and unlikely events in branch conditions
Add missing O3 flag to the shim makefile
Use demi_wait_any instead of regular demi_wait to reduce the number of demi calls and background processes run (greatly improves tail latency)

Use demi_wait_any instead of regular demi_wait to reduce the number of demi calls and background processes run (greatly improves tail latency)

@stolet I cannot find this enhancement in this PR.

For some reason the demi_wait enhancement didn't show up. I will create another pull request in a different branch so that we can add this change independently. I noticed that the other changes in this PR were broken up and added in different merges.


Built app requires admin perms when installed in C:\Program Files

If the program is run without admin perms, it crashes immediately.
I have isolated the problem to this call: .invoke_handler(create_ipc_handler(ApiImpl.into_handler()))
I assume it has something to do with exporting types.

Thanks for reporting, this should be fixed in version 0.2.7. Now we're only exporting the types on development builds. Hopefully this works for you.

Fixed, thank you


notebooks (.ipynb) loader

I was looking for a .ipynb loader and realized that there isn't one. I already started to build one where you can specify if to include cell outputs, set a max length for output to include, and decide if to include newline characters. This latter feature is to avoid useless token usage, as openai models can detect spaces (at least davinci does), but could be useful to include it for other applications.

Hi!
I have some problem with the NotebookLoader loader:
I'm trying to access my repo and detect all of the .ipynb files, and then load them to the LLM Chain I'm implementing using LangChain. The repo can be viewed here
    for ext in extensions:
        glob_pattern = f'**/*.{ext}'
        try:
            loader = None
            if ext == 'ipynb':
                loader = **NotebookLoader**(str(repo_path), include_outputs=True, max_output_length=20,
                                        remove_newline=True,  loader_kwargs={"content_type": "text/plain"})

Yet I don't know how to pass the glob_pattern to this loader, resulting in going to the base dir and not being able to look for the notebook files...
[Errno 21] Is a directory: 'my_dir'

Can you please help me figure it out? Considering I don't want to pass each ipynb file-path individually?


BC - Retrieve and Display All Users in List

What

[x] User is able to view all other user profiles
[x] User is able to click and expand the user profile with more information
[x] #25

Evidence

LGTM


Numerical custom reactions

If you make a custom reaction with a number (in this case, it was somebody using "3", which I'll admit was a bad idea in the first place), and then turn .crca on for that reaction, if the trigger shows up in the ID, it can't be deleted, nor can .crca be turned off (because Nadeko will react to the number as opposed to completing the command).  The only way to get rid of it that I could find was just removing all of them using .crclear.

yes, tracked in #2172


Performance issues on Windows

Cobe tested on windows, the GPU goes to 100%
Sites tested: https://upstash.com, https://vercel.com, https://cobe.vercel.app

any idea why this might be happening @shuding? I don't mind digging into this if you can give a starting point :)

though i hope it's not, i'm afraid it's related to #9, someone gonna have some checking?

I can report the same issue happening on mac on a personal project of mine. GPU usage goes way up to the point where my laptop becomes unusable. What is strange is that this never happened before and just started happening. Anyone have an idea of a fix?


feat: Deduplicate instructions across blocks

Description
Problem*
Summary*
Deduplicates instructions across multiple blocks, mostly for brillig improvements.
Uses a dominator tree to ensure the instruction we're replacing the current with dominates the current block.
Additional Context
This should resolve the duplicate make_array instructions in https://github.com/noir-lang/noir/pull/6071
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

This is ready for review now; the dom check was accidentally reversed before causing the optimization to trigger less. I also updated the block iteration order to follow the actual control flow a bit more closely by popping from the front of the queue instead of the back.


Optimization: Use str join to replace if

Use str join to replace if
full_name = "_".join(filter(None, [namespace, subsystem, name]))

linked： https://github.com/prometheus/client_python/pull/1034/files


Incubator eventmesh fix 3228

Fixes #3228
Modifications
Describe the modifications you've done.
string comparision chnage in 3 lines in handle(HttpExchange httpExchange) method in HTTPClientHandler.java

This issue has been fixed, I'll close this pull request.


param.Range does not check if values are numbers

Param doesn't complain when the bounds of a Range Parameter are set with weird values.
import param

class X(param.Parameterized):
    xlim = param.Range(bounds=('a', 'b'))

x = X()

This is because _valudate_bounds are not checking if the values are numbers, e.g., this is a valid comparison "a" < "b".
https://github.com/holoviz/param/blob/ddcd5f36bcff1712f2c7fb984268a0ad6dc9649f/param/__init__.py#L2086-L2096

I can replicate this behavior, and also consider it an error that we should catch.

I think the code to fix this would be something like
     def _validate_bounds(self, val, bounds, inclusive_bounds):
-        if bounds is None or (val is None and self.allow_None):
-            return
+        if bounds is None:
+            return
+
+        for b in bounds:
+            if b is not None and not _is_number(b):
+                raise ValueError(f"Range bound '{b}' can only be None or a "
+                                 f"numeric value, not type '{type(b).__name__}'.")
+
+        if val is None and self.allow_None:
+            return
+

but there will be merge conflicts if #808 is merged first, so we can come back to it after merging that.

Yep it will look like something like that. You'll probably want to make sure that it's a change valid for the DateRange and CalendarDateRange subclasses.


Allow plugins to read and write close codes/reasons as well as read Pong bodies

Plugins currently cannot read or write the status code or reason string for close frames. Incoming close frames are completely hidden by the module, and server->close() does not take any code or reason string in its parameter list.

We also hide incoming pong data, which means plugins can't use ping reflection for anything.


installation issue

After following the install instructions, I got the following error.   Thanks
pip install jax==0.4.20 jaxlib==0.4.20
pip3 install --upgrade intel-extension-for-openxla
>>> import jax
>>> import jax.numpy as jnp
>>> import jax
>>> print("jax.local_devices(): ", jax.local_devices())
Platform 'xpu' is experimental and not all JAX functionality may be correctly supported!
Traceback (most recent call last):
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 623, in backends
    backend = _init_backend(platform)
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 734, in _init_backend
    backend = registration.factory()
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 470, in factory
    xla_client.initialize_pjrt_plugin(plugin_name)
  File "/home/users/test/.local/lib/python3.10/site-packages/jaxlib/xla_client.py", line 159, in initialize_pjrt_plugin
    _xla.initialize_pjrt_plugin(plugin_name)
jaxlib.xla_extension.XlaRuntimeError: INVALID_ARGUMENT: Mismatched PJRT plugin PJRT API version (0.2) and framework PJRT API version 0.38).

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 877, in local_devices
    process_index = get_backend(backend).process_index()
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 779, in get_backend
    return _get_backend_uncached(platform)
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 759, in _get_backend_uncached
    bs = backends()
  File "/home/users/test/.local/lib/python3.10/site-packages/jax/_src/xla_bridge.py", line 639, in backends
    raise RuntimeError(err_msg)
RuntimeError: Unable to initialize backend 'xpu': INVALID_ARGUMENT: Mismatched PJRT plugin PJRT API version (0.2) and framework PJRT API version 0.38). (you may need to uninstall the failing plugin package, or set JAX_PLATFORMS=cpu to skip this backend.)

The most likely reason is that you are using an Extension that does not match the JAX version. Each Extension version can only work with specific JAX version, such as 0.1.0 vs. 0.4.13, 0.2.0 vs. 0.4.20... Currently you can find the match info in release notes: https://github.com/intel/intel-extension-for-openxla/releases
We will maintain a clear table in the future in case you miss it, thanks.

This question has been inactive for more than 2 weeks, will close it soon if no more feedback, thanks!


How do I run this?

I am new to Chef.  I am trying to get a replica set going.  Where do I specify the nodes or ip addresses to run this on?  Do I use a knife command?  Do I do something like  knife bootstrap ADDRESS --run-list 'mongodb::replicaset, node['node1']['mongocluster'],node['node2']['mongocluster']'   ?
That does not work.  When I just run it with 'mongodb::replicaset' I get a 400 Bad Request error.

Learning chef with this cookbook is the equivalent of learning plumbing on the death star.

I strongly encourage you to look at https://github.com/chef-brigade/mongodb-cookbook, which is maintained.


After accessing the user location. It's asking for the user location again and again it's not stopping. Please find the below screenshot for your reference if anyone could help me in it will be beneficial for me.

sir, it's showing me in loop, after allowing it from the browser. It asks for the user permission again. How to stop the same?

action.py code for the same
class ActionSearchHospitals(Action):
def name(self) -> Text:
return "action_search_hospitals"
def run(self, dispatcher: CollectingDispatcher,
        tracker: Tracker,
        domain: Dict[Text, Any]) -> List[Dict[Text, Any]]:
    dispatcher.utter_message(text="Please allow me access to your location", json_message={
        "payload": "location"
    })
    print()
    print("====Inside ActionSearchHospitals====")
    print()
    location = tracker.get_slot("location")
    lat = tracker.get_slot("latitude")
    print("Latitude_slot", lat)
    lon = tracker.get_slot("longitude")
    print("Longitude_slot", lon)
    latEntity = next(tracker.get_latest_entity_values("latitude"), None)
    print(latEntity)
    lonEntity = next(tracker.get_latest_entity_values("longitude"), None)
    print(lonEntity)
    user_locationEntity = next(tracker.get_latest_entity_values("user_location"), None)
    print(user_locationEntity)
    ## if we latitude & longitude entities are found, set it to slot
    if latEntity and lonEntity:
        lat = latEntity
        lon = lonEntity
    if user_locationEntity or (latEntity and lonEntity):
        ## check if we already have the user location coordinates stoed in slots
        if lat == None and lon == None:
            dispatcher.utter_message("Sure, please allow me to access your location 🧐")
            dispatcher.utter_custom_json({"payload": "location"})
    return [UserUtteranceReverted()]

rule.yml

training data for inform intent.

do you get an error in slot validation or in another custom action? you can check this in the console

@bawa-v  thanks for your comment, but I am able to solve it.

@shreyashgupta68 okay great! :)


dictionary changed size during iteration

I get this error pretty often in TransactionsMetricSet:
RuntimeError: dictionary changed size during iteration
  File "elasticapm/utils/threading.py", line 79, in run
    rval = self._function(*self._args, **self._kwargs)
  File "elasticapm/metrics/base_metrics.py", line 97, in collect
    for data in metricset.collect():
  File "elasticapm/metrics/base_metrics.py", line 215, in collect
    for (name, labels), t in compat.iteritems(self._timers):

Environment (please complete the following information)

OS: Debian stable
Python version: 2.7.13
Framework and version [e.g. Django 2.1]: 1.11.20
APM Server version: 7.6.0
Agent version: 5.3.3

@starenka that's interesting. It probably happens because while we iterate over the metrics in the background thread, the foreground thread (the one that is handling Django requests) is adding new metrics data.
There are two ways to fix this: we could either take the lock before iterating, or turns the items iterator into a list before iterating over it.
Taking a lock would probably the cleanest way, but it'll block the main thread, even if it is for a very short amount of time. OTOH, turning the iterator into a list would consume a little bit more memory, but wouldn't block the main thread.
@basepi WDYT?

I guess I could go either way. I'm loathe to block the main thread -- I feel like I'd rather (briefly) lose a little memory during the operation. But I don't think either option is particularly bad.


Make Select.ready() async iterable

Make Select.ready() an async iterator
The async iterator yields a set of receivers that are ready to be consumed. Users need to consume() explicitly from the receivers that are ready and are not automatically consumed() by the select object if they were not consumed in the select loop.
Example:
select = Select(recv1, recv2)
async for ready_set in select.ready():
    if recv1 in ready_set:
        msg = recv1.consume()
        # do whatever with msg, consume() can also raise an error as normal
    if recv2 in ready_set:
        msg = recv2.consume()

If a receiver is stopped, then it will be automatically removed from the select loop.
Fixes #47.

This is a new attempt (based on #61, so excuse the duplicated commits), I got it as a draft in my repo from the time I was working on it and cleaned it up a bit while cleaning up the exceptions stuff that I also had in draft.
For me it makes the interface (and implementation) of select much simpler and clear. Maybe we can try it on the new comers to see if it really is.

Also updated. Moved the Don't raise exceptions in Receiver.ready() commit to #61 too, so only the last commit (Make Select.ready() an async iterator) is relevant for this PR (the others should be reviewed in #61).

Rebased on the current head.

OK, so this review got a bit deep. Thanks for the thoughtful and in depth review, and bearing with me with all the clarifications, I definitely underestimated some of the complexity that was there and was there for a reason :grimacing:
To summarize these are my take-aways:
Things to change for sure:

[ ] Rename ready() to __aiter__() [*]
[ ] Clarify in the examples that msg = await recv.receive() can be used too, but it would be less efficient than msg = recv.consume() and explain a bit better the differences.
[ ] Favor using hash() as the key for the internal dict/name for the tasks if we keep returning a set (which is probably not the case because of the starvation thing)

As to avoid starvation. I see 2 main paths:

Leave the current mechanism with some wrappers and keeping an internal state of what was consumed and what wasn't.
Revive the one-by-one approach somehow randomize which receiver is returned.

As to avoid missing receiver handlers in the loop, also 2 main alternatives:

Look into match to see if it can help us
Keep using a wrapper to keep track that all possibilities were covered.

What I don't like that much about the approach above, is there is no way to add/remove receivers to the select. I know we said if you need to do this is probably not a use-case for select, but still it makes noise in my mind, select seems to be a very convenient tool for those cases too.
Let me know if there is something missing or wrong.

Yup,  I think we are in agreement about the requirements.  I have developed a slight preference for the one-by-one approach.
It looks like in any case,  we'll need a wrapper,  unless there's some pattern matching magic that would help with detecting missing handlers.

Yup, I think we are in agreement about the requirements. I have developed a slight preference for the one-by-one approach.

I was thinking of having the one-by-one approach as the default and the async iterator interface. This will even consume()  the message, so we don't even need to recommend consume() or receive() and we also don't run into the problem of what to do if the user didn't consume the message (to drop or not to drop). The only problem with this issue is how to handle exceptions, because the async for loop will raise as a whole if there is no explicit consuming, but I'll think about it.
Then maybe provide an advance interface for getting multiple ready receivers at once, for cases with more advanced usage like the mentioned above. For this method if we can have safety mechanisms in place to avoid the mentioned common bugs, then great, otherwise it should be clearly flagged as unsafe (like async for ready_set in select.unsafe.all_ready).

It looks like in any case, we'll need a wrapper, unless there's some pattern matching magic that would help with detecting missing handlers.

:+1:

Closing as the solution we decided on is different to this one, so we can start fresh with a new PR.

Superseded by #114


Llama support

What does this PR do?
This add support for sharded Llama models on TPU, tested on TPU v5e litepod-8.
A test that show inference with Llama3-8b on TGI has been added.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you make sure to update the documentation with your changes?
[x] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Does "sharded llama models" imply that this could cover 70b as well?

For now I have only tested with an 8B model on a single-host TPU v5e 4x2. I reckon we would need something bigger to test the 70b model.

Do you need help with capacity?


added service implementation 101 doc

Signed-off-by: Dan Chiarlone<EMAIL_ADDRESS>

@devigned ~ Thank you for your review! I've committed all your suggestions, fixed the indentation for the Makefile rule, and added a link to the service-implementation-101.md doc in the main README.md!

Thank you for finding all my "its'", @devigned 😆~ fixed!


ModuleNotFoundError: No module named 'mmcv._ext'

Hi @MengyangPu
Can you help with this error.
I followed the below steps:
pip install -r requirements.txt
pip install mmcv
pip install mmsegmentation

And I get the mentioned error when I run python tools/test.py
I am using:
Ubuntu 22.04
GCC: 9.5.0 (default was 11.3 but I changed it to 9 assuming it would work)
Python: 3.10.6
CUDA: 11.4
Torch: '1.13.1+cu117'

Thanks in advance

Maybe you can refer to the installation.

I was able to resolve the issue by downgrading the Gcc version to 9 and fresh installation of Pytorch, Mmcv and Mmsegmentation. After many trail and errors with versions it was resolved. Thanks


feat: 'setup codestyle for team' implementation

First of all you should to download the ESLint and Prettier extensions for VSCode

@vzanimonets
We need to resolve conflicts in package-lock.json and merge this branch


[SPARK-37324][SQL] Adds support for decimal rounding mode up, down, half_down

What changes were proposed in this pull request?

Adds support for Decimal RoundingMode.UP, DOWN and HALF_DOWN by letting users to pass the rounding mode as argument to round function.
bround function calls round function with the argument "half_even"

Why are the changes needed?
Currently there's no easier and straight forward way to round decimals with the mode UP, DOWN and HALF_DOWN. People need to use UDF or complex operations to do the same.
Opening support for the other rounding modes might interest a lot of use cases.
SAP Hana Sql ROUND function does it :
ROUND(<number> [, <position> [, <rounding_mode>]])
REF : https://help.sap.com/viewer/7c78579ce9b14a669c1f3295b0d8ca16/Cloud/en-US/20e6a27575191014bd54a07fd86c585d.html
Sql Server does something similar to this :
ROUND ( numeric_expression , length [ ,function ] )
REF : https://docs.microsoft.com/en-us/sql/t-sql/functions/round-transact-sql?view=sql-server-ver15
Does this PR introduce any user-facing change?

Now, users can specify the rounding mode while calling round function for round modes up, down, half_down. Calling round function without rounding mode will default to half_up.
> SELECT round(3.145, 2)
3.15

>SELECT round(3.145, 2, 'down')
3.14

df.withColumn("value_rounded", round('value, 0)

df.withColumn("value_rounded", round('value, 0, "down")

How was this patch tested?

This patch was tested locally using unit test and git workflow.

Can one of the admins verify this patch?

Test Fails on compatibility check against spark-sql_2.12:3.2.0! but it is normal, no ? any idea how can we fix it ?
error] spark-sql: Failed binary compatibility check against org.apache.spark:spark-sql_2.12:3.2.0! Found 2 potential problems (filtered 203)
[error]  * static method round(org.apache.spark.sql.Column,Int)org.apache.spark.sql.Column in class org.apache.spark.sql.functions does not have a correspondent in current version
[error]    filter with: ProblemFilters.excludeDirectMissingMethodProblem
[error]  * method round(org.apache.spark.sql.Column,Int)org.apache.spark.sql.Column in object org.apache.spark.sql.functions does not have a correspondent in current version

@gengliangwang Could you please kindly take a look at this ? thank you very much.

Test build #145261 has started for PR 34593 at commit 3b1357b.

Test build #145261 has finished for PR 34593 at commit 3b1357b.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145261/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49730/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49730/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49730/

Can one of the admins verify this patch?

Test build #145282 has started for PR 34593 at commit 0366617.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49752/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49752/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49752/

Test build #145282 has finished for PR 34593 at commit 0366617.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145282/

Test build #145341 has started for PR 34593 at commit 97220a2.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49810/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49810/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49812/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49812/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49812/

Test build #145350 has started for PR 34593 at commit 5dc12af.

Test build #145350 has finished for PR 34593 at commit 5dc12af.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49821/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145350/

Test build #145339 has finished for PR 34593 at commit 36538d1.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Test build #145341 has finished for PR 34593 at commit 97220a2.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49821/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49821/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145339/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145341/

Test build #145406 has started for PR 34593 at commit 42f637e.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49879/

Test build #145410 has started for PR 34593 at commit f93e759.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49879/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49882/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49879/

@HyukjinKwon All tests are passing. I'm not sure why the Kubernetes integration test is failing, could you please kindly take a loot at it ? thanks !

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49882/

Test build #145406 has finished for PR 34593 at commit 42f637e.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49882/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145406/

. I'm not sure why the Kubernetes integration test is failing, could you please kindly take a loot at it ? thanks !
it should be unrelated w/ this change.

Test build #145410 has finished for PR 34593 at commit f93e759.

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

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145410/

@HyukjinKwon May I know the status of this PR please ?

I am fine as long as this syntax matches with other DBMSes. Would better to wait for other committers' feedback though such as @cloud-fan or @sarutak.

Test build #145551 has started for PR 34593 at commit b7c2cc6.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50023/

Test build #145552 has started for PR 34593 at commit ed83e8b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50024/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50023/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50023/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50024/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50024/

Test build #145552 has finished for PR 34593 at commit ed83e8b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145552/

Test build #145551 has finished for PR 34593 at commit b7c2cc6.

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

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145551/

Test build #145597 has started for PR 34593 at commit e7f6261.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50069/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50069/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50069/

Test build #145597 has finished for PR 34593 at commit e7f6261.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145597/

Sql Server does something similar to this :

ROUND ( numeric_expression , length [ ,function ] )

REF : https://docs.microsoft.com/en-us/sql/t-sql/functions/round-transact-sql?view=sql-server-ver15

This doesn't seem not related to the proposal in this PR.
Is there any other DBMS supporting the rounding mode as 3rd parameter?

I investigated whether the major DBMS and query processing systems (PostgreSQL, BigQuery, Snowflake, MySQL, SAP HANA, MS SQL Server, Firebird, DB2, Teradata, Hive) support the third parameter of round but I found only SAP HANA and MS SQL Server do.
@sathiyapk
How many users need to change the rounding modes and how often they are used?
If users really need up, down and half_down, I think it's not difficult to implement using BigDecimal.setScale.
@HyukjinKwon @gengliangwang What do you think?

@sarutak yeah I did some investigations too. This feature seems not commonly used.

I think people can just use floor and ceil functions if they need a different rounding mode?

I think people can just use floor and ceil functions if they need a different rounding mode?

floor and ceil can't control the position of rounding directly

Currently, we are relying on UDF for rounding, when i googled to do it via spark native methods, i found a lot of people have the same issue and it's not complex to support it via spark native methods, so i opened this PR.

@cloud-fan @gengliangwang I confirm floor and ceil don't match our use case.

Then can we add a scale parameter to floor and ceil? This leads to better API design IMO: we have 3 functions for different rounding modes, and each function takes a scale parameter.

@cloud-fan I like the idea of adding scale parameter to floor and ceil. This would simulate the rounding mode UP and down for positive integers, but for negative integers it will work differently i believe ?

@sathiyapk you are right, but I can also argue that the round function with a rounding mode can not do what I want by using the floor/ceil function with a scale parameter. The problem is which behavior is more common/reasonable and can be useful to more users?
We can collect more data points, I found one example that snowflake supports scale parameter in floor/ceil: https://docs.snowflake.com/en/sql-reference/functions/floor.html

@cloud-fan In our case, the first function we looked into was floor/ceil but since it didn't take the scale parameter we had to look for other ways. So i believe adding a scale parameter to floor/ceil is a good idea and also I believe the rounding of negative numbers are not so common.
If everyone agree I will open a new PR for the scale parameter to floor/ceil function.

+1 for adding the scale parameter to floor and ceil.

@gengliangwang @HyukjinKwon what do you think ?

+1 for adding the scale parameter to floor and ceil.


feat: Initial port of HAL from ch32x035 to ch32V307

Some changes:

Another ADC added, should be rewritten to macros
USBPD removed, so far exclusive to the ch32x series
USART4 removed, as the CH32V307 does not have it (UART4-8 are asynchronous only) (but the CH32V20x_D6 variation has), UART will have to be added later
USB stuff appears to be different, so removed it, more investigation will be needed
delay_ticks changed, the underlying hal now provides access to the whole 64 bit counter, opcode overhead will need to be investigated
Default clock set to 96 MHz, this should provide a good tradeoff between speed and peripheral compatibility
Changed interrupt initialization
USART is messy, someone at WCH thought it would be a good idea to divide routing to two separate registers
Did some dirty pointer casts to get it to compile, should be rewritten to macros later
Fixed timestamp overflow panic in time_driver_systick.rs on line 159

What is left/what I noticed:

Second remap of UART2 does not seem to work, could be my board not working or cold solder joint.
I haven't tested SPI or UART, I could test the SPI using a Raspberry Pi Pico, but I have no reliable way to generating ADC.

Somewhat tested the ADC, it seems that there was a bug preventing it from starting, you have to actually write a single bit to ADON to start it. Fixed it.

Tested the SPI and added a simple example for it. I think that is enough for now.

This is a lot of work. Well done!
I will take the time to review this.


[Bug]: expert App not contain textcolor

I'm sure that

[X] This issue is still present in the current beta version of this adapter
[X] There is no other (open) issue with the same topic (use the search!)
[X] This issue is not described in the adapter documentation / FAQ (read the docs!)

Version of awtrix-light firmware
0.94
The problem
i tried to setup the weather expoert app as described. but the script tries to set also textcolor which is not exsiusts as datapoint in the expertApp.  My expectation was set the adapter create all needed datapoints insite the expertapp.
iobroker.current.log (in debug mode!)
No response
Version of nodejs
v18.19.0
Version of ioBroker js-controller
5.0.17
Version of adapter
0.12.0

look slike its fixed in 0.13.0


American express CVC

Summary
American express is only meant to have a 4 char cvc, this allows a 3 char cvc to be entered
Steps to reproduce

Run this project's demo (yarn demo)
Open the demo (http://localhost:8080/)
Copy the American Express test card number<PHONE_NUMBER>10005)
Paste it into the card number field (CTRL+C then CTRL+V)
Observe that the American Express CVC allows for a 3 digit cvc

This is invalid

Hey @dalefrancis88! While Amex cards generally have 4 digit CVCs, we've seen cases where 3 digits are accepted or expected as well. For this reason, we allow both 3 or 4 digit CVCs for Amex cards.
Hope that helps!

Yeah it does, thanks for letting me know.


When you upload the first verion of a Frank config, the Automatic Reload checkbox does not work

Describe the bug
When you upload the first verion of a Frank config, the Automatic Reload checkbox does not work. Even though you checked this checkbox in the Upload Configuration dialog, you need to press Reload in the Adapter Status page before the config is found in the database.
Category

Frank Framework

To Reproduce
Steps to reproduce the behavior:

Start the Frank!Runner with: start.bat -Djdbc.migrator.active=true -Dconfigurations.names="${instance.name.lc},NewHorizons" -Dconfigurations.NewHorizons.classLoaderType=DatabaseClassLoader -Dwork=work -DloadDatabaseSchedules.active=true
Ensure that no configs have been uploaded so far.
Download this config:
forFrankConsole.zip
Go to Configuration | Manage Configurations | Upload Config. Browse to the zipfile you downloaded. Check "Activate Config" and "Automatic Reload".
Press Send. The "Back".
Wait more than a minute and refresh your browser page.
The NewHorizons entry within the Manage Configurations page remains red, indicating it was not loaded.
 Now you can see the config was loaded/

Expected behavior
After step 6, the NewHorizons config should become a link instead of staying red.
Screenshots
I hope it is clear this way.
Environment:

Frank!Runner
Microsoft Edge
Frank!Framework version 7.6-20200512.092218.

Additional context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

This issue only has been fixed partly. I did the following:

DROP ALL OBJECTS.
Restart Frank!Runner.
Upload first version of configuration with "Activate Config" and "Automatic Reload" checked.
Go to Adapter Status page. To the top there is a red bar.
Wait about two minutes, the red bar does not vanish.

When I refreshed my browser page, the red bar did vanish. But this is not sufficient I think. The red bar should go away without the need for a browser refresh.

Marijn zegt:
Issue 717 is niet helemaal gefixed. Je moet nog steeds je browser refreshen in de Adapter Status pagina, voordat je ziet dat automatic reload effect heeft gehad. Kunnen jullie dit issue heropenen?

Cannot reproduce, can you provide a screenshot of the red bar you're talking about?

I tried to reproduce with version IAF 7.6-20200519.180727, but I could not. The red bar I talked about does vanish.

I updated the Frank!Manual to remove the reference to this issue.


Scripts, guide export and import child user USPS account credentials

New Python scripts and instructions to help mass-export and mass-update USPS credentials for all child users under a parent account

@Justintime50 I still need your help to test this, since my personal account is borked.

Please also add a description to this PR since we'll have others looking at it in the future I'm sure.

@nwithan8 looks like prettier doesn't like your changes to the README


[Request] Configure on which pokemon to use razzberries

I have the experience that I am always out of razzberries. The bot uses them on every harder to catch pokemon. It would be great if we could decide which pokemon is worth a razzberry.
Keep up the wonderful work! 👍 😃

+1 Only on the S and A class pokemon!

Don't quote me on this, but I think it does it based off the chance of Pokemon being caught.

Correct, so it will use it to catch Rattatas etc that have a high CP. (Not worth anything though)

Duplicate of #1487


kexi not building on nixos22

Describe the bug
kexi not building
Steps To Reproduce
Steps to reproduce the behavior:

nixos-rebuild switch
error message:

-- Detecting CXX compile features - done
--
-- Check for working CXX compiler: /nix/store/npm4g1zsj5yzygf6bq46pbi9fqhxisha-gcc-wrapper-10.3.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
--
CMake Error at CMakeLists.txt:15 (find_package):
Could not find a configuration file for package "Qt5" that is compatible
with requested version "5.15.2".
The following configuration files were considered but not accepted:
/nix/store/gszycghs77nlqa58fp1ydw2bxpy998ci-qtbase-5.14.2-dev/lib/cmake/Qt5/Qt5Config.cmake, version: 5.14.2
-- Configuring incomplete, errors occurred!
See also "/build/kconfig-5.89.0/build/CMakeFiles/CMakeOutput.log".
error: builder for '/nix/store/6ryr8drmhk9gx9a3v235mab7sq03c4pa-kconfig-5.89.0.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/kvqw0vp1iy0y0rdlzlh2vr60z2r1cp6s-kexi-3.2.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/lblcrnzacn9iblyjp3gkmlkn12r3y8s4-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/m7wzfkm5ksr5vnry306vlp3p3ar854pm-xsession-wrapper.drv' failed to build
error: 1 dependencies of derivation '/nix/store/yppskr5vfswznfsfx16bm975dmz5sfl3-nixos-system-bx26-22.05pre346004.5aaed40d22f.drv' failed to build
Expected behavior
nixos-rebuild switch without errors
Notify maintainers
Thomas Tuegel
https://github.com/ttuegel
David Mell zraexy
https://github.com/zraexy

Metadata
/nix/store/jaa5l5g36aj1wwlmk9lqhslclmdqms3x-bash-interactive-5.1-p12-dev
copying path '/nix/store/jaa5l5g36aj1wwlmk9lqhslclmdqms3x-bash-interactive-5.1-p12-dev' from 'https://cache.nixos.org'...

system: "x86_64-linux"
host os: Linux 5.10.91, NixOS, 22.05 (Quokka)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.5.1
channels(root): "nixos-22.05pre346004.5aaed40d22f"
channels(k): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Tried fixing this, but wasn't entirely successful (https://github.com/FliegendeWurst/nixpkgs/tree/kexi).


Coloring the letters in sections in different colors?

As the title suggests: I would like to give the 3 letters of the sections 3 different colors. For example: the first letter in red, the second in blue and the last in green.
Terrific job btw.

I don't understand why you're considering this, but if you really want to this below is the simplest way I could conceive of doing it.
It requires a few minor edits to  awesome-cv.cls.
I've included some edits for resume.tex (and cv.tex and coverletter.tex if you intend to use them as well) to make the modification easier to work with.
Modifying Section Color Behavior in awesome-cv.cls
Within awesome-cv.cls change the \ifbool under % Awesome section color from this:
\ifbool{acvSectionColorHighlight}{{\color{awesome}#1#2#3}}{#1#2#3}
to
\ifbool{acvSectionColorHighlight}{{\color{awesomeSecOne}#1}{\color{awesomeSecTwo}#2}{\color{awesomeSecThree}#3}}{#1#2#3}
This change allows for each of the colors of the first three letters to be defined individually.
Defining Colors in Appropriate .tex Files So You Can Leave the .cls file Alone
Within the appropriate .tex file (resume.tex, cv.tex, and/or coverletter.tex), presumably with the other color definitions, add the following:

\definecolor{awesomeSecOne}{HTML}{789455}
\definecolor{awesomeSecTwo}{HTML}{145876}
\definecolor{awesomeSecThree}{HTML}{445566}

Adjust the HTML color codes to whatever you want. If you want to use the predefined awesome colors you can find their html color codes within the .cls file.
Note: For the sake of completeness...\definecolor{awesomeSecThree}{awesome-red} will not work but \colorlet{awesomeSecThree}{awesome-red} will.

Thank you @dcsim! I don't think this is something that will be natively supported, at least not without a much broader scope overhaul, so I'll close this now grateful for your explanation on OP's specific request.


Update the pypi badge to link to tickit-devices

Currently the pypi badge in the readme still links to the old skeleton. This needs to be changed to link to tickit-devices.

Resolved by #43


Upgrade from eval to prod profile fails on Kyma 2.0 with issue in PVC patching

Description

When Kyma 2.0 is upgraded from evaluation to production profile, the upgrade fails for 3 components. Patching PVC seems to be causing the issue.
reason: cannot patch with kind PersistentVolumeClaim: PersistentVolumeClaim is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims

Expected result

Upgrade succeeds
Actual result

3 components (serverless, monitoring and rafter) fail
Steps to reproduce

Install Kyma 2.0 with evaluation profile (using latest reconciler)
Upgrade Kyma 2.0 to production profile

Troubleshooting

3 components namely monitoring, rafter and serverless fail with the same issue:
cannot patch \"monitoring-grafana\" with kind PersistentVolumeClaim: PersistentVolumeClaim \"monitoring-grafana\" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims\n

cannot patch \"rafter-minio\" with kind PersistentVolumeClaim: PersistentVolumeClaim \"rafter-minio\" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims\n

cannot patch \"serverless-docker-registry\" with kind PersistentVolumeClaim: PersistentVolumeClaim \"serverless-docker-registry\" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests for bound claims\n

Switching profiles is not the main use case that's why I removed release blocker label.

Duplicate of https://github.com/kyma-incubator/reconciler/issues/557.


Update troubleshooting.rst

Follow-up from

https://mattermost.atlassian.net/browse/PLT-5635
https://github.com/mattermost/platform/pull/5667
https://github.com/mattermost/platform/issues/5386

Also fix two broken links

Resbumitted in #1032


is this app  can build and run on windows?

or only linux support?  golang is  cross platform

ok,it's  cross platform


pipelineX Add pending finish dependency timer

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Showing NaN and Infinity on the overview screen

Just installed log today. Really neat software. Just thought I'd drop in this bug report. It's likely an issue specific to brand new users.
I'm willing to make this a pull request and fix it if you'd like.

It's already fixed here. I haven't updated itch.io yet


Add additional goal fields for additional OWL expressivity

Note: a separate ticket will be created for the population of these. Individual fields vary from low to medium priority.
Some of these fields will make use of a owl-in-json representation (cc @dosumis), TBD, most likely extending the existing Minerva serialization (to be moved into own library? owl-json?) and thus reuse https://github.com/berkeleybop/class-expression/ .
Association Documents

Add annotation_extension_owl_json - this will be a non-lossy representation of conjunctions and disjunctions in c16
Add annotation_relation - this is equivalent to the relation field in GPAD. OWLTools code already exists for inferring this
We also need something to accurately represents conjs+disjs in the WITH column in gaf2.1

ontology_class Documents

Add equivalent_class_expressions_json - for any class document C this will contain json(CE) for all axioms of form EquivalentClasses(C ... CE ....). Note id_label map should be complete for all values here
Add disjoint_classes [populating this is low priority]

annotation_relation: is this a single ID, or something else?
disjoint_classes: looks muiltiple and not a closure, so then this would be unpacked to disjoint_class_list and disjoint_class_list_label?

annotation_relation is a single ID
disjoint_classes. Correct, list, list_label, no closure

does annotation_relation need a corresponding label?


Demo site seems down

Trying to open the demo website what I see is a DNS lookup error for demo.serverfire.net.
Not sure if it's on your side, but most probably it is. I am using Google's DNS servers.

Yes we have problem in demo server will fix that

Still down. And the docs. Are you planning to revive them?

Please note that there is a piece of code that sends an Ajax request to check the version: https://github.com/serverfireteam/panel/blob/152bf630afbd9118fad29e1029a26eb9a2bae6c0/src/views/dashboard.blade.php#L59
I'd suggest to remove this if there is no plan to get the site up and running again.
Thanks in advance


Add Dynamic Yield/Conv optimization tool

Website:
https://www.dynamicyield.com/
Example websites:
https://www.jimmyjazz.com/
https://www.juniqe.it/
https://www.synchronybank.com/
@AliasIO Hey mate . I am not sure which additional cats i can add

Just the one is fine, thanks!


Possible to create a const constructor that then cannot be used in a const context

Dart SDK Version (dart --version): Dart SDK version: 2.14.2 (stable) (Wed Sep 15 12:32:06 2021 +0200) on "macos_x64"
Whether you are using Windows, MacOSX, or Linux (if applicable): macOS Big Sur 11.6

I have a case of a class which has a const constructor that is then not callable in a const context:
import 'package:meta/meta.dart';

@immutable
class Sample {
  final List<String> strings;

  const Sample({
    required this.strings,
  })  : assert(strings.length >= 1);
}

The compiler complains with 'Evaluation of this constant expression throws an exception.' when I write this:
const s = Sample(strings: ['abc']);

If I make the constructor not const, my linter complains that @immutable classes should have a const constructor. I know that I can ignore it, but the question is - why does the compiler allow writing code which cannot be called? I would expect the analyzer/compiler to fail earlier, right where the constructor is defined.

@lrhn @munificent @leafpetersen – should this be moved to the language repo?

This is working correctly and as specified.
An expression of the form e.length is potentially constant if e is a potentially constant expression. It is further constant if e is a constant expression that evaluates to an instance of String, such that length denotes
an instance getter invocation.

strings.length is a potentially constant expression, so the declaration of the const constructor is valid, but the invocation is invalid since strings does not evaluate to a String.  Agreed that this is a less than useful specification, since strings can never evaluate to something of type String.  @lrhn @eernstg I thought that at some point we talked about fixing this specification so that .lengthwould only be potentially constant if the target wasdynamicorString`?
Modulo changes to the spec, I see two possible actionable things here in the short term:

This seems like a great candidate for an analyzer warning (and there may be a few other things in the this category).  cc @bwilkerson @scheglov @srawlins

The analyzer error message is exceptionally unhelpful here. The CFE error is much better (see below). cc @bwilkerson @stereotype441 @srawlins who have talked about trying to push on error message quality/consistency.

leafp-macbookpro:Constructor-tear-offs leafp$ ~/src/dart-repo/sdk/xcodebuild/ReleaseX64/dart-sdk/bin/dart  ~/tmp/test.dart
../../../../../../../../tmp/test.dart:10:9: Error: Constant evaluation error:
  const Sample(strings : ["abc"]);
        ^
../../../../../../../../tmp/test.dart:6:24: Context: The property 'length' can't be accessed on '<String>["abc"]' in a constant expression.
  })  : assert(strings.length >= 1);
                       ^
leafp-macbookpro:Constructor-tear-offs leafp$ ~/src/dart-repo/sdk/xcodebuild/ReleaseX64/dart-sdk/bin/dartanalyzer  ~/tmp/test.dart
Analyzing /Users/leafp/tmp/test.dart...
  error • Evaluation of this constant expression throws an exception. • /Users/leafp/tmp/test.dart:10:3 • const_eval_throws_exception
1 error found.

The analyzer error message is exceptionally unhelpful here. The CFE error is much better (see below). cc @bwilkerson @stereotype441 @srawlins who have talked about trying to push on error message quality/consistency.

Yeah, the analyzer's constant evaluator is really bad at error reporting.  Since constant evaluation is essentially a limited form of code execution, it would make sense to just display a stack trace when something like this happens.

Yeah, the analyzer's constant evaluator is really bad at error reporting. Since constant evaluation is essentially a limited form of code execution, it would make sense to just display a stack trace when something like this happens.

Possibly, but I don't think that's enough.  I think that would be reasonable if this was an assertion failure, but here, it's that the code in the assertion is not a valid constant.

Yeah, the analyzer's constant evaluator is really bad at error reporting. Since constant evaluation is essentially a limited form of code execution, it would make sense to just display a stack trace when something like this happens.

Possibly, but I don't think that's enough. I think that would be reasonable if this was an assertion failure, but here, it's that the code in the assertion is not a valid constant.

Yeah, the kind of thing I was imagining would look something like:
test.dart:9:24: Error: during constant evaluation, `.length` can only be used on strings, not on `List<String>`.
  })  : assert(strings.length >= 1);
                       ^^^^^^
test.dart:12:10: Context: while evaluating constant
const s = Sample(strings: ['abc']);
          ^^^^^^

(With additional context lines if the constant evaluation stack goes deeper than this)

We originally had rules saying that c.length would only be potentially constant if c had type String or dynamic, but we took the type checking out of being "potentially constant" due to requests from the parser writers at the time. They wanted to be able to check during parsing whether something was potentially constant.
That means that the language specification doesn't prevent you from writing something which we know will fail due to type-checking during constant evaluation (and because of that, it's technically a valid program as long as you never call the constructor as const).
I think that was a mistake, and we should fix it at some point.
We can define being potentially constant as a predicate that can be tested (and failed) at any stage of compilation, and just let the parser allow any expression in const constructors, with the side-requirement that they must be potentially constant, which we then check later. (That is, it doesn't have to be a parsing error to write const Foo() : x = print("hello world");. As long as it's eventually a compile-time error, everything is fine.)


Implement MarkOptional

Implemented @kalbert312 proposal mentioned in #77, because I needed it in my project.

@quezak done.

Good job. It seems useful 👍

Released as<EMAIL_ADDRESS>


feature: allow to congfiure the worker_shutdown_timeout

The default 3s may be too low.

many thx, merged


Tell clippy it's wrong

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@859f869). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #342   +/-   ##
=========================================
  Coverage          ?   79.81%
=========================================
  Files             ?       26
  Lines             ?     6883
  Branches          ?        0
=========================================
  Hits              ?     5494
  Misses            ?     1389
  Partials          ?        0

Impacted Files
Coverage Δ

src/lib.rs
56.2% <ø> (ø)

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 859f869...344f1c8. Read the comment docs.


Allow splitting spec file using jinja2 env and/or json references

Fixes #254 .
This breaks almost all tests, most probably because this change affects the way definitions are loaded and the Swagger spec file is loaded.
It's still work in progress, and any feedback or help is welcome. It's "works on my machine ™" quality till now.
Changes proposed in this pull request:

Use a jinja2 environment when rendering the YAML swagger spec to allow to include other jinja2 files in the template (including macros, etc.).
Resolve JSON references, and render those too using jinja2 when applicable (based on file extension)
Use jsonschema's RefResolver to load all definitions (WIP)

I'm closing this PR for now (as it's pretty old).


Allow Rails 5.2.x

Rails 5.2 requires minimum Ruby version 2.2.2, however RVM said this version was deprecated and recommended version 2.4.1.
Rails 5.2 also requires specifying the ActiveRecord::Migration version with lowest possible version 4.2 so I set the minimum required Rails version accordingly.

Coverage remained the same at 99.796% when pulling 8f0f920f96f87b3d79a415fee562e5f635a80882 on spiria-toronto:master into aa216756d0475a0ef35ff195f406de64e1d79615 on sungwoncho:master.

Hey, any updates? Are there any plans to support rails 4.2 ?

@sungwoncho it looks like there are plenty of people using this gem and require some amount of involvement to keep it up.
Are you still interested in being the maintainer?

@chevinbrown I cannot maintain this gem at this time because I do not use it personally and do not have bandwidth. Are you interested in maintaining this gem or a fork?

I would be happy to share in maintenance and possibly expand the contributor group if you're willing to share. This is a great gem, it just needs a little love.

I would be happy to share in maintenance and possibly expand the contributor group if you're willing to share. This is a great gem, it just needs a little love.
❤

@sungwoncho 👀

@jmajonis it’s been a bit! Thanks for the contribution!

@sungwoncho, how would you like to handle gem updates?

@sungwoncho if you're comfortable adding me to the gem owner, I'll prepare a release.
gem owner --add<EMAIL_ADDRESS>has_friendship

I will delete this once you've read it.

@sungwoncho are you willing to share gem ownership? If not, I'm not sure I can provide much value to this project since moving forward will require a few frequent releases.


[24.x] Aggregatted PR WFCORE-6825 WFCORE-6833

Do not merge, this is just an aggregated to verify WFCORE-6825/WFCORE-6833

Core -> Full Integration Build 9 outcome was UNKNOWN using a merge of 8ed12c377e40f89b1bb0ee56da6950331261edbd
Summary: Canceled Build time: 00:01:01

Core -> Full Integration Build 9 outcome was UNKNOWN using a merge of 8ed12c377e40f89b1bb0ee56da6950331261edbd
Summary: Canceled Build time: 00:01:02


Cyrillic symbols in URL

Currently, as pointed out by @Kristinita, the acceptance and decoding of Cyrillic symbols is not being handled.
Eg. http://kristinita.ru/logo/Снежинка.jpg

Fixed with https://github.com/alvesjtiago/hover-preview/commit/d0504f2b9434f828d3d025a48c1bb3f23144ccf5


Add temporal clustering

Use a complexity invariance distance to calculate distance between a matrix of time series to run a hierarchical clustering between these different time series. This can potentially be used to cluster spatial areas of interest. Closes #368

Everything looks like in working order, thank you.
Confirm tests pass with minor change to a metric (@Zapiano to submit another PR to fix this).


xchain allowed chains should be read from onchain config - contract

Description
In order to prevent a malicious user from creating a space referring to testnet while on mainnet, the list of allowed chains should be held onchain and respected by the contract when trying to set a rule.

The contract is written and all work for extending contract key values is contained in #567


Week of January 18: Cut buildpack releases

Superseded by https://github.com/paketo-buildpacks/web-servers/issues/175


Coffeescript, Maybe?

The source is in javascript and javascript has some extra brackets and stuff that is not necessarily needed.
I think we should convert this to CoffeeScript. What is your opinion?

While I don't really have a problem with coffee-script, Id rather not take up converting it right now. Most likely the functionality of this package will be in the 1.0 release anyhow and I have little coffee-script experience so the syntax would be a learning curve. If you'd like to take a stab at it, be my guest, but not sure it's worth it.
On a side note, i'm still trying to get serialization working, any thoughts on #21?

@steelbrain Hey. Sorry for being MIA lately. I will take a look over things tonight and merge. Thanks for all your work!


Emit new child class in @Module decorator

Instead of reusing the prototype of the constructor to be decorated
directly, we create a child class and thus keep the whole original class
intact.
Previously any metadata on the undecorated module class was lost. Now it
lives on in the prototype chain.
Cf. https://github.com/rbuckton/reflect-metadata
Fixes #9

All the existing tests pass :smile:
Mmh, maybe I should add another one for the specific issue I’m trying to fix here.


Exact Search for TX, Account, Block

Story
As a user, I want to be able to search for a transaction by it's hash, an account by name, and a block by block number, so I can view the details of the TX/account/block to debug without interpreting the URL schema or finding a link.
Acceptance Criteria

[ ] User can search by TX hash
[ ] User can search by account name
[ ] User can search by block number
[ ] User is redirected if a match is found
[ ] User receives a message "Result not found" if no match
[ ] Tested

Assets

Designs

@deacix Added the designs for this (in Zeplin)

@icerove Adding you to this issue as well. Just needs an enhancement:
Currently, you can search by block hash, whereas we expect the user to search by block number (since they are more likely to have that)

@kcole16 there is not a one-to-one mapping between block height and block, especially for recent blocks.

@bowenwang1996 Interesting, is there ever a guaranteed one-to-one mapping, or should we just keep search to block hash?

For finalized blocks yes we can say that the mapping from blocks to heights is injective, but still not surjective though. In other words, for some height, there might not exist a corresponding block.

So do we still want to add the function to search from block height? @kcole16

@icerove Yes, let's add block height in addition to block hash, so users can search by either


Add an example notebook for the counting cans example

Changes
Add an example notebook for the counting cans example.
Add matplotlib dependency to avoid module not found errors.

Looks good! Can you also provide a link to this example in the README? Maybe in a quickstart section or something so people can find it

Sounds good. Let me merge it so I have a real link to work with, will add it in the next PR.


Activity not detected

Hey guys,
my bot sometimes detects the current Activity of a member, sometimes don't. I have cache and intents enabled, but nothing helps.

Filling out the issue template would be a lot better as you can provide your JDABuilder code there.

Please fill out the issue template. Just saying "my code isn't working" without providing any code is completely useless. We have these templates for a reason.


Allow running script for swift plugin

This change allows you to run scripts to prepare the release before uploading to swift.

we've moved to a new plugin model in 0.4, where plugins are external docker container. They are stored in separate projects. We have a placeholder for a Swift plugin here if you are interested in helping out! https://github.com/drone-plugins/drone-swift


Could you share the intuition behind my_Layernorm?

Wonderful work!
Could your share your insight on the design and the usage of my_Layernorm?

After layer normalization on the feature/channel dimension, the bias (mean of sequence dimension for each batch and feature) was removed. Why is the removal of bias necessary (for the seasonal component)?

The original Transformer has layer normalization after every attention or feed forward operation, but Autoformer seems to only apply normalization after the last decoder. What is the intuition behind the choice?

Thanks!

Hi, you can conduct ablation studies on these designs for more intuitive senses.
(1) Why is the removal of bias necessary?
This corresponds to the definition of autocorrelation, which is to remove the expectation for calculation
(2) Autoformer seems to only apply normalization after the last decoder.
I think you can still follow the vanilla transformer design, and the performance will be unchanged.


[incubator/elasticsearch] Elasticsearch 2.4 elasticsearch-client never reaches minimum availability: master not discovered

Is this a request for help?: Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report.

What you expected to happen:
Cluster is normal after a couple of minutes.
How to reproduce it (as minimally and precisely as possible):
helm install --set image.tag=2.4 --name elasticsearch incubator/elasticsearch
I am unsure whether this is a GKE specific issue.
Works fine with newer versions.
Anything else we need to know:

Hi @phidah, might this be an RBAC problem? It worked for us internally  with GKE 1.9.3 and ES 2.4

I am not sure. In the meantime I migrated to Elasticsearch 6 so the problem was solved 👍

As far as I can tell; this is because the the initial first master POD tries to do master-discovery via the service resource. But as the master-POD is still not in READY state, the service got no endpoints - so discovery fails.
I solved this by adding publishNotReadyAddresses: true to the master-svc.yaml file. In addition this makes the kubernetes plugin obsolete so even the ES docker images form the official library are working now.
The project https://github.com/fabric8io/elasticsearch-cloud-kubernetes also recommends to not use the kubernetes plugin and instead using a headless service: https://github.com/fabric8io/elasticsearch-cloud-kubernetes#kubernetes-cloud-plugin-for-elasticsearch


Fix quiz button width, when navigating from tutorial to docs and back

Bug/issue #, if applicable: 82666933
Summary
Fixes a small CSS specificity issue, where styles from the docs are overwriting the ones from Tutorials/Quiz.vue, for the ButtonLink component.
Dependencies
NA
Testing
You can use the bundle attached:
public.zip
Steps:

run VUE_APP_DEV_SERVER_PROXY=path/to/unzipped/bundle npm run serve
go to http://localhost:8080/tutorials/slothcreator/creating-custom-sloths
Assert buttons are big
Click on the Sloth link in the header of the page
Go back
Assert the buttons are still big.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests - no need, css only
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

@swift-ci test


calrify query behaviour

add test and clarify docs on how unspecified query strings affect matching

Coverage remained the same at 96.346% when pulling d7bfe560575d7b6d1b2b43eaedaff416590cf2c0 on ignore-irrelvant-qs into 5446946a5019269e66ec460996367a64923e5e92 on master.


@model(subscriptions: null) broken. Error in graphql-auth-transformer: Cannot read property 'level' of null

Having a schema
type Todo @model(subscriptions: null) {
  id: ID!
}

and running amplify api gql-transform will give
Cannot read property 'level' of null

in @aws-amplify/graphql-auth-transformer/src/graphql-auth-transformer.ts.
The code expects there to be an object with a level property.
Using amplify v7.5.4

hi @BeaveArony - just confirming, did you mean to type amplify api gql-compile?

I couldn't reproduce this issue on my end.

I couldn't reproduce this issue on my end. Is that the full schema?

This is not the full schema, as this would be too long, but I guess it's the @auth directive as the error comes from graphql-auth-transformer.js. Here is one type:
type Profile
  @model(subscriptions: null)
  @auth(
    rules: [
      { allow: owner, ownerField: "id", operations: [create, update] }
      { allow: groups, groups: ["SuperAdmin"] }
      { allow: groups, groups: ["Admin"], operations: [create, update, read] }
      { allow: private, operations: [read] }
      { allow: private, provider: iam }
    ]
  ) {
  id: ID!
  email: String!
  phone: String
  firstname: String
  lastname: String
  roleDescription: String
  joinedAt: AWSDateTime
  lastInvitedAt: AWSDateTime
  lastAuthenticatedAt: AWSDateTime
  cognitoUserStatus: CognitoUserStatus
  lastSelectedTenantId: String
  photoUrl: String
  tenants: [TenantMembership!] @connection(keyName: "byProfile", fields: ["id"])
}

When I change @model(subscriptions: null) to `@model(subscriptions: { level: off }) I can compile using the transformer v2.
Note: A fix for me was opening graphql-auth-transformer.js and changing two places from this:
subscriptions.level

to this:
subscriptions?.level

Getting this as well when running amplify api override, after migrating the API.


fix(data): database update

Fixes #1661
Changelog

challenge_contribution tables updated in the challenge and organization services (651 rows → 693)

Preview
Database

App

What are the other changes?

@tschaffter oh, additional annotations were added to some challenges.  In a previous effort (I think when we were implementing challenge count into the UI?), I noticed that some organizations had a count of 0.  So I went back and tracked down what challenges they were associated with.


[BUG] adding quest entity link to a journal entry prevents the journal entry from being opened.

Module Version: v0.6.0
Describe the bug
Adding a quest entity link to a journal entry prevents the journal entry from being opened.
To Reproduce
Steps to reproduce the behavior:

Copy quest entity link from the quest
Paste it into a journal entry
save the entry
try to open it again

Expected behavior
Journal entries should open even with quest entity links.
Browser:

Chrome

Foundry Version:
0.8.6
Game System:
DND 5e
Additional context
This issue is reproducible without any other modules enabled.

Duplicate of #46

Also this is fixed in the forthcoming release of FQL this week. I'll be closing out all the issues in the tracker hopefully before the release. This was actually broken due to the 0.8.x switch.


Use anonymized errors in populateScratchBucketGcsPath

Ensure that anonymized error is used as the first argument to daisy.Errf.

Anon as in anonymous or anonymized. Updated to expectedAnonymizedError


Scheduled mail sent multiple times

A scheduled mail was sent over 100 times to an forgiving acquaintance.
My suspicion;
Mail sender was a Gmail alias. (sent as other email account), so I suspect that because of this the script was not capable of removing the schedule label.

Thanks for your report. Yes, it looks like it was not capable of removing the schedule email.
The program was able to add labels so we are not sure why it could not remove the labels (as permissions are available). Is it possible to have a screenshot of the email with the labels? None of the other users have reported such an issue so far.

Thx for your reply.
I don't have a screenshot, because I took the 9 am label off. This to make sure it would not get send anymore.
Will try to reproduce soon with an email adress owned by myself.

Did another test and a few things went strange:
The Queue label and the "timestamp label" are removed. The mail is sent, but the mail is for some reason still a draft.(concept)
I also received the following error:

Can it be that the language setting of Gmail has an influence? (for me this is Dutch)
Thanks already

Thanks for trying this out again.
It looks like gmail cannot remove the label for some weird reason.
Can you please try to uninstall and install the app again?
Uninstall GmailScheduler - https://script.google.com/macros/s/AKfycbw6hnnKGeG6xUsbRE9c3WSvJibTbaW88DP9f83e8lFnc1v1kL0/manage/uninstall
Then https://script.google.com/macros/s/AKfycbw6hnnKGeG6xUsbRE9c3WSvJibTbaW88DP9f83e8lFnc1v1kL0/exec run again and approve permissions to add again.

Ok, done.
Shall I try again?

yes, all the best :+1:

@sjoerdvh - shall we close this?

Okay
Met vriendelijke groet,
Sjoerd van Heummen
Cursusleider/Adviseur
Mobiel: 06-49678282
<EMAIL_ADDRESS>www.wordpresscursus.com
Op 18 mrt. 2015 11:49 schreef "Webdigi - Web Development" <
<EMAIL_ADDRESS>
@sjoerdvh https://github.com/sjoerdvh - shall we close this?
—
Reply to this email directly or view it on GitHub
https://github.com/webdigi/GmailScheduler/issues/15#issuecomment-82889441
.


docs: correct Android MainActivity import path

@kevinboosten I release new version, problem is still throwing?

@bazuka5801 I see you already changed the README in other PR's, so this can be closed.

@kevinboosten Thanx!


low quality documentation

I think ppl (like me) who only know the basics, but never used an event storage in a project, won't understand how to use this lib, because the documentation is too low quality. It is just a bunch of examples without any indication why and when we should use the actual function.

I agree.

@inf3rno , I agree.
@adrai , maybe you could copy some bits from a project of yours and post them on the docs.
At this point, I've deciphered by trial and error.

Hey everyone 👋
New maintainer here… we, i.e. @thenativeweb, have taken over the responsibility to maintain this module from @adrai, and I would like to give a little update on this issue:
We agree that there is a strong need for a better documentation, and this will be one of the first things we are going to do with this repository. Hence, I am going to close this issue for now.
If you have any questions or anything else, please feel free to re-open it, or to open a new one 😊


functions with destructuring parameters are not inferred as type predicate correctly

🔎 Search Terms
infer type predicate, destructuring
🕗 Version & Regression Information

This changed between versions 5.5
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
https://www.typescriptlang.org/play/?#code/C4TwDgpgBAGlC8UDeVSQFxQOQEEsG4oBDTAZ2ACcBLAOwHMoBfKAH2VXAkywCECoARmUq0GjfACgANhGBQAHqUwwA2gF0EUdZIkB6XVFIALAPYBXKQBMoNE3IgUKJihIDGJmuSgAzKlOAOEJYAjJgoaFzYeIQkhiL0TOqaihJQUAB0vv4OABQ54ZxMAJQIAHwckAjwiLhYRTrunnJZARRBAExhFZG1McLUCYxJiClpmX6tOfJlCukRVTV49RJAA
💻 Code
type X = { type: 'A'; a: string } | { type: 'B'; b: string };
let xs: X[] = [];

// should not error
const filtered1: { type: 'A'; a: string }[] = xs
  .filter(({ type }) => type === 'A');

const filtered2: { type: 'A'; a: string }[] = xs
  .filter(x => x.type === 'A');

🙁 Actual behavior
error on filtered1
🙂 Expected behavior
not error on filtered1
Additional information about the issue
No response

That's (partly) because there is no identifier to use there:
const filtered1: { type: 'A'; a: string }[] = xs
  .filter(({ type }): ??? is { type: "A"; a: string; } => type === 'A');

One could be generated though but it would slightly go against the recent "reuse as much as possible from the source file" goal. It would require replacing the whole binding pattern with an auto-generated identifier

But there is an identifier there: type.
It would be beautiful for the predicate to be:
const filtered1: { type: 'A'; a: string }[] = xs
  .filter(({ type }): type is "A" => type === 'A');


Refactor Watson input to connected components

Won't mark as completed, but route to send transcript to server has been added. Will mark complete after checking for other needed connections.