Alexa can no longer set bright/dim percentage

I've had a couple dozen lights working on HA-bridge with Amazon Echo since 2016. Now out of the blue, just tonight, Alexa will no longer set the light percentage. I can use the HA-bridge web interface to set a Dim percentage just fine. Alexa can also turn lights ON and OFF with no issue. But if I now specify a percentage as part of the voice command, the response is, "Bedroom lamp is not responding."
Does anyone know if Amazon changed something about the way it parses dim/bright percentages, or how it passes those to HA-bridge? Clearly something has changed somewhere. (And yes, I've rebooted my modem, router, Echos, and RPi a few times to no avail.)
Anyone else having this problem?

I had this problem too... In my setup to fix it was to enable the following on each device:
"On with First Dim" = true
"Dim only when On present" = true
"Send dim when color request present and dim present" = true

Thanks your your reply!  I finally ended up removing all the devices from Alexa and re-discovering them. When I did that, everything worked again (bright/dim) and Alexa stopped saying that every device was "unresponsive" with a red status indicator.
I'll keep your solution noted in case this happens again. Thanks so much!


Feature Request: Warning if DeletionPolicy is not specified

Sorry for not implementing and submitting pull request but currently have no time for that.
DeletionPolicy is not required in for example DynamoDB Table and defaults to Delete.
That is not a good default value IMHO so always setting DeletionPolicy explicitly would be a nice recommendation.

Cool "Best Practice" style addition.  I'll label it as an enhancement

Thanks :)


jsonschema: ignore extension fields

x- fields are documented as fields we ignore, so make it so jsonschema validations ignore it as well.
example:

Test failures have to be flakes, right?

Otherwise LGTM. Rerunning the tests, will approve when they pass

Fix for the failure is in https://github.com/Azure/dalec/pull/415


Support "use_http_header" configuration for PassThroughClusters

Describe the feature request
This feature request is to allow PassThroughCluster to be configured with use_http_header  when creating a destination rule. This allows us to route traffic to ip:port specified in the header x-envoy-original-dst-host.
Describe alternatives you've considered
Currently there are no alternatives available.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Couple of possible options

Add a boolean flag here.
Add a feature flag to generate the config for default PassThroughCluster and we can use the wild card route?

@rshriram I know https://github.com/istio/api/pull/899 might possibly address this case - But thinking first class support for this may be good. What do you think? Any other suggestions?

Under what case, do you need to pass this in header?
If u really want to specify he host, why not try ServiceEntry or Headless service? Without thinking too much,  maybe both of these can satisfy you..

This is a use case of dynamic request routing where the ip:port is determined based on some logic. It is not known ahead - so we can not create service entry and wait for it to be pushed to all Envoys.
Sorry, I should have made this point clear.

It is really special, also a doubt now that you can already set the header according your logic, why can not access it directly?

Because we want to take the benefit of mTLS from proxy instead of application taking care of SSL + cert rotations etc.

seems like a perfect use case for EnvoyFilter

seems like a perfect use case for EnvoyFilter

I don't think destination rule will work since Passthrough Cluster is shared by everyone

Do you mean a Passthrough Cluster created by a destination rule is shared by every one? If that is the case, we can add this config as an optional/configurable thing for the default PassThroughCluster - that also should work for our use case

There is only one "PassthroughCluster", its always there whether or not you configure a destinationrule or not.
I guess you probably mean the PASSTHROUGH loadbalancer type though so that makes sense

Yes, I meant specifying PASSTHROUGH loadbalancer type while creating DestinationRule.
So which approach should we take here - add that configuration in DestinationRule or add a flag to either in feature flags/mesh config and set this config for default 'PassThroughCluster'? Either would work for us.
I am leaning towards option #2 for now as it is simple.
We are blocked on this for one  of our use cases so based on what we decide here, I will submit a PR.

Will EnvoyFilter not work for this? I haven't kept too much up to date on its development but I think this is like the exact type of use case it is intended for

I think it might work. But the reason I am proposing alternative is because

We need this immediately , so looking for a solution that we can start with and migrate to EnvoyFilter if it works later
And possibly exposing API for this does not harm as we do not have to go via complex EnvoyFilter manipulation for this simple setting.

@howardjohn @rshriram Any objections  on adding the "use_http_header" to default passthrough cluster based on a config? I will push a PR to that effect if you are fine with it.

this seems like a security vulnerability waiting to happen. For instance someone sets this on their DR, now users through ingress gateway can set this header and he routed to arbitrary services? Maybe I misunderstand the feature though

Yes, it is a possibility as documented here https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/cds.proto#cluster-originaldstlbconfig - That is why we only enable only few namespaces with care. I think PASSTHROUGH LB it self is for advanced use cases and must be used with care as documented here https://github.com/istio/api/blob/master/networking/v1alpha3/destination_rule.proto#L304.

Sorry for the delay. So, I am planning on finishing up the EnvoyFilter asap in the next week or so - all the things in https://github.com/istio/api/pull/899 [the CDS piece should be dead simple]

Thank you. Will wait for your PR then.
On Thu, 11 Jul 2019, 20:51 Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

Sorry for the delay. So, I am planning on finishing up the EnvoyFilter
asap in the next week or so - all the things in istio/api#899
https://github.com/istio/api/pull/899 [the CDS piece should be dead
simple]
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/15183?email_source=notifications&email_token=AEDINKBMWSBCKCZZPMRYPK3P65FV5A5CNFSM4H3Y7EW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXBLEQ#issuecomment-510530962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEDINKFKBXJC7WGWMTV3YSLP65FV5ANCNFSM4H3Y7EWQ
.

@howardjohn  No. Not yet. but I am sure it will work. We can close this and will reopen if it becomes an issue.

@howardjohn @ramaraochavali I went through your conversations in this thread but I could not really tell what's the conclusion here ... Sounds like the EnvoyFilter should be able to fulfil the need here but may I have a working example on how to configure the EnvoyFilter via istio resources and the filter can actually select an upstream endpoint based on the request header?
Thanks in advance

My use case is as follows, I have a EDS cluster using k8s service discovery, this is pretty default. But then the each endpoint in the upstream cluster is exclusive, so one endpoint can only serve one client. This brings the need that we would like to use a HTTP header to control which upstream endpoint should be used for a given client. What I have imagined is that to the very least we have LEAST_REQUEST LB rule in place so most of cases we trust envoy to find the idle upstream. But in case one client lands on an already serving upstream, the upstream can instead give a spare upstream to the client (e.g. 302 redirect with the chosen upstream ip:port, later on client can include this ip:port in the follow up request) So envoy can use the ip:port as specified in this header.
Or any other advices would be greatly appreciated!

