There are some bug need to be fixed when we use the Up-to-date esp32 lib on Arduino

Environment

Core (if using chip or module):  ESP-WROOM32
IDF version   b85e8e10b90ab7089ec7989ba513f7a2235f9ea4
Development Env:		Arduino IDE
Operating System:		Windows
Power Supply:         USB

Problem Description
After i updated the hareware/espressif/esp32  directory  using "git pull". Then the I2C module is halted whenever i used the I2C module on Arduino IDE.
The default I2C module has some bug. Maybe it is I2C0. The I2C module will be halted.
Please fix it quickly. Thank you！

The current Arduino release has a bug with ReSTART operations, I have a fix pending pr 1717 That fixes this problem.
Chuck.


Does this only work for react-native-maps

I am using react-native-mapbox and neither the useClusterer or Clusterer work (or render in any way). Is this library only compatible with react-native-maps?

This library doesn't concern itself with how the markers are displayed; only with whether markers need to be clustered or not and providing GeoJSON objects for those markers/clusters.
The only thing that comes to mind that one would need to do to get this library to work with react-native-mapbox is to calculate the latitude & longitude deltas.
How are you rendering the map & using clusterer?


Provide docker images for the samples

Description
Instead of we have REPLACE_IMAGE in the samples we could have the docker images which should be used with. Also, these images should be changed/tagged and pushed after each release/sample upgrade.
PS.: I think that would be helpful impl first https://github.com/operator-framework/operator-sdk-samples/issues/86

This is a possibility especially if we get CI running for this repo; we could build a new image on every commit and release.
@hasbro17 wdyt about hosting this in quay.io/operator-framework?

HI @estroz this is my idea. We just need a docker/quayio operator-sdk or operator-framework account and do as it is done here in my personal projec: https://github.com/dev4devs-com/postgresql-operator/blob/master/.circleci/config.yml#L26 . Also see here the makefile target.

Closing this one since because we decided to make a proposal with the suggestions for this repo. I will add this topic as well.


systemd.mounts.*.before/after do not work

Describe the bug
systemd.mounts = [
      {
        #...
        before = [ "foo.service" ];
        after = [ "bar.service" ];
      }
];

Does not add the before or after to the unit section of the file. unitConfig.Before/After  work.
Steps To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
before/after should be in the [Unit] section of the file.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

@Artturin
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 5.10.90, NixOS, 22.05 (Quokka)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.6.0pre20211217_6e6e998`
 - channels(root): `"nixos"`
 - channels(jkolb): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Still valid.


Implement the web.socialProviders.callbackRoot config option

This PR implements the web.socialProviders.callbackRoot config option.
Fixes #32.
Discussion
See the discussion on https://github.com/stormpath/express-stormpath/pull/318 regarding preceding / and config.web.socialProviders vs. config.socialProviders.
How to verify

Checkout master
Run npm link and then npm link stormpath-config in your express-stormpath project
Then link express-stormpath to your sample express app
Add a console.log to stormpath-node-config/lib/strategy/EnrichIntegrationFromRemoteConfigStrategy.js, so it looks like this:

if (!localProvider.callbackUri) {
localProvider.callbackUri = callbackRoot + '/' + remoteProvider.providerId;
console.log(localProvider.callbackUri);
}

Start your sample app
Verify that you get this in your terminal (depending on what social providers you have):

/callbacks/linkedin
/callbacks/facebook
/callbacks/github
/callbacks/google

Now checkout this branch
Add the same console.log as in step 4
Run your app again and verify the same result
Now edit your config and set web.socialProviders.callbackRoot to "/cb"
Run your app again an verify you get this result:

/cb/linkedin
/cb/facebook
/cb/github
/cb/google

See my discussion before merging

Closing, as we updated the spec for social configuration and this PR is no longer accurate.  Please see comments in #32 for link to latest spec


Pull request

SAMOA-MOA Instances integration
SAMOA-67 : Integration of MOA Instances into SAMOA

@abifet Can you please have a look at this and give us the OK?


Access values inside DOMStringMap as object attributes

I have the following variable
var dataset: DOMStringMap = ...

Trying to read the attributes of the object will make the compilation to js fail
var someValue: string =  dataset.someValue

Treating the DOMStringMap as an array works but is not allowed by the linter
var someValue: string =  dataset["someValue"]

Is there any way to allow the attributes inside DOMStringMap to be accessed as object attributes?

The type any is useful for this, though you'll get back an any instead of a string.
Reconfiguring your linter may be the better option, depending.


Add unit test for docker DependencyFileNotFound

Add a unit test to guard against regressions resulting in bugs like https://github.com/dependabot/dependabot-core/pull/6142.
I didn't include this with the original PR because I was uncertain if it'd be affected by the removal of the kubernetes_updates feature flag in https://github.com/dependabot/dependabot-core/pull/6144.

This passes just fine locally in the dev container, not sure why https://github.com/dependabot/dependabot-core/actions/runs/3474850880/jobs/5808469712 failed with Errno::ENOENT:...

Oh silly me, I forgot to git add the new file...


ImportError: cannot import name Corpus

When I try to import glove, I get this. Does anyone know a solution?

Use from glove import Corpus or import glove.corpus

Weird! Yesterday I did that and it didn't work. After u said, it worked! lol Thanks very much! :-)

same error appeared for me as well. Somebody please post the solution if any..Thanks in advance

what is the name of python file? Is it glove.py?

Could someone please post the solution (if any)

Getting the same error even using a different file name
File "glove_embeddings.py", line 10, in
from glove import Corpus, Glove
ImportError: cannot import name 'Corpus' from 'glove' (C:\Program Files\Python37\lib\site-packages\glove_init_.py)

Try installing the glove package through the following command:
! pip install glove_python
And then import Corpus and Glove:
from glove import Glove, Corpus

Try installing the glove package through the following command:
! pip install glove_python
And then import Corpus and Glove:
from glove import Glove, Corpus

Unfortunately, still unable to import Corpus. Did anyone find other solutions?

Not yet.

I am still getting the same error. Someone please help.

I also had the same problem. The problem was solved when I installed as follows.
pip install glove-python-binary


DropDown Validation Issue

Hi ,
In Serenity,  if we are not filling the mandatory drop-down field, it is showing the red cross mark over the field. But the cross mark is appearing even after we have selected value for that drop down. But for the second time, we select any value the red cross mark gets disappeared.
For the first time, once we select the value itself, the red cross mark should disappear, right?
Thanks in advance.

Can anyone please help me on this.

Closing due to inactivity.


Readding code to add prefixes to URLs in signups

This code was removed because adding prefixes in production breaks things at the moment. This PR readds it.

:+1:


Steven get blog messages

Also update the return type to "void"?

I have it return a list right now because the function modifies tagsToSearch and since that's a local variable in the doGet I thought it would be best to have the function return the modified tagsToSearch since it still needs to be used in the response.getWriter() at the end.


can i hide some url in docs? somes like  /graphql

quest easy ,see title . thanks.

Yeah, there is param for router include_in_schema
Example:
app = FastAPI()
@app.get('/', include_in_schema=False)
def foo():
    return {'success': True}

Yeah, there is param for router include_in_schema
Example:
app = FastAPI()
@app.get('/', include_in_schema=False)
def foo():
    return {'success': True}

This is the perfect answer! How about we close this issue?

Yeah, there is param for router include_in_schema
Example:
app = FastAPI()
@app.get('/', include_in_schema=False)
def foo():
    return {'success': True}

This is the perfect answer! How about we close this issue?

yes .thanks.i see it just now.

Thanks for the help here @SirTelemak ! :clap: :bow:
Thanks for reporting back and closing the issue :+1:


Warning: Type "ToolchainContext" is not indexable

For sample rule implementation:
def _impl(ctx):
    info = ctx.toolchains["//:my_toolchain_type"].my_info

Getting:

Put up a temporary fix here: https://github.com/withered-magic/starpls/issues/252
However, the result of the indexing operation will be Unknown instead of ToolchainInfo, the full fix is blocked by https://github.com/withered-magic/starpls/issues/253 so will leave this open until that gets fixed as well

This should be fixed on master now!


As a user I want to see the location of a given appointment

so that I can plan for travel

Subtasks: #55  #31  #26  #25


Eliminate compilation warning

solved compilation warning:
warning: deprecated conversion from string constant to 'char*' [-Wwrite-strings]

Fixed in the async-udp branch which will become master at some point.


Add ability to copy the console content to the clipboard

This is a great idea! Thanks for adding this 😀


Where does input filtering happen in Django/the new OTF site (equivalent of Drupals input filters)?

Is it configured in code or in some UI?

It's all in code.


How to send a message to the client from server directly?

Hey guys. I want to use this library to make a instant message app which user from on client could send message to other client through the server router the message. I didn't find how to send a message from the server directly without the callback of stanza. How to do that? Thanks.

I don't understand what you mean by without the callback of stanza.
If it helps there are client examples here https://github.com/node-xmpp/node-xmpp-client/tree/master/examples

Thanks  foryour reply.  I  means if  server  get  a  message  from  one  client,  how  to  send  the message  to  the  target  client(another  client which  rece ive  the message) .
Sent from Outlook Mobile
On Thu, Mar 3, 2016 at 5:47 AM -0800, "Sonny Piers"<EMAIL_ADDRESS>wrote:
I don't understand what you mean by without the callback of stanza.
If it helps there are client examples here https://github.com/node-xmpp/node-xmpp-client/tree/master/examples
—
Reply to this email directly or view it on GitHub.

If a message is addressed to a client, the server should forward that message to the client.
For example if you send this message from a client A to B
`

hello

