Namespace prevents using statements

Using statements can't be used because EditorCoroutines is both the namespace and class name. This requires fully qualifying every use of the class, which results in code bloat. Sharing the namespace and class name is ambiguous to the compiler, to resolve this the namespace could be changed to something like marijnz.EditorCoroutines
For example
using EditorCoroutines;

...

EditorCoroutines.StartCoroutine(foo, bar); // Won't compile due to ambiguous resolution

Hey, changed it. https://github.com/marijnz/unity-editor-coroutines/commit/6f418df16de82573d63b04473f0758a5d9769376. Thanks for the suggestion.


The Road to Composability

Here are some thoughts about the architecture of the project going forward, from the perspective of composability. In the next 4 paragraphs, I propose some changes to the design of the base classes.
Function-level composability
Few of the existing Augmentation modules use more than the __call__ method to perform their transformations. All of this behavior should be factored out into other functions that can then be called in the ~call~ method in sequence, or as the composition of those functions. These functions ideally would all be written in the "pure" style, where they operate only on their inputs and return a result, rather than operating on state defined elsewhere. This will make debugging easier and will also most likely surface some functions as candidates for refactoring into another library. As an example, the create_scanline_mask method in DirtyRollersAugmentation is a prime candidate for splitting up into smaller functions.
Module-level composability
The current modules are all written in a tightly coupled style, where operations are applied to input images and then stored directly in a pipeline phase, from the __call__ method of the augmentation. This should be changed so the call method instead takes an image as argument, then returns itself and the result of the completed operation as a tuple or list. Then the calling pipeline can sequence these on its own, without the augmentations being able to "see" the pipeline they're a part of. We would then be free to modify the internal behavior of augmentations or pipelines, so long as we maintain their interfaces.
This would facilitate direct composition of Augmentations too; in this case, it would be possible to write an Augmentation definition like lambda img: Augmentation2(Augmentation1(img)[1]), which ignores the first element of the tuple returned by Augmentation1 (namely, Augmentation1 itself) and operates on the output image.
Pipeline-level composability
Since all Augmentations are fundamentally matrix operations on the numpy.array representation of image data, their compositions are (or can be) given by matrix compositions, which gives us some nice mathematical properties. In particular, the associativity of matrix composition lifts to associativity of Augmentation composition, once module-level composability is ensured. This means that Augmentation3(Augmentation2(Augmentation1(image))) is the same no matter whether we combine Augmentation3 and Augmentation2 first or combine Augmentation2 and Augmentation1 first.
It gets better: AugmentationSequences are really just wrappers around lists, and so they also compose associatively: running Sequence1 and then Sequence 2 is the same as running (Sequence1.augmentations + Sequence2.augmentations).
Better still: AugmentationPipelines are dictionaries underneath, and have an associative composition too, but may involve renaming keys in the addition. AugmentationPipelines are actually already a mechanism of Augmentation composition, in the sense that running Pipeline1 and then Pipeline2 in sequence should be the same as running one pipeline that contains all phases of Pipeline1 followed by all phases of Pipeline2.
Factor probability out of Augmentation?
Currently the only state & behavior inherited by extenders of Augmentation is the probability. I submit that "probability of being applied" is not a property inherent to Augmentations, but rather to the pipeline running the Augmentations. As such, probability should be factored out of every Augmentation and into the pipeline class, along with the relevant calculations. This would allow, for example, OneOf to just sample its sequence to get an augmentation to run, rather than needing to inspect every member of the AugmentationSequence it is given, and perform an extra calculation with the probabilities it finds.

Right now, if you run the test in the latest commit here, you should get an error that AugmentationSequences are not callable. Of course, this makes sense because they don’t have a __call__ method, but the existing pipeline seems to treat them as if they did. I’m pretty sure this is erroring because at some point I removed the direct dependency onAugmentation from AugmentationSequence, but sequences are not functions and should not be applied.
I started a proof of concept fork for moving probability out of individual augmentations and into the pipeline here. I still need to remove all of the force parameters from every __call__ method, and the corresponding if (self.should_run or force=True) checks, but I got distracted exploring a much deeper refactor, in a new “composability” branch.
I want to do more work before I put this other branch up for review, but basically it removes most of the object structure and treats Augmentations (remember, these are just matrix operations under the hood) as first-class functions. The pipeline phases are then just lists (AugmentationSequences already are!) of Augmentations, with the AugmentationPipeline just reducing each phase-list over the input image to produce the dictionary of AugmentationResults.

After thinking hard about this all week and reading documentation and source from other libraries in this space, I'm retracting this proposal and closing this issue. Much of what I intended above would be too far-reaching for our goals, and mostly should now be ignored. Here are some responses to stuff above, in no particular order:

We want a familiar interface for users of other augmentation libraries, like Albumentations and Imgaug. Those libraries (and ours) use pipelines declared as a list of augmentation constructors passed to a pipeline constructor. In contrast, the initial proposal here would change the pipeline to a simple list of functions sequentially applied to the input, removing the object structure from augmentations entirely and moving responsibility for their execution elsewhere. This would be a dramatic change for a casual user.
We want a familiar codebase for contributors to other augmentation libraries. Currently, the architectural style of this project and the others is similar enough that contributing to both should be a low-friction experience. The original proposal here would introduce a very different structure, and increase the contribution overhead for developers coming from those libraries.
Composition at the level of augmentations can be achieved by producing a wrapper augmentation which calls the two (or more) being composed. This has the benefit that, while it would reduce the amount of code written in the pipeline declaration, all component augmentations will produce separate AugmentationResults in the final execution, allowing for more granular inspection of the pipeline process. Composing augmentations via their __call__ methods (i.e., defining Augmentation2(Augmentation1(image)) would require a significant architectural change already voided by points 1 and 2 above.
Pipelines are currently composable in one way: for two AugmentationPipelines named pipeline1 and pipeline2, the call pipeline2.augment((pipeline1.augment(img)["output"])) is their sequential composition. There's another sense of composition in which the phases of each pipeline would be interleaved, allowing for the ink phase of pipeline2 to run after the ink phase of pipeline1, but before the paper phase of pipeline1. Similar to the case of point 3 above, this form of composition should be expressible via a more generic class that accepts the component AugmentationPipelines in its constructor.
Other libraries set the probability of running an augmentation in the constructor of the augmentation, and not externally in the pipeline as I originally wanted. Again, for conceptual compatibility with the ecosystem, we should not factor probability out of augmentations.


Delivery cannon recipes for ingots

https://mods.factorio.com/mod/bzvery/discussion/636fe3d98e7ce16459b8f290

Change forthcoming


Move tab and Whisp chat BUG

Whenever you get a new whisp chat it will straight go to a separate tab instead of staying on the main chat tab, if you close it or /reload and the same person whisp you again you will not be able to see the chat, it's going to be empty and you'll have to close the chat and ask whisp the person again to fix it.
When you trade to move trade or general tab to a separate tab it will not work, the tab will be created but the chat will still be on the main general chat for all other normal chats, a way I found of fixing this is disabling Glass, creating a new tab for Trade/general/guild chat and enabling Glass again, that's the only way of doing it.

There's the photo of how the separate whisp window looks if you close the whisp chat and they whisp you again. it looks like that. You have to close it and whisp the person back to recieve more whisps but the old whisp chats are gone of course.

These appear to be 2 separate issues.
I'll address the first part (new whisper chat) in a PR here shortly. Consider creating a second bug for the other piece (moving tab, trade chat).

These appear to be 2 separate issues.
I'll address the first part (new whisper chat) in a PR here shortly. Consider creating a second bug for the other piece (moving tab, trade chat).


added handling for adding rpms to an image as well as the relevant tests

Currently working on getting elemental registration through combustion working in eib. So far, I've been able to get it work with some few hacks (which are omitted from here, along with the Elemental specific stuff as it is not complete). To get there though, I needed to be able to add the RPMs to the image, so I built the handling for that as well as the tests. I’m not sure if this is how you guys would have gone about it, so I’ve made this PR a draft for now

Question:

the folder rpms is required? I think we should follow the same as currently doing here: https://documentation.suse.com/sle-micro/5.1/html/SLE-Micro-all/cha-images-combustion.html
WDYT??? (To be fully compatible with the current combustion + ignition implementation)

So a few things, first, I added a test for the situation where the rpm dir is empty, as well as handling for that, let me know how you guys feel about that. Also, because I decided to keep the rpm dir in "testData" using .gitkeep I had to add handling for that in getRPMFileNames() which I really dislike so that might not survive this pull request.
As for the other tests, I'm not sure if there was a more graceful way to go about what I did, so let me know if what I did was fine or if it's not convential. The main reason I didn't use defer here was to ensure the order of events


Ability to log more than 1 passenger in tow aircraft

Pacific Region conducts fam flying in their 182 tow planes that can accommodate up to 3 passengers. The app currently only supports 1 passenger. They need the ability to log all passengers in the plane while conducting fam ops with these aircraft.

Adding this will require the following general steps:

Create a new version of the SQL model
Add "Passenger2" and "Passenger3" relationships to the Aircraft entity
Similarly, the FlightRecord entity that stores the records of each flight permanently would need a "Passenger2" and "Passenger3" relationship added
Add a number of passengers field to the plist from which the app loads the aircraft attributes so that the app knows which aircraft support 3 passengers
Add 2nd and 3rd passenger fields to the "Edit Aircraft" view controller that shows up when you tap an aircraft
Revamp the aircraft UI in the "Airplanes" view controller which controls how the aircraft appear in the right side of the app.

An alternative to #2 would be to change Passenger from a one-to-one relationship to a to-many one. However, this could break code in some places. For example, if Bloggins is already a passenger in a glider and we add Smith as passenger in that same glider, Core Data, which manages the SQL database, will currently automatically remove the relationship between the glider and Bloggins. If passenger becomes a to-many relationship, then that code would incorrectly result in both of them being passengers in the same glider. We would have to add a check to find and remove existing passengers for 2 seat aircraft when adding a new one.
After this some general debugging will be required, because the app does not currently look for flights flown as second or third passenger so they would not, for example, appear in a pilot's list of past flights or log book. That said, the 2nd and 3rd passengers would generally not be pilots and even if they are the time would not be loggable, so this might not actually matter. Nevertheless the potential ramifications of having multiple passengers would have to be studied.
Overall this change is certainly doable but would take a bit of work.

I would suggest we go with the to-many relationship as all the checks (same passenger to more than once on a flight, same passenger not on two different flights at the same time), would need to be changed anyway, and are simpler when looking at a simple place (same relationship tables).
That relationship would then be limited by the max number of passenger.


backuprestores3.ipynb - EXIST WHERE clause does not match CREATE for certificate.

Exist check uses IP without port in the WHERE clause, but creates the cert with the port number in the name.
Current:
USE MASTER
GO
IF EXISTS (SELECT * FROM sys.credentials WHERE name = 's3:///backups')
DROP CREDENTIAL [s3://:9000/backups];
GO
Should be:
USE MASTER
GO
IF EXISTS (SELECT * FROM sys.credentials WHERE name = 's3://:9000/backups')
DROP CREDENTIAL [s3://:9000/backups];
GO

Huh - code between carets was removed in the comment. (let me know if it's not clear)

fixed in notebook


fix uwsgi config for docker image

I don't think kazoo is an optional dependency because when from iris.sender.coordinator import NonClusterCoordinator runs, coordinator will still try to import the kazoo libs.

good catch :+1:  updated the PR.


Can't create git repo in macOS client

I tried creating a personal git repo in the macOS Keybase client app, however it never gets created.
The create button displays the spinning icon endlessly.
EDIT: I recently updated to macOS High Sierra.
What should I try ?
Thanks !

We will take a look if you ‘keybase log send’. Thank you.

@maxtaco log id is cb12b9bd422b2048df6a621c

Thanks. We are investigating. We have a service outage.
On Tue, Nov 14, 2017 at 8:06 AM Iosif Miclaus<EMAIL_ADDRESS>wrote:

@maxtaco https://github.com/maxtaco log id is cb12b9bd422b2048df6a621c
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/9541#issuecomment-344253280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA05_9pGYBI8DSupRKChL4nz7p_eCu09ks5s2ZBrgaJpZM4QdQ8q
.


Create and update hacs.json

To render readme as information in HACS

Is this card even working?

Is this card even working?


fix: replace deprecated IntegrationFields type with IntegrationField type

Note: This PR should not be merged until https://github.com/prismicio/prismic-types/pull/57 is merged and published.

[ ] Update this package's @prismicio/types peer dependency version to the newly published version to ensure prismicio/prismic-types#57 is available.

Types of changes

[ ] Chore (a non-breaking change which is related to package maintenance)
[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This PR fixes prismic-ts-codegen by using the correct non-deprecated IntegrationField type.
IntegrationFields (with an "s") was deprecated in @prismicio/client v7. Although IntegrationFields is still a valid API, TypeScript will warn about its deprecation status, and the type will eventually be removed from @prismicio/cilent.
Checklist:

[ ] My change requires an update to the official documentation.
[x] All TSDoc comments are up-to-date and new ones have been added where necessary.
[x] All new and existing tests are passing.

🐰

Codecov Report

Merging #48 (a02ca39) into main (68c6fb9) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main      #48   +/-   ##
=======================================
  Coverage   98.73%   98.73%
=======================================
  Files          23       23
  Lines        1655     1655
  Branches      142      142
=======================================
  Hits         1634     1634
  Misses         21       21

Impacted Files
Coverage Δ

src/lib/addInterfacePropertiesForFields.ts
98.64% <100.00%> (ø)


Allow hot module replacement in "webworker" targets

This is the same as #1521, now merging into the webpack-2 branch since this includes breaking changes (i.e. the removal of window.addEventListener).

Thanks

@sokra https://github.com/webpack/webpack-dev-server/pull/298 is still open (and is needed to use HMR with the new hot/emitter.js change). Will there be a new webpack-dev-server v2 release alongside webpack v2?


not able to upload image using attachment

I am facing problem while trying to prompt image to the bing thorught attachment but facing the following error
`import asyncio
import os
from sydney import SydneyClient

os.environ["BING_U_COOKIE"] = '''1EGoJt1yjZ4phWsfhRb-jOz_kn02a2aNSJ-ZTepKf9RD5FiP0NBvSRPkrUqOF8qxyG9qs2Zq6U6THoi74O3LzaxWYlXC6o3x3LlygK0JBTwAoLZQ9OFMFa_zCh1E8WAs9XybXsJtmNqjGlnr7qu7DVOsdXfJQv6sH_stxoT44n1pe_XM2hD2nvi2mTHIh4T009XUusjzCk3ESouAZ9lpErBT0mSeB_WwjnS_yMCxJhuo'''

async def main() -> None:
   async with SydneyClient() as sydney:
       while True:
           prompt = input("You: ")

           if prompt == "!reset":
               await sydney.reset_conversation()
               continue
           elif prompt == "!exit":
               break

           # Provide the URL to your image here
           image_url = "https://th.bing.com/th/id/OIP.TILseDM6LQr7VTeARsInPQHaFj?pid=ImgDet&rs=1"

           print("Bing ai: ", end="", flush=True)
           response = await sydney.ask(prompt, attachment=image_url)
           print(response, end="", flush=True)
           print("\n")

if __name__ == "__main__":
   asyncio.run(main())
`

For which i am getting the following error
Traceback (most recent call last):
  File "C:\wamp64\www\project_1\api_demo6.py", line 27, in <module>
    asyncio.run(main())
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\asyncio\runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\asyncio\runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "C:\wamp64\www\project_1\api_demo6.py", line 22, in main
    response = await sydney.ask(prompt, attachment=image_url)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\site-packages\sydney\sydney.py", line 459, in ask
    async for response, suggested_responses in self._ask(
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\site-packages\sydney\sydney.py", line 316, in _ask
    attachment_info = await self._upload_attachment(attachment)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Dell\AppData\Local\Programs\Python\Python311\Lib\site-packages\sydney\sydney.py", line 275, in _upload_attachment
    raise ImageUploadException(
sydney.exceptions.ImageUploadException: Failed to upload image, received empty image info from Bing Chat
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x0000017F24685D90>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x0000017F245E2A50>, 10168.265)]']
connector: <aiohttp.connector.TCPConnector object at 0x0000017F24685E90>

Hi @Parampatel07 Which version of the library are you using? There was a small change in the API, so 0.17.0 contains a fix for that

Hi @Parampatel07 Using the latest version (0.17.1), I cannot reproduce this error. This is my output:
You: What does this show?
Bing ai: The image you sent shows a pile of okra, both whole and sliced. Okra is a herbaceous hairy annual plant of the mallow family and its edible podlike fruits. Okra is native to the tropics of the Eastern Hemisphere and is widely cultivated in the tropics and subtropics of the Western Hemisphere [^1^]. The tender unripe fruits are commonly cooked as a vegetable [^1^]. The okra in the image is bright green in color, both whole and sliced. The sliced okra is cut into small pieces and is arranged in a pile. The whole okra is arranged in a pile and is pointing in different directions. The background is white [^2^].

I hope this helps!

Please, reopen this issue if the problem persists on you on the latest version, thanks!

Works well form me too after using latest version , Thanks for the help


MSGate not in top level

Description of the issue
cirq.MSGate does not exist, but cirq.ops.MSGate does.  Think it should be at the top level too?

Adding triage discuss to determine whether to expose at the top level.

Ill take this issue


AtomicCell without lock for non-usize values in stable.

Now that std::atomic::AtomicU{8,16,32,64} has been stabilized, please allow AtomicCell to store values with non-usize widths without a lock.
This would require increasing the min rust version. Let me know if you like me to send a pull request.
Thanks.

Ah, we are waiting for cfg(target_has_atomic) to be stabilized, I guess?

Honestly, I would just use those non-usize atomic types. Platforms on which they don't exist are niche anyway...

@stjepang, I created pull request #454. I had to use cfg(target_pointer_width) on stable to make the CI pass. The code can be cleaned up later when cfg(target_has_atomic) is stabilized.
I don't quite understand why dependency tree check is failing now. Anyways, we need a new release (with breaking change), and that would most likely fix the dependency tree check issue.

The dependency tree check was failing because we needed cfg-if version 0.1.10 instead of 0.1.2. Fixed that.

I reworked the patch to use autocfg crate. The code is cleaner and we don't need the MSRV bump anymore.


doc: add pprof doc

What type of PR is this?
doc
What this PR does / why we need it (en: English/zh: Chinese):
en: add pprof doc
zh: 增加 pprof 文档中文部分
Which issue(s) this PR fixes:

补充英文


Refused error is throwing but i am providing proper hostname

I am providing proper endpoint, still, error displaying the localhost IP and throwing connection refused error
Cmd line :
newman run test_fail.json -e Auto_QA.json -r @reportportal/agent-js-postman --reporter-@reportportal/agent-js-postman-debug=true --reporter-@reportportal/agent-js-postman-endpoint=http://xxxxxxxxxxx.com:8080/api/v1 --reporter-@reportportal/agent-js-postman-token=8f9d4d9c-xxxx-xxxx-xxxx-fe08ddc7fada --reporter-@reportportal/agent-js-postman-launch=SampleRunJai --reporter-@reportportal/agent-js-postman-project=SUPERADMIN_PERSONAL --reporter-@reportportal/agent-js-postman-description=LAUNCH_DESCRIPTION -x
Error: connect ECONNREFUSED <IP_ADDRESS>:80
at C:\Users\xxxxxxx\AppData\Roaming\npm\node_modules@reportportal\newman-reporter-agent-js-postman\node_modules@reportportal\client-javascript\lib\rest.js:31:23
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: connect ECONNREFUSED <IP_ADDRESS>:80
at C:\Users\xxxxxxx\AppData\Roaming\npm\node_modules@reportportal\newman-reporter-agent-js-postman\node_modules@reportportal\client-javascript\lib\rest.js:31:23
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: connect ECONNREFUSED <IP_ADDRESS>:80
at C:\Users\xxxxxxx\AppData\Roaming\npm\node_modules@reportportal\newman-reporter-agent-js-postman\node_modules@reportportal\client-javascript\lib\rest.js:31:23
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: connect ECONNREFUSED <IP_ADDRESS>:80
at C:\Users\xxxxxxx\AppData\Roaming\npm\node_modules@reportportal\newman-reporter-agent-js-postman\node_modules@reportportal\client-javascript\lib\rest.js:31:23
at processTicksAndRejections (internal/process/task_queues.js:93:5)

When i add some console logs, following details are passing to "axios", is my argument mismatched with the expectation?
newman run https://postman-echo.com/status/200 -r @reportportal/agent-js-postman --reporter-@reportportal/agent-js-postman-debug=true --reporter-@reportportal/agent-js-postman-endpoint=http://xxxx-xxx-xxxxx.na.xxxxx.com:8080/api/v1 --reporter-@reportportal/agent-js-postman-token=8f9d4d9c-xxxx-xxxx-xxxx-fe08xxxc7xxx --reporter-@reportportal/agent-js-postman-launch=SampleRunJai --reporter-@reportportal/agent-js-postman-project=SUPERADMIN_PERSONAL --reporter-@reportportal/agent-js-postman-description=LAUNCH_DESCRIPTION -x
URL : //launch
method  : POST
options  : {"headers":{"User-Agent":"NodeJS","Authorization":"bearer undefined"}}
data  : {"name":"Newman launch","startTime":1617173255565,"launch":"Newman launch","attributes":[{"key":"agent","value":"@reportportal/newman-reporter-agent-js-postman|5.0.0","system":true},{"key":"client","value":"@reportportal/client-javascript|5.0.3","system":true},{"key":"os","value":"Windows_NT|x64","system":true},{"key":"RAMSize","value":8490938368,"system":true},{"key":"nodeJS","value":"v14.15.4","system":true}]}
Error: connect ECONNREFUSED <IP_ADDRESS>:80

This is same as the problem I've reported a long time ago: #42

Hi @jayanthktn @AdamHepner
This is an axios problem. By default, axios redirects us to <IP_ADDRESS>:80 if it doesn't find requested URL or http method(GET/POST/PUT). I guess the problem might be with the server http://xxxxxxxxxxx.com:8080/api/v1. It may not be running, or it may not work, or there is no such server at all.

In our case we use the same report portal instance with multiple programming languages/agents, and only this one is having problems

Hi, @AdamHepner
Thank you for your comment! It gave me a hint. The point is that you use the command line to work with newman-reporter-agent-js-postman and the custom reporter receives an object options with keys of a certain kind reportportalAgentJsPostman<YourOption>. Since our reporter does not process options of this kind, we have undefined values. And this causes the given error. As a quick fix, you can run the reporter programmatically (it works without this kind of error). As soon as possible new agent's version with the fix will be released that will allow you to work with the command line.

Let me try it programmatically, same host I am trying for UI
automation(java), it is working. It's only failing when I use it for Newman
cli.
Thanks
Jayanth
On Wed, 7 Apr 2021, 5:37 pm KatsiarynaTatarynovich, <
@.***> wrote:

Hi, @AdamHepner https://github.com/AdamHepner
Thank you for your comment! It gave me a hint. The point is that you use
the command line to work with newman-reporter-agent-js-postman and the
custom reporter receives an object options with keys of a certain kind
reportportalAgentJsPostman. Since our reporter does not
process options of this kind, we have undefined values. And this causes the
given error. As a quick fix, you can run the reporter programmatically (it
works without this kind of error). As soon as possible new agent's version
with the fix will be released that will allow you to work with the command
line.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reportportal/agent-js-postman/issues/43#issuecomment-814860531,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGOA2PAIYY5AQD3GL2P5C23THRDHRANCNFSM42D253ZQ
.

For me, the work-around was to remove the port 8080

Hi there!
We've already released a fix in the version 5.0.1.
Now, as @KatsiarynaTatarynovich noted, it is possible to correctly specify the agent parameters via the CLI.
I'll close this issue but feel free to open it again if you have any other questions on the topic.


Unable to create VkSurfaceKHR when following vulkan raii examples with cmake and vcpkg

Hey all!
I'm trying to follow the Vulkan-Hpp::raii samples with a cmake project that handles dependencies through vcpkg. Samples 1 through 4 work fine, but sample 5, creating a swapchain, blows up after failing to create a VkSurfaceKHR with glfwCreateWindowSurface, warning of missing VK_HKR_win32_surface. The context of the terminating code is:
// This warns 'glfw: (65542) Win32: Vulkan instance missing VK_KHR_win32_surface extension'
auto result{glfwCreateWindowSurface(static_cast(*instance), window.handle, nullptr, &_surface)};
//_surface = 0x0000000000000000
vk::raii::SurfaceKHR surface(instance, _surface);
//surface = {m_instance={m_instance=0x000001c5c0830080 {...} } m_surface={m_surfaceKHR=0x0000000000000000  } ...}
//terminates here
uint32_t presentQueueFamilyIndex = physicalDevice.getSurfaceSupportKHR(graphicsQueueFamilyIndex, surface)
? graphicsQueueFamilyIndex
: checked_cast<uint32_t>(queueFamilyProperties.size());
std::println(std::cerr, "not printed");
I've rigged up a minimal example here. Any hints as to what I might be doing wrong? Or better build systems and package manager combos for vulkan/glfw than cmake/vcpkg?

For anyone else who might run into this, I wasn't enabling the correct extension.


Missing information in "Enabling Continuous Delivery" lab

In Task 2 in Exercise 3 in the "Enabling Continuous Delivery" lab the configuration for the Source in  Windows Machine File Copy task is missing \Dev\ in the path.
I configured the path as the instructions said to:
$(Build.Repository.LocalPath)\FabrikamFiber.CallCenter\FabrikamFiber.Web
But the build failed. So I checked the path and at least on my ALMVM the correct path is
$(Build.Repository.LocalPath)\Dev\FabrikamFiber.CallCenter\FabrikamFiber.Web

@simbi Thanks for noticing and reporting. Yes the build fails because the Dev parameter in the Source property is missing. Will update the same. Thanks :-)


Use km-xxxx.ini if km-xxxxxxxx.ini doen't exist

upper 16 bits of keylayout value indicates keyboard layout.
lower 16 bits of keylayout value indicates country/language.
If the keymap file doesn't match exactly to keylayout value,
the typical keyboard of the country/language should be used.
For example [1]:
0x00000409: US English
0x00010409: US Dvorak
0x00020409: US International
0x00030409: US Dvorak for left hand
0x00040409: US Dvorak for right hang
0x0000040e: Hungarian
0x0001040e: Hungarian 101-key
[1] https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/windows-language-pack-default-values

If the keymap file matches exactly to keylayout value,
the typical keyboard of the country/language should be used.

Oops, DOESN'T here. Commit message edited.

You can just amend the existing commit and force-push it.
I like switching from %4.4x to %08x format
Please calculate the shorter number once and make a variable for it if needed. Generally, try to reuse as much as possible in the log messages so that they reflect the actual behavior.
If a file cannot be loaded, It's better to report it with the full path. That's more helpful in case of actual problems. No need to report what would be next.
I would want log messages like this:
[INFO] Cannot find keymap file /etc/xrdp/km-00010809.ini
[INFO] Cannot find keymap file /etc/xrdp/km-0809.ini
[INFO] Loading keymap file /etc/xrdp/km-0409.ini

@proski
Do you mean all km-%4.4x.ini files to be renamed to km-%08x.ini?
If so, I like it.
@jsorg71
What do you think? I like %08x too.
New keymap file loading would be:

When the client reports 0x00010809, find km-00010809.ini
If not found, find km-00000809.ini
If not found, find km-00000409.ini

I actually meant using 8 hex digit format for the numbers that don't fit 4 hex digits. For example, the US Dvorak keyboard is represented as km-10409.ini now, but it would become km-00010409.ini. We don't even have such keymaps yet.
But I agree it makes sense to rename all keymaps to use 8 hex digit. Distinguishing "full" and "fallback" maps doesn't always make sense. For example, the standard US English keyboard is not a good fallback for US Dvorak.
Now I think we should have some way to indicate that XRDP specifically supports some keyboard variant. Fallback to the default variant should be a cause for concern and an invitation to support the new keyboard variant. It should be [WARNING], not [INFO].
Symlinks would be a poor solution. It would be better to make it possible for a keymap to inherit data from another keymap and override a few symbols if needed. By the way, I don't think km-*0411.ini are supposed to be identical.

FYI, I found the official definition of locale identifier (keylayout in xrdp).

A  32-bit value which consists of the language ID in the low word (bits 0-15) and the sorting ID (bits 16-19) and a reserved value (bits 20-31) in the high word.

https://www.microsoft.com/Language/en-US/Search.aspx?sString=locale&langID=es-es

By the way, I don't think km-*0411.ini are supposed to be identical.

Yes. They're not supposed to be identical.  It has been confirmed that four km-0411.ini, km-e0010411.ini, km-e0200411.ini and km-e0210411.ini are identical.
In CJK languages, probably, the differences among them are IMEs. Not the keyboard variants.
https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown#keyboard-input-method-editors-imes

Is this patch still relevant? I suggest that we switch to 8 hex digit format for all km*.ini files.

I'll make another pull request just converting to 8 hex digit format.
And then rework this.

As #437 was merged, I updated patch and force pushed.
@proski could you look at this again?

Looks good to me.


Discussion - Highlights: after changing a highlight style, should that become the default?

I'm posting this to start a discussion.
I feel like it would be the most intuitive that if a user adds a highlight, then changes the style to pink, the next applied "highlight" should use pink too until the user selects a different style. So, the highlight style will always default to the last used style.
Thoughts?

I agree with you @kjantzer this should be use the last used style.


[Neural Speed] Update Setup.py

Type of Change
fix https://github.com/intel/neural-speed/issues/193 and https://github.com/intel/neural-speed/issues/194
Description
detail description
Issues: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

torch+cup needs the index-url which can not be worked in setup.py.


Crash Bugs

-Crash on left resize
-Crash on title bar hold
-Crash on debug prompt interact

Fixed titlebar hold crash (maybe) and command prompt interaction crash, but left hand resize remains. Still debugging this but other changes will be released with 0.2-pre


pass the generation_config when using stream function

Fix for the issue: #308

+1 really need this, took me a long time to figure it out can you merge it?


Hitachi projector

Hey @KimBurgess , I'm not sure what else to do to cleanup the command forming as there doesn't seem to be a structure or consistent pattern with commands and they all seem pretty random to me. These are the docs if you want to have a look https://aca.im/driver_docs/Hitachi/cp-tw-series.pdf

The first few pages of that doc lay out the protocol structure. It looks like there are two levels to this:

Commands (which include a fixed header, CRC, action, type and code)
Which are they wrapped in a secondary layer for the IP comms.

Where a clearly defined structure like this exists, drivers should model this rather than being a collection of preformed strings.

@KimBurgess I get that there is technically a structure according to the docs but there might as well not be as each command is pretty unique even for the same subset of commands like input selecting.
For example for input selecting, the CRC is different for HDMI1 and HDMI2 which is fine. However, their setting code is also different which doesn't really make such sense to me and why I think the structure in this protocol is useless IMO and also makes it harder to write nice structured code to build commands.

So to me, it seems like most commands need 4 bits to uniquely identify them which is 2 bits for CRC and 2 for setting code but annoyingly they are separated by 2 bits for Type which seems to be the same for all commands in a subset like input selecting. The only thing that makes sense in this protocol implementation to me is the 2 bits for Action which is [0x01, 0x00] for Set or [0x02, 0x00] for GET. This is why I'm not sure it's worth cleaning up the command building in the driver because of this.

Writing this all out, I can see what you're saying though @KimBurgess so I'll give it a try. Type can be used to identify what subset of commands (e.g. input switching) is being used and CRC+Setting code can be used to represent the specific command of a subset (e.g. HDMI)

I've made this commit to show my approach on this. Let me know if you think this better before I fully commit to refactoring this @KimBurgess https://github.com/PlaceOS/drivers/commit/cd1621b4975d038d1b7380612dc43d1989a5ce9e

@pkheav - sorry for the delayed response - just catching up on some of the PR's.
You can likely break that down a little more. If you look at the protocol structure there are three components to each command:

Action
This is one of: Set, Get, Increment, Decrement, or Execute and can pipe directly into an enum.

enum Action
  Set       = 0x0100
  Get       = 0x0200
  Increment = 0x0400
  Decrement = 0x0500
  Execute   = 0x0600
end

Type

Setting Code

Unintended keyboard mash... reopening.

you probably could skip the def self.query_requests by doing
   q = Hitachi::Projector::CpTwSeriesBasic::QueryRequests

Nice, thanks @caspiano , did not know that was possible and way neater :)
https://github.com/PlaceOS/drivers/pull/73/commits/05cc8fd1190b640bb15bab0ebe168f094f1c5437


Added case study on probabilistic programming and inference

Added the case study Inference that contains the contents of my bachelor's thesis Probabilistic Programming and Programmable Inference in Effekt.
The content includes Slice Sampling and Metropolis-Hastings algorithms, as well as some examples to show how these algorithms can be applied.

The tests are failing since a check file is missing. You just need to create a file with the same name that ends with .check and contains the expected outputs. You can look into the other case studies to see how this works.

The expected output might be a bit difficult to state since it could rely on random. Is it possible to use a different (deterministic) source of randomness for the tests?

Thanks for your contribution, @sinaschaefer. In order for the tests to pass, we need to take care of two more things:

As you can see here, you need to annotate your extern definition of pow with our new "feature-flag". Since we have multiple different backends, one extern definition is ambiguous and compiler can not safely figure out for which backend your extern definition works.
This may all sound horribly complicated, but in the end, you just need to prepend js to the right-hand side of the definition:
extern pure def pow(x: Double, y: Double): Double = js "Math.pow(x, y)"

Now, we can finally get the CI to run. Since your examples only target the JavaScript backend, we need to ignore your tests when testing the other backends (or add definitions for other backends to the extern definition). For that, you need to add the line examplesDir / "casestudies" / "inference.effekt.md" to the files
https://github.com/effekt-lang/effekt/blob/master/effekt/jvm/src/test/scala/effekt/LLVMTests.scala
https://github.com/effekt-lang/effekt/blob/master/effekt/jvm/src/test/scala/effekt/ChezSchemeTests.scala
https://github.com/effekt-lang/effekt/blob/master/effekt/jvm/src/test/scala/effekt/MLTests.scala
that is, to all backends for which your extern definitions do not work.

I hope this is helpful, and if not, do not hesitate to shoot us a message.

@sinaschaefer, if you'd give me write permission to your fork, I can happily make these changes for you.

@sinaschaefer, it appears you gave me permissions for the wrong repository. I need them for this one: https://github.com/sinaschaefer/effekt. Thanks in advance!

@dvdvgt Oh sorry, now it should be right. Thanks!

@dvdvgt could you round to make test go through?

It seems there's no simple solution for this. An generic Emit[R] effect is used for printing the results. Therefore, it is not know wether R is something that can be rounded before printing. Rounding where do emit is envoked does not work either because, there as well, the type of the thing being emited is not know and cannot be assumed to be a double.
I am enclinded to just comment out the parts that cause the failing of the tests due to varying precision of doubles depending on the machine it is run on.

We could handle into a structure like List[T] instead of inspecting. This would make testing much easier anyways.
What do you think @phischu ?

Merge it and revise it later.

I agree that we need to merge it soon -- but you know that we will never revise it, if we do not fix it now. Since @dvdvgt is already working on it, we could "quickly" fix it. Otherwise somebody in the future has to wrap their heads around it again and again just to enable these tests.

I did some inference myself and tried to explain most of the parts of the case study, as I found it hard to follow without pre-existing knowledge. The "metropolis hastings section" might still need some more explanations, though.
I tried to add some formalisation to the linear regression example. I am not sure if my interpretation is correct, and I will happily discuss it.

It's great that this was finally merged! 💯
However... with #590 we now support effects like emit better. Maybe you could refactor the emit effect to a singleton operation, still?


add head option for select view

address: https://nanopay.atlassian.net/browse/NP-2634
nanopay side: https://github.com/nanoPayinc/NANOPAY/pull/11154
add header for select view

How does this differ from RichChoiceView sections?

How does this differ from RichChoiceView sections?

I believe this is just adding support for default html select.

I think people have been using the RichChoiceView, not because they needed RichChoices, but just to get this header.
But my question is how is this different than the placeholder?

How does this differ from RichChoiceView sections?

RichChoiceView only take Dao


stake-pool: Check that initialized accounts are distinct

Fixes: https://github.com/solana-labs/solana-program-library/issues/2267

Looks good!


Add Spark version 1.3.0

Adding update of init.sh for Spark 1.3.0 release.
Successfully launched a Spark 1.3 cluster by pointing spark-ec2 to this branch.

Thanks @freeman-lab -- LGTM. Merging this.

Can you also open a PR against branch-1.4 ?


undefined method `configuration' for RSpec:Module (NoMethodError)

I've added packwerk and stimpack to our rails monolith but unfortunately if I start bin/rails c it fails with this exception:
bin/rails c
/Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack/integrations/rspec.rb:8:in `block in install': undefined method `configuration' for RSpec:Module (NoMethodError)
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack/packs.rb:36:in `each_value'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack/packs.rb:36:in `each'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack/integrations/rspec.rb:7:in `install'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack.rb:22:in `load'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/stimpack-0.4.0/lib/stimpack/railtie.rb:6:in `block in <class:Railtie>'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:68:in `block in execute_hook'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:61:in `with_execution_control'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:66:in `execute_hook'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:51:in `each'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:96:in `inherited'
	from /Users/user/Projects/app/app/config/application.rb:19:in `<module:Flowspace>'
	from /Users/user/Projects/app/app/config/application.rb:17:in `<top (required)>'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:92:in `require'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:92:in `preload'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:157:in `serve'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:145:in `block in run'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:139:in `loop'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:139:in `run'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application/boot.rb:19:in `<top (required)>'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
	from /Users/user/.rbenv/versions/2.7.5/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'

I added a binding.pry right before this line to look at what is available for the ::RSpec module and it's not much. I'm not sure why it is defined here:
[3] pry(Stimpack::Integrations::RSpec)> cd ::RSpec
[4] pry(RSpec):1> ls
constants: Rails
locals: _  __  _dir_  _ex_  _file_  _in_  _out_  pry_instance

When executing $ it shows the module is defined here:
From: /Users/user/.rbenv/versions/2.7.5/lib/ruby/gems/2.7.0/gems/rspec-rails-5.1.2/lib/rspec/rails/feature_check.rb:1
Module name: RSpec
Number of monkeypatches: 2. Use the `-a` option to display all available monkeypatches
Number of lines: 47

Any ideas why this is occurring?

I added this as a fix https://github.com/rubyatscale/stimpack/pull/13

Experiencing the same issue, I believe this can happen fairly easily if any of your dependencies extends RSpec


Set GH_TOKEN on deploy-storybook job

Description
https://github.com/storybookjs/storybook-deployer/issues/77

Hold on, I also need to fix the concurrency issue. Right now only one job is executing for a given branch, instead of one of each kind

I think it worked! https://github.com/oddbird/Metecho/runs/6313978941?check_suite_focus=true

 Deploy Storybook docs via GH action on pushes to main branch.


Models/services infrastructure planning

We had a chat on 2024-01-11 about what the user experience would be like for configuring models. It also seemed like running ingress, and maybe some other things as well, would benefit from similar user actions being available, so we are more broadly calling these things services, as Pat suggested already months ago.
The simplest version we would go and implement would look like this:

There's a page with all services. E.g. "Rothamsted data ingress", "GES", "Arima".
Each service has a page where one can enter a schedule on which this service will be run, and hit schedule.
Alternatively/in addition on that page there is a button for "Run now". Start by implementing either scheduling or "Run now", whichever seems easiest.
That page also has a text box where the user can write JSON, that will be passed to the service as an argument. This is used for e.g. setting model parameters. Maybe not in the first iteration, but eventually, this JSON will be validated against a schema for each service.
There's also a list of current schedules, and an option to edit their arguments.

In general, a service is a URL to which the backend sends a request to do a thing, together with arguments. The service then either returns something useful over HTTP, or in turn calls some backend end points to e.g. insert data.
In the first instance all our services will probably be Azure functions, and the scheduling mechanism can start out being bespoke for them.
In the future we might also directly display the output of a service run on the service page. In the first version you'll have to navigate elsewhere on the site to see the outcome, e.g. new data or model results. We might also later add a prettier version to set service arguments, prettier than a pure JSON block.
For the backend side of this, I think each service would need to have in the database at least

name
url
JSON schema for arguments
current schedules

I'm a bit unclear still on how the backend will make sure that the services actually get run on time. Do we run something like cron internally? For now might be good enough to set some parameters on Azure function apps.

#184 - This issue has a more detailed discussion of what the backend does to allow these features.

The minimal version of this now exists: On the front end you can create a service, give it a JSON payload, and click "Run". One can also see a history of runs and the responses to their HTTP queries.
Missing are:

Scheduling. See #193 and #194.
JSON schemas for service parameters.
Handling responses from services in a meaningful way. Currently we just log that the service returns a status code and a message. Any actual data that the service wants to send us has to go via the service making backend API calls. BaseService makes doing those calls easy though. Ideally we would have for instance ways of seeing whether a service has finished running, and having the outputs data in the database linked to the service run.
Preprocessing data in the backend before sending it to the service, and sending it as part of the payload. Currently payload parameters are fixed rather than read from the database, and if the service needs data from the backend it needs to get it through an API call. BaseService makes doing those calls easyish though.


refactor(operator): ensure parameter type safety for each subscriber …

…ctor
This PR is aligning changes followed by https://github.com/ReactiveX/RxJS/pull/296 for each subscriber construction. Previous PR ensures parameter type of call to Subscriber<> and each subscriber constructor still able to accept Observer<>. This isn't big issue since call already guards type so subscriber constructor won't be able to accept other than Subscriber<> but better to have build type safety.

LGTM

merged with 9e7e560
It was a tough merge because I changed a lot of files in my big PR the other day (#316) ... some of your changes may have been reverted.
Thanks again!

Thanks, I'll check TOT and create following PR if any following change's required.


Plans to release PPP support?

Hello!
Do you plan to release PPP support for next process f.e. by lwip pppos?
May be I can help?
Now I discovered for structure of library and have many questions - how to make better.

I am listening :)

I has take IPCONN as example.
lwgsmr_t
lwgsm_ppp_start(void* const arg, lwgsm_evt_fn conn_evt_fn, const uint32_t blocking) {
    LWGSM_ASSERT("conn_evt_fn != NULL", conn_evt_fn != NULL);

    return lwgsm_call_start("*99#", arg, conn_evt_fn, blocking);
}

in lwgsm_init.c has added section in parser
#if LWGSM_CFG_PPP
        } else if (CMD_IS_CUR(LWGSM_CMD_ATD)) {
                if (!strncmp(&rcv->data[0], "CONNECT" CRLF, 7 + CRLF_LEN)) {
			is_ok = 1;
                } else if (!strncmp(&rcv->data[0], "NO CARRIER" CRLF, 10 + CRLF_LEN)) {
			is_error = 1;
		}
#endif

now need to forward data from uart (lwgsmi_process()) to pppoe parser of lwip.
How to do it better? Also need some event to detect end of data connection...

m? what kind?

From your code
lwgsmr_t
lwgsm_ppp_start(void* const arg, lwgsm_evt_fn conn_evt_fn, const uint32_t blocking) {
    LWGSM_ASSERT("conn_evt_fn != NULL", conn_evt_fn != NULL);

    return lwgsm_call_start("*99#", arg, conn_evt_fn, blocking);
}

It seems that you are using call module of LwGSM library. The lib provides you events when call is being picked up or has been hanged-up
https://docs.majerle.eu/projects/lwgsm/en/latest/api-reference/lwgsm/evt.html#group___l_w_g_s_m___e_v_t_1LWGSM_EVT_CALL_CHANGED


Bump the DWARF format to version 4 on Darwin.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

This unifies the output across all supported platforms and
brings swiftc in sync with clang.
rdar://problem/28231982

@swift-ci please test and merge

This affects Linux too, right?

Yes, that's right. It affects everything besides Cygwin (which was already at 4).

Updated commit message.
@swift-ci please test and merge

The linux test failure appears to be unrelated.
@swift-ci please test Linux platform and merge

@swift-ci please smoke test Linux platform

Please test with following pull request:
https://github.com/apple/swift/pull/50
@swift-ci Please test Linux platform


include/netinet: Add missing IP_TTL definition

Summary
Impact
New option
Testing

Shouldn't we also add the handling logic for this new option to ipv4_setsockopt and ipv6_setsockopt?

@no1wudi will provide the patch in the next step.


SpFx Extensions Cannot be Deployed to new Dev Tenant

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
It should be possible to deploy a vanilla "hello world" extension to the app catalog on a dev tenant
Observed Behavior
Created a dev tenant per instructions at https://dev.office.com/sharepoint/docs/spfx/set-up-your-developer-tenant
Attempt to deploy a vanilla extension to the tenant produces the error: The requested operation is part of an experimental feature that is not supported in the current environment.
Steps to Reproduce
SharePoint
Create a dev tenant per instructions at https://dev.office.com/sharepoint/docs/spfx/set-up-your-developer-tenant
Create an app catalog
Local
Install nodejs LTM
npm install gulp yo @ microsoft/generator-sharepoint
yo @ microsoft/sharepoint

Select extension(preview) all other defaults
gulp build
gulp package-solution
drag/drop solution into app catalog

The requested operation is part of an experimental feature that is not supported in the current environment.

What is the URL of your tenant (we'd like to confirm it is a dev tenant).

demro2.sharepoint.com
demro3.sharepoint.com

Demro2 and Demro3 are NOT dev tenants.  What lead you to believe they were?  Just curious as I'm not seeing it in the backend and want to make sure there isn't some other issue.

The reason I thought these were dev tenants is because I followed the instructions from the linked article Set up your Office 365 tenant, completed the form at https://profile.microsoft.com/RegSysProfileCenter/wizardnp.aspx?wizid=7a6e3d71-b057-49cc-b2aa-158ff23432f3&lcid=1033&culture=en-us&dir=LTR, and finally signed up for the 30 day trial
Do you know if there is another way to create a dev tenant @mcmynn83 ?  It sounds like this might be an issue related to the documentation, or possibly an issue with the dev tenant provisioning process

Here is a link to the complete process used to set up both of these tenants.  What step did I miss?
https://dev.office.com/devprogram.

Hi @pdemro, I went through the steps myself to verify and I also did not get a dev tenant on the other side.  It looks like we may have an issue either with the documentation or provisioning.  We'll follow up and figure out what's going wrong.  As far as I can tell there are no steps you could have missed.

Whoops, the curse of multiple account management.  "Fizzlenik" is me, so yes we're actually looking at it.  -Jeremy Kelley

@JeremyKelley Where can I open a ticket to troubleshoot Dev Tenant provisioning?


feat: Basic details: explanations about the producer are in a b…

Hi everyone!
There's a new Widget available from the POC: SmoothBanner which allows displaying info at the bottom of the screen.
In this PR, there's also an initial implementation with the producer info on Basic details:

Note: the UltraBlack color was invalid (fixed ✅)

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

Project coverage is 6.83%. Comparing base (4d9c7fc) to head (d281ce8).
Report is 481 commits behind head on develop.

Files with missing lines
Patch %
Lines

..._app/lib/pages/product/add_basic_details_page.dart
0.00%
77 Missing :warning:

packages/smooth_app/lib/widgets/smooth_banner.dart
0.00%
18 Missing :warning:

...smooth_app/lib/pages/product/owner_field_info.dart
16.66%
5 Missing :warning:

.../smooth_app/lib/widgets/v2/smooth_buttons_bar.dart
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5870      +/-   ##
==========================================
- Coverage     9.54%   6.83%   -2.72%
==========================================
  Files          325     429     +104
  Lines        16411   23609    +7198
==========================================
+ Hits          1567    1614      +47
- Misses       14844   21995    +7151

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

Looks good to me. We will probably to color them for other uses with more urgency in the future.

This one is more for info.
I think we need something different for alerts.


Add expectedArguments for debug_print_backtrace() and debug_backtrace()

While we're on it, can someone explain me the difference between:
Variant 1
 expectedArguments(\debug_backtrace(), 0, DEBUG_BACKTRACE_PROVIDE_OBJECT|DEBUG_BACKTRACE_IGNORE_ARGS);
Variant 2
 expectedArguments(\debug_backtrace(), 0, DEBUG_BACKTRACE_PROVIDE_OBJECT, DEBUG_BACKTRACE_IGNORE_ARGS);
When should we use which variant?

Variant 1 is for constants used as flags (bit-wise OR) in code like this:
debug_backtrace(DEBUG_BACKTRACE_PROVIDE_OBJECT | DEBUG_BACKTRACE_IGNORE_ARGS);
Variant 2 means you can have only one const in your calls:
debug_backtrace(DEBUG_BACKTRACE_PROVIDE_OBJECT);
or
debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
Basically it depends how the constant is defined (bit-wise constants typically have values like 1, 2, 4, 8, 16, ....).


[minisite] Update theme

Note: added breadcrumb and bottom page nav (inspired from mainstream doc solutions like docusaurus), can be worth checking it is compatible and complies to css var?


Added function for email notifcations

Issue #48

Thanks!  I'll try to review this in the next day or two.

Yeh I plan on hooking this into task_manager in a later pull request, because I still need to figure out how.

Sounds good.  I see you made some updates since my initial review, let me know if/when the PR is ready for re-review.
BTW, The call to send the notification can probably be done somewhere around here:  https://github.com/google/turbinia/blob/7d185da0af88460497eda43aa8f9e2c23ae097d3/turbinia/task_manager.py#L456
I think you can get the requester from the Task that is passed in to that method.   Ideally it would send the 'status' report in the email, but you might need to plumb in the client similar to here:  https://github.com/google/turbinia/blob/7d185da0af88460497eda43aa8f9e2c23ae097d3/turbinia/workers/finalize_request.py#L43
Or maybe read directly from Datastore.  Let me know if you want me to dig into that more.

@aarontp Thank you, It's ready for another review.

Thank you @aarontp , I've ran yapf, and fixed the formatting with the help of pylint.

@aarontp I got the CI build to work now.

Hi @CiaranFahy :  It looks like a few of the previous comments still need to be addressed, could you take a look?  I tried to resolve the ones that have already been addressed, but if the comment is no longer relevant you can hit "resolve conversation".  I think the big one is just adding a parameter for the address the mail will be sent to (so we can default to the person who made the request).

Hi @CiaranFahy :  I see you've added a few commits since the last review.  Please ping me in a comment when you're ready for re-review.  Thanks much!

Hi @aarontp it's ready for re-review, However for some reason the yapf style enforcement fails on the Travis ci build while it runs cleanly on my machine.


Fix for 32-bit compilation and MSVC compilation

Replaced all 1L with 1LL, otherwise produces wrong results when compiled on 32-bit
#include  solves missing min() declaration when compiled with Visual Studio

This package appears to have been abandoned. Would you be interested in publishing your fixed version of editdistance to PyPI under a new name, for example editdistance-contd? See also my comment in #6, I think my suggestion to ship stdint.h with the software should also be included in such a continuation.
@mireq You appear to be working on portability and performance improvements as well. Would you be interested in participating in a reboot?
If neither of you wants to publish a continuation package, I can do it.
@aflc If you resume maintaining editdistance, of course we will notify users that they can go back to installing the original editdistance.

@jgonggrijp I'm very busy, i do not want to be maintainer.
My fork has some optimizations and one new function - distance_matrix. In internal project I needed to calculate the distance between pairs of text. Function distance_matrix should not be in official repository.

Thanks it installed correctly after manually putting the file. It would be great if these dependencies were mentioned in the readme.md

Thanks, @aflc. I retract everything I said about starting a fork.

Maybe you should also bump the version number from 0.2 to something else to reflect this fix?


Past Reports Functionality

Can test with the credentials:
Email<EMAIL_ADDRESS>Password: testuser


GetAppXPackage has database malform, can't load Program plugin

Microsoft PowerToys version
0.57.2
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

PowerToysReport_2022-04-15-19-06-07.zip
✔ Expected Behavior
Try to launch program from "powertoys run", It will open the app
❌ Actual Behavior
It is not opening and I realize that I have already seen the error alert.
Other Software
No response

/bugreport

Hi there!We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here?    Then drag the zipfile from your desktop onto the GitHub comment box in this issue.  Thanks!

@nguyen2234
Sory. I didn't saw your report

[2022-04-15 18:26:13.9398] [ERROR] [C:\a\_work\1\s\src\modules\launcher\Wox.Plugin\PluginPair.cs::204]
-------------------------- Begin exception --------------------------
Message: Fail to Init plugin: Program

Exception full name  : System.AggregateException
Exception message    : One or more errors occurred. (The database disk image is malformed (0x87AF000B))
Exception stack trace:
   at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.WaitAll(Task[] tasks)
   at Microsoft.Plugin.Program.Main.Init(PluginInitContext context)
   at Wox.Plugin.PluginPair.InitPlugin(IPublicAPI api)
Exception source     : System.Private.CoreLib
Exception target site: Void ThrowAggregateException(System.Collections.Generic.List`1[System.Exception])
Exception HResult    : -2146233088

Exception full name  : System.Runtime.InteropServices.COMException
Exception message    : The database disk image is malformed (0x87AF000B)
Exception stack trace:
   at WinRT.ExceptionHelpers.<ThrowExceptionForHR>g__Throw|20_0(Int32 hr)
   at WinRT.ExceptionHelpers.ThrowExceptionForHR(Int32 hr)
   at ABI.Windows.Management.Deployment.IPackageManagerMethods.FindPackagesForUser(IObjectReference _obj, String userSecurityId)
   at Windows.Management.Deployment.PackageManager.FindPackagesForUser(String userSecurityId)
   at Microsoft.Plugin.Program.Programs.PackageManagerWrapper.FindPackagesForCurrentUser()
   at Microsoft.Plugin.Program.Programs.UWP.CurrentUserPackages()
   at Microsoft.Plugin.Program.Programs.UWP.All()
   at Microsoft.Plugin.Program.Storage.PackageRepository.IndexPrograms()
   at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
   at Microsoft.Plugin.Program.Main.<Init>b__19_1()
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
Exception source     : WinRT.Runtime
Exception target site: Void <ThrowExceptionForHR>g__Throw|20_0(Int32)
Exception HResult    : -2018574325
-------------------------- End exception --------------------------

It seems your app database has some issues? 🤔
Can you run this in PowerShell?
GetAppXPackage

Does it list the apps you have installed or does it throw an error? /needinfo

Seem it throw an error

would stop any UWP app i believe from loading but could try catch and detect error code

@nguyen2234 i raised this internally and the feedback is this is a pretty nasty error and has very little recovery options.  We could catch it but your computer is in a bad state.
The error code basically is the database is corrupt.  An example would be opening up a jpeg in notepad, adding in random chars and saving.

@nguyen2234 i raised this internally and the feedback is this is a pretty nasty error and has very little recovery options. We could catch it but your computer is in a bad state.
The error code basically is the database is corrupt. An example would be opening up a jpeg in notepad, adding in random chars and saving.

Yup, I have tried some search already and seen it no hope. Anyway, thank you for your help, I already known that my OS is in a very bad state  and I intend to fix it next month.


Consistent bundling

Note: I had to close #829 and open a new one to switch the branch.
This PR updates the rollup config and package.json metadata to ensure that the bundles work consistently, regardless of the module format, and to allow you to access every public entrypoint you can access from lib via the bundles.
This is a breaking change because it changes the modules you are allowed to access, and will cause consumers that were loading the code in lib that was transpiled by babel to use the code in dist that is transpiled by rollup + babel.
These changes allow the following code to work in the browser, in Node.js, and when using a bundler like Webpack:
import { Button } from 'radiance-ui';
import { SPACER } from 'radiance-ui/lib/constants';
import { CameraIcon } from 'radiance-ui/lib/icons'

Notably the lib imports will use the rollup ESM modules in dist instead of the babel ESM modules in lib.
Imports of paths that aren't defined in exports will no longer work:
// not allowed:
import { FlexContainer } from 'radiance-ui/lib/shared-components/optionButton/style';
import { primary } from 'radiance-ui/lib/constants/colors/primary';

We're doing that in a few places currently so those usages will need to be updated before this can be merged.
I tried to follow the Webpack guidelines for package exports and the Node.JS suggestions as much as possible. The setup is also very similar to Preact's.
This PR also drops support for UMD builds because they aren't able to use the same import paths as every other module system, requiring additional documentation, and UMD builds aren't as important anymore now that Node.JS and browsers support ES modules.

Also need to look into this rollup warning:
(!) Mixing named and default exports
https://rollupjs.org/guide/en/#outputexports
The following entry modules are using named and default exports together:
src/shared-components/checkbox/index.tsx
src/shared-components/button/index.tsx
src/shared-components/radioButton/index.tsx
src/shared-components/button/components/roundButton/index.tsx

Consumers of your bundle will have to use chunk['default'] to access their default export, which may not be what you want. Use `output.exports: 'named'` to disable this warning
created dist/cjs in 15.3s

hared-components/checkbox/index.tsx

@matt-allan I've been moving this repo away from default exports in favor of named exports in almost all cases. I expect we can just remove the default exports in there and it'll be fine.

Oh that's a much longer build step now. Interesting.
(!) Entry module "src/icons/emojis/svgs/ElatedEmoji.tsx" is implicitly using "default" export mode, which means for CommonJS output that its default export is assigned to "module.exports". For many tools, such CommonJS output will not be interchangeable with the original ES module. If this is intended, explicitly set "output.exports" to either "auto" or "default", otherwise you might want to consider changing the signature of "src/icons/emojis/svgs/ElatedEmoji.tsx" to use named exports only.
https://rollupjs.org/guide/en/#outputexports
src/icons/emojis/svgs/ElatedEmoji.tsx
We should probably suppress this warnings as well, I think they ultimately do not matter because of how we re-export them from /icons

@matt-allan Is the work that you were doing that necessitated these changes still on track for this cycle? I will be introducing some breaking changes this cycle and just want to make sure we don't end up blocking each other at any point 🙂

@michaeljaltamirano it's going to  be a minute before I can work on this again. Feel free to make any changes necessary, it's easy enough for me to recreate the config now that I know how to do it.


No 44.1khz sampling rate or S32 format on librespot -d ?

Compatible Device

[X] I'm running Raspotify on a compatible Device

Are you sure?

[X] I'm not trying to run Raspotify on a ARMv6 device

Compatible OS

[X] I'm running Raspotify on a compatible OS

Compatible Configuration

[X] I'm running Raspotify on a compatible Configuration

Latest Version

[X] I'm running the latest version of Raspotify

Are you sure?

[X] I'm not running Raspotify <IP_ADDRESS> on a Pi v1 or Pi Zero

Due Diligence

[X] I have done my due diligence

What happened?
Can't see 44.1khz, S32 format and hw:CARD intead of dmix:CARD supported on
`librespot -d ?
[2023-07-04T12:40:51Z INFO  librespot] librespot 0.4.2 a6e1258 (Built on 2023-06-21, Build ID: g9ifMDjd, Profile: release)
    Compatible alsa device(s):

    --------------------------------------------------------------------

    Device:

            dmix:CARD=sndrpihifiberry,DEV=0

    Description:

            snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
            Direct sample mixing device

    Supported Format & Sample Rate Combinations:

            Format: **S16**   Sample Rate(s): **48kHz**

    --------------------------------------------------------------------`

On /etc/raspotify/conf, i've set:
LIBRESPOT_FORMAT="S32"
LIBRESPOT_BACKEND="alsa"
LIBRESPOT_DEVICE="hw:CARD=sndrpihifiberry"
LIBRESPOT_INITIAL_VOLUME="100"
LIBRESPOT_NORMALISATION_PREGAIN="-10.0"

aplay -L is:
root@DietPi:/etc/raspotify# aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
hw:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
    Direct hardware device without any conversions
plughw:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
    Hardware device with all software conversions
sysdefault:CARD=sndrpihifiberry
    snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
    Default Audio Device
dmix:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
    Direct sample mixing device

amixer:
root@DietPi:/etc/raspotify# amixer
Simple mixer control 'Tx Source',0
  Capabilities: enum
  Items: 'S/PDIF RX' 'AIF'
  Item0: 'AIF'

My audio card is a SPDIF digital transport compatible with hifiberry-digi-pro, displayed as:
hw:0,0 : sndrpihifiberry HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
(it's dtoverlay is not necessary entered in /boot/config.txt)
My interest is to support native 44.1khz on raspotify and select, if possible hw:0,0 instead of dmix
DietPi v8.19.1 : 12:52 - mar 04/07/23 (debian)
Device model : RPi 4 Model B (aarch64)
6.1.21-v8+ kernel
nothing relevant on journalctl -u raspotify -b
mpd service and upnprender are disabled, nothing is using the soundcard
hifiberry-digi-pro works well before raspotify with mpd and upnprenderer enabled
thanks for support
Relevant log output and/or the contents of /etc/raspotify/crash_report if any ( sudo journalctl -u raspotify -b and sudo cat /etc/raspotify/crash_report )
jul 04 13:42:05 DietPi systemd[1]: Stopped raspotify.service - Raspotify (Spotify Connect Client).
jul 04 14:40:48 DietPi systemd[1]: Started raspotify.service - Raspotify (Spotify Connect Client).
jul 04 14:40:49 DietPi librespot[4477]: [2023-07-04T12:40:49Z WARN  librespot] Without the `--enable-volume-normalisation` / `-N` flag normalisation options have no effect.

Is it muted?

I hadn't tested it with music playback, just 'librespot -d ?' output idle.
Now it's working ok, according to my dac, input is 44.1Khz.
This what 'librespot -d ? says:
`root@DietPi:~# librespot -d ?
[2023-07-16T17:05:38Z INFO  librespot] librespot 0.4.2 a6e1258 (Built on 2023-06-21, Build ID: g9ifMDjd, Profile: release)
    Compatible alsa device(s):

    --------------------------------------------------------------------

ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave`

You can't prove devices while they are in use.


content-sources: add client CreateRepository.

Description
The CreateRepository the repositories function that will be used to create repository in content-sources.
100% coverage
FIXES: THEEDGE-3208
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] 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 run make pre-commit to check fmt/vet/lint/test-no-fdo

/retest

/retest

/retest

/retest

/retest


Frontend Dev

create the following:

HTML
CSS
JS file

Front end Dev completed - html code in template folder, css and js code in static folder


arch: arm64: mmu: Rework defines

Every time I try to decode all the defines in this driver what I get is
only a huge headache. This patch:

adds a few sensible comments
remove the redundant defines
rename the defines to be more self-explanatory
reorder the defines
try to make sense of some mysterious derived values

@Abhishek-brcm @sandeepbrcm are you ok with these changes?


Use 3d-dna to assist in assembling pacbio hifi data

Hello
I used hifiasm to complete the preliminary assembly(no polishing) of pacbio hifi, and then used 3d-dna to anchor the contigs to the chromosome, but the number of chromosomes(n=7) obtained is different from my species(n=9). How should I improve my results?
Thanks

Hi xiaobaiymq,
Take a look at the Genome Assembly Cookbook hosted on dnazoo.org/methods. This should give a good overview of the options available within the 3d-dna suite. Also, check out the aidenlab.org/forum.html for a number of discussions on how to read and interpret 3d-dna output.
Closing since this is not a bug. Hope this helps,
Olga


Simplify inputs for common symbols/types

Consider this blend effect
        <LayerMaterial transparent depthWrite={false} side={THREE.FrontSide} blending={THREE.AdditiveBlending}>

With strings:
        <LayerMaterial transparent depthWrite={false} side="front" blending="additive">

Side has 3 options, front, back, both. Blending does have a lot more, so you could still allow it to be passed, but otherwise make it easier...

I agree this is better to look at. Currently LayerMaterial accepts all ShaderMaterial props. I just think it would break consistency with other Materials in the library
For blending, isn't it possible to define a custom blending function in that prop?

Closed via 1.1.1


Deprecation warning from Bleak on BLEDevice.rssi

When using claranet4 0.2.0, Bleak prints the following warning:
claranet4/lib.py:52: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead

Thanks for raising. I have noticed this, but found the AdvertisementData
API a bit confusing. I should look into it again.
On Fri, 28 Jun 2024 at 15:01, Chris Dzombak @.***>
wrote:

When using claranet4 0.2.0, Bleak prints the following warning:
claranet4/lib.py:52: FutureWarning: BLEDevice.rssi is deprecated and will be removed in a future version of Bleak, use AdvertisementData.rssi instead
—
Reply to this email directly, view it on GitHub
https://github.com/bede/claranet4/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHWAAFMDMLO3WODFUNUZ7DZJVUEVAVCNFSM6AAAAABKB63YYCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DANJRGMZDMOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you! It's not at all urgent.
In the meantime, for people using claranet4 as a library, it's possible to bring this warning into the standard library's logging system, and you can then silence it or do as you please:
logging.captureWarnings(True)

Thanks for the tip! And again for raising.
I'm planning to add the ability to query more than one fields at a time as
a string, which would be useful with xbar (MacOS menu bar integration)
On Fri, 28 Jun 2024 at 18:00, Chris Dzombak @.***>
wrote:

Thank you! It's not at all urgent.
In the meantime, for people using claranet4 as a library, it's possible to
bring this warning into the standard library's logging system, and you can
then silence it or do as you please:
logging.captureWarnings(True)
—
Reply to this email directly, view it on GitHub
https://github.com/bede/claranet4/issues/2#issuecomment-2197322645, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHWAADKHLEW3BUEDTFV4Z3ZJWJB5AVCNFSM6AAAAABKB63YYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGMZDENRUGU
.
You are receiving this because you commented.Message ID:
@.***>


Change maps from markers to polylines

Increase efficiency/speed
Increase readability

Thanks Nick, This has now been merged with the master branch


Prevent loading readline config on fennel stdio

This fixes #166. The bug was caused by readline inserting control
characters into the fennel repl. By skipping the user readline config,
they are prevented from modifying the repl in arbitrary dangerous ways.
This is fine, because the readline editing facilities are completely
useless in the context of conjure, since we rely solely on neovim's
editing capabilities.
Note: The user is still able to configure the lua readline library
through their ~/.fennelrc file, for example, to persist their history.

needs more testing


services obs test failed for insufficient balance

OBS test has been disabled. We will bring it back when our sponsor is ready.

No actions to take so far.


Remove domain param from directories query

Description
We no longer support querying directories by domain.
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

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

Comparison is base (3f6d26c) 85.89% compared to head (ea36d28) 85.89%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #230   +/-   ##
=======================================
  Coverage   85.89%   85.89%
=======================================
  Files          31       31
  Lines        1234     1234
=======================================
  Hits         1060     1060
  Misses        174      174

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


ESR Fix [2/2]: UX Changes

Screens
QR scan confirmation screen
QR scan success screen
Spec
Take the data in ESR Data - defined here: https://github.com/JoinSEEDS/seeds_light_wallet/issues/1259
Then show the confirmation screen with a list of actions, rather than a single action. Simply display all actions in a list.
Then show the success screen with also a list of actions.
Right now both confirm and success screen receive a single action as Strings name, contract, and a map object for data.
The ESR Data object will contain a list of actions, we show the same data but one UX element for each action.

UX/UI Update:
Easy Scroll card system for seeing multiple transactions.

For confirmation
User can select See Transaction Actions to see additional details from the Transaction.

.

✅ Test Case 1

Login to the app.
Tap the Code Scanner button.
Scan the 2-action code:

Observe the Confirmation screen with 2 actions.

Test Case 1 passes! However, I'm often seeing a glitch of multiple screen transitions, which I don't believe is expected. Made a new ticket: Scanning a QR code results in multiple screen transitions #1363.


Is there a way to cache the installed conda?

I'm currently using environment caching to speed up by CI runs as described by: https://github.com/conda-incubator/setup-miniconda#caching-environments
But, the installation of conda itself takes about a minute of runtime on our CI. It would be nice to cache this step since we do not need to check for new miniconda versions every run - once a day or once a week would be more than sufficient.
It's not clear to me if there's a way to achieve this. I can use the cache action to cache the installed directory, but then putting the setup-miniconda action inside an if statement would be problematic because it would also lose the environment activation behavior.
Thanks for any help!

Hi @tbenthompson,
Regarding:

But, the installation of conda itself takes about a minute of runtime on our CI

if you do not require the "latest" miniconda, you could just use the bundled one that comes with all runners, so there would not be any installation step!

Oh, that's a good point. Thanks. I guess this can be closed then! Maybe it would be good to have a note on runtime in the documentation that using "latest" will be much slower. It makes sense in retrospect, but I didn't think of it until now.

Will make the update, thanks for the suggestion.
Reopening the issue to track it :)


have vscode match pyenv env

update conf to have vscode env match pyenv according to https://github.com/lewagon/data-setup/issues/156

@brunolajoie looks like the python.pythonPath setting is still required otherwise VSCode would ask me to select the default interpreter before running a script and I had to :
Cmd + Shift + Python: Select Interpreter
Then select :
⚙ Use Python from `python.defaultInterpreterPath` setting
~/.pyenv/shims/python

Once I did that VSCode created a local .vscode containing the python.pythonPath setting with the value ~/.pyenv/shims/python


New version: JetBrains.DataGrip version 2024.1

Created by 🥟 Dumplings in workflow run #4141.
Logs
Updated: 2023.3.4 → 2024.1
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

Hi @SpecterShell,

This PR's version number 2024.1 has 2 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 2023.3.4, which has 3 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 876)

Hi @SpecterShell,

This PR's version number 2024.1 has 2 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version 2023.3.4, which has 3 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 876)

It is normal for JetBrains products to have two-parts version. Can you add an exception for JetBrains products? @stephengillie

It is normal for JetBrains products to have two-parts version. Can you add an exception for JetBrains products? @ stephengillie

I did and I forgot. Sorry for missing this one.


Swift Package Manager Support

Is your feature request related to a problem? Please describe.
Not really.
Describe the solution you'd like
Add in swiftpm support.
Describe alternatives you've considered
Wait for swiftpm to be the default.
Additional context
Flutter is switching to use the Swift Package Manager instead of Cocoapods. Each plugin a package depends on needs to be updated before a project can upgrade.
Also, I'm on macOS. I haven't written Swift in ages, but I'd be willing to give this a shot!

Feel free to propose a PR. However, I probably won't merge it until it is stable and the default.
As long as Cocoapods is the default and one needs to explicitly enable the new system, there is really no point in migrating


Add "create connector" endpoint

Add "create connector" enpoint

Thx!
@mdrillin, so here's the endpoint for registering connectors :)

@mdrillin aaand the /api/connect-clusters endpoint as well!


[BUG] Support sign in integer casting of strings

I came across this inconsistency when I was playing around with some basic benchmarks.
Bug description
Pocketpy main
>>> a = int('123')
>>> a
123
>>> a = int('-123')
Traceback (most recent call last):
  File "<stdin>", line 1
    a = int('-123')
ValueError: invalid literal for int(): '-123'
>>>
>>> a = int('+123')
Traceback (most recent call last):
  File "<stdin>", line 1
    a = int('+123')
ValueError: invalid literal for int(): '+123'

Considering this as a bug towards consistency of code as float conversion already supports this -
>>> a = float('-3.14')
>>> a
-3.14
>>> a = float('+3.14')
>>> a
3.14

Very helpful~ Thank you :)


Random data deletions?

Hi
I am not sure this is a waterline issue but I can't think what else it could be. We have a postgres DB which we use waterline to interact with.
Every now and then a random table will have it's data deleted! Today it was our users table but it could be any table.
We've searched the logs (when it first happened we turned on logging for literally everything) and we can't find anything hinting at delete or truncate on the users table - it's just gone!
Does anyone have any clues what this could be?

OK so going through the logs on the server I can actually see there are delete table statements:
2015-06-13 11:51:22 UTC LOG:  statement: DROP TABLE "eventInstance";
2015-06-13 11:51:22 UTC LOG:  statement: DROP TABLE "filteredlineup";
2015-06-13 11:51:33 UTC LOG:  statement: DROP TABLE "image";
2015-06-13 11:53:00 UTC LOG:  statement: DROP TABLE "artist";
2015-06-13 11:53:29 UTC LOG:  statement: DROP TABLE "attempt";
2015-06-13 11:53:30 UTC LOG:  statement: DROP TABLE "auth";
2015-06-13 11:53:30 UTC LOG:  statement: DROP TABLE "campsite";
2015-06-13 11:53:30 UTC LOG:  statement: DROP TABLE "discoursesso";
2015-06-13 11:53:30 UTC LOG:  statement: DROP TABLE "eventInstance";
2015-06-13 11:53:30 UTC LOG:  statement: DROP TABLE "filteredlineup";
2015-06-13 11:53:40 UTC LOG:  statement: DROP TABLE "image";
2015-06-13 11:53:41 UTC STATEMENT:  DROP TABLE "image";
2015-06-13 11:55:19 UTC LOG:  statement: DROP TABLE "artist";
2015-06-13 11:55:48 UTC LOG:  statement: DROP TABLE "attempt";
2015-06-13 11:55:48 UTC LOG:  statement: DROP TABLE "auth";
2015-06-13 11:55:49 UTC LOG:  statement: DROP TABLE "campsite";
2015-06-13 11:55:49 UTC LOG:  statement: DROP TABLE "discoursesso";
2015-06-13 11:55:49 UTC LOG:  statement: DROP TABLE "eventInstance";
2015-06-13 11:55:49 UTC LOG:  statement: DROP TABLE "filteredlineup";
2015-06-13 11:55:59 UTC LOG:  statement: DROP TABLE "image";

LOADS of them!
Why is waterline doing this? the model hasn't changed in ages!

You need to make sure your migrations are off. I'm guessing you have your migrate strategy set to drop or alter (which is the default). If using Sails in production mode it should never touch your database or if you set the migration strategy to safe your database won't be touched.

Yea, what @particlebanana said. If this is in production, then like any node.js application, you should set NODE_ENV=production.

That feels backwards though, shouldn't data safety be something you have to
opt out of ?
Understand it's probably too late to change in this instance, but I
sympathize a lot with the OP.
-kevin
On Jun 13, 2015, at 19:46, Travis Webb<EMAIL_ADDRESS>wrote:
Yea, what @particlebanana https://github.com/particlebanana said. If this
is in production, then like any node.js application, you should set
NODE_ENV=production.
—
Reply to this email directly or view it on GitHub
https://github.com/balderdashy/waterline/issues/1058#issuecomment-111773490
.

@dmarcelino what's the state of those changes made to migration defaults?  I think this behavior has changed in recent versions of waterline.

 That prompt only goes away once you've manually configured a migrate setting in the config files. Therefore, you have alter or drop in your configs, and you did not set NODE_ENV to production, nor did you start sails with the --prod flag. In production mode, Sails has a hardcoded override that forces safe migrations. The OP has blown through two levels of safeguards Sails has in place to try to protect against this situation.
For those reasons, I'm having a difficult time being very receptive to the argument that Sails makes it too easy to corrupt data.
The convention-over-configuration approach of Sails is relevant and useful during development, but deploying to production should be treated as a big deal, where there's no substitute for careful and proper configuration. If you don't tell Sails that it's in production mode, and you have it configured incorrectly, then Sails doesn't know that it needs to save you from yourself.

I run sails with sails debug and never see that output btw :)
I do feel it could be made clearer that it is experimental and you (most-likely will?) probably lose data if you use anything other than safe...
This has cost us no end of headache and we have had to re-initialise our system loads of times because of data corruption - I'm just glad we found out what it was!! We haven't gone live yet so it's not technically production but the fact we were losing data was a real headache.
Now then - how are we all managing change in Postgres if we aren't using alter?!
Aside from all of this - we are loving sails + waterline for our backend - super super productive (coming from .NET I guess even my gran would be a more productive API framework but still! )

I think the question here is answered, so I'm going to close this out.  If there's actually more to say here, just flag me to reopen it!

We just put migrations in a folder, sorted by date, and run them by hand, with a checklist. Not the "most scalable" or whatever, but it works..

I run sails with sails debug and never see that output btw :)
This has cost us no end of headache and we have had to re-initialise our system loads of times because of data corruption

@wayne-o Then just like the OP, you've manually set migrate already. But I don't need to argue with you, I can just show you what actually occurs:
tjwebb@latitude:/home/tjwebb $ sails generate new test1
info: Created a new Sails app `test1`!
tjwebb@latitude:/home/tjwebb $ cd test1/
tjwebb@latitude:/home/tjwebb/test1 $ sails generate api TestModel
info: Created a new api!
tjwebb@latitude:/home/tjwebb/test1 $ sails lift

info: Starting app...

-----------------------------------------------------------------

 Excuse my interruption, but it looks like this app
 does not have a project-wide "migrate" setting configured yet.
 (perhaps this is the first time you're lifting it with models?)

 In short, this setting controls whether/how Sails will attempt to automatically
 rebuild the tables/collections/sets/etc. in your database schema.
 You can read more about the "migrate" setting here:
 http://sailsjs.org/#/documentation/concepts/ORM/model-settings.html?q=migrate

 In a production environment (NODE_ENV==="production") Sails always uses
 migrate:"safe" to protect inadvertent deletion of your data.
 However during development, you have a few other options for convenience:

 1. safe  - never auto-migrate my database(s). I will do it myself (by hand)
 2. alter - auto-migrate, but attempt to keep my existing data (experimental)
 3. drop  - wipe/drop ALL my data and rebuild models every time I lift Sails

What would you like Sails to do?

info: To skip this prompt in the future, set `sails.config.models.migrate`.
info: (conventionally, this is done in `config/models.js`)

warn: ** DO NOT CHOOSE "2" or "3" IF YOU ARE WORKING WITH PRODUCTION DATA **

prompt: ?:


Improving the UI

Redesigning of the search bar and the cards needed.
I would like to work on this issue.
Please assign it to me.

I would like to contribute to this issue , kindly assign me under jwoc .

@arnab2001 I completed the redesigning of the search bar but due to errors with the get request with the apis I cant see the cards. Can you assist me as to hoe to resolve this error?


Add better status message

Create .gitignore in order to ignore tracking *.log and *.pid files
Added $HOST and $PORT for the command status' message

@chapeupreto good stuff


Split VaryHeader into VaryAllowList and VaryUtils to organize vary-related logic.

Commit Message: Split VaryHeader into VaryAllowList and VaryUtils to organize vary-related logic.
Additional Description: Just a refactor.
Risk Level: Low
Testing: Existing tests
Docs Changes: None
Release Notes: N/A
Platform Specific Features: N/A

Mistaken early submit, will resubmit shortly.