you have add an envoy filter (see example https://github.com/istio/istio/wiki/EnvoyFilter-Samples) that targets the upstream cluster and set that flag to true.

you have add an envoy filter (see example https://github.com/istio/istio/wiki/EnvoyFilter-Samples) that targets the upstream cluster and set that flag to true.

Oh, I see, I will give it a shot, thanks for the direction!

I'd recommend you just use PASSTHROUGH lb https://istio.io/latest/docs/reference/config/networking/destination-rule/#LoadBalancerSettings-SimpleLB for most cases though. You can match on a header and send to a subset w/ that policy if you don'rt always want it

I'd recommend you just use PASSTHROUGH lb https://istio.io/latest/docs/reference/config/networking/destination-rule/#LoadBalancerSettings-SimpleLB for most cases though. You can match on a header and send to a subset w/ that policy if you don'rt always want it

The EnvoyFilter worked for me thanks to @ramaraochavali . To be more precise, I used the PASSTHROUGH and EnvoyFilter together to achieve that the client could use the header to select an endpoint in upstream.
On the other hand, IIUC just use PASSTHROUGH won't get me anywhere in k8s? Because the original destination would always be the ingress's IP:PORT. Am I getting something wrong here? @howardjohn


Feature Request: Landing Page

First impressions are everything, I feel that the landing page even without playback history data it could still be quite engaging by showing a page with sections such as:

Recently Added Tracks (using date_modified metadata)
Random Tracks (well, it says it all - doesn't need complex logic to it in its first iteration)
And for something like this maybe haha:
***Recently Released Tracks (using online music db like musicbrainz or lastfm?)

I understand I had brought up a similar suggestion before and rightfully so, you had genuine reasons why it couldn't be implemented at time.

Hello @gerryflux
Please check out the latest release. It's not much, but it's a start.


IOS-11336 - user is unable to exit destination folder selection window

Because the createFolderViewController is setting the navigation bar to be opaque, when the user later navigates back to the folderViewController, the search bar becomes hidden by the navigation bar. This commit ensures the folderViewController navigation bar appearance is restored to its original appearance when it appears again.

Verified that @adempsey has signed the CLA. Thanks for the pull request!

+2

@adempsey these calls are unbalanced.
viewDidLoad should get called just once (assuming it does not become unloaded), but viewWillDisappear can get called many times (for example if VCs keep getting pushed on top of this and popped off repeatedly, modals, etc).


Array binary search

[x] Top-level README “Table of Contents” is updated

[x] Feature tasks for this challenge are completed
[x] Unit tests written and passing

[x] “Happy Path” - Expected outcome
[x] Edge Case (if applicable/obvious)

[x] README for this challenge is complete

[x] Summary, Description, Approach & Efficiency, Solution
[x] Link to code
[x] Picture of whiteboard


Popover placement bottom-right doesn't work when using a template

Bug description:
Popover placement doesn't work when using a template
Link to minimally-working plunker that reproduces the issue:
http://plnkr.co/edit/rCZjwlwnACkyY8BUFsBY?p=preview
Version of Angular, UIBS, and Bootstrap
Angular: 1.5.0
UIBS:
Bootstrap: 3.3.6

This looks correct in the Plunker to me - it is aligned with the bottom and right, although perhaps @RobJacobs might have more to add here.

Just double check, doesn't work on mine and others machine.

What OS & browser?

Window 10, Chrome 49
OSX 10.11.3, Chrome 48
OSX 10.11.3, Chrome 49
screenshot attached if you need it

@wesleycho The css selector for the arrow in the tooltip.css needs to be adjusted to include all the tooltip/popover flavors.  I'll create a PR shortly...


[C++][Parquet] Compilation breaks on GCC 4.8

Reporter: Uwe Korn / @xhochy
Assignee: Uwe Korn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uwe) / @xhochy
Note: This issue was originally created as PARQUET-1042. Please see the migration documentation for further details.

Wes McKinney / @wesm:
Issue resolved by pull request 359
https://github.com/apache/parquet-cpp/pull/359


Extension causes high cpu load

Issue Type: Performance
Extension Name: python
Extension Version: 2019.5.18875
OS Version: Linux x64 4.15.0-51-generic
VSCode version: 1.35.1

:warning: Make sure to attach this file from your home-directory:
:warning:/home/ariel/ms-python.python-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Thanks for reporting the issue, however you failed to upload the file /home/ariel/ms-python.python-unresponsive.cpuprofile.txt
Closing this issue until that file is uploaded when the issue spare appears again.


Create more claims

@guimou  to provide the prompts he's used so far, so that ours can be more consistent.

Here are a few examples (I pointed the differences). Of course, feel free to experiment and create your owns!
PROMPT
You are a customer writing an email to your insurance company for a claim about a recent car accident. Provide information about the location and the circumstances about the accident. Put as many details as you can.
+
Replace all the placeholders with fictitious names or values. (this after the first generation that may not include those information)
PROMPT
You are a really angry customer writing an email to your insurance company for a claim about a recent car accident. You want answers as fast as possible. Your tone is quite agressive.
Provide information about the location and the circumstances about the accident. Put as many details as you can.
+
Replace placeholders with fictitious names, locations, time,...
Follow-up prompts:
PROMPT
Write the same thing in the style of someone who does not exactly know how to present things clearly
PROMPT
Write the same thing in the style of someone who is really mad and wants and a fast answer.

Then ideally, all of this has to be formatted as follows (mind the doubled apostrophes in the text for proper escape!):
INSERT INTO claims.claims (claim_number, category, policy_number, client_name, subject, body, summary, location, time, sentiment)
    VALUES ('CLM502803', 'Multiple vehicle', 'AC-987654', 'Jane Doe','Urgent: Car Accident Claim Assistance Needed', '
    Dear Parasol Inc.,

    I hope this email finds you well. I''m writing to, uh, inform you about, well, something that happened recently. It''s, um, about a car accident, and I''m not really sure how to, you know, go about all this. I''m kinda anxious and confused, to be honest.

    So, the accident, uh, occurred on January 15, 2024, at around 3:30 PM. I was driving, or, um, attempting to drive, my car at the intersection of Maple Street and Elm Avenue. It''s kinda close to, um, a gas station and a, uh, coffee shop called Brew Haven? I''m not sure if that matters, but, yeah.

    So, I was just, you know, driving along, and suddenly, out of nowhere, another car, a Blue Crest Sedan, crashed into the, uh, driver''s side of my car. It was like, whoa, what just happened, you know? There was this screeching noise and, uh, some honking from other cars, and I just felt really, uh, overwhelmed.

    The weather was, um, kinda cloudy that day, but I don''t think it was raining. I mean, I can''t really remember. Sorry if that''s important. Anyway, the road, or, well, maybe the intersection, was kinda busy, with cars going in different directions. I guess that''s, you know, a detail you might need?

    As for damages, my car has, uh, significant damage on the driver''s side. The front door is all dented, and the side mirror is, like, hanging by a thread. It''s not really drivable in its current, uh, state. The Blue Crest Sedan also had some damage, but I''m not exactly sure what because, you know, everything happened so fast.

    I did manage to exchange information with the other driver. Their name is Sarah Johnson, and I got their phone number (555-1234), license plate number (ABC123), and insurance information. So, yeah, I hope that''s helpful.

    I''m not sure what, um, steps I should take now. Do I need to go to a specific, uh, repair shop? Should I get a quote for the repairs? And, uh, how do I, you know, proceed with the insurance claim? I''m kinda lost here, and any guidance or assistance you can provide would be really, um, appreciated.

    Sorry if this email is a bit all over the place. I''m just really, uh, anxious about the whole situation. Thank you for your understanding.

    Sincerely,

    Jane Doe
    Policy Number: AC-987654
    ',
    '',
    '',
    '',
    ''
    );

I'll do proper formatting later, but here is my entry:

Subject: Claim for Car Accident - Policy #: XXXXXXXX
Dear Parasol Insurance Team,
I hope this email finds you well. I'm reaching out to file a claim regarding a recent incident involving my car, which is covered under my policy with Parasol. The accident occurred last night on the streets of Los Angeles, and I wanted to provide you with all the necessary details.
Location: The accident took place at the intersection of Sunset Boulevard and Vine Street in downtown Los Angeles. It was one of those crazy nights, where the streets were alive with the sound of engines and the glow of neon lights.
Circumstances: So, here's the deal. I was out cruising with the crew, enjoying the vibe of the city, when suddenly we found ourselves in the middle of a high-speed chase. There was this dude, let's call him Johnny Tran for the sake of this email, who thought he could outmaneuver us. Little did he know, we don't play by the rules.
 Naturally, being the king of the streets that I am, I had to show him what real speed looks like. So, I hit the nitrous and went full throttle.
But then, outta nowhere, this semi-truck decided to make a left turn without signaling. I had to make a split-second decision, and I ended up launching my car off a ramp, trying to clear the truck like we're in one of those crazy action flicks. It was like something straight outta the movies, I tell ya.
Long story short, the stunt didn't exactly go as planned. My car ended up crashing into a billboard, flipping over a couple of times before finally coming to a stop. Yeah, it was a total wreck. But hey, at least we walked away without a scratch, just a little shaken, not stirred, if you catch my drift.
Damage: As for the damage to my car, let's just say it's gonna need more than a few wrenches and some duct tape to fix this baby up. The front end is smashed in, the windows are shattered, and I'm pretty sure the chassis is twisted beyond recognition. It's gonna take a miracle to get her back on the road.
I understand that accidents happen, but I'm counting on Parasol to have my back in times like these. I've been a loyal customer for years, and I trust that you'll handle my claim with the same speed and precision that I handle my rides.
Please let me know what steps I need to take to get the ball rolling on this claim. I'm ready to do whatever it takes to get my car back in top shape and back on the streets where it belongs.
Looking forward to hearing from you soon.
Sincerely,
Dominic Toretto

Here's another one:
INSERT INTO claims.claims (claim_number, category, policy_number, client_name, subject, body, summary, location, time, sentiment)
    VALUES ('CLM502803', 'Multiple vehicle', 'AC-987654', 'Saul Goodman', 'Where’s My Money? Urgent Attention Needed for My Car Accident Claim', '
    Dear Stoneheart Insurance Claims Department,

    I am absolutely *thrilled* (read: infuriated) to be writing yet another heartfelt missive to the void that is your customer service. My recent car accident claim has vanished into the ether, much like my patience and the professionalism I expected from your company. How about we resolve this before the next ice age?

    Let''s recap the blockbuster event:
    On March 28, 2023, at around 4:15 PM, at the intersection of 5th Avenue and Main St in Springfield, my car was passionately sideswiped by another vehicle. Why? Because the other driver blasted through a red light and T-boned my car’s passenger side. It was a harrowing scene, made worse by your glacial pace of response.

    It’s been over two weeks, and your commitment to delay is almost impressive. I demand a comprehensive review and prompt update on my claim within the next 24 hours. This isn’t just a request—it’s a necessity driven by sheer frustration and the urgent need for resolution.

    Please treat this matter with the urgency it clearly deserves. I expect a detailed plan of action and a swift response, or be assured, further actions including legal recourse will be considered.

    Looking forward to an expedited resolution,
    Saul Goodman

    CC: My 17 Twitter Followers

    Attach: Police Report No. 12345, Photos of the Incident, Documented Calls and Emails
    ',
    '',
    '',
    '',
    ''
    );

INSERT INTO claims.claims (claim_number, category, policy_number, client_name, subject, body, summary, location, time, sentiment)
VALUES ('CLM605208', 'Automobile Collision', 'AC-768901', 'Tyrion Lannister', 'Urgent Claim Review Required: Collision in King’s Landing', '
Dear Westeros Insurance Claims Department,
This correspondence is from Tyrion Lannister, currently not in a tavern but rather dealing with the aftermath of an unpleasant vehicular incident. As a man known for resolving conflicts, I find myself ironically embroiled in one that requires your immediate attention.

Here are the distressing details:
On April 15, 2023, at about noon, within the confines of King’s Landing, my car was struck by another. As I navigated through the bustling streets near the marketplace, a distracted driver—likely admiring the view of the Blackwater Bay instead of the road—rammed into my car’s side. This not only caused significant damage to the vehicle but also disrupted my travel plans significantly.

Nearly a month has elapsed since the accident, and yet, I’ve seen more action in the Small Council meetings than in the progress of my claim. Your lack of promptness in handling this matter is both noted and distressing. I require an exhaustive review and a swift update on my claim within the next 48 hours. This is not a mere request, but a necessity fueled by urgent needs and dwindling patience.

Please address this claim with the seriousness it merits. I expect a detailed response and a rapid resolution, or rest assured, further actions, potentially involving the Crown, will be considered.

I await your expedited action,
Tyrion Lannister

CC: Master of Coin

Attach: Car Damage Photos, Eyewitness Accounts, Incident Report No. KL509
',
'',
'',
'',
''
);

actually, that would be another interesting thing we could do in the processing pipeline:
if the claim is "humourous" , or likely to be a joke, or makes too many references to pop culture, maybe it's not worth processing the images attached, for example.
Since we would have both serious and less serious examples in the DB, that'd be cool.


[WIP] Add Development section to README

Adding a short section to readme explaining how to use the provided Makefile to set up a dev environment, format their code and install/run the pre-commit hooks.
Other changes

Removed the language version for the black hook, to prevent hook failure if python3.6 is not present.
added lifelines as an editable dependency dev-requirement
added the dev-requirements.txt to doc-requirements.txt so the developer doesn't need to execute 2 separate commands to install them.

Lgtm. The current lint failures still need to be fixed (and tested), tbd later

Happy holidays @kilo59!

Whoops can’t merge over a phone. I will later this week :)


BUG - Related not working when rule URI has changed

To Myself,
When a rule's URI has changed and it is being used as a related rule, it won't show up in the 'related' section.
Related rules should work even if the rule URI changes.

Fix related rules that have changed URIs

https://www.ssw.com.au/rules/awesome-documentation

Figure: Related rules is empty
Thanks,
-Brady
AB#61569

Hi,

Fix related rules that have changed URIs

Done - If the old URI is in the redirects list, it will still show up in the related section
https://www.ssw.com.au/rules/awesome-documentation

Figure: Related rules working
Thanks,
-Brady


comparison typo and script flow fix

refer to issue #1598

Good catch :) Thx.