`
var message = new Stanza('message', {to: 'B@domain/web', type: 'chat'} message.c('body').t('hello') client.send(message)
the server will forward that message to the resource (client) web of the user B.
http://xmpp.org/

Here is my scripts
server
var xmpp = require('node-xmpp-server')
var server = null
var startServer = function (done) {
  // Sets up the server.
  server = new xmpp.C2S.BOSHServer({
    port: 5280,
    domain: 'localhost'
  })

  // On connection event. When a client connects.
  server.on('connection', function (client) {
    // That's the way you add mods to a given server.
    // Allows the developer to register the jid against anything they want
    client.on('register', function (opts, cb) {
      console.log('REGISTER')
      cb(true)
    })

    // Allows the developer to authenticate users against anything they want.
    client.on('authenticate', function (opts, cb) {
      console.log('server:', opts.username, opts.password, 'AUTHENTICATING')
      if (opts.password === 'secret') {
        console.log('server:', opts.username, 'AUTH OK')
        cb(null, opts)
      } else {
        console.log('server:', opts.username, 'AUTH FAIL')
        cb(false)
      }
    })

    client.on('online', function () {
      console.log('server:', client.jid.local, 'ONLINE')
    })

    // Stanza handling
    client.on('stanza', function (stanza) {
      console.log('server:', client.jid.local, 'stanza', stanza.toString())
        client.send(stanza)
    })

    // On Disconnect event. When a client disconnects
    client.on('disconnect', function () {
      console.log('server:', client.jid.local, 'DISCONNECT')
    })
  })

  server.on('listening', function(){})
}

startServer();

client a
var xmpp = require('node-xmpp-server');
var Client = require('node-xmpp-client');

function test() {
  var clienta = new Client({
    jid: 'clienta@localhost',
    password: 'secret',
    bosh: {url: 'http://localhost:5280/http-bind/'},
  })
  clienta.on('online', function () {
    console.log('clienta: online')
  })
  clienta.on('stanza', function (stanza) {
    console.log('clienta: stanza', stanza.root().toString())
  })
}
test();

clientb
var xmpp = require('node-xmpp-server')
var Client = require('node-xmpp-client');
var Stanza = require('node-xmpp-core').Stanza

function test() {
  var clientb = new Client({
    jid: 'clientb@localhost',
    password: 'secret',
    bosh: {url: 'http://localhost:5280/http-bind/'},
  });
  clientb.on('online', function () {
    console.log('clientb: online')
    var message = new Stanza('message', {to: 'clienta@localhost', type: 'chat'});
    message.c('body').t('hello');
    setInterval(function() {
      clientb.send(message);
    }, 3000)

  })
  clientb.on('stanza', function (stanza) {
    console.log('clientb: stanza', stanza.root().toString())
  })

}
test();

Client b will send message to clienta every 3 seconds. However, clienta didn't print any log to the console. Did I miss something?

node-xmpp-server is a library so it doesn't implement routing out of the box, you have to do it yourself.

Maybe take a look at @chris-rock's radiowave? http://www.hnwatcher.com/r/2041625/Radiowave-Node-js-JavaScript-xmpp-server


Persist last used URL for future events

This addresses issue #92.
When a new TrackMe reaches the tracker, we check if it has QueryParams.URL_PATH set.

If it has a url parameter, we check if it is valid, possibly fix it, then store it in the default TrackMe object the tracker maintains (mDefaultTrackMe).
If it doesn't have a url parameter, we use the parameter stored in the Tracker's default TrackMe.

TrackMe's should be threadsafe meaning no crashes or bad behavior, but we are obviously still susceptible to race conditions, e.g.:

Thread1: Track screen1.
Thread1: Track event1.
Thread2: Track screen2.

event1 could be tracked with the URL from screen2.
I don't see how we can fix or prevent this, this is up to the developer to do correctly.
I'm preparing another PR that refactores the whole tracking API which will also adress trackEvent not taking a url parameter.

:+1:


Create webpack.ym name: NodeJS with Webpack  on:   push:@jessetheriau…

<EMAIL_ADDRESS>       branches: [ "main" ]   pull_request:     branches: [ "main" ]  jobs:   build:     runs-on: ubuntu-latest      strategy:       matrix:         node-version: [14.x, 16.x, 18.x]      steps:     - uses: actions/checkout@v3      - name: Use Node.js ${{ matrix.node-version }}       uses: actions/setup-node@v3       with:         node-version: ${{ matrix.node-version }}      - name: Build       run: |         npm install         npx webpack

刚刚看见


Generate go response internals

Current response generation is limited to top level object.
Need to generate any nested internal struct/interfaces for those top level response objects.

superseded by #131


Use literal match for free suffix subdomain match

Before this www.** would match any "www" prefixed domain (like
www.example.com, wwwxxx.example.com), but now it will only match
domain whose first part exactly matches (i.e. www.example.com).

The commit message above is kind of confusing, but I couldn't come up with anything better...

Superseded by #10, closing.


[SPARK-47390][SQL] PostgresDialect distinguishes TIMESTAMP from TIMESTAMP_TZ

What changes were proposed in this pull request?

Regarding SPARK-47375, this PR fixes the issue of converting PG TIMESTAMP_TZ & TIME_TZ to our NTZ.
Why are the changes needed?

bugfix
Does this PR introduce any user-facing change?

yes, as 3.5 is out, this PR add a migration guide for this.
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?

mo

cc @cloud-fan @dongjoon-hyun, thanks.

Merged to master.
Thank you for the review @cloud-fan


Some downloads result in DF-BPA-33 error

The majority of apps that I've tried downloading seem to work OK, but some seem to not work any time that they're attempted to be downloaded.  In the console is the error:
Error retrieving information from server. [DF-BPA-33]
A search of this error pulls up pretty much nothing except for https://www.quora.com/Do-you-know-what-is-the-df-bpa-33-error-on-Google-play-store , which suggests a time synchronization problem.   Why this is only happening for certain apps is beyond me.
An example app with this problem is:
https://play.google.com/store/apps/details?id=com.hutchgames.hotwheels

I can download that hotwheels app just fine.
I'm not quite sure, but I seem to recall that you can get in trouble, if your device (Raccoon in this case) has a "weird" system time (e.g. in the future). This can happen if timezone and local time don't match.

Hmm, the VM that has the Raccoon software has its clock synchronized via NTP, and I've manually confirmed that it's accurate.   I've even tried changing the time zone to "Europe/Berlin", as I've seen a reference to that in the code.  But that didn't affect things either.
I'd say that I have about an 80% success rate across all apps that I've tried, with the remaining apps nearly all giving the DF-BPA-33 error.  And for those that do give the DF-BPA-33 error, it happens 100% of the time.  Any ideas on how to proceed?


Styled components extending React components Does not work as documented

Styled components extending React components Does not work as documented
use this online failing example to see for yourselves
Environment
The online example is using codesandbox.io with create-react-app
Expected Behavior
I expect to be able to apply styles to the child react component from the parent and extend it.
Actual Behavior
The styles on the parent (B) have no effect on child (A)

You're using what we refer to as a "component selector" for those styles to be applied, A would need to physically be inside B in the DOM.

I have tried your solution here
As you can see it does NOT solve the problem
Can you please fork my example and provide a working code BEFORE closing this issue?
That would be kind of you

https://codesandbox.io/s/ly03yqn0l9

Thanks for that :)
I've been messing with it for too long and the documentation does not mention this...
cheers


Add example notebooks for compiling with opencv and an adaptation of a CUDA training series

I am trying to adapt this CUDA training series to use our library in order to create possibly the most efficient way to learn CUDA C++ available on the internet. The first session was adapted, but I would require some feedback. @andreinechaev If you have the time, you can run the notebook on either Colab or Kaggle. I will add a README.md in the "notebooks" directory at some point describing how to import from Kaggle these notebooks straight from GitHub.

@cosminc98 Thank you for your contribution. I think you provided clean notebooks, it is easy to read and to follow them.
If you think that we should merge, I can proceed.
If you're looking for enhancements, CUDA is very verbose, so splitting the solution in multiple cells, can make it even better. It will involve splitting the files, so it might be an overkill. Anyway, I leave it for your judgment.
Thanks!

@andreinechaev Thanks for the feedback! I'll try to have a look ASAP if there's a way to split them in a way to be as easy to read as possible.

@andreinechaev I've split the code in the OpenCV notebook into more manageable pieces. As for the CUDA intro notebook, I think it may be a bit too confusing to beginners to have the kernel function in a separate cell (as I think that would be the only split that can be reasonably done). If it's all in one cell, they can immediately run the cell and see if they got the correct assignment solution. I think we can introduce more modularity in the next notebooks, as users will have had a bit more experience (with both CUDA and the library). What do you think?

@andreinechaev I've split the code in the OpenCV notebook into more manageable pieces. As for the CUDA intro notebook, I think it may be a bit too confusing to beginners to have the kernel function in a separate cell (as I think that would be the only split that can be reasonably done). If it's all in one cell, they can immediately run the cell and see if they got the correct assignment solution. I think we can introduce more modularity in the next notebooks, as users will have had a bit more experience (with both CUDA and the library). What do you think?

I see, thank you @cosminc98 . I believe it's a reasonable explanation. The notebook looks good. Shall we proceed with merging?


DxList - Dxi-Item Grouped Possible?

Using 16.2.2-beta.2.
Not sure how to get grouping working with dxi-items. Can you give an example?
This does not work.
<dx-list class="ptx-who-are-we-list" grouped="true" selectionMode="none" activeStateEnabled="false" collapsibleGroups="true"
    scrollByThumb="true">
    <dxi-item key="a">A1</dxi-item>
    <dxi-item key="a">A2</dxi-item>
    <dxi-item key="b">B1</dxi-item>
</dx-list>

Hello @stonecourier
It's the same issue as in #269. So, I am closing the current ticket. As a workaround, do the following:
<dx-list class="ptx-who-are-we-list"
    [grouped]="true"
    selectionMode="none"
    [activeStateEnabled]="false"
    [collapsibleGroups]="true"
    [scrollByThumb]="true">
    <dxi-item [items]="['A1', 'A2']">
        Group 1
    </dxi-item>
    <dxi-item [items]="['B1']">
        Group 2
    </dxi-item>
</dx-list>


Add query dsl

Three layers:

Something data-oriented like {:select [:x :y] :where [{:x := 1}]}, which allows us to target clauses by type when compiling the query. This might be redundant and unnecessary given representation number 2.
Also data-oriented, but as a collection, like [{:t :select :v :x} {:t :select :v :y} {:t :where :k :x :op := :v 1}]. This allows the user to easily compose/modify queries, since a query is a (recursive, with subqueries) collection of clauses.
A convenience layer, e.g. (q (select x y z) (where= x 1)). The q function should compile directly to the collection representation above, flattening values returned from query building functions/macros into a single list. This should recur into subqueries as well.

A compile function should take any of the three representations above and turn it into a string, escaping literals and identifiers as necessary. If the input is a string already, it should just return it.
Execution functions shouldn't know about this layer, but should expose a configuration option for preparing queries, which can be configured by setting it to compile.

It might be worth replacing unpack with something in this layer for creating aliases. This would:

Solve the same problem as unpack, but would be faster since postgres would be doing the work.
Unpacked/calculated columns could be used in non-select clauses


file missing or corrupted

hi this app isn't working anymore when I add a song I tried to play it by pressing that button near the song it says file missing or corrupted that's bull because my songs play on the other music apps but not yours can you help me this app is literally unusable please fix it asap thanks for everything

The "file missing/corrupted" message really means that the app couldn't read the file for whatever reason, not necessarily that there is anything wrong with the file. I'll update the message in an update to make this more clear.
If the file missing/corrupted message is appearing when there is nothing wrong with the actual file, then it's likely appearing due to some permission related problem. I'm not sure why that would happen though. Is it only happening to one specific file, or it is also happening for other files as well? You could also try removing the track, then re-adding it and seeing if that works. Even if it stops working again, it might help narrow down the problem.

Its happening with all files
On Thu, Nov 21, 2024, 9:54 PM Nicholas Hochstetler @.***>
wrote:

The "file missing/corrupted" message really means that the app couldn't
read the file for whatever reason, not necessarily that there is anything
wrong with the file. I'll update the message in an update to make this more
clear.
If the file missing/corrupted message is appearing when there is nothing
wrong with the actual file, then it's likely appearing due to some
permission related problem. I'm not sure why that would happen though. Is
it only happening to one specific file, or it is also happening for other
files as well? You could also try removing the track, then re-adding it and
seeing if that works. Even if it stops working again, it might help narrow
down the problem.
—
Reply to this email directly, view it on GitHub
https://github.com/CliffracerMerchant/SoundAura/issues/62#issuecomment-2492137107,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNDURDYESGDKME7N76W2KBD2BY26XAVCNFSM6AAAAABSGTJNUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJSGEZTOMJQG4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


new ci for dh-backend

Description

References

#0000

Codecov Report

Merging #1105 (334df77) into main (2201b2e) will increase coverage by 7.42%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1105      +/-   ##
==========================================
+ Coverage   68.40%   75.82%   +7.42%
==========================================
  Files          18       30      +12
  Lines         269      484     +215
  Branches       25        0      -25
==========================================
+ Hits          184      367     +183
- Misses         75       97      +22
- Partials       10       20      +10

Impacted Files
Coverage Δ

...ce/DataHub.WebApi/Controllers/ChargesController.cs
27.77% <0.00%> (-5.56%)
:arrow_down:

...Api/Controllers/MarketParticipantControllerBase.cs
0.00% <0.00%> (ø)

...stration/JwtTokenSecurityRegistrationExtensions.cs
46.66% <0.00%> (-53.34%)
:arrow_down:

...gistration/HealthEndpointRegistrationExtensions.cs
36.84% <0.00%> (-42.11%)
:arrow_down:

...WebApi/RequireNonNullablePropertiesSchemaFilter.cs
80.00% <0.00%> (-8.00%)
:arrow_down:

apps/dh/api-dh/source/DataHub.WebApi/Startup.cs
93.90% <0.00%> (ø)

.../DataHub.WebApi.Tests/Integration/EndpointTests.cs
100.00% <0.00%> (ø)

...sts/Integration/Controllers/ControllerTestsBase.cs
100.00% <0.00%> (ø)

...ntegration/Controllers/WholesaleControllerTests.cs
100.00% <0.00%> (ø)

...ce/DataHub.WebApi.Tests/Fixtures/WebApiTestBase.cs
100.00% <0.00%> (ø)

... and 8 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Added JSDoc

This PR adds generated JSDoc documentation to Prism (#1777) using the Minami theme. The generated docs directory will be accessible from prismjs.com/docs.
This contains the doc of all highlight functions, insertBefore, extend, all hook functions, and Prism.Token. I used the docs from our extending page as a base and added a few sentences.
This includes complete type information for all documented function (except for hooks where the type of the env parameter depends on the hook).
Because JSDoc requires a README for the index.html, I used Prism's README. We can also make one specifically for the doc. (I just didn't know what to write.)
Interactive demo. (Will only be available during the time this PR is open.)
Right now, only prism-core is used to generate the doc. Other documented plugins and languages will need some adjustment before JSDoc can handle them. And there's also the question of whether these components should even be part of the doc.
Implementation
I used gulp-jsdoc3, so npx gulp will also re-generate the doc (this takes less time than minifying the language definitions, so the build process won't take too much longer).
Because of some ... features of JSDoc, I had to make some debatable adjustments to the doc generation process:

JSDoc only adds the newly generated doc. It doesn't remove outdated files, i.e. if the file documented was deleted or renamed. So to fix this, gulp will first delete the whole doc directory.
You cannot disable the generation time in the Minami theme, so I use a regex on the HTML files to remove the date.
JSDoc also includes a few font files which our theme doesn't use, so those get removed.

Another rather unfortunate thing is that JSDoc doesn't use Prism to highlight source code.
We could make it with a few regex replacements but that would only add another point on my list of debatable decisions.

This resolves #1777.
This resolves #1555.
This resolves #1774.

/cc @mAAdhaTTah @LeaVerou @Golmote

It works decently with TypeScript’s checkJs, although that doesn’t yet support @memberof.

I looked a little into this and there don't seem to be any workarounds for this, are there?

The only solution would be if TypeScript would add support for @memberof or if we would migrate portions of this project to TypeScript.

Well, there is an issue so the hope is there...
I'm actually quite a fan of TS but I think that:

Porting the project for the sake of JS-Check isn't worth it.
TS isn't necessary for Prism.

Also, TS is not as popular as JS, so some people might get held back from contributing.

That's a good idea. I'll change all similar occurrences.

I actually also had a TokenStream type at one point but discarded it because of two reasons:

I want to keep it simple and the TokenStream type has essentially zero value documentation wise.
This is about documentation, not types (though, both are related of course).
The generated doc-website doesn't have a nice hover-for-type-definition-summary feature. This means that the TokenStream type in a e.g. function definition will hide the actual type information until one clicks the link to go to the definition.
So instead of adding TokenStream, which makes the code a little cleaner, I choose to write its definition again and again to make the doc easier to read.

What happened here? It seems this was just abandoned, which is a shame.

Approval pending happened.
And also a change of heart in myself. I tried TSDoc and ohh boi it's not as good as you think it is. Both TSDoc and JSDoc are a pain to setup and use.

JSDoc vs TSDoc for Prism
While JSDoc is kinda nice when you want to get a nice documentation page out, it can't do anything else. JSDoc type annotations are compatible with TS but that's it. Everything else like namespaces and membership is not supported by TS, so the namespaces of documentation don't work in code. Luckily, everything in Prism is in the Prism namespace, so nothing (except trivial stuff) works.
You need these annotations because for JSDoc everything is declared in global scope unless declared otherwise and if everything is global, you don't get the nice structure you want which makes JSDoc useless. So if we really use JSDoc, we break with TS which I do NOT want. I love TS.
So what about TSDoc? Well, if you don't write everything in TS, it's almost useless. It can parse JS files like JSDoc but it doesn't understand the annotations which make JSDoc useful, so everything is global. You now have two choices: 1) convert to TS or 2) use declaration files. 1) is way to much work just for documentation, so 2) it is. The problem with declaration files is twofold.
Firstly, your types and documentation are now far away from the actual code, so they can easily become outdated. And secondly, you know have to fight the TypeScript ecosystem.
I love TS and its strict compiler but when you venture outside Typescript's usual system of static imports (of whatever kind) and dare to use features like ref comments it's not a pleasant experience. If we just don't check the types (why have them then?), the types itself are a problem too.
Prism has a few things which cannot be expressed in TS's type system. A good example are Prism grammars. You can't express them in TS because of rest properties. It's not possible to declare an object in which all keys have a certain type except for one key that has a different one. You cannot do it (related: this simply doesn't work). Tbh, most of these problems are suboptimal design on our side (e.g. why can't you have a token named rest? Similar for a language named extend).
You can make TS work with Prism but we have to make 2 breaking changes:

Remove rest. I plan to do that someday anyway. The spread syntax is a thing after all and rest also has other problems.
Move the Prism.languages functions. I have no idea why DFS is not in util but extend and insertBefore also have to be moved.

We can talk about these changes some other day. I just wanted to show that full types, while impossible right now, are not far off.

It seems this was just abandoned

That's because I kinda did abandon JSDoc.
I want Prism to move closer TS and a major step toward that goal was TSDoc. The problem: I failed miserably one 3 separate occasions. I just couldn't find a way to make it work with Prism without basically rewriting 50% of the library.
I'm now at the point of giving up on TSDoc for now. So yeah...
JSDoc:
It's still a pain to use, I mean, I even had to hack in something as basic as determinism and not even the code display works out-of-the-box. Also, almost all changes to any file with documentation will cause the generated website to change because the line numbers of function/classes/types change.
However, my main problem is this: JSDoc can generate some nice-looking docs but it messes with TS in all the wrong ways. It annoys me to no end that I have to decide whether I want type annotations that actually work and help me code (TS) or whether I want type annotations that generate good doc. You can't have both! (note: Maybe you can right now? This was the state of things one year ago but I doubt that it changed and put simply: I'm not willing to put any more days (yes, days) of my life into marrying JSDoc and TS. If there is a reliably way, I'll do it but I won't put any more hours into finding that way.)
So let's get this over with: Before I touch this again, I want a bit of clarity. What do we want?
I say it as it is: I want TS and JSDoc blocks that path as it is now.
I want to slowly move Prism, so that one day the whole codebase is still JS but most strongly typed via comments so that the TS can check everything. There already have been a few occasions where TS would have pointed out a bug but that didn't happen, so some user reported it instead.

Thank you! I was considering JSDoc for another project, and this further reassures me I made the right choice deciding against it.

Ok, so no JSDoc. That's good.
But also bad because some way of publishing our documentation would be great. When I made my research a year, there were some competitor but all of them were basically abandoned at this point in time. Are there any other static site documentation generators or something else we can use?

Do we want generation from source or a separate app?
I can see the DRY argument for docs from source, but it can also be quite restrictive in a number of ways.
Since the argument for generating from source is obvious, I'm going to play devil's advocate here and argue keeping docs separate from comments, but don't assume that's my position. I'm fine with whatever you folks decide :)

Often the kind of docs one wants in source are not the docs one wants on a website. It can be extremely tedious to scroll through several paragraphs of documentation comments to spot the code, so there's a tendency to keep them terser and with fewer examples than if they were separate.
Comments are not meant for long-form text of that sort. E.g. line breaking needs to be done manually and is quite a pain to align multiline documentation for params (especially when documenting object literal params)
Generators tend to follow a specific, more rigid syntax and a more formulaic output, whereas with a separate app, the sky is the limit, with interactive filters, custom structured data, live demos etc.

The counterexample here would be Rust. They even do simple tests in doc comments. It's actually pretty awesome.

or a separate app

What can app X do that our website can't do?
Maybe the CS student with limited experience shouldn't talking like he knows stuff but:
From what I see we need 2 types of documentation. The first is the one we have right now. It's the short documentation that tells how you use the library without going into the nitty-gritty details that you only need to know when you want to dive deep. This also includes docs for our development setup and everything else that can't be a comment in our code.
The second kind is the one we lack. It's the detailed documentation you need when you can't go the easy way (e.g. Prism's automatic highlighting) and have to do things yourself. This should include a detailed description of every public and internal function/class/constant.
For the first kind, a website like we already have is perfect. Elaborate articles and demo. You can do it all.
For the second kind, I think static site generation from doc comments is ideal. Sure, it's limited but you don't need interactive demos in technical documentation (at least, I never did). The problem with those generators is outlined in the comment above.

Comments are not meant for long-form text of that sort.

I disagree with that. Sure, your next novel shouldn't be published as a doc comment but up to 200 lines are fine IMO. Everything beyond that should probably be an article for the first kind of documentation anyway.
Also, what you then describe seems to be a general lack of comment formatters in JavaScript (after a quick google search, I found none). Java has excellent comment formatters with both the Eclipse IDE and IntelliJ. In C/C++ you can count on clang-format for at least reflow your comments which is usually all you need.
(Looking at from a different perspective: It's the state of JS tooling when it comes to documentation pretty bad? Shouldn't documentation be a major part of writing code? Especially since you don't have types that by there name alone do have the documenting in other languages.)

How do others do this?
I've never seen a tools like JSDoc being used in the wild. In languages like Java and C/C++ you see these static sites generated from comment for many projects.
Also, I think I'll look into JSDoc once more. There seems to be some recent activity on their GitHub, so hopefully, things improved a little.

Ok. It's done.
After this comment, I gave it another try. This time with the goal of just getting something that works even if it barely works.
The main problem with marrying TS and JSDoc was that TS couldn't do namespaces and wasn't smart enough to figure out some things about the structure of Prism instances. That was a year ago. TS has since become a bit smarter and we had a PR that made it easier for TS to figure out Prism. So TS could now understand Prism. One problem solved.
Now namespaces. Screw namespaces! I just didn't use them. Without using namespaces, the generated doc is somewhat odd because all classes and type definitions are part of the global namespace. This isn't really scalable documentation-wise but TS can understand it, so sure why not. We only have 5 types in global space right now, so it isn't a big deal.
After some tinkering and hacking, I finally had something that worked with both TS and JSDoc.
I also used a different theme that is a lot more configurable and just plain better than the previous one.
It finally works and it even looks kinda nice. Demo.
The hacking
I still have a small CSS file to change/fix the theme but it's better now.
The real hacking comes with JSDoc's parser. It can't deal with some TS syntax (e.g. intersection types and type imports) and will throw an error.
To fix that, I added a handler for JSDoc parser events that will just remove all type imports via a small regex and hopes that it works then. This is nothing more than a hack but it works and I don't plan to change anything about it because the JSDoc team doesn't intend to support this syntax, so this is the best I can do.
TS
One of the main intentions was to get good type checking, so did that turnout?
Amazing. It works really well. You have to kinda work around some issue but it's doable. My goal of moving Prism toward strict typing via doc comments is almost fulfilled. There are only 2 type problems left in Core. For that alone, I want to see this merged.
Other nice things
Documentation is opt-in. You can add doc comments however you like and for whatever you like. Only if you mark a doc comment as @public will it be part of the generated documentation site.
Thanks to the new theme, we now have a search bar and we can add your own links to the nav.
Not so nice things
The doc site includes a "jump to source" function. This means that every change to Core will result in changes in the doc site. To mitigate this a little, the gulp docs task is not part of the default build task. If you make changes to the doc, you have to rebuild the site manually. Not nice, but not too bad either.
Closing thoughts
It's not perfect but it works. You can write some doc and it will generate a nice site for you.
I criticize JSDoc and my solutions to all the problems I had to deal with a lot but I'm actually really happy with this result.
Let me know what you think.
Awaiting review.

In another project, I actually wrote everything in JS and managed to generate .d.ts files from them. If we're going to put all this work into writing & maintaining the documentation, is it possible to do that here? Not a requirement for this PR, by any means, just throwing it out there.

is it possible to do that here?

Should be possible. Let's make an issue of this after this PR is through.

I'm generally ok with punting off defining TokenStream to a future PR and not blocking this on it.

Well, if we really narrow down the definition of a Token after this, then that's a breaking change.
Actually, let's just take the current definition of Token and TokenStream as they are in here right now. This will resolve #2071.

I'm definitely on board with these API docs in general. I would love to eventually get to a world where we generate both types of docs into a single cohesive website, but this works for now.

I should probably point out that we now have API doc, but I haven't actually linked to it yet... Let just me do that real quick.

Minor change: I narrowed down the type definition of a Token (reason).
I'm gonna merge now.


Image sharing on existing Multi-site

It is a problem when I install this plugin on the existing multi-site, I can't get the image on the subsites.
I suggest we can check the image before it returns the result on wp_get_attachment_image_src filter function. If the image array is empty after switched to the media site, we can get the image from the current blog.

Thanks for the report. This is not a use case that this plugin will support because it greatly increases the complexity. I recommend checking out the alternatives.


qbittorrent-nox

start.sh tries to start qbittorent-nox but qbittorent-nox is not installed as part of the docker build
I was able to start the qbittorent UI only after manually installing qbittorent-nox in the docker. Still I was unable to start any downloads.
start.sh gives the following error - 2023/03/24 13:19:34 socat[172] E bind(5, {AF=2 <IP_ADDRESS>:8080}, 16): Address already in use

Hey @th0masfrancis - how were you able to resolve this? I am getting the same issue when running the docker container
2023-04-06 01:32:30 qbitmf  | /start-unpriv.sh: line 14: qbittorrent-nox: command not found


ctrl+f not working in *.ipynb files

Bug: Notebook Editor, Interactive Window, Python Editor cells
Steps to cause the bug to occur

Open a .ipynb file
Try to ctrl-f

Actual & Expected behavior
Actual : Nothing happens
Expected : I can search
Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running:                       Local
Extension version:                               2019.10.41019
VS Code version:                                1.40.0-insider
Setting python.jediEnabled:               true
Python and/or Anaconda version:     3.7.4
OS:                                                      Mac:
Virtual environment:                           virtualenv

Hey @loftusa. Thanks for reporting this. Currently the notebook editor is implemented as a webview extension, which means that we don't get lots of the base vscode functionality by default. We're looking at adding in what we can to better improve this experience. Currently we already have an issue for adding in Ctrl-F support.
https://github.com/microsoft/vscode-python/issues/7903
I'll close down this issue a duplicate of that one, but if you upvote that issue we do consider which issues have the most votes when figuring out our priority.


Unnecessary screenshots

The problem
Selenide is making screenshots even if the tests is not failing with the 'shouldNot' condition and a collection that does not exist.
Anyone else got this bug?
Example:
There is no div named body
$$("#body").get(0).shouldNot(visible) --> Screenshot
$("#body").shouldNot(visible) -> No screenshot)

(I know these two things are the same)
When there is only one div called test
$$("#test").get(1).shouldNot(visible) -> No screenshot
Environment
Selenide 4.10.01
Chrome Version 69.0.3497.92 (Official Build) (64-bit)

Closing due to inactivity


fix to make actions list i18n ready and Japanese translation

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Currently, actions list is generated from internal name of actions, so it is displayed only in English.
This PR makes action name i18n ready. And, adds Japanese message translations of actions.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 67.27% when pulling 58f3a76da76e65cc53f8d8ca7ff60b3e1579083e on node-red-hitachi:fix-action-list-i18n into 81a4fe59d9c738c79332af72e16b38ea3a99442a on node-red:dev.

Thanks for raising this @HiroyasuNishiyama
This approach will work for actions provided by the core, but it will not work for actions provided by nodes/plugins - it assumes the translations are in the core message catalog.
We need to consider how to make it work more generally.
The only way to do that is for the code registering the action to also be able to provide the message catalog identifier to use as its label.
Actions are registered by calling: RED.actions.add(name, handler).
The most backward compatible way of doing this would be to add a third argument as an optional options object:
RED.actions.add(name, handler, options);

That means any nodes/plugins updated to provide that extra option will still work as they do today with older versions of NR.
The options object then gives us a place to add various properties now and in the future, without having to worry about changing the signature again.
For this feature in particular, I'd suggest we introduce a label property to the options object. Combining that with the logic you already have means:

If options.label is set, lookup the i18n message with RED._(options.label).
If options.label isn't set, then strip the prefix (the part before :) and lookup RED._("action-list."+actionname). If that doesn't resolve, use the existing code to transform name to the presented version

That would allow a plugin to provide a message identifier that is scoped to their own catalog.
The work to resolve the label value should be part of RED.actions.add(...). That means we don't duplicate the logic in the different places that displays the action (keyboard dialog + action-list dialog).
That will mean modifying how that module stores the actions. At the moment it is a simple object mapping name to handler function. That would need to change to be name mapped to {handler: handler, label: label, options: options}.

Thanks for your comment.
I have updated the PR according to your advice.


chore: Introduce FileHandler

First MR towards having a cache file for saving the trusted packages into a file (#143).
Created a new class FileHandler, which will hold all the interactions towards reading/writing files.
Adapted AbstractParser to use it.
In the following MRs:

adapt ConfigHandler to also use it.
save trusted packages to a file.

Looks reasonable! Can you give me 2cents on what you mean by caching the file? I assume you mean vendoring it in the repository?

That was the original idea but in a way, vendoring it in the repo would be just another source. So twyn would be mirroring the actual TopPypiReferences to guarantee more availability, and then we can provide different options to chose from where to retrieve the data.
The caching I'm referring to in this MR is a local one, so that you would save locally the list of trusted packages without having to download the whole list again.


Update: VMware.HorizonClient version <IP_ADDRESS>410

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run


Hardware Sync

Hi Just want to know if the following information are true or not?
Only hardware depth sync is available on D435, not color syn. Is it true that we can only hardware synchronize the depth images but not the color images from multiple D435s?? Or does it not matter since the color cam is already synchronized to the depth if they are running at same framerate?
Auto exposure for the depth camera D435 has to be off if hardware sync is needed?
Thanks

A past answer provided by. @dorodnic is: "D435 allows Depth to Color sync, and Depth to another Depth sync, but not Color to another Color, so at least one (or both) of the color sensors will not be synced".
This comment is sourced from an excellent discussion on hardware sync that is worth reading.
https://github.com/IntelRealSense/librealsense/issues/2637
Regarding auto-exposure: the common advice seems to be to disable Auto-Exposure Priority during hardware sync.  This setting is not the same thing as Auto-Exposure.
https://github.com/IntelRealSense/librealsense/issues/2637#issuecomment-434203140
Typically when Auto-Exposure Priority is disabled, Auto-Exposure should be left enabled.  The reason for disabling Auto-Exposure Priority is usually to enforce a constant FPS.

Thanks MartyG for the info. I guess my next question is what frame rate do I set the D435 to if I want to asynchronously externally trigger it? any other info you can provide on asynchronous hardware triggering would be greatly appreciated. Thanks

Currently there is no asynchronous triggering feature. You want to trigger of an external signal of any frequency, correct?  This feature will come but right now you stand different cameras to exactly the same frequency determined by the master camera (being a Realsense camera).

Is there any more question?
**Please be informed that we will close this ticket in seven (7) days if we have not heard back from you.

That's all for now :-) Thanks for all the help


Add full support for PostgreSQL backend

I added the missing part in order to fully support the PostgreSQL backend with PowerDNS. This means that the database, user and schema gets automatically created just like with the MySQL backend. Note here that I added two additional params pgsql_backend_package_name and pgsql_schema_file which are distribution dependent as the PowerDNS PostgreSQL database backend package has a different name on RedHat and Debian. There is now a new dependency on the puppetlabs-postgresql puppet package. RSpec unit tests have all passed as well as UAT for debian8.

@ju5t thanks for your feedback. I've been using the master branch for my changes where the $authoritative_configdir does not exist yet in the params.pm file. I guess I should have been using the develop branch instead... Shall I still add $authoritative_configdir back as an additional commit to this PR?

@brigriffin it should be sorted now. Thanks a lot!

Fantastic, thank you for your fast response!


travis: Add go 1.8 to the test matrix

Signed-off-by: Damien Lespiau<EMAIL_ADDRESS>

Coverage remained the same at 13.4% when pulling 4d10b15943344d3347e8fd24bdb5b312a11ac341 on dlespiau:20170223-ci-go-1.8 into e4cedaad52c2e48c9af7a7ffc3adf4b90561b57a on clearcontainers:master.

LGTM


drivers: modem: gsm: allow using custom modem setup commands

Sometimes there is a need to use a custom setup sequence for the GSM modem so add the possibility to use your own
setup_cmd structure with commands that are required.
Signed-off-by: Bartosz Bilas<EMAIL_ADDRESS>

I missed this PR because it's not prefixed with gsm_ppp, just so you know.

There's many ways to accomplish this. I will try to submit a PR today with an alternative.

Hi!
I'm looking forward to the merge of this PR - it would solve many problems.
Also I was thinking if there's a way to add the custom setup commands after gsm_query_modem_info() function is finished. That way we could support multiple modems and add commands based on gsm->minfo. Now I'm modifying gsm_ppp.c and using gsm->minfo.mdm_model to branch into two different setup paths depenging on the modem used.
Cheers!

Hi! I'm looking forward to the merge of this PR - it would solve many problems. Also I was thinking if there's a way to add the custom setup commands after gsm_query_modem_info() function is finished. That way we could support multiple modems and add commands based on gsm->minfo. Now I'm modifying gsm_ppp.c and using gsm->minfo.mdm_model to branch into two different setup paths depenging on the modem used. Cheers!

I've re-opened that MR since I'm coming back to this topic this or next week since it's needed for my project. I'll consider your suggestions and we'll see how to deal with them.


Reduce cloudflared log spam

When using wrangler tail, the logs from cloudflared are fully visible:
[INFO] Version 2020.6.3
[INFO] GOOS: darwin, GOVersion: go1.13.1, GoArch: amd64
[INFO] Environment variables map[metrics:localhost:8081 proxy-dns-upstream:https://<IP_ADDRESS>/dns-query, https://<IP_ADDRESS>/dns-query url:localhost:8080]
[INFO] Starting metrics server on <IP_ADDRESS>:8081/metrics
[INFO] cloudflared will not automatically update when run from the shell. To enable auto-updates, run cloudflared as a servic⠒   This may take a few seconds...
⠠   This may take a few seconds...
⠖   This may take a few seconds...
[INFO] Each HA connection's tunnel IDs: map[0:3zq71z0c5k2puvxkt97h6pgtsktax0iz0xf4ugyl37g8snx6fxfg]
[INFO] +------------------------------------------------------------+
[INFO] |  Your free tunnel has started! Visit it:                   |
[INFO] |    https://punishment-vsnet-solve-yacht.trycloudflare.com  |
[INFO] +------------------------------------------------------------+

This isn't really useful for devs, it also seems like unnecessary log spam. Maybe this should be hidden by default?

shouldnt happen with latest version of cloudflared, this was a regression in the version you have installed i believe

Yep, thanks. Looks great now.


auro-radio-group: option selected feature

Is your feature request related to a problem? Please describe.
Similarly to auro-select or auro-menu, the ability to have the option selected from the auro-radio-group would be very useful. This can be use to make decisions after the user has selected one of the options form the radio-group.
Describe the solution you'd like
The option to have a property for a selected option on the radio-group.
For instance:

In the case of the image, the option "No" would be the option selected.
e.g this is an example of how it is in the auro-select component

Isn't it better to have selected or checked property instead in the auro-radio element, since radio component can only have one selected items in it ?

A radio group is a set of checkable buttons, known as radio buttons, where no more than one of the buttons can be checked at a time.
(https://www.w3.org/WAI/ARIA/apg/patterns/radio/)

But its fine if we want to make it the same as auro-select implementation.


Opamp

Allow for configuration of the internal opamp peripheral. Only the disabled, voltage-follower and open-loop modes are implemented. Other states can be added later on.
It's my first time implementing such a module. Feedback and remarks are more than welcome!

hey @Geens, Thanks for implementing it! I haven't started work on Hal part of OpAmp myself, so great timing :) as I'll have use for it in my project.
In the mean time I've added OpAmp enum definitions to stm32-rs crate https://github.com/stm32-rs/stm32-rs/pull/486
I think once it lands you might be able to remove some of the magic values from your PR.  You can try building that crate locally and add it to local build in cargo, to play with it before its merged.
I'll appreciate any feedback on the Enum PR too - if you think anything is missing, or should be differently named.

Hi @pawelchcki, cool that you're working on this too. I just had a quick look at your commit and I can definitely see the advantage of using the right enum definitions. I also noticed the table you mentioned and realized I did not enable opamp 6 for the devices that have opamps 1, 2, 3, and 6.
I'll try and build with your stm32-rs branch this weekend and update to use the enum defs. Since your branch is not yet part of any release, how do we fix the dependencies for this crate? Do we just leave this pull-request open until the stm32-rs is updated?

@Geens I'm hoping to get this reviewed quite soon, will ping the maintainer tomorrow (don't want to bother them too often).
Once it lands in stm32-rs master it will be available via https://github.com/stm32-rs/stm32-rs-nightlies - that you can use directly in HALs cargo.toml. I think if you like the Enum's it would make sense to review and wait until the stm32 is released, and only then merge this into this crate.
Actually I'll try to push the updated stm32 in my own nightly repository - could be useful for myself too.

Ok seems it  worked, feel free to use this repo/branch to work with these changes.
[dependencies.stm32g4]
git = "https://github.com/pawelchcki/stm32-rs-nightlies"
branch = "opamp"
features = ["stm32g431", "rt"]

@pawelchcki, The stm32g471 is missing opamp 6 in the PAC. This was mentioned in STM32G4 #486. For me, it's not really necessary so I don't mind commenting it out. But it seems like it's not  hard to add it either.
Also there are no features for the stm32g491 and stm32g4a1 in this crate yet. Also not really needed for me but I would think it's better to add them sooner than later.
How would you continue?

@pawelchcki, The stm32g471 is missing opamp 6 in the PAC. This was mentioned in STM32G4 #486. For me, it's not really necessary so I don't mind commenting it out. But it seems like it's not hard to add it either.

I'm not sure stm32g471 actually has the 6th Opamp - the manual says shoud have it, but STM Cube sources only have first 3 opamps defined there. From what I've read, sadly the STM CubeMX generated files are usually most accurate.

Also there are no features for the stm32g491 and stm32g4a1 in this crate yet. Also not really needed for me but I would think it's better to add them sooner than later.

I don't have strong opinion there. We can always add them in a separate PR

Thanks for the input! I removed opamp6 from the stm32g471.
@dotcypress I think this pull request is ready for review.

Thank you @Geens and @pawelchcki


Add JDK_NATIVE_OPTIONS in jdk_net

Resolve: https://github.com/eclipse/openj9/issues/12081
Signed-off-by: lanxia<EMAIL_ADDRESS>

JDK Version
impl
Grinder

17
openj9
Grinder/14075

11
openj9
https://ci.adoptopenjdk.net/job/Grinder/7521/

8
openj9
https://ci.adoptopenjdk.net/job/Grinder/7524/

11
hotspot
https://ci.adoptopenjdk.net/job/Grinder/7525/

Looks like more native tests are continually | gradually  being added for new jdk version. Instead of keeping adding JDK_NATIVE_OPTIONS when error happens I think we can add JDK_NATIVE_OPTIONS to all jdk_* testcases( exclude jdk_custom). And add $(JVM_NATIVE_OPTIONS) to all other testcases.
That is JDK_NATIVE_OPTIONS is one of default options for jdk_* testcase and JVM_NATIVE_OPTIONS is one of default options for non jdk_* testcases. We have limited those two native options to jdk8+ and exist(TESTIMAGE_PATH) so it won't hurt if there is no testimage available.

As this is a fix we can merge this first and update other target later.

Might be worth updating all as suggested in https://github.com/AdoptOpenJDK/openjdk-tests/pull/2342#issuecomment-796169726, since there are other targets that also have new native tests blended into their targets, see related: https://github.com/AdoptOpenJDK/openjdk-tests/issues/2380

I close this PR as we would like to add the option as default.


Add support for dbt 1.x.x

Currently we support version 0.21.x.
dbt 1.0.0 introduced some breaking changes that should be handled.
The breaking changes can be found here and here.

Seems resolved by  #3851 and/or earlier.
Please re-open if this is still broken.


gitignore!

What is deleting the R file?

I found this when I googled about it and I think it might have to do with it deleting.
"Make sure that anything the R. links to is not broken. Fix all errors in your XML files. If anything in the ADKs are broken, R will not regenerate."
I'm not sure how to fix it though


Ability to add --no-offsite-links mid grab

Would it be possible to add this mid grab (so say if the grab is running out of control/getting spam sites etc)
5vqqwfgciq4y7ksb6e4olk5ao is a key example of when this could be done.

This is controlled by a wpull command-line switch (see https://github.com/ArchiveTeam/ArchiveBot/blob/master/pipeline/archivebot/seesaw/wpull.py#L83-L86).
As far as I know, this is not under wpull script control, and modifications to wpull will be necessary.  Paging @chfoo.


Chapter 2: Housing plots

The axes are not correct in all of the California housing plots in handson-ml and handson-ml2 repositories. x-axis should be latitude and y-axis should be longitude.

For the simple reason that latitudes are represented horizontally and longitudes vertically. You can see any map or globe to find out this. At one point in chapter two, California png image is retrieved. If you observe this png file or other actual map of California, you can observe a slight difference especially on the border of the map on the top left hand side.

For the simple reason that latitudes are represented horizontally and longitudes vertically. You can see any map or globe to find out this. At one point in chapter two, California png image is retrieved. If you observe this png file or other actual map of California, you can observe a slight difference especially on the border of the map on the top left hand side.

I'm afraid that is not true. Please take a look at the following link. It is quite clear that the latitudes are defined by the y-axis (ordinate), and the longitudes with an x-axis (abscissa) in the planar projections. Latitudes are going from the Equator (0 degrees) to North (90 degrees) at the northern hemisphere; this is obviously a y-axis reference.

For the simple reason that latitudes are represented horizontally and longitudes vertically. You can see any map or globe to find out this. At one point in chapter two, California png image is retrieved. If you observe this png file or other actual map of California, you can observe a slight difference especially on the border of the map on the top left hand side.

I'm afraid that is not true. Please take a look at the following link. It is quite clear that the latitudes are defined by the y-axis (ordinate), and the longitudes with an x-axis (abscissa) in the planar projections. Latitudes are going from the Equator (0 degrees) to North (90 degrees) at the northern hemisphere; this is obviously a y-axis reference.

I'm sorry that your response is not true. In the very link that you have shared, there is the picture of Equator and you can see that this does not go from 0 degrees to North. Equator spans the earth horizontally. There are tons of images in Google which shows the latitudes and longitudes and you can verify them.

For the simple reason that latitudes are represented horizontally and longitudes vertically. You can see any map or globe to find out this. At one point in chapter two, California png image is retrieved. If you observe this png file or other actual map of California, you can observe a slight difference especially on the border of the map on the top left hand side.

I'm afraid that is not true. Please take a look at the following link. It is quite clear that the latitudes are defined by the y-axis (ordinate), and the longitudes with an x-axis (abscissa) in the planar projections. Latitudes are going from the Equator (0 degrees) to North (90 degrees) at the northern hemisphere; this is obviously a y-axis reference.


Ghostly Essence can be used to dye sheep

Description (Required)

Ghostly Essence is actually white dye, it can be used to dye sheeps.
Steps to reproduce the Issue (Required)

Get Ghostly Essence
Find a Sheep (not white)
Right-Click said Sheep with the Ghostly Essence
Watch the Sheep turn white

Expected behavior (Required)

Ghostly Essence can't used to dye sheep
Server Log / Error Report

None
Environment (Required)

Tuinity git-Tuinity-"c303521" (MC: 1.16.5)
Slimefun DEV - 861 (git 73b5ef8b)
Metrics-Module #21
Java 11
Installed Addons: (3)
InfinityExpansion vDEV - 98 (git 4cf7e322)
FoxyMachines vDEV - 42 (git ae8d8aba)
DynaTech vDEV - 88 (git c06f0e25)

Being able to dye sheep with ghost essence is intended behavior


Song information not showing

Describe the bug
[ The song information does not come up, even after reinstalling rainmeter and Spicetify-cli. In rainmeter, it shows a error: Plugin:Unable to load "Chameleon" (error 126), and Plugin: Unable to load "SpotifyPlugin" (126)]
To Reproduce
idk
Screenshots
[

The same happens with the Monstercat visualiser, but I use another visualiser for now.
]
System information

Rainmeter Version: <IP_ADDRESS>.3321 (64-bit)
OS Version: Windows 10 pro 2009 64-bit (build 19042)
Skin Version: 2.1.0
Spotify Version: [<IP_ADDRESS>0.g2ae50076]

Additional context / media
[ Add any other context or screenshots about the problem here. ]

I believe the new spotify UI update, and the new spicetify completely broke it. I've got the same issues. All of my earlier spicetify skins are broken too...

Had the same problem. To solve the problem I've restored the backup with the code spicetify restore backup and after it I did a fresh install of Spicetify with the following code: Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/khanhas/spicetify-cli/master/install.ps1" | Invoke-Expression
Everything is working fine now.

... Perhaps, this recent patch could be of help. More info. about here. Hope this helps!


Challenge-04 by @MaldoAlberto

proposal solution: Task 3

It looks like you've created two files, one in the general directory for the 4th challenge – could you delete it?

I've just skimmed through it, but otherwise seems legit :)

@mstechly the duplicates have been removed, thanks for your feedback.


reservoir reads 0.0 on 723 2.4A

openaps 0.0.3
Medtronic 723 v2.4A
$ openaps use pump reservoir returns 0.0
Reservoir actually at 203.5U

Can you send me results of mm-send-comm.py --serial xxyyzz tweak ReadRemainingInsulin, the data file that results from adding --save might be interesting too.

Sorry it took me awhile; here's what I get (actual reservoir is 58.0 U):
pi@raspberrypi ~/hannemannopenaps $ mm-send-comm.py --serial 345192 tweak ReadRemainingInsulin --save
## do stuff with an insulin pump over RF
using ` Namespace(autoinit=False, begin=None, bytesPerRecord=None, command='tweak', descr=None, dryrun=False, effectTime=None, end=None, init=False, maxRecords=None, name=None, no_postlude=False, no_prelude=False, no_rf_prelude=False, other='ReadRemainingInsulin', page=None, params=None, port='', postfix=None, prefix=None, prefix_path='', save=True, saveall=False, serial='345192', session_life=10, verbose=None) `

```javascript
{'radio': {'errors.crc': 0,
           'errors.naks': 0,
           'errors.sequence': 0,
           'errors.timeouts': 0,
           'packets.received': 7L,
           'packets.transmit': 7L},
 'usb': {'errors.crc': 0,
         'errors.naks': 0,
         'errors.sequence': 0,
         'errors.timeouts': 0,
         'packets.received': 33L,
         'packets.transmit': 33L}}