+cp into dev branch


The readme file has a wrong command for the polymer-loader.html

Hello,
The instructions on how to use this file read:

Second, import the component to your application with the following tag in your head.
<link rel="import" href="/bower_components/px-widget-cards/px-widget-cards.html"/>

This results in an error as there is no px-widget-cards.html file.
Fatal error: ENOENT: no such file or directory, open '/srv/git-tree/predix/predix-rmd-ref-app/rmd-ref-app-ui/public/bower_components/px-widget-cards/px-widget-cards.html
This should be changed to reflect that there is a separate template for each card:

Second, import the component to your application with the following tag in your head.
`
...
 `

Fixed


Unable to use recent JS syntax (babel)

Do NOT ignore this template or your issue will have a very high chance to be closed without comment.

Describe the bug
I don't find a way to configure Vite/Babel
The issue is probably not a bug but more a misunderstanding of how to configure the build

./vite.config.js

import babel from '@rollup/plugin-babel'
import path from 'path'

module.exports = {
  plugins: [
    babel({
      babelHelpers: 'bundled',
      include: [
		// these modules are using private method syntax
        path.resolve('node_modules/@hydre/shimio'),
        path.resolve('node_modules/event-iterator')
      ],
      plugins: [
        ["@babel/plugin-proposal-class-properties", { loose: true }],
        ["@babel/plugin-proposal-numeric-separator"],
        ["@babel/plugin-proposal-private-methods", { loose: true }]
      ]
    })
  ]
}

./package.json > devDependencies

  "devDependencies": {
    "@babel/core": "^7.10.2",
    "@babel/plugin-proposal-class-properties": "^7.10.1",
    "@babel/plugin-proposal-numeric-separator": "^7.10.1",
    "@babel/plugin-proposal-private-methods": "^7.10.1",
    "@babel/preset-env": "^7.10.2",
    "@rollup/plugin-babel": "^5.0.3",
    "@vue/compiler-sfc": "^3.0.0-beta.14",
    "pug": "^3.0.0",
    "stylus": "^0.54.7",
    "vite": "^0.20.0"
  }

Reproduction
not needed
System Info

required vite version: "^0.20.0"
required Operating System: arch
required Node version: 14.4

Logs (Optional if provided reproduction)
The error is quite easy to understand but after trying all kind of configuration setup it still doesn't seems to work
Using vite build --debug
  frame: '43:   }\n' +
    '44: \n' +
    '45:   get #overflowing() {\n' +
    '          ^\n' +
    '46:     return this.#ws.bufferedAmount > this.#threshold\n' +
    '47:   }',
  hook: 'transform',
  code: 'PLUGIN_ERROR',
  plugin: 'commonjs',

Error: Error parsing JavaScript expression: This experimental syntax requires enabling one of the following parser plugin(s): 'classPrivateProperties, classPrivateMethods' (1:1)

Plugins in vite.config.js expect Vite plugins, not Rollup plugins. Read the types for a better understanding of how to write a custom transform.


Map Credentials does not work some times

MapCredenitals are converted to List<Object> by providers using:
ListCredentials.asList(credentials)

current implementation of this method, simply takes returns new ArrayList<Object>(map.values())
note that, in map order of entries is not defined. so credential parameters might be in wrong order;
you can verify the same by following test:
        Map<String, String> map = new LinkedHashMap<String, String>();
        map.put("secretKey", "ZZZZZZZZZZZZZZ");
        map.put("accessKey", "AAAAAA");

        System.out.println(map.values());
        Credentials credentials = Credentials.MapCredentials.from(map);
        DNSApiManager manager = Denominator.create("route53", CredentialsConfiguration.credentials(credentials));
        ZoneApi zones = manager.api().zones();
        for(Zone zone: zones)
            System.out.println(zone);

the above code fails to list zones. but if accessKey is inserted before secretKey, then it works
I fixed the issue in my fork branch map-credentials:
https://github.com/santhosh-tekuri/denominator/tree/map-credentials
please evaluate the fix and merge

@santhosh-tekuri I understand what you are doing, I hadn't run into this as we used deterministic order maps and issued put in the right order. I agree that this could be a problem.
I looked at your pull request and it is a lot of code and also api breaking to fix ListCredentials.asList. I think there are two viable ways out.

Enhance javadoc of MapCredentials.from to highlight the input map must be a deterministically ordered map, and that entries in that map should iterate in the same order as credentials configuration. The simplest way is to use a LinkedHashMap and do the put commands in the correct order.
Deprecate and change code to stop using ListCredentials.asList, raising a later issue to remove it.

Thoughts?

also, if javadocing, probably best to say insertion order, other sorts would be confusing.

In my case, i get credentials in json format. which is read into Map.
for route53 it works fine. but for dynect it failed. after digging into source, i found the issue.
my suggestion will be, do two steps:

Deprecate and stop using ListCredentials.asList
add MapCredentials.asMap and use it where ListCredentials.asList is used. it is more easier and intuitive to convert list credentials to map credentials.

If you are satisfied by my suggestion, I can submit a pull request for this change

Part one makes sense. I don't think that the second part is needed. The
only use case for credential conversion is in provider code.
When a list is present, the implementation could easily use it. In other
words, instead of adding another utility and forcing more conversions that
allocate new objects, let's just test Map vs List in the providers
themselves.

My concern is as a user I am forced to use following workaround in my code:
    public static denominator.Credentials getCredentials(Map<String, String> credentialsMap, String provider){
        Provider provider = Providers.getByName(provider);
        Map<String, Collection<String>> stringCollectionMap = provider.credentialTypeToParameterNames();
        for(Collection<String> c: stringCollectionMap.values()){
            Map<String, String> map = new LinkedHashMap<>();
            for(String param: c){
                String value = credentialsMap.get(param);
                if(value==null)
                    break;
                map.put(param, value);
            }
            if(c.size()==map.size())
                return denominator.Credentials.MapCredentials.from(map);
        }
        return Credentials.AnonymousCredentials.INSTANCE;
    }

and i can't enforce users, to provide credentials in json in correct order.

I agree we don't want people to have to guard this. What I am suggesting is
that we change the provider code to not be sensitive to the order of the
map.
When we deprecate and stop using ListCredentials.asList, we will end up
with three supported scenarios. Either the Credentials object is an
instance of List, Map, or anonymous. The provider code for list will be
exactly as it was before. Each provider will need to add logic to extract
keys by name when credentials is an instanceof Map.
Make sense? I will send an example shortly for how to change Route53