PUMP MODEL: ReadPumpModel:size[64]:data:'723'
<class 'decocare.commands.ReadRemainingInsulin'> {}
response: ReadRemainingInsulin:size[64]:data:0.0
hexdump:
0000   0x00 0x00 0x09 0x14 0x00 0x00 0x00 0x00    ........
0008   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0010   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0018   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0020   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0028   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0030   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........
0038   0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00    ........

decoded:
0.0

end stats

{'radio': {'errors.crc': 0,
           'errors.naks': 0,
           'errors.sequence': 0,
           'errors.timeouts': 0,
           'packets.received': 9L,
           'packets.transmit': 9L},
 'usb': {'errors.crc': 0,
         'errors.naks': 0,
         'errors.sequence': 0,
         'errors.timeouts': 0,
         'packets.received': 41L,
         'packets.transmit': 41L}}

Is the --save file

After reviewing it, the data seems to be there:
0000   0x00 0x00 0x09 0x14 0x00 0x00 0x00 0x00
So that is (9 x 256 + 20 x 1) / 40 = 58.1. I'm assuming the 40 is from the motor step size (0.025 U minimum delivery step). Nate and I checked it out on his 723 as well and at a few different reservoir values and they are consistent.

Nice work all!
Hmm, Might make sense to do something like this:
class ReadRemainingInsulin (PumpCommand):
   ...