Here's an example. Note that it seems route53 still has wrong formatting, so I will raise a PR in a minute to correct.
-        List<Object> creds = ListCredentials.asList(currentCreds);
-        String accessKey = creds.get(0).toString();
-        String secretKey = creds.get(1).toString();
-        String token = null;
-        if (creds.size() == 3)
-            token = creds.get(2).toString();
+        String accessKey;
+        String secretKey;
+        String token;
+        if (currentCreds instanceof List) {
+            List<Object> creds = (List<Object>) currentCreds;
+            accessKey = creds.get(0).toString();
+            secretKey = creds.get(1).toString();
+            token = creds.size() == 3 ? creds.get(2).toString() : null;
+        } else if (currentCreds instanceof Map) {
+            Map<String, Object> creds = (Map<String, Object>) currentCreds;
+            accessKey = checkNotNull(creds.get("accessKey"), "accessKey").toString();
+            secretKey = checkNotNull(creds.get("secretKey"), "secretKey").toString();
+            token = creds.containsKey("sessionToken") ? creds.get("sessionToken").toString() : null;
+        } else {
+            throw new IllegalArgumentException("Unsupported credential type: " + currentCreds);
+

This does cost a few lines per provider, but the lack of indirection makes the contract clear. It also avoids duplicating objects or needlessly converting them.

the change looks good, as you said adds few lines per provider

ps will merge #284 momentarily, which should help avoid you needing to do an ugly rebase.


Object with single skipped field but with ComplexObject

How do you have a object where the only field is skipped but has fields in ComplexObject? Eg, something like this:
#[derive(SimpleObject, Serialize, Deserialize, Clone, Debug)]
#[graphql(complex, name = "Test")]
pub struct GqlAudio {
    #[graphql(skip)]
    foo: String,
}

#[ComplexObject]
impl GqlAudio {
    async fn bar(&self) -> Option<String> {
      Some(self.foo)
    }
}

This gives an error:
error: A GraphQL Object type must define one or more fields.

Except if you add an useless field like this:
    #[graphql(skip)]
    foo: String,

+   unneeded_field: bool

It's just an #[Object], as you may see in the example:
use async_graphql::*;

struct MyObject {
    value: i32,
}

#[Object]
impl MyObject {
    async fn value(&self) -> String {
        self.value.to_string()
    }

    async fn value_from_db(
        &self,
        ctx: &Context<'_>,
        #[graphql(desc = "Id of object")] id: i64
    ) -> Result<String> {
        let conn = ctx.data::<DbPool>()?.take();
        Ok(conn.query_something(id)?.name)
    }
}

🤦🏾 Thanks for that.


add projects for maven, gradle and sbt for java and scala

assembly works for all of them
sbt and gradle can figure out DSE classpath (thanks Russ)

Are there meant to be Gradle examples as well? This PR seems to remove them all.

@bcantoni  yes, there are moved to scala/gradle and java/gradle dirs

These should all be converted to use the now publicly available DataStax Spark dependency that Artem and Predrag built

will do

In this PR I see two build.gradle files which are being deleted, but none which are being added or moved. Under scala and java I just see maven and sbt dirs.
Regarding the readme file and discussion of dependencies, would it help to have a few concrete examples with real version numbers listed? This seems to be a tricky part for people, so I think a couple of real examples here would be helpful, like:

With DSE

DSE 5.0.0
DSE 4.8.8
DSE 4.7.8

Without DSE

Spark 2.0, Cassandra 3.0, Connector 1.6
Spark x, Cassandra y, Connector z
etc.

@bcantoni you are right, sorry, my .gitignore file ate gradle examples

@RussellSpitzer moved to publicly available DataStax Spark dependency that Artem and Predrag built
@bcantoni channged to project structure to dse vs oss. dse uses dependency that Russ mentioned, which is available only for 5.0.1. Do we want to have "custom" examples for older versions of DSE?
For oss the version compatibility table should be sufficient. We could mention it in the readme file, wdyt?

The version compatibility table on the connector site is good and we can point to it. However it (intentionally) does not list the DSE version.
In any case if I take a step upwards, I think we want to answer the use case of "I'm using DSE version x.y, how do I set up my Spark project to work with it?". A table full of versions would probably be impossible to maintain, so maybe just an explanation of how to find and set the Spark and Spark Connector versions based on the DSE version you're using. The DSE Release Notes pages might be helpful in this regard.

I left a few notes

@RussellSpitzer  applied your remarks
@bcantoni at the moment there is no way to use current dse template for DSE version lower than 5.0.0 (no connector artifact published). We have two options here.

Restore previous project template for DSE < 5.0.0
Talk to Artem if it is possible to publish connector artifact for DSE < 5.0.0 and if it is, use current project template for all DSE versions

I'll talk to Artem when he is back from vacation and get back to you. Let's treat (1) as a backup plan.

I'm +1, This is a great starting point for our users. We can always do more tweaks later

Russ, could you please merge this (I do not have required privileges)?


Error: Used disallowed intents

Environment
Running on Steam Deck Desktop Mode.
Steps To Reproduce
Launched using npm run start
Software Version
3.0.0
Expected Behavior
Not entirely sure what I'm expecting from this point.
Actual Behavior
error - Error: Used disallowed intents appears after info - Logging in...
Screenshots
No response
Severity
Trivial
Priority
Low
Type
Other
Additional Information
This is likely entirely user error. I'm very new to both Linux and Discord. I'm trying to proof of concept for a Project Zomboid server I'm an admin for. I was hoping to be able to use this tool to send commands to this server hosted on DebianOS. At the moment I am testing and working out how to do this with SteamOS as it is all I have in the Linux world.
Thanks for any insight you may be able to provide.

I'm not sure what I've done but I'm now at error - DiscordAPIError[50013]: Missing Permissions
I'm fairly certain now that my troubles are purely user inflicted. Sorry for the trouble, I will play with the Discord bot I made.

The bot works! I still receive the error in the above post, but it responds to commands from the Discord and can Start and Kill the server, not sure how to quit it cleanly yet, but thats a me problem.
Thank you for this wonderful tool.

Check if you have enabled all intents the Discord Developer Portal


Added QuartzPen

FontTools supports drawing on macOS via the CocoaPen, which transforms a path into an NSBezierPath. However, for lower-level drawing on macOS, animation with CoreAnimation, and other use-cases, it’s useful to have outlines represented as CGPath instead of NSBezierPath. RoboFab used to have a QuartzPen but it’s no longer functional under Python 3. This PR adds a QuartzPen back to FontTools, together with some unit tests that only run when PyObjC is installed.

Wow, Travis really does take forever. A few minor improvements:

I added tests for CocoaPen too, since it didn’t have any;
I removed an unused import in the QuartzPen tests;

I think it would be nice if the Travis osx build environment installed pyobjc by default, so the tests actually run there, but I don’t know how to do that.

it would be nice if the Travis osx build environment installed pyobjc by default

sure, but maybe better to do that after we hafe completed the migration to Github Actions (#2100)

can you please try to rebase off master? I just merged GH Actions PR

Done, I’ve rebased the PR off of ae07ce6e554f5b4a2d6e7a6524f5a1307b307bcd and squashed all my commits in one.


Redis rpoplpush() and rpoplpushAsync()

Replaces #1624
All credit to @rimiti

@GAntoine Thank you !


Lint, prettier, travis

Use eslint
Use prettier
Make travis do linting
Remove some unimplemented test things and unused stuff.
Update dev dependencies
Disable some lint things that affect code for now

LGTM


Optional authorization model / not require explicit authorization of feeds

It would be great if hyperdbs could replicate freely without the need of a power dynamic where the db creator has implicit control over access. We've seen in practice that this is sometimes not desirable (e.g. in cabal, where we employ a connection stream hack to auto-authorize).

I’m not convinced the “auto-add” hyperdb will actually scale, so I think it’d be smart to use the protocol extensions being discussed to test how well it works before baking it into the protocol

On Jun 1, 2018, at 8:56 PM, Stephen Whitmore<EMAIL_ADDRESS>wrote:
It would be great if hyperdbs could replicate freely without the need of a power dynamic where the db creator has implicit control over access. We've seen in practice that this is sometimes not desirable (e.g. in cabal, where we employ a connection stream hack to auto-authorize).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Copying from https://github.com/datprotocol/DEPs/pull/27:
I'm concerned about spam attacks too. Like: What happens if somebody shows up and starts dumping large datasets into it? Is there a way to stop that and remove the data they add?

@pfrazee The argument for authorization being optional is so that each app can decide what model it wants. If I feel that I am likely to face spammers, maybe I want hyperdb's default auth model. If I'm sharing among close friends only, I may not want the hassle of managing authorizations. Or maybe I want to implement my own auth model that looks different than hyperdb's. Authorization feels very policy and not very mechanism: there are many opinions on how to do it, and one size doesn't really fit all.

This can almost be done at the hypercore layer using Feed messages to establish a new channel. Currently Feed messages have only a discoveryKey, so both peers need to know the actual public key ahead of time.
If the Feed message type was extended to have an optional publicKey field, then a peer wanting to push/propose a new hyperdb feed to be authorized could announce it that way. Could be useful in other contexts as well, achieving "push" or "submission" of multiple feeds to an aggregator.

@bnewbold one downside of that approach is it forces you to manage authorization at the connection-level. You have to connect to the authorizer to get authorized. If hyperdb were policy neutral, then you could allow replicators to freely authorize new peers.

@lukeburns I believe with my proposal above you could push to any "authorizor" to get authorized, not just the original. Presumably, with liberal authorization, almost any peer would be authorized, so making that connection shouldn't be hard (and if you're offline it doesn't matter if you are authorized). Not perfect; you might connect offline to another unauthorized peer.
Having not thought about this in some time: what if the creator of a feed wrote the secret key, or some equivalent secret material, to the feed itself? Then replicators/readers have the power to append/write. This doesn't quite work with existing multiwriter because there would be collisions on the "world-writable" feed... maybe we could have some extension where a messaged signed by an authorized secret key is sufficient? I don't see how this would all pull together, just a thought.

Oh, didn't realize that authorized members can already authorize new members. Looks like this is what cabal's stream hack is using https://github.com/cabal-club/cabal-core/blob/master/index.js#L71.
I could imagine this being tricky in cases where you do wish to limit access control, e.g. private messaging, and trust that other members cannot be added by those you authorize.


Circuitbreaking thrift

Though circuit-breaking is often referenced as a thing clients can do (particularly if clients are responsible for service discovery), it also makes sense on the server.
In this case, the simplest form of circuit-breaking that achieves robustness is limiting concurrency.  In the past this was done by limiting the number of connections.  Unfortunately, I see at least two problems with this.

It appears that we are still accepting connections above the connection limit, just not processing work on them.  This will cause stalls, and is the likely reason that people are reluctant to use max_concurrency.
The expensive part of the lifecycle isn't handling the connection, it's doing the request work.  Therefore, the limitation is better applied on a per request basis.
When the limit is hit, the correct behavior is to queue a small number of requests, then drop requests that will never be serviced inside the SLA of the service.  In practice, you don't need an explicit queue.  Assuming a typical db-bound web service, if max_concurrency is 100, and the db has a connection pool of size 10, then that's a 90 item implicit queue.  Therefore, the correct behavior is to reject requests that exceed max_concurrency.

This will have the effect of replacing stalls with failures.  Ultimately, this is healthier behavior, because it is more explicit over implicit, it allows the upstream service to react faster, and it is quicker and less wasteful of server resources.

Thanks for doing this! I'm going to close this PR out since we've got the design doc and the WIP PR for implementation. As for error messaging, @bradengroom is about to drop a design doc for some standard error structs that I think would solve that problem.

(Let's catch up on the current status of all this soon)


BSP should supply custom entry macro

Currently we use the #[entry] macro from cortex-m-rt in every application. The BSPs should provide their own alternative, but where main is given all the stuff you usually need as a single struct. This would hugely reduce boilerplate in every application.
This would be optional and you can ignore the macro and do it the old way if you wish.

This is similar to: https://github.com/rust-embedded/cortex-m/issues/403


Main development done!

It still has to tested for frontend implementation. Add cypress or playwrigth automatic testing.

update docker to use https://github.com/orgs/thingsdb/discussions/366#discussioncomment-9056754


Adjustment factors for Non-annual PV simulations

Describe the bug
When running a non-annual simulation where the weather data doesn't start at timestep 0, such as in https://github.com/NREL/pysam/blob/main/Examples/NonAnnualSimulation.ipynb
the adjustment factors are not properly aligned and result in a adjustment factor of 0, zeroing out all ac power as in the example above.
The length of the adjustment factors vector is the length of the weather file (810), but when accessing the adjustment factor, the timestep is used (3096) and since this is larger than the length, the default of 0 is returned.
To Reproduce
Steps to reproduce the behavior:

Run the above notebook and see that the prediction line at the bottom is 0

Expected behavior
Adjustment factor should be aligned

@dguittet I would have expected the haf setup function to fail with the adjustment factors vector length of 810- my read of it is that it is supposed to require a complete 8760 (or subhourly) even for non-annual simulations, so indexing into hour of year would work even for non-annual simulations. I think we either need to (1) fix the checks so that it fails if non-annual arrays are passed in (not obvious to me why it didn't catch this), or (2) change the setup function to check that the length of the adj timeseries is equal to wf nrec, which requires the haf function knowing whether it's annual or non-annual....

@janinefreeman Apologies it took so long to get back to this.
So this issue of adjustment factors shows up when it's Non Annual and not starting at the beginning of the year. The adjustment factors are set up with adjust_constant = 0, not with "adjust_hourly" timeseries of adjustment factors. So then adjustment_factors runs haf.setup(nrec, nyears) which creates a vector of nrec:
https://github.com/NREL/ssc/blob/5010af992f298d600cbeddf4c5dd1fad17cf4b27/ssc/common.cpp#L1073
However in this case, the hour_of_year != idx and the call to haf() returns 0 instead of 1.
if ( time < m_factors.size() ) return m_factors[time];
https://github.com/NREL/ssc/blob/5010af992f298d600cbeddf4c5dd1fad17cf4b27/ssc/common.cpp#L1189
resulting in ac being 0.
I've set up a test showing this: https://github.com/NREL/ssc/pull/1113/commits/5010af992f298d600cbeddf4c5dd1fad17cf4b27
You can see
p_ac[idx] = (ssc_number_t)(ac * haf(hour_of_year));
And the NonAnnualSummerStart test will fail, with ac = 0. Changing it to
haf(wdprov->annualSimulation() ? hour_of_year : idx) fixes it.
I'm open to different ways to adjust for the indexing issue

Thanks for the additional details @dguittet ! I was looking at the wrong part of the setup function I think. Seems to me that your approach makes the most sense!

@janinefreeman Thanks for the review. I've switched the code so that the tests should pass. After they pass, I'll merge


Docker Endless restart loop.  Missing file.

sudo journalctl -f -u containerd
Apr 25 16:52:06 pi3 containerd[1010]: time="2024-04-25T16:52:06.114888515-04:00" level=warning msg="cleanup warnings time="2024-04-25T16:52:06-04:00" level=info msg="starting signal loop" namespace=moby pid=22000 runtime=io.containerd.runc.v2\n"
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.183769555-04:00" level=info msg="loading plugin "io.containerd.event.v1.publisher"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.184311455-04:00" level=info msg="loading plugin "io.containerd.internal.v1.shutdown"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.184375454-04:00" level=info msg="loading plugin "io.containerd.ttrpc.v1.task"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.185146481-04:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 pid=22344 runtime=io.containerd.runc.v2
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.381230782-04:00" level=warning msg="error from *cgroupsv2.Manager.EventChan" error="failed to add inotify watch for "/sys/fs/cgroup/system.slice/docker-3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217.scope/memory.events": no such file or directory"
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.438649971-04:00" level=info msg="shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.439030651-04:00" level=warning msg="cleaning up after shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 namespace=moby
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.439094853-04:00" level=info msg="cleaning up dead shim"
Apr 25 16:53:06 pi3 containerd[1010]: time="2024-04-25T16:53:06.468233201-04:00" level=warning msg="cleanup warnings time="2024-04-25T16:53:06-04:00" level=info msg="starting signal loop" namespace=moby pid=22386 runtime=io.containerd.runc.v2\n"
Apr 25 16:54:08 pi3 containerd[1010]: time="2024-04-25T16:54:08.041648455-04:00" level=info msg="loading plugin "io.containerd.event.v1.publisher"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Apr 25 16:54:08 pi3 containerd[1010]: time="2024-04-25T16:54:08.042233466-04:00" level=info msg="loading plugin "io.containerd.internal.v1.shutdown"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Apr 25 16:54:08 pi3 containerd[1010]: time="2024-04-25T16:54:08.042306039-04:00" level=info msg="loading plugin "io.containerd.ttrpc.v1.task"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Apr 25 16:54:08 pi3 containerd[1010]: time="2024-04-25T16:54:08.043167231-04:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 pid=22721 runtime=io.containerd.runc.v2
Apr 25 16:54:08 pi3 containerd[1010]: time="2024-04-25T16:54:08.878390714-04:00" level=warning msg="error from *cgroupsv2.Manager.EventChan" error="failed to add inotify watch for "/sys/fs/cgroup/system.slice/docker-3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217.scope/memory.events": no such file or directory"
Apr 25 16:54:09 pi3 containerd[1010]: time="2024-04-25T16:54:09.423631174-04:00" level=info msg="shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217
Apr 25 16:54:09 pi3 containerd[1010]: time="2024-04-25T16:54:09.479496544-04:00" level=warning msg="cleaning up after shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 namespace=moby
Apr 25 16:54:09 pi3 containerd[1010]: time="2024-04-25T16:54:09.479554673-04:00" level=info msg="cleaning up dead shim"
Apr 25 16:54:09 pi3 containerd[1010]: time="2024-04-25T16:54:09.510272977-04:00" level=warning msg="cleanup warnings time="2024-04-25T16:54:09-04:00" level=info msg="starting signal loop" namespace=moby pid=22764 runtime=io.containerd.runc.v2\n"
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.621137720-04:00" level=info msg="loading plugin "io.containerd.event.v1.publisher"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.621646658-04:00" level=info msg="loading plugin "io.containerd.internal.v1.shutdown"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.621713268-04:00" level=info msg="loading plugin "io.containerd.ttrpc.v1.task"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.622509739-04:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 pid=23095 runtime=io.containerd.runc.v2
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.836823972-04:00" level=warning msg="error from *cgroupsv2.Manager.EventChan" error="failed to add inotify watch for "/sys/fs/cgroup/system.slice/docker-3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217.scope/memory.events": no such file or directory"
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.889898394-04:00" level=info msg="shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.890086484-04:00" level=warning msg="cleaning up after shim disconnected" id=3db9f248d6a14f9a83dcfef5f619edecfee6b20fca2818bd083d33da21191217 namespace=moby
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.890177798-04:00" level=info msg="cleaning up dead shim"
Apr 25 16:55:09 pi3 containerd[1010]: time="2024-04-25T16:55:09.923019441-04:00" level=warning msg="cleanup warnings time="2024-04-25T16:55:09-04:00" level=info msg="starting signal loop" namespace=moby pid=23140 runtime=io.containerd.runc.v2\n"

Hi,
thank you for your message and the log.
Without context I cannot understand.
I need some more information...
What machine are you using? What version of docker?

RaspberryPi4
Linux pi3 6.1.28-v8+ #1651 SMP PREEMPT Wed May 17 14:34:39 BST 2023 aarch64 GNU/Linux
$ docker info
Client:
Context:    default
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc., v2.26.1)
Server:
Containers: 6
Running: 2
Paused: 0
Stopped: 4
Images: 12
Server Version: 20.10.24+dfsg1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 1.6.20~ds1-1
runc version: 1.1.5+ds1-1
init version:
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 6.1.28-v8+
Operating System: Raspbian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.704GiB
Name: pi3
ID: ZN5P:JLJE:TZNH:DH4Y:NABV:GUUL:NUKS:AYIT:3IVJ:IWKH:H54K:KCLF
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
WARNING: No memory limit support
WARNING: No swap limit support
Linux pi3 6.1.28-v8+ #1651 SMP PREEMPT Wed May 17 14:34:39 BST 2023 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
Last login: Fri Apr 26 16:17:27 2024
@.:~ $ uname -a
Linux pi3 6.1.28-v8+ #1651 SMP PREEMPT Wed May 17 14:34:39 BST 2023 aarch64 GNU/Linux
@.:~ $ docker info
Client:
Context:    default
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc., v2.26.1)
Server:
Containers: 6
Running: 2
Paused: 0
Stopped: 4
Images: 12
Server Version: 20.10.24+dfsg1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 1.6.20~ds1-1
runc version: 1.1.5+ds1-1
init version:
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 6.1.28-v8+
Operating System: Raspbian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.704GiB
Name: pi3
ID: ZN5P:JLJE:TZNH:DH4Y:NABV:GUUL:NUKS:AYIT:3IVJ:IWKH:H54K:KCLF
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
WARNING: No memory limit support
WARNING: No swap limit support
@.***:~/matterbridge $ less docker-compose.yml
services:
matterbridge:
container_name: matterbridge
image: luligu/matterbridge:latest # Matterbridge image with the latest tag
network_mode: host # Ensures the Matter mdns works
restart: always # Ensures the container always restarts automatically
volumes:
- plugin:/pi/home/matterbridge # Volume: matterbridge_plugin
- storage:/pi/home/.matterbridge # Vloume: matterbridge_storage
volumes:
plugin:
storage:
docker-compose.yml (END)

On Apr 26, 2024, at 5:14 PM, Luligu @.***> wrote:
Hi,
thank you for your message and the log.
Without context I cannot understand.
I need some more information...
What machine are you using? What version of docker?
—
Reply to this email directly, view it on GitHub https://github.com/Luligu/matterbridge/issues/15#issuecomment-2080126715, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4WTTEONFA2UJB6LKWU75LY7K7SRAVCNFSM6AAAAABGZTMCQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGEZDMNZRGU.
You are receiving this because you authored the thread.

Hi,
thanks you for your replay.
I see nothing that gives me any idea about the reason.
If you have time I try with image: luligu/matterbridge:dev that is a manifest list image.

Last thing what is the architecture of your machine?
The matterbridge:latest was the first beta and supports only arm64 but if your machine is linux/arm/v7 cannot work.
luligu/matterbridge:dev is a manifest list image and should work.
Let me know

aarch64=arm64. Running raspberry pi OS 64 bit. Running v8 OS.
Switched to :dev, no difference.
failed to add inotify watch for "/sys/fs/cgroup/system.slice/docker-c53dfc7c79d958eb0609b260e431186202755d51702f6db59d2b7c2952481219.scope/memory.events": no such file or directory"
Can’t even add memory.events manually due to permissions.  It dies after this error.  Don’t know docker enough to know what inotify watch is.

On Apr 27, 2024, at 3:59 PM, Luligu @.***> wrote:
Last thing what is the architecture of your machine?
The matterbridge:latest was the first beta and supports only arm64 but if your machine is linux/arm/v7 cannot work.
luligu/matterbridge:dev is a manifest list image and should work.
Let me know
—
Reply to this email directly, view it on GitHub https://github.com/Luligu/matterbridge/issues/15#issuecomment-2081165927, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4WTTHDAP3UEASURRB2LN3Y7P7QPAVCNFSM6AAAAABGZTMCQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGE3DKOJSG4.
You are receiving this because you authored the thread.

Still getting the memory.events error but it started running OK after a couple of restarts.  port 8283 is working remotely for the UI, too.
Thanks for the amazing work on this.

On Apr 28, 2024, at 10:51 AM, Kevin Kenyon @.***> wrote:
aarch64=arm64. Running raspberry pi OS 64 bit. Running v8 OS.
Switched to :dev, no difference.
failed to add inotify watch for "/sys/fs/cgroup/system.slice/docker-c53dfc7c79d958eb0609b260e431186202755d51702f6db59d2b7c2952481219.scope/memory.events": no such file or directory"
Can’t even add memory.events manually due to permissions.  It dies after this error.  Don’t know docker enough to know what inotify watch is.

On Apr 27, 2024, at 3:59 PM, Luligu @.***> wrote:
Last thing what is the architecture of your machine?
The matterbridge:latest was the first beta and supports only arm64 but if your machine is linux/arm/v7 cannot work.
luligu/matterbridge:dev is a manifest list image and should work.
Let me know
—
Reply to this email directly, view it on GitHub https://github.com/Luligu/matterbridge/issues/15#issuecomment-2081165927, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4WTTHDAP3UEASURRB2LN3Y7P7QPAVCNFSM6AAAAABGZTMCQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGE3DKOJSG4.
You are receiving this because you authored the thread.

Hi,
thank for the replay.
We use docker compose with arm64 and amd64 without any problem.
I use it on a raspberrypi 4 like yours too and everything is correct.
May try to update or reinstall it...
Sorry but I don't know how to help you.
Or run Matterbridge standalone or with systemctl.


Re-introspection overwrites manually added @relation columns

Bug description
When I re-run prisma introspect my manually added @relation fields disappear from schema.prisma. I understood from the documentation at https://www.prisma.io/docs/concepts/components/introspection#introspection-with-an-existing-schema that they should be maintained.
I'm assuming I'm adding the relationships incorrectly (though they worked, which was exciting!) so please forgive any naiveté...
How to reproduce

Introspect existing database for the first time with npx prisma introspect
Add 1-1 relation fields eg the owner field below which references my user table

model Stream {
  ...
  owner_id            String    @db.VarChar(32)
  owner               User      @relation(fields: [owner_id], references: [id])
  ...
}

I subsequently ran npx prisma format to add corresponding relation field in the User table:
model User {
  ...
  Stream                    Stream[]
  ...
}

Make changes to underlying postgres schema (eg add new table or new column)
Re-introspect npx prisma introspect and the owner field added above has been removed. Introspection is successful, models have warning:

✔ Introspected 17 models and wrote them into prisma/schema.prisma in 1.96s

*** WARNING ***

These models were enriched with `@@map` information taken from the previous Prisma schema.
- Model "AbcIds"
...

... but no comment about the missing @relation fields
Expected behavior
The manually added relationship fields should be preserved and merged with the new introspection.
Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: 15.11.0
Prisma version:

prisma               : 2.21.2
@prisma/client       : 2.21.2
Current platform     : darwin
Query Engine         : query-engine e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt e421996c87d5f3c8f7eeadd502d4ad402c89464d (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : e421996c87d5f3c8f7eeadd502d4ad402c89464d
Studio               : 0.371.0

I understood from the documentation at prisma.io/docs/concepts/components/introspection#introspection-with-an-existing-schema that they should be maintained.

That is unfortunately a misunderstanding:

Introspection maintains the following manual changes:

...
Custom @relation names

Easy one to make though: This applies only to the name attribute of @relation, not complete relations. That is variable and can be changed by the user. The existence of a relation depends on the database schema instead.
Do you know why your existing relations are not picked up by Prisma Introspection in the first place? Do you now have foreign keys in place maybe? Then the better solution would probably be to add these - and then Prisma should pick those up properly in the beginning already.

Ah well that explains it :) Thanks for the explanation.
As you suspected, I hadn't declared the foreign keys when I first set up the schema in Postgres, and for some reason assumed that doing so in Prisma would be enough. I will go back and do them in the db so they can persist.
Perhaps it could be clearer in the section on relations that these should ideally be set in the database? Thanks so much.

Opened: https://github.com/prisma/docs/issues/1702
I am going to close this one in favour of the docs issue.


[EN] Update NEO Node / API Reference

I will update the API reference section for EN.
I am doing this because it is pretty outdated and it will help a lot of developers, especially with the new invoke methods. This will bring the EN version beyond the CN version.
Do let me know if there is any overlap of work.

👍  go for it...


Fix /sense2vec endpoint

the /sense2vec endpoint gives a null response body when there are no entities found in the sentence matching the requested phrase.

Fixed in #27


MLP Model

Provide MLPModel as abstraction layer

closing due to https://github.com/NVIDIA-Merlin/models/pull/205


Fix CVE-2024-3727 in cri-o by patching vendored github.com/containers/image

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
[x] Ready to merge

Summary

Address https://github.com/advisories/GHSA-6wvf-f2vw-3425 by patching vendored github.com/containers/image.
Change Log

Cherry pick commits in https://github.com/containers/image/pull/2403
Prune to only the relevant sections.
Adjustments to backport the fix.

Does this affect the toolchain?

NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2024-3727

Test Methodology

github.com/containers/image w/ patch built locally.
github.com/containers/image w/ and w/o patch produce same results for make test.
Built specfile with patch locally in 2.0 container.
PR checks succeeded below.

Auto cherry-pick results:

main :x: -> https://github.com/microsoft/azurelinux/pull/9488

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=590353&view=results


Recommended structures for Nirvana projects

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
We did discuss this before, the proposed (slightly modified) structure is:
.                                   #
├── Gopkg.toml                      #
├── Makefile                        #
├── README.md                       #
├── apis                            # 存放 apidocs (swagger json)
│   ├── api.v1.json                 #
│   └── api.v2.json                 #
├── bin                             # 存放编译后的二进制文件
│   └── nirvana-myproject           #
├── build                           # 存放 Dockerfile
│   └── nirvana-myproject           #
│       └── Dockerfile              #
├── cmd                             # 存放项目的启动命令
│   └── nirvana-myproject           #
│       └── main.go                 #
├── nirvana.yaml                    #
├── pkg                             # 存放 api 需要用到的结构体与相应的 converters, 按版本区分
│   ├── apis                        #
│   │   └── v1                      #
│   │       ├── converters          #
│   │       │   └── converters.go   #
│   │       └── types.go            #
│   │       ├── descriptors          #
│   │           ├── descriptors.go      #
│   │           └── message.go          # 对应 message 业务逻辑的 API 定义
│   ├── filters                     # 存放 HTTP Request 过滤器
│   │   └── filter.go               #
│   ├── handler                     # 存放 API 需要用到的逻辑处理
│   │   └── message.go              #
│   ├── middlewares                 # 存放中间件
│   │   └── middlewares.go          #
│   ├── modifiers                   # 存放 Definition 修改器
│   │   └── modifiers.go            #
│   └── version                     # 项目版本信息目录
│       └── version.go              #
└── vendor

Refer to the discussion for details.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

As with @ddysher's comments at nirvana-practice, I have no problem with the current structure in nirvana-template-project repo, except that the handler directory should be renamed to handlers.

Strictly speaking, handler/middlewares/modifiers should all be moved into pkg/apis/v1 (e.g. you can't say for sure that modifiers won't touch any v1 data structure).
But this makes the code hard to reason about. I'd vote for current structure and keep it as is. The pkg/apis is only used for user-facing structures and routes.


Closes: #1

Fixed behavior of validate_user function in validations.py. Accounted for non-alpha characters beginning username.
Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Are we supposed to use pytest or unittest to do the unit testing part of the HW?

@AhmedCode99 We, G5, have used pytest for the unit test and the content is also about the pytest.

@AhmedCode99 I think pytest is the one prof. recommended because it is easy to use in the GitHub action. If you can get the output from unittest in GitHub action, that will work too.

@AhmedCode99 I think pytest is the one prof. recommended because it is easy to use in the GitHub action. If you can get the output from unittest in GitHub action, that will work too.

Good one

both, i think


When using Single Table Inheritance, child entities' classes will be the base class and not their concrete class in some cases.

Describe the bug
When using Single Table Inheritance, child entities' classes will be the base class and not their concrete class in some cases.
You get the concrete child classes when loading the entities directly in a clean entity manager.
You get the super class when in a running entity manager you have loaded other entities that reference our STI super class and then you try to load the STI entites.
I have an example here:  https://github.com/rhyek/mikro-orm-single-table-inheritance-test
This code: https://github.com/rhyek/mikro-orm-single-table-inheritance-test/blob/main/nest-app/src/app.controller.ts#L25-L29
will always output:
[
  'BossEntity',
  'EmployeeEntity',
  'BossEntity',
]

On the other hand, this code: https://github.com/rhyek/mikro-orm-single-table-inheritance-test/blob/main/nest-app/src/app.controller.ts#L32-L42
will always output:
[
  'PersonEntity',
  'PersonEntity',
  'PersonEntity',
]

To Reproduce
Steps to reproduce the behavior:
Run tests in linked repository.
Versions

Dependency
Version

node
v16.13.1

typescript
4.4.4

mikro-orm
4.5.9

your-driver
mysql

I've managed to work around this "issue" by forking the entity manager. So this works:
  @Get('tasks-then-fork-em-then-persons')
  async getTasksThenForkEmThenPersons(): Promise<any> {
    const tasks = await this.tasksRepository
      .createQueryBuilder()
      .getResultList();
    const persons = await this.em
      .fork(true)
      .createQueryBuilder(PersonEntity)
      .where({
        id: tasks.map((task) => task.person?.id).filter((id) => id),
      })
      .getResultList();
    return persons.map((person) => person.constructor.name);
  }

That will return:
[
  'BossEntity',
  'EmployeeEntity',
  'BossEntity',
]

That kinda implies those entities already existed in the identity map as references, and for references we dont know the correct type. We cant change the prototype once the instance exists, only thing we can do is to automatically join the relation and select the type right ahead when loading the parent entity.

Yeah, this is rather a limitation than a bug, will see if I can get around it via the auto-join as mentioned above, similarly to how we handle 1:1 relations on the inverse side.
Closing as this is a duplicate of #2364 (with a repro in #2404). That issue has a bit different title, but it is the exact same problem - unless we join the target table and select the discriminator value together with the PK, we can't create the right reference instance for it.

@B4nan sounds reasonable. Although I'd wonder what the configuration for something like that would be. If done automatically for the developer, an implicit join might not be something they'd expect and could potentially have performance issues for some use cases. Setting something explicitly on the relation definition (on the owner side) would make more sense, but its something that if could be avoided would be best.
Out of curiosity, what issues do you see arising from using something like https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/setPrototypeOf?
This makes sense to me and works for my use case:
const tasks = await this.tasksRepository
  .createQueryBuilder()
  .getResultList();
const persons = await this.personsRepository
  .createQueryBuilder()
  .where({
    id: tasks.map((task) => task.person?.id).filter((id) => id),
  })
  .getResultList();
for (const person of persons) {
  let targetPrototype: object = null;
  if (person.type === 'BOSS') {
    targetPrototype = BossEntity.prototype;
  } else if (person.type === 'EMPLOYEE') {
    targetPrototype = EmployeeEntity.prototype;
  }
  if (targetPrototype instanceof PersonEntity) {
    Object.setPrototypeOf(person, targetPrototype);
  }
}
return persons.map((person) => person.constructor.name);

that returns:
[
  'BossEntity',
  'EmployeeEntity',
  'BossEntity',
]

Out of curiosity, what issues do you see arising from using something like developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/setPrototypeOf?

Interesting, I didn't know about that! Sounds like much easier solution, let's do it this way. It should probably happen as part of hydration.

@B4nan I agree. That makes the most sense. Should this issue be re-opened or do you think #2364 covers it? I think this case might be a little different because it deals with child entities being hydrated later. In general, IMO, it makes sense for the initial references to be instances of the super class when the discriminating values aren't available yet.

It is the very same issue. I will test both reproductions after its fixed, but I am quite sure about that.


Provide a higher arity version of merge(…)

I've got a use case where I have an unknown number of AsyncChannels that I want to merge into a single stream of events.
It'd be wonderful if merge(…) and friends supported more than an arity of 3 - ideally accepting a sequence?
Thanks!

Hi
from what I know this is something that should arrive when generic variadics are available so we are not constrained to merging the same types of AsyncSequence.
Perhaps there are workarounds in your case. One that comes to my mind is (perhaps not the most efficient though)
Having a task group where you iterate over every channel you have (a task per channel) and send the elements to a single Channel. This “output” channel will act as a merging bus. You can then iterate over this single channel in another task.

@twittemb Is right here that this is something we ought to be able to do one variadic generics land. My position right now is to avoid adding sequence based APIs since they have a few downsides such as introducing an array allocation which could be avoided.
What I can recommend you for the time being is either of these two:

If merge is last transformation applied to your sequence chain then you can as @twittemb pointed out maybe use a task group and merge from there by just creating a child task for each upstream and calling next on the group repeatedly.
You could copy the code that is used for the implementation of merge and just extend it to whatever arity you need. This involves very minor changes and a bit of code duplication.

Thanks to you both - that guidance and info is much appreciated.
I'll see if I can work out how to extend the existing code to support different arities in my local project.
I'll also go read up on the parameter packs pitch by Holly and Slava - I'm really excited by this bit of work!


Run without optional values or rates file

If any of the work hours (Notion), rates config (/tempo folder), or finances data (Notion) are missing then df_comparison is never set, so the check for it being empty errors.
This confirms those exist.
I'd prefer to check that df_comparison has been set, but that is slightly more awkward given the current style of the code.
This also guards the existing call to figureSpentTimePercentage behind checking for the rates config, as it requires it.

Please check the commits, one commit is probably enough :)

I was planning to squash before merging using the GitHub feature. I can squash it and force push, if that's our preferred workflow. 😄

IMHO the commits are also part of a review. I can't know what you're going to do after it's approved ;)


UP-4777: Guard for missing dynamic variable in skin generator - rel-4-3-patches

https://issues.jasig.org/browse/UP-4777
Issue
Skin generator crashes when there is a missing dynamic variable.
Resolution
Check if value is empty or missing, skip that variable and warn.

/cc @drewwills @alasak

Coverage decreased (-0.001%) to 22.873% when pulling c6f68ff8682ee87d869a543eabaa196a09a72665 on ChristianMurphy:UP-4777-guard-missing-vars-rel-4-3 into 9817e750f3f13416e01bd20a6fea4ce269937a80 on Jasig:rel-4-3-patches.

Coverage decreased (-0.001%) to 22.873% when pulling c6f68ff8682ee87d869a543eabaa196a09a72665 on ChristianMurphy:UP-4777-guard-missing-vars-rel-4-3 into 9817e750f3f13416e01bd20a6fea4ce269937a80 on Jasig:rel-4-3-patches.


Update container

Add method to update an already existing container host configuration.

Current coverage is 61.89% (diff: 66.66%)

Merging #592 into master will increase coverage by 0.02%

@@             master       #592   diff @@
==========================================
  Files           130        131     +1
  Lines          2544       2556    +12
  Methods           0          0
  Messages          0          0
  Branches        350        351     +1
==========================================
+ Hits           1574       1582     +8
- Misses          828        832     +4
  Partials        142        142

Powered by Codecov. Last update 16b1267...1708845


Kysely Migrations fail because VercelPostgresDialect fails to report that VercelPostgres does not support transactions

The Migrator class in Kysely will use transactions if the provided dialect says that the db supports them:
https://github.com/kysely-org/kysely/blob/680eb46d257f58d437ad8f6334255b48d1e9722d/src/migration/migrator.ts#L425
The VercelPostgresDialect class does provides the standard Kysely PostgresAdapter (it fails to override PostgresDialect.createAdapter) which reports that transactions are supported:
https://github.com/kysely-org/kysely/blob/680eb46d257f58d437ad8f6334255b48d1e9722d/src/dialect/postgres/postgres-adapter.ts#L10
This causes the Kysely Migrator class to attempt to use transactions when running migrations against Vercel/Neon Postgres, which of course fails.
The solution is for the VercelPostgresDialect to report that transactions are not supported by either:

Subclassing PostgresAdapter to create an adapter where get supportsTransactionalDdl returns false and returning it
Returning a proxy to the regular PostgresAdapter that intercepts the get and returns false

Submitted a PR to fix this:
https://github.com/vercel/storage/pull/551

thanks for the fix @jwishnie! the PR has been merged 👍


mtcars is not in the intellisense list

type mt - only mtext is in the list. if you complete typing mtcars and press Enter, window does print out the dataset.

True for all variables, like airmiles. Looks like caching misses variables

https://github.com/Microsoft/RTVS/commit/47a5094efbcf5ae54100e2f719fb938fd0c7afbd


How to make sure analyzer and dartdoc don't fail?

I published this package (https://pub.dartlang.org/packages/flutter_sidekick) yesterday.
The flutter analyze and dartdoc failed and the package lost 30 points 😞 .
I don't think the package is responsible for this, because I ran the analysis and dartdoc before publishing and I got nothing wrong.
Also the descriptions of the issue don't help to understand why it's failing:

Fix platform conflicts. (-20 points)
Error(s) prevent platform classification:
Make sure flutter analyze runs.

Running dartdoc failed. (-10 points)
Make sure dartdoc runs without any issues.

I'm not sure it's the right place for this issue, because it involves other parties as well. So don't hesitate to tell me if I have to create a separate issue for the other parties as well.
How can I reproduce the error within the same environment pub uses?
Is the analysis launched periodically or should I publish a new version to trigger it?
When I looked at the dartdoc logs, I saw that the analyzer failed for a specific class, but I don't know more. It's maybe related to https://github.com/dart-lang/sdk/issues/34873.

@letsar: What was the Flutter version you have used to develop the package?
The package page contains the version of Flutter we have used for the latest analysis (in this case: 0.10.1). Did you tried running flutter analyze with that? If you want to reproduce the code analysis part, you can also use pana.
As your code uses mixins, and their support changes in the dev versions, it is possible that it will report different errors in different VM versions (as they are changing). In case of dartdoc it may be even more complex, as we use a version that is independent of the Dart/Flutter SDK used for the analysis.

I've checked this package with different SDK versions:

2.0.0 run dartanalyzer successfully but reported errors
2.1.0-dev.5.0 and 2.1.0-dev.7.1 failed to run dartanalyzer on the sources.
2.1.0-dev.8.0 and 2.1.0-dev.9.1 was successful in running dartanalyzer, and reported no issues.

It looks like there was a bug in dartanalyzer which got fixed some time ago, but the Flutter version on pub does not use it yet.
@letsar: that also means your issue will go away once we upgrade the Flutter SDK on pub site to a version that uses at minimum 2.1.0-dev.8.0. I've checked, and Flutter 0.10.2 uses that, so the upgrade timeline is up to the pub site. I'll prepare the upgrade alongside with a new changes in pana, and hopefully it can be deployed in the second half of the week. Thank you for being patient with us until then.

Hi @isoos ,
I used Flutter 0.9.4 to develop this package and analyze it, but I also analyzed it with the master branch (which was something like 0.10.3 I think).
Thank you for the great explanation 🙂.
No problem I'll wait for the fix to be deployed on pub 🙂.
Should I publish a new version of my package to trigger a new analysis when the fix will be deployed?

Should I publish a new version of my package to trigger a new analysis when the fix will be deployed?

There is no need to publish a new version, we will reanalyze the existing ones with the new runtime.

@letsar: the new release was deployed, and your package seems to be doing great!


Making sure auto-bind works for non class modules too

The reason for this change is so that we're able to also bind es5 modules except from es6 classes.
Example:
const anInstance = new MyClass();
autoBind(anInstance); // works

^ works
module.exports = autoBind({
    hasSetup: true,
    setup() {
        // do sth cool
    }
});

^doesn't work

I think you want: https://github.com/sindresorhus/bind-methods

Ok, yes this is what I want.
Thanks


Update guava to 33.1.0-jre

About this PR
📦 Updates com.google.guava:guava from 32.1.3-jre to 33.1.0-jre ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.guava", artifactId = "guava" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.guava", artifactId = "guava" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #65.

Superseded by #70.


CheckpointSaverHook does not check Graph of Saver

The following code will run just fine, but will not save any Variables to checkpoints:
import tensorflow as tf

graph = tf.Graph()
with graph.as_default():
    v = tf.get_variable("test", shape=(100, 100), dtype=tf.float32)

save = tf.train.CheckpointSaverHook("test_dir", 10)
with graph.as_default():
    tf.train.create_global_step()
    a = tf.constant(1)
    with tf.train.MonitoredSession(hooks=[save]) as sess:
        sess.run(a)

This is because the CheckpointSaverHook does not find an existing Saver, so it creates a new one in its constructor, which is executed with a different default Graph.

Is it possible to set the graph manually? Got the same problem ...
https://stackoverflow.com/questions/46299112/tensorflow-how-to-setup-a-checkpointsaverhook

I'm assuming you want to save the variable test. The default saver created in the constructor of CheckpointSaverHook will execute on the same graph if it's initialized in the same graph scope as your variables.
import tensorflow as tf

graph = tf.Graph()
with graph.as_default():
    v = tf.get_variable("test", shape=(100, 100), dtype=tf.float32)

    save = tf.train.CheckpointSaverHook("test_dir", 10)
    with graph.as_default():
        tf.train.create_global_step()
        a = tf.constant(1)
        with tf.train.MonitoredSession(hooks=[save]) as sess:
            sess.run(a)

The above code prints [('test', [100, 100])].

You need to initialize the CheckpointSaverHook in the same scope as your variables.
import tensorflow as tf

graph = tf.Graph()
with graph.as_default():
    v = tf.get_variable("test", shape=(100, 100), dtype=tf.float32)
    save = tf.train.CheckpointSaverHook("test_dir", 10)

with graph.as_default():
    tf.train.create_global_step()
    a = tf.constant(1)
    with tf.train.MonitoredSession(hooks=[save]) as sess:
        sess.run(a)

prints [('test', [100, 100])].

Maybe I should have been a bit clearer in my description, but my original issue was not meant as a question on how to fix the presented code (on the user side), but as code that I would have expected to work, but which did not.
As the Hook has a dedicated begin which is called in the correct graph, and supposed to do any  modifications of that graph. So I think it is at least surprising that in this case the Saver is added during the __init__ and not the begin call.


errors on compile

hey there are missing files
i cannot compile this project in visual studio
is there any solution for me?

please respond

He won't respond. I have contacted him through other means before and he never helps with any issue. I think he abandoned his project and gave up because he is upset that the source code got leaked and he can't profit.

Uh sorry didnt saw the issue until now. You have to build the different projects in a specific solution. Cant remember in which right now but my guess is that you have to start with the FastCallDll.

He won't respond. I have contacted him through other means before and he never helps with any issue. I think he abandoned his project and gave up because he is upset that the source code got leaked and he can't profit.

I am just low on time. No need for assumptions.

can you please add a description how to compile this bot?

sorry couldnt compile it myself and had no time to further check on. will investigate why it didnt build for me the next days when i have a minute.

thanks alot
#closed

Does questing work?

atm nothing is working.
you cannot even compile this bot :(

This is not true.... i download compiled just foine, even removed the auth server code and made it just compile but not tested. @Nackenschelle give me your email and ill send you that source.

@caffeine239 awesome.
here is my e-mail<EMAIL_ADDRESS>

still no e-mail from you -.-

im sorry data was on my laptop and ive been on my desktop, let me see if i can find it real fast.

ZzukBot_WPF.zip

thanks alot

@caffeine239 any chance you could upload or send me mmaps? Thanks<EMAIL_ADDRESS>

@caffeine239 any chance you could upload or send me mmaps? Thanks<EMAIL_ADDRESS>
https://www.mediafire.com/file/udgpmypeb573yb2/mmaps.rar/file should be the correct mmaps.

I was trying to check out this project, but I'm getting an error on building ZzukBot_WPF "error MSB3103: Invalid Resx file. Could not find file 'D:\ZzukBot_V3-master\ZzukBot_WPF\Resources\beep'. Line 222, position 5."

@caffeine239 any chance you could upload or send me mmaps? Thanks<EMAIL_ADDRESS>
https://www.mediafire.com/file/udgpmypeb573yb2/mmaps.rar/file should be the correct mmaps.

Where are these files supposed to go?

Is this intended to work with modern wow (Classic specifically)? I've added the mmaps (they go in \ZzukBot_V3-master\ZzukBot_V3-master\Release\Internal) and added a filler beep sound file to get it to compile but after it launches wow.exe I get a "A 32 bit processes cannot access modules of a 64 bit process." I'm wondering if that's because this bot was created for the 1.12 client and there have been too many dramatic changes since then.

Is this intended to work with modern wow (Classic specifically)? I've added the mmaps (they go in \ZzukBot_V3-master\ZzukBot_V3-master\Release\Internal) and added a filler beep sound file to get it to compile but after it launches wow.exe I get a "A 32 bit processes cannot access modules of a 64 bit process." I'm wondering if that's because this bot was created for the 1.12 client and there have been too many dramatic changes since then.

no this does no work on wow classic 1.13.xx only original from 2004 1.12.1.


Cannot read property '1' of null

Setting up new React Native app in .
To run your app on iOS:
   cd /Users/isaac/github/ios-go/future-app/native
   react-native run-ios
   - or -
   Open /Users/isaac/github/ios-go/future-app/native/ios/FutureApp.xcodeproj in Xcode
   Hit the Run button
To run your app on Android:
   Have an Android emulator running (quickest way to get started), or a device connected
   cd /Users/isaac/github/ios-go/future-app/native
   react-native run-android
Installing Pod dependencies
Updating local specs repositories

CocoaPods 1.0.0.beta.6 is available.
To update use: `sudo gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
Downloading dependencies
Installing Ambly (0.7.0)
Installing GCDWebServer (3.3.2)
Generating Pods project
Integrating client project

[!] Please close any current Xcode sessions and use `FutureApp.xcworkspace` for this project from now on.
Sending stats
Pod installation complete! There is 1 dependency from the Podfile and 2 total pods installed.

[!] The `FutureApp [Debug]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-FutureApp/Pods-FutureApp.debug.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `FutureApp [Release]` target overrides the `OTHER_LDFLAGS` build setting defined in `Pods/Target Support Files/Pods-FutureApp/Pods-FutureApp.release.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.
Updating Xcode project
Cannot read property '1' of null

What versions of Xcode and OSX are you using?

@dmotz
xcode 7.3
OS X el Capitan 10.11.4

Sorry I haven't been able to reproduce this, though I have Xcode 7.2.
Does it happen on every attempt?

Yes, every time.

Just came across this myself too. I have the same OS/Xcode version numbers as @gfZeng.
@dmotz - is there any other debugging information you might need?

@dmotz Also experiencing this myself and happy to help debug

👍 Have the same problem on the same OS/Xcode versions