class ReadRemainingInsulin723 (ReadRemainingInsulin):
  basalStrokes = 40

Then in models.py we can have it use the right "command."  Thoughts?

Would that take care of the byte location discrepancy as well?

[sorry, a bit new at this]
I tried changing commands.py to this:
class ReadRemainingInsulin(PumpCommand):
  """
  """

  code = 115
  descr = "Read Remaining Insulin"
  params = [ ]
  retries = 2
  maxRecords = 1
  basalStrokes = 10.0
  startByte = 0
  endByte = 2

  def getData(self):
    data = self.data
    log.info("READ remaining insulin:\n%s" % lib.hexdump(data))
    return lib.BangInt(data[startByte:endByte])/basalStrokes

class ReadRemainingInsulin523(ReadRemainingInsulin):
  """
  """

  basalStrokes = 40.0
  startByte = 2
  endByte = 4

and models/init.py to this:
class Model523 (Model522):
  strokes_per_unit = 40
  larger = True
  read_carb_ratios = Task(commands.ReadCarbRatios)
  read_reservoir = Task(commands.ReadRemainingInsulin523)

Is that what you had in mind? I'm struggling to get it to work, but I'm not sure if that is because I'm not installing it properly or because the code above is simply wrong.
Also, we still need verification that the 523 and 723 act similarly, but I rolled it into the 523 for the time being (which the 723 inherits from).

Yeah, this is basically what I had in mind.
Feel free to start a new branch: git checkout -b wip/channeman/read_reservoir to get a new branch.  Check in your changes, and push them to your fork: git push origin wip/channeman/read_reservoir.
What exactly is not working?  As you point out, the benefit of doing it this way is all the models inheriting will use the newer version you're providing.
AH:
Try this line:
  return lib.BangInt(data[startByte:endByte])/basalStrokes

to:
  return lib.BangInt(data[startByte:endByte])/self.basalStrokes

and rename strokes_per_unit to basalStrokes.  The name has to be the same.
HTH!  If you check in and push to github, I can do per-line comments to help. :-)

Same thing for the other values... in the "class definition", foo=bar means a class level variable.  In the method, to access "this instances" version of the property, we need to do self.foo, so same thing for self.startByte, and self.endByte.

Fixed and tested on my 723 v2.4A: wip/channeman/read_reservoir. PR submitted to dev branch of decoding-carelink (https://github.com/bewest/decoding-carelink/pull/120).
Thanks for all the assistance with basic git help, @loudnate and @bewest!
(btw, I copied your line above directly, so "channeman" is spelled incorrectly in the branch—should have four n's).


Update compatible-controllers.md

Updated pin information for SP530e based on my experience flashing WLED

FYI LEDPIN is no longer supported in 0.15. Instead users should use DATA_PINS override.
Please update this across the document while you're at it.
Is it correct that you only added MIC and "onboard LEDs"?


Fixes #36

Fixes the issue by using the proper parameter type.

@sbhklr Thanks again for working on this one.
Since we aren't actually using the representation in this object, I don't want to force the parameter to be an XMLIndexer. I understand that using Any causes the retain issue. What about using AnyObject? That seems like a happy medium where we keep it relatively flexible, but it should be retained since we are confirming that it is an object.

Actually, wouldn't we be able to make the representation type Any?.
Making it optional might stop the crashing without any other issues.
Let me run a few tests and see what I can do.

Any? doesn't stop it from crashing and AnyObject leaves me with S3Test/ViewController.swift:116:70: Cannot convert value of type '(Response<S3ObjectMetaData, NSError>) -> ()' to expected argument type 'Response<_, NSError> -> Void' Hmm, not sure how to get rid of that 🤔

Hmmm that's really odd. Can you send me an example project so I can see this bug for myself? Also, in #36 I mentioned changes I made in develop. Can you see if those changes fix this please.

Sure. I'll try out your changes first.

Looks like the other changes fixed. Closing this.


[Compose] Vertical chain does not respect the horizontal guideline

I'm using constraintlayout-compose version 1.0.0-rc02
This is what I want to achieve: Suppose the height of the screen is divided into two equal halves. I want to vertically center two Text composables in the lower half.
This is the code I'm using:
    ConstraintLayout(modifier = Modifier.fillMaxSize()) {
        val (text1, text2) = createRefs()
        val guideline = createGuidelineFromTop(0.5f)
        createVerticalChain(text1, text2, chainStyle = ChainStyle.Packed)
        Text(
            modifier = Modifier.constrainAs(text1) {
                top.linkTo(guideline)
                bottom.linkTo(text2.top)
            },
            text = "Text1"
        )
        Text(
            modifier = Modifier.constrainAs(text2) {
                bottom.linkTo(parent.bottom)
                top.linkTo(text1.bottom)
            },
            text = "Text2"
        )
    }

The above code gives the following output which is wrong. Basically, the vertical chain is ignoring the fact that the top of the top Text composable is constrained to the guideline, not to the top of the parent.

Not sure but could be related to #392

Unfortunately You tried created chains in two ways.
 createVerticalChain(text1, text2, chainStyle = ChainStyle.Packed)
This created a vertical chain by default attached to the parent.
      top.linkTo(guideline)
      bottom.linkTo(text2.top)

      bottom.linkTo(parent.bottom)
      top.linkTo(text1.bottom)

This created another chain.
Unfortunately the first one won.
So you can ether remove the first one. (but how do you define packed?)
or remove the second.
if  you would need to add some lines...
    val guideline = createGuidelineFromTop(0.5f)
    val chain = createVerticalChain(text1, text2, chainStyle = ChainStyle.Packed)
    constrain(chain) {
        top.linkTo(guideline)
    }

The way I implemented the above layout in Compose is based on how I would implement it in the View System. Let's say I want to implement the same layout using XML. I use the following code:
<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <androidx.constraintlayout.widget.Guideline
        android:id="@+id/guideline"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:orientation="horizontal"
        app:layout_constraintGuide_percent="0.5" />

    <TextView
        android:id="@+id/text1"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Text1"
        app:layout_constraintBottom_toTopOf="@id/text2"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toBottomOf="@id/guideline"
        app:layout_constraintVertical_chainStyle="packed" />

    <TextView
        android:id="@+id/text2"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Text2"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toBottomOf="@id/text1" />

</androidx.constraintlayout.widget.ConstraintLayout>

The above XML layout produces the following output which is correct:

Anyway, let's say I use the second solution you provided. I mean this:
    val guideline = createGuidelineFromTop(0.5f)
    val chain = createVerticalChain(text1, text2, chainStyle = ChainStyle.Packed)
    constrain(chain) {
        top.linkTo(guideline)
    }

The problem is that createVerticalChain returns Unit. This means that the following line gives an error because constrain requires an instance of ConstrainedLayoutReference whereas chain is Unit:
constrain(chain)

The way I implemented the above layout in Compose is based on how I would implement it in the View System. Let's say I want to implement the same layout using XML. I use the following code:
<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <androidx.constraintlayout.widget.Guideline
        android:id="@+id/guideline"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:orientation="horizontal"
        app:layout_constraintGuide_percent="0.5" />

    <TextView
        android:id="@+id/text1"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Text1"
        app:layout_constraintBottom_toTopOf="@id/text2"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toBottomOf="@id/guideline"
        app:layout_constraintVertical_chainStyle="packed" />

    <TextView
        android:id="@+id/text2"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:text="Text2"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toBottomOf="@id/text1" />

</androidx.constraintlayout.widget.ConstraintLayout>

The above XML layout produces the following output which is correct:

Anyway, let's say I use the second solution you provided. I mean this:
    val guideline = createGuidelineFromTop(0.5f)
    val chain = createVerticalChain(text1, text2, chainStyle = ChainStyle.Packed)
    constrain(chain) {
        top.linkTo(guideline)
    }

The problem is that createVerticalChain returns Unit. This means that the following line gives an error because constrain requires an instance of ConstrainedLayoutReference whereas chain is Unit:
constrain(chain)

Both have issues for you. No packed command in the traditional way.
The createVerticalChain is in the source code now (added Dec 15 ) but we have not done a release.
The only way to achieve this in the current release is in the JSON syntax.
We will be working on a release in the next few weeks.

Closing as this is supported in 1.0.0
Modifier:
   ConstraintLayout {
       val (tex1, text2) = createRefs()

       val vChain =  createVerticalChain(text1, text2)
       constrain(vChain) {
           top.linkTo()
           bottom.linkTo()
       }

       Text(modifier = Modifier.constrainAs(text1) {...}
       ...
   }

ConstraintSet:
   ConstraintSet {
       val text1 = createRefFor("text1")
       val text2 = createRefFor("text2")

       val vChain =  createVerticalChain(text1, text2)
       constrain(vChain) {
           top.linkTo()
           bottom.linkTo()
       }

       constraint(text1) {...}
       constraint(text2) {...}
       ...
   }


Build from sources, build issues

Hi, everyone.
I'm trying to build tensorflow from sources as https://www.tensorflow.org/get_started/os_setup#installing_from_sources illustrated.
however, when I came to the step bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
it followed with "[2,302 / 3,143] Still waiting for 200 jobs to complete: " with more than 20 hours.
how long does it need to finish the job.
thanks.

It certainly should not take 20 hours to compile. From your top output, it doesn't seem like tis chugging on CPU either. What architecture are you running this on? Which version of gcc? If you cancel the build and retry, does it still get stuck?

Closing due to lack of recent activity. Please update the issue if it persists and we will reopen.


issue38 Align joinLRA methods timelimit attribute

issue #38
Signed-off-by: xstefank<EMAIL_ADDRESS>

Looks good

Closing per discussion in the issue


¿ why does the PDOX not have a function called union all there ?

My need is the following: I need to make a union of all, between two tables and to that data make a page

Hi @Darknet17 ,
Actually I thought this but i did not any development for that. Maybe we can put it on top of the To-Do list.
Thank you for your feedback!

always @izniburak , I have the need to apply it, to the project that I am doing, and this stopped by this part of which I cannot make the union there to those two tables and then make the page. I am using the ligne_php framework.


Share errors with guests (build errors, linter warnings, analyzers, etc.)

Currently, Live Share doesn't share the errors the host sees in their editor, which means if the host is experiencing build issues, linter warnings (e.g. ESLint), test failures (E.g. XUnit), etc. then than context isn't visible to participants within their collaboration session. This is a critical component for effective pair programming, and therefore, Live Share needs to automatically remote errors from the host to their guests, including errors that were generated from 3rd party extensions.
Note: Refer to #141 and #133 for details on specific scenarios where this general issue occurs.

This feature has been released in the latest extension update! Let us know if you run into any issues after you update and give it a try. Thanks 👍

This feature has been released in the latest extension update! Let us know if you run into any issues after you update and give it a try. Thanks 👍

Hey we still have the same problem is there any fix?

@Timmermann00 could you provide some more info about the issue you're seeing, and ideally open up a new issue? Thanks!

This feature has been released in the latest extension update! Let us know if you run into any issues after you update and give it a try. Thanks 👍

Hey we still have the same problem is there any fix?

Same, exact same issue, not fixed whatsoever.

Visual Studio 2019 16.11.18, Live Share 1.0.5701.0, still no errors are shared between host-guest. Autocomplete works, in some capacity.


[iOS] Add 3DSecure

I'm going to do another PR for Android and propose to update the documentation once both are merged :)

Love it! Apologies for the late response. Thanks!


CLOUDP-40809: Create a canonical build script

Also improves docker caching and pins alpine version

Oops—gave this the wrong branch name. 🤦♂

I assume this is what you meant today to use the binary instead of rebuilding?

No, this is only a partial measure. I want to stop building the binary twice at all.


Add kubefed-operator to community-operators.

…essary OLM artifacts
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Have you tested an update to your Operator when deployed via OLM?

Your submission should not

[x] Modify more than one operator
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@anik120 @robszumski this PR renames the federation operator to kubefed-operator, hence touches both the directories.

do-not-merge/work-in-progress

/do-not-merge

/hold

/work-in-progress

/unhold

/hold cancel

/cc @aneeshkp
/assign @robszumski

@aneeshkp, @robszumski can this PR be merged? Request a review please.

/test scorecard

/test scorecard

/retest

/retest

/test CVP

/test CVP

The CVP pipeline had a bug trying preparing the local copy of the PR for testing. The problem is fixed and testing is underway.


Add button_just_down and button_just_up methods to PointerInput

Objective
Upstream two small methods present in bevy_mod_picking but not in bevy_picking.
There might be a few more of these.

should these be called pressed and released instead of down and up to match the methods on ButtonInput? https://dev-docs.bevyengine.org/bevy/input/struct.ButtonInput.html#method.just_pressed

I would prefer that, but for ease of migration, let's keep the names for now.

This is not exactly the same api as in mod_picking so exact migration replication isn't needed. These get around PointerAction not being Eq for some common cases.
I'll change them to pressed/released.

should these be called pressed and released instead of down and up to match the methods on ButtonInput? https://dev-docs.bevyengine.org/bevy/input/struct.ButtonInput.html#method.just_pressed

If we're doing this, it should be a global concept rename (ex: Pointer<Down> and Pointer<Up> types, all of the methods)
I'm guessing the Down / Up vs Pressed / Released conversation has already happened somewhere, so we should make sure we aren't retreading ground.

I'm guessing the Down / Up vs Pressed / Released conversation has already happened somewhere, so we should make sure we aren't retreading ground.

It has not, actually! I'm all in favor, but I'd rather not do this in 0.15. The migration from the old crate will already be somewhat complex without renaming some of the events.

@aevyrie any strong opinions here?

We do currently have PointerAction::Pressed, which can either be "pressed" down or up, which I do find a little confusing given that "press" is generally thought to be a "down" action (at least in my experience).

Can we rename PointerAction::Pressed to PointerAction::Button?

This also seems to conflict with the PointerPress component, which uses bool flag indicators (presumably true == Down and false == Up).

Can we rename PointerAction::Pressed to PointerAction::Button?

Yep. That along with Pressed/Released is consistent with winit's new pointer api as well.

I made the suggestion changes to the function names. Can we merge this and leave the other suggestions for follow up (ideally slated for 0.16)?


Modeling with stochastic simulation | MIT Computational Thinking Spring 2021 | Lecture 10

Modeling with stochastic simulation | MIT Computational Thinking Spring 2021 | Lecture 10
7:16 Introduction
8:10 Julia features
9:00 Individual-based ("microscopic") models
11:55 Modelling time to success (or time to failure)
12:50 Visualizing component failure
21:15 String interpolation
28:30 String interpolation (HTML example in Pluto)
35:24 Math: Bernoulli random variables
42:10 Julia: Make it a type!
49:50 Running the stochastic simulation
56:15 Time evolution of the mean: Intuitive derivation

Done!


lib/tests/formulae_dependents: link only installed formulae

We started trying to link recursive dependencies in #711. However, this
causes test-bot to attempt to link runtime dependencies of build
dependencies (see reviews at #659). This will error out because those
dependencies will not be installed (cf. Homebrew/homebrew-core#89573).
Let's fix this by only attempting to link recursive dependencies that
are actually installed.

Thanks @carlocab!


'Include Icon/IIR' should be hidden before 'connect'

The new tick boxes are showing by default, before the pedal is connected.

After a disconnect they are (correctly) hidden.

Wrong project... :-(


adding images for skill assessment

Adding images for the input, output, and label for skill assessment. Also creates a trial number folder within directory to place images in.

Added option for image generation from model yaml file, with option for user defined spacing.
Also caught/fixed a bug in the dataset loader where precip unit conversion was also needed in the norm functions.


Tweak theme query functions and add a test.

Fixes #1100
Any ideas how to improve the tests are welcome.

@jmervine: can you look one last time? I improved the newly added test..


Updated & upgraded frontend dependencies

Most notably React 16 -> 17

import React from 'react' is no longer necessary

Typefaces were left to current versions.
Prettier is kept at 2.2.1, as 2.3 introduced formatting difference
Bootstrap was kept at 4.6, as 5.0 introduced breaking changes

Is this occurring to you?

No, can't say it is
The @babel/code-frame is in yarn.lock, so it should be installed... did you remove the node_modules directory and then reinstall? I got few other errors without doing that

The @babel/code-frame is in yarn.lock, so it should be installed... did you remove the node_modules directory and then reinstall? I got few other errors without doing that

True: I don't know why this occurs. I removed node_modules and reinstalled with yarn install with no luck.
I also tried deleting the whole project and git cloning it. Installed the dependencies in master and then used yarn upgrade on this branch. I get the same error msg still

What I did, was:
cd frontend
git checkout frontend-update-deps
rm -rf node_modules
yarn

So, basically I had to remove and reinstall the deps on the upgraded branch, otherwise the old ones would cause problems

it complained about every single file not matching end of line rules

The files all have (and should have) LF line endings, so you probably have git changing those locally.
Anyways, I added that


ref: Update transaction status to match final protocol

schema def here: https://github.com/getsentry/semaphore/pull/326

Since nobody reviews this I'll just merge it.

Since it got merged, let's say I "approved" it 😎 .

I did reviewed it.

@untitaker will this land in SaaS soon? 😄


⬆ Update Icons: Playwright, Puppeteer(Update new Image), StoryBook, Testing-Library, React-Query, Recoil

List of Contents

Testing tools commonly used in frontend development
Libraries commonly used in frontend development
Etc...(Figma)

Testing Tools
1. Playwright

What?

An end-to-end testing tool that allows you to test all modern rendering engines, including Chromium, WebKit, and Firefox, using a single API.
It is gaining popularity due to its extended features such as auto-waiting, retry-ability, support for testing all modern rendering engines, improved test speed (through the reuse of browser contexts, parallel testing, etc.), convenient debugging tools, and support for various languages.

3. StoryBook

What?

Storybook is a tool that supports a component-level UI development environment. With Storybook, you can proceed with component-level UI development independently of the actual web application environment. Additionally, it can also be used as a documentation tool for components.

4. Testing-Library

What?

React Testing Library is a collection of tools that facilitate the testing of React components without relying on the details of their implementation. This approach makes refactoring easier and enables best practices for accessibility.

Libraries
5. React-Query

What?

React Query is a library that supports fetching, caching, and synchronization with server data. It eliminates the need for complex and verbose code, allowing for simple and intuitive API usage within React Components.

6. Recoil

What?

Recoil is one of the many global state management libraries available for React projects. Using Recoil, you can create a data-flow graph that flows from atoms (shared states) through selectors (pure functions) to React components. Here, atoms are units of state that components can subscribe to, while selectors transform this state synchronously or asynchronously.

Etc

This is a Figma file containing images of the icons I have worked on.

Icon Images Figma File

Hello :) @LelouchFR
PTAL when you have time 🙇🏻♂

@osohyun0224 Plz make the icon names lowercase
for example: ReactQuery-Dark.svg -> reactquery-dark.svg

@LelouchFR Oh you so fast merged! But I keep update README.md HAHA😆
I made new PR ~! Thank you for merged it!🫶🏻

@LelouchFR Oh you so fast merged! But I keep update README.md HAHA😆 I made new PR ~! Thank you for merged it!🫶🏻

No problem, I'm working on fixing it myself ;) thank you again!


CI enhancements

Add Rpi and Oracle/CentOS/RHEL builds to Travis

use docker images
use qemu for Rpi (docker w qemu saves messing about with sysroot for cross-compilation)
possibly cache docker images if installing build tools/deps slow

Add 32bit linux builds using -m32 and multilib
Caching for incremental builds (same approach on Travis and Appveyor)

cache source and build dirs, then git pull from the fresh clone - this should result in incr. build
do a full build from fresh clone on tagged commits

Caching for homebrew packages on OSX

this should speed things up a lot because I think homebrew builds from source

https://ownyourbits.com/2018/06/27/running-and-building-arm-docker-containers-in-x86/

All builds working
- had to cross compile for rpi because qemu was too slow
- had to cross compile for OEL because v6 is too old to install build libs natively
No caching yet for incremental builds


Add kokoro AWS integration and corresponding test jobs.

Implemented by @amidlash and @jtattermusch. The code in the source branch has already been reviewed (by @amidlash or @jtattermusch) and now I'm importing the implementation into upstream/master.
The PR adds test jobs for bazel C/C++, ruby, php, csharp and python that run on real ARM64 hardware.
See go/kokoro-on-aws for internal docs.

Easy CLA is ok since all authors are googlers.

@amidlash can you please try to resolve the EasyCLA check failures (I think you need to associate @google.com email with your github account so that EasyCLA can tell you're a googler).

adding a comment to bump the easyCLA bot.

@googlebot please rescan

I tried to rebase but EasyCLA is still reporting a problem.


update install docs; silence doc build warning

closes #434

circle fails with
E: Failed to fetch http://deb.debian.org/debian/pool/main/libs/libsndfile/libsndfile1_1.0.28-6_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]

Probably needs a sudo apt update before any sudo apt install call (and apt-get should be changed to apt if it hasn't already)

notes for my future self: CI failures now are this:
___________ ERROR collecting expyfun/_sound_controllers/_pyglet.py ____________
C:\Users\VssAdministrator\AppData\Roaming\Python\Python37\site-packages\pyglet\media\codecs\wmf.py:836: in __init__
    ole32.CoInitializeEx(None, COINIT_MULTITHREADED)
_ctypes/callproc.c:935: in GetResult
    ???
E   OSError: [WinError -2147417850] Cannot change thread mode after it is set

I did some poking around and it looks like current main of pyglet catches this error and converts it to a warning:
https://github.com/pyglet/pyglet/blob/d1876a9415bb51a59c2248f7d5ecd74b81d9638b/pyglet/media/codecs/wmf.py#L834-L838
added here (april 2020) and it should be in pyglet 1.5.4 and above (windows py37 CI installs pyglet 1.5.21 so I'm confused as to why we're seeing this error)

Thanks @drammock !