Required Code Snippet - Get Share to Teams for Education Document

Type of issue
Missing information
Feedback
Hi
Regarding document  : Share to Teams from web apps - Teams | Microsoft Learn
We have tested as per the document, One scenario is working fine and able to see the output.

Share to Teams for Education
Share to Teams for Education is not working as expected after adding html attributes to a given span as mentioned in doc, the behavior is same as first Scenario.
In the doc it is given shareToMicrosoftTeams.renderButtons(options) but not given proper code snippet of this method how and where to use this line of code.
Can you please confirm from Doc-Team/Engg-Team and provide us code snippet to get expected output?
Thanks !!
Page URL
https://review.learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/share-to-teams-from-web-apps?branch=pr-en-us-10484
Content source URL
https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
Author
@surbhigupta
Document Id
9cb013cb-3a19-2142-5286-692ff9b32ea6

@ChetanSharma-msft Do we have any updates w.r.t the issue?

@Mohammed-MSFT was able to test Share to Teams for Education successfully.


Popover incorrect positioning on Android

Current Behavior
When the position is set to bottom, the popover content overlaps with the popover trigger. The popover content is always positioned higher than expected.

Expected Behavior
The popover can be correctly positioned.
Tamagui Version
1.105.5

Platform (Web, iOS, Android)
Android

Reproduction
https://github.com/LiZhequ/tamagui-popover-position

import { Popover, Text, View, YStack } from 'tamagui'

export default function Index() {
  return (
    <YStack flex={1} ai={'center'} jc={'center'}>
      <Popover allowFlip placement="top">
        <Popover.Trigger asChild>
          <View w={100} h={100} bg={'red'}>
            <Text>Trigger</Text>
          </View>
        </Popover.Trigger>
        <Popover.Content
          bg={'green'}
          borderWidth={1}
          borderColor="$borderColor"
        >
          <View h={100} w={100} bg={'yellow'}>
            <Text>Content</Text>
          </View>
        </Popover.Content>
      </Popover>
    </YStack>
  )
}

### System Info

```markdown
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 1.69 GB / 15.34 GB
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.0.2 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.7.6 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (126.0.2592.87)
    Internet Explorer: 11.0.19041.1202
  npmPackages:
    @babel/core: ^7.24.6 => 7.24.6
    @expo/metro-config: ~0.18.4 => 0.18.4
    @expo/metro-runtime: ~3.2.1 => 3.2.1
    @react-navigation/native: ^6.1.17 => 6.1.17
    @tamagui/babel-plugin: ^1.105.5 => 1.105.5
    @tamagui/config: ^1.105.5 => 1.105.5
    @tamagui/lucide-icons: ^1.105.5 => 1.105.5
    @tamagui/metro-plugin: ^1.105.5 => 1.105.5
    @tamagui/toast: ^1.105.5 => 1.105.5
    @types/react: ~18.2.79 => 18.2.79
    @types/react-native: ^0.73.0 => 0.73.0
    babel-preset-expo: ^11.0.6 => 11.0.6
    burnt: ^0.12.2 => 0.12.2
    expo: ~51.0.9 => 51.0.9
    expo-font: ~12.0.6 => 12.0.6
    expo-linking: ~6.3.1 => 6.3.1
    expo-router: ~3.5.15 => 3.5.15
    expo-splash-screen: ~0.27.4 => 0.27.4
    expo-status-bar: ^1.12.1 => 1.12.1
    expo-system-ui: ~3.0.4 => 3.0.4
    expo-web-browser: ~13.0.3 => 13.0.3
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    react-native: 0.74.1 => 0.74.1
    react-native-reanimated: ~3.10.1 => 3.10.1
    react-native-safe-area-context: 4.10.1 => 4.10.1
    react-native-screens: ~3.31.1 => 3.31.1
    react-native-svg: 15.2.0 => 15.2.0
    react-native-web: ^0.19.12 => 0.19.12
    tamagui: ^1.105.5 => 1.105.5
    typescript: ^5.5.2 => 5.5.2

https://github.com/floating-ui/floating-ui/issues/2904
https://github.com/facebook/react-native/issues/19497
when sameScrollView is true,  floatingui use 'measure ' method and reference's coord always return 0.
when sameScrollView is false, which is same as tamagui used, floatingui  use ’measureInWindow‘ method, but the y coord is wrong.


Different results with MPI when halo larger than rank domain

the following results produces different results with and without mpi with more than 4 workers
import numpy as np
from devito import Grid, Function, TimeFunction, Eq, Operator, norm

udata = np.arange(300).reshape(3, 10, 10)

grid = Grid((10, 10))

u = TimeFunction(name="u", grid=grid, time_order=2, space_order=8)
u.data[:] = udata
w = Function(name="w", grid=grid, space_order=8)

Operator(Eq(w, u.dx))(time_M=5)

print(norm(w))

I think the above behaviour is expected. You start to see errors in cases where you have inhalo's hitting outhalo's which should be triggering a warning. But when I wrote the code I missed this case. See: https://github.com/devitocodes/devito/blob/62d14742987b6f8fc262eda54fda39ecdcbffee6/devito/types/dense.py#L319
Will correct and update the warning when I get the chance. But I don't think this is an MFE for the original problem.
Also, can we double check whether the problem is with 'MPI' workings or with the norm? @jkwashbourne, if you get the chance, you could gather all the data on a single rank and hit it with np.linalg.norm to see what you get? When you get around to this, hit me up on slack if you need and I can give you some code for the gather.

I found the problem, unrelated to this. Tag this issue when you update the warning

added further warning in #1370 , closing this


Total disposal proceeds excludes fees

TL;DR: it looks to me like fees are removed from the disposal proceeds instead of added to allowable costs. I would've thought they should be added to allowable costs.
Reading the Capital gains summary notes (2024) from http://www.gov.uk/government/publications/self-assessment-capital-gains-summary-sa108 (see quote below), I get the impression that the Total disposal proceeds shown in the report should be the num_shares * price (or better, amount + fees) before the fees are taken off, and the transaction-specific fees should be part of the costs. The calculator seems to parse the amount as the amount after fees have been taken off (see e.g. https://github.com/KapJI/capital-gains-calculator/blob/main/cgt_calc/parsers/mssb.py#L161-L162) and then sum those to calculate the Total disposal proceeds (https://github.com/KapJI/capital-gains-calculator/blob/main/cgt_calc/main.py#L307).

Sale or disposal proceeds
Proceeds may include:

cash, payable now or in the future, or anything that can be turned into cash, unless it’s taxable as income
the market value of an asset you were given in exchange for the asset you disposed of
the value of a right to receive future payments where you do not know the amount of the payment at the time you sold it

Sometimes you need to use the market value of the asset instead of the sale or purchase price.

Allowable costs
For Capital Gains Tax purposes, you deduct your costs to work out the gain or loss on the sale or disposal of an asset. Only some costs are allowable. These include:

the price paid to buy the asset
the costs of any improvements made to your asset – but they must be reflected in the asset when you dispose of it
incidental costs of acquiring or disposing of the asset, such as Stamp Duty or Stamp Duty Land Tax

...

What do others think? Did I misunderstand something?

I believe it should include the fees. (which are part of the allowable costs too)
Sources:

CG15250 https://www.gov.uk/hmrc-internal-manuals/capital-gains-manual/cg15250
TCGA92/S38 https://www.legislation.gov.uk/ukpga/1992/12/section/38


Artifact section missing in the UI for the playground 2.1 branch

Hi,
I have followed https://www.ververica.com/blog/analyzing-github-activity-with-ververica-platform-community-edition but when I open the Ververica platform UI the "Artifacts" sections isn't displayed.
Could it be that the blob storage hasn't been registered properly?
Im on windows with minikube and all the pods starts correctly.
Any advice would be appreciated.
Thanks,
Regards
Dan

Hi Dan,
thank you for trying out Ververica Platform CE. Did you change any of the values files before installation, or did you simply run setup.sh?
Could you send me the content of http:///ui/config.json as well as the output of kubectl -n vvp get configmaps vvp-ververica-platform-config -o yaml?
Cheers,
Konstantin

Hi and thanks for your reply. Ive removed minikube and installed everything again but still experience this problem.
http:///ui/config.json doesnt work and below is the output from the kubectl.
Thanks again,
/Dan
PS C:\Windows\system32> kubectl -n vvp get configmaps vvp-ververica-platform-config -o yaml
apiVersion: v1
data:
application-prod-user.yaml: |
spring:
datasource:
url: jdbc:sqlite:/vvp/data/vvp.db?journal_mode=WAL&synchronous=FULL&busy_timeout=10000
vvp:
appmanager:
cluster:
kubernetes.artifact-fetcher.image-registry: registry.ververica.com/v2.1
kubernetes.artifact-fetcher.image-repository: vvp-artifact-fetcher
kubernetes.artifact-fetcher.image-tag: 2.1.1
auth:
enabled: false
blobStorage:
baseUri: s3://vvp
s3:
endpoint: http://minio.vvp.svc:9000
flinkDeploymentDefaults:
registry: registry.ververica.com/v2.1
repository: flink
globalDeploymentDefaults: |
spec:
state: RUNNING
template:
spec:
resources:
jobmanager:
cpu: 0.5
memory: 1G
taskmanager:
cpu: 0.5
memory: 1G
flinkConfiguration:
state.backend: filesystem
taskmanager.memory.managed.fraction: 0.0 # no managed memory needed for filesystem statebackend
high-availability: vvp-kubernetes
metrics.reporter.prom.class: org.apache.flink.metrics.prometheus.PrometheusReporter
kubernetes:
pods:
annotations:
prometheus.io/port: '9249'
prometheus.io/scrape: 'true'
license:
acceptCommunityEditionLicense: true
persistence:
type: local
platformKubernetesNamespace: vvp
registry: registry.ververica.com/v2.1
ui:
linkTemplates:
metrics: http://localhost:3000/d/77Nra5XZz/flink-dashboard?var-deploymentId=<%=
deploymentId %>
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: vvp
meta.helm.sh/release-namespace: vvp
creationTimestamp: "2020-07-04T12:58:25Z"
labels:
app.kubernetes.io/managed-by: Helm
chart: ververica-platform-4.1.1
component: ververica-platform
heritage: Helm
release: vvp
system: ververica-platform
managedFields:

apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:data:
.: {}
f:application-prod-user.yaml: {}
f:metadata:
f:annotations:
.: {}
f:meta.helm.sh/release-name: {}
f:meta.helm.sh/release-namespace: {}
f:labels:
.: {}
f:app.kubernetes.io/managed-by: {}
f:chart: {}
f:component: {}
f:heritage: {}
f:release: {}
f:system: {}
manager: Go-http-client
operation: Update
time: "2020-07-04T12:58:25Z"
name: vvp-ververica-platform-config
namespace: vvp
resourceVersion: "816"
selfLink: /api/v1/namespaces/vvp/configmaps/vvp-ververica-platform-config
uid: c5459f9d-fee8-4ae3-86eb-7db88ad44f41

Sorry for the late reply. Github swallowed part of the URL there. I meant http://<vvp-host>:<port>/ui/config.json. The configuration looks good otherwise.

No worries! Here is the output from ui:
{"version":"2.1","server":{"endpoint":"/api/v1"},"platformKubernetesNamespace":"vvp","refreshMs":5000,"messageHideMs":3000,"dateFormat":"YYYY-MM-DD, HH:mm:ss","linkTemplates":{"flinkUi":"/flink-ui/v1/<%= namespace %>/jobs/<%= jobId %>/","metrics":"http://localhost:3000/d/77Nra5XZz/flink-dashboard?var-deploymentId=<%= deploymentId %>"},"licenseInformation":{"licensedTo":null,"isCommunityEdition":true,"expiresOn":null,"cpuQuotaType":"UNLIMITED","cpuQuota":null,"isTrial":null,"isNotForResale":null},"flinkVersions":["1.8","1.9","1.10"],"flinkImageTags":["1.10.0-stream1-scala_2.12","1.10.1-stream1-scala_2.12","1.8.2-stream1-scala_2.11","1.8.3-stream3-scala_2.11","1.9.0-stream1-scala_2.11","1.9.0-stream1-scala_2.12","1.9.1-stream2-scala_2.12","1.9.2-stream2-scala_2.12","1.9.3-stream1-scala_2.12"],"components":{"artifacts":{"enabled":true},"blobStorage":{"baseUri":"s3://vvp"},"logging":{"enabled":false},"metrics":{"enabled":true},"sql":{"enabled":false}},"extraConfig":null}

Ok, it seems that the side bar does not behave well with your screen resolution. If you scroll in the small section of the navigation bar that is scrollable, you should be able to find the "Artifacts" entry. We will improve the side bar in our upcoming release.

Ok thanks. Now I found the scrollbar also so I can continue with the series :-)

Great. Let us know if you run into problems.


Fix frame range attributes for instances + validations

Changelog Description

Discard 'step' for pointcache/animation since it did not influence the output alembic at all.
Default the frame range to current context task entity instead of current scene
Add handle start and handle end attributes to be explicit about that, defaulting to current task attribs.
Actually fix passing along the start and end frame to the Alembic export from creator to instance data.
Add support for validating frame range against the instance's task/folder entity for review, pointcache, animation, etc. + support repair method for those.
Remove redundant 'scene overrides' that tried to use that to affect what the alembic export did - but it didn't do much, and the export command has dedicated arguments for that.

Additional info
I have no idea whether the step attribute does work for the other export methods, e.g. FBX or alike but we may need to double check that to see whether the step attribute is relevant anywhere.
Sorry for the big changes, but this really was way easier to fix when combining them.
Testing notes:
The following product types should adhere to the frame ranges specified on the instances, be validated against the frame range (optionally) and when invalidated should allow repair to work.

[x] animation
[x] camera
[x] pointcache
[ ] render
[x] review

@LiborBatek any chance you can test the render?

Thanks @LiborBatek - should be fixed now.
There was definitely a lot broken since the merge of #1


lock should expire automaticaly if lock owner gone

Currently if redisson client was shutdown abnormally locks created by this client will  remain forever.
This solution will create all locks as keys with expiration time set in redis. I'm not sure if this is best solution and what to do with lock() - lock(time, unit) - lock() sequences but it works for me.
Any suggestions or changes are welcome.

Are there any thoughts or alternative solutions?

i submitted a pull request that could help you out

@JacobJohansen Sorry but I don't understand how ttl check can help.
TTLs for locks doesn't looks like good idea in most cases. If lock set with ttl then application should make sure not spend too much time inside locked section or periodically extend lock's ttl.

Isn't this done automatically as you set Expiration directly on key of the lock which is hold in Redis?

What if you set expiration time 1 minute and operation under lock will last longer?

It's rare cases where you will need expiration time more than eg. 30 sec but yes I agree.

closed as fixed in #176


How to Add href or Link to console.message

Thanks a lot for this console script, but I have an issue.
Anytime I add  .element('feedback') to console.message(). It still repeat the same way in the console. How do add a link to it
below is my code:
console.message()
.span({ fontWeight: 'normal'})
.text('Please don't copy-paste something or hack here!', {background: 'red', color: 'white',fontWeight: 'bold',fontSize: 15 })
.element('feedback')
.spanEnd()
.print();

.element() method expects HTMLElement instance. You could do console.message().element(document.querySelector('CSS selector here')).print()
What do you mean "add a link to it"?

What I meant by add a link is: an hyperlink or href

Unfortunately, this isn't supported by the browser console APIs. I can make a utility function that only colors the link but it still won't be possible to click it. Closing this.
Sorry for the delayed answer 😂. I didn't commit to this repo for the past 8 years. Now I've started working on it all over again.


CyberRT topics to ROS and vice versa

I am working on an external component that has ROS interface. I would like to connect Apollo cyber topics into ROS topics. Is there a way to convert CyberRT topics and messages into ROS topics/messages?

maybe you can try apollo_ros_bridge

maybe you can try apollo_ros_bridge

maybe you can try apollo_ros_bridge

apollo_ros_bridge, this project is on github. but It's not offical. maybe you can try.

Hi @Prj1508,
Have you tried if apollo_ros_bridge is working successfully or have you found another solution?
@lx18233184051 and @SeasoulChris
I am planning to use the other simulator for my project ( VIRES VTD) not LGSVL.  As far as I know, there is no
Cyber RT integration available yet. VIRES VTD offers ROS integration and API for C ++ Integration.
There are bridges connection between LGSVL to Apollo and Carla to Apollo. Is there any chance to
modify these bridges to use them for VIRES VTD to Apollo? If you have knowledge in this area please give
me some suggestions. I am totally new to this area and just start my project.
Thank you.

Yes, the bridge is working fine. If your simulator has ROS interface, then Apollo+  apollo_ros_bridge should do it for you I think. Any specific reason you are not using LGSVL or Carla? Just curious
Sent from my iPhone

On Feb 23, 2021, at 07:17, Thinsheep<EMAIL_ADDRESS>wrote:

Hi @Prj1508,
Have you tried if apollo_ros_bridge is working successfully or have you found another solution?
@lx18233184051 and @SeasoulChris
I am planning to use the other simulator for my project ( VIRES VTD) not LGSVL. As far as I know, there is no
Cyber RT integration available yet. VIRES VTD offers ROS integration and API for C ++ Integration.
There are bridges connection between LGSVL to Apollo and Carla to Apollo. Is there any chance to
modify these bridges to use them for VIRES VTD to Apollo? If you have knowledge in this area please give
me some suggestions. I am totally new to this area and just start my project.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @Prj1508
Thanks for your reply, actually, we already have LGSVL, we just want to try a commercial simulator for the comparison. We are developing the simulation testing technique.

Thank you.
It is very nice. Have you installed Apollo 6.0 on your PC? I am currently looking for a PC to install Apollo 6.0 and Simulator. I am going to go with GPU RTX 3090/3080 but I have read the information that "NVIDIA Turing GPU (2080/2080 Ti) is strongly recommended". Do you know if RTX 3090/3080 (faster and not much more expensive but not Turing GPU) is ok to run Apollo 6.0?

Hi Prj1508,
I need Vires VTD communicating with Apollo 6.0. I need to build a ROS interface for Vires VTD as they only have an example for 1 signal not completed package (I do not know if Vires VTD was developed for Autonomous software platform because they do not build the communication bridge with current popular AV stacks). I have a few questions below if you have experience with this please share some information.

To build the interface for Vires VTD, I need to know which message VTD will need to provide-publish to and which message VTD can get-subscribe from Apollo. VTD will send sensor data and get the AV commands (accelerator, brake, throttle). How can I get the full list of sensor data and AV commands so I do not miss any interface?

Is apollo_ros_bridge is the completed package that I can directly use for Apollo 6.0? because they have only some ROS topics like Path, Odometry, PointCloud2 and IMU but not all. I also do not see if they publish AV commands like accelerator, brake and throttle.

Can Vires VTD interface and apollo_ros_bridge can publish/subcribe data directly or do I have to build something to establish the communication?

Hi @Prj1508 ,
I am looking for a tutor for this topic. If you are available please drop me an email at<EMAIL_ADDRESS>we can discuss further :).

Yes, the bridge is working fine. If your simulator has ROS interface, then Apollo+ apollo_ros_bridge should do it for you I think. Any specific reason you are not using LGSVL or Carla? Just curious
…

Hi @Prj1508
I will be glad if you can help me!
I'm trying to figure it out with apollo_ros_bridge.
https://github.com/AuroAi/apollo_ros_bridge
But when I run the bridge in docker, then the frequency of received channels in apollo_ros_bridge does not match the frequency of messages in Apollo.
I am attaching a photo showing the frequencies.
Maybe you have an idea how to fix this ??

Hi @AlexandrZabolotny
apollo_ros_bridge was developed for Apollo 3.5. Do you know any chance to use this apollo_ros_bridge for Apollo 6.0?

Hi @AlexandrZabolotny
apollo_ros_bridge was developed for Apollo 3.5. Do you know any chance to use this apollo_ros_bridge for Apollo 6.0?

bridge also works in version 6

Hi @AlexandrZabolotny
apollo_ros_bridge was developed for Apollo 3.5. Do you know any chance to use this apollo_ros_bridge for Apollo 6.0?

bridge also works in version 6

Thanks for your information.
Importing these three packages to Apollo 6.0 Master is the right idea to run the bridge in version 6.0?

Hi @AlexandrZabolotny
apollo_ros_bridge was developed for Apollo 3.5. Do you know any chance to use this apollo_ros_bridge for Apollo 6.0?

bridge also works in version 6

Thanks for your information.
Importing these three packages to Apollo 6.0 Master is the right idea to run the bridge in version 6.0?

I use Apollo pre6

@AlexandrZabolotny
Sorry, I am lacking knowledge in this. This bridge was built in Apollo 3.5. How did you transfer it into pre6?

Hi @AlexandrZabolotny
apollo_ros_bridge was developed for Apollo 3.5. Do you know any chance to use this apollo_ros_bridge for Apollo 6.0?

bridge also works in version 6

@AlexandrZabolotny, hello.
Maybe you know, does apollo_ros_bridge work with Apollo ver 8.0?


use actual list of grants instead of "ALL"

some managed database providers (like mariadb-rds) do not allow to set GRANT ALL for security reasons and require a specific list of Grants.
The provided Grants are basically all permissions a user can have, see https://mariadb.com/kb/en/grant/#global-privileges

@shreddedbacon
mhh, good question. From a technical point of view GRANT ALL and GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER is exactly the same. So it should not cause any issues for other clusters.
I'm happy to do the mariadb-rds type approach, I just feel this is something that the operator should handle automatically?

@shreddedbacon
mhh, good question. From a technical point of view GRANT ALL and GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER is exactly the same. So it should not cause any issues for other clusters.
I'm happy to do the mariadb-rds type approach, I just feel this is something that the operator should handle automatically?

Easy, I'll merge this now then.

Easy, I'll merge this now then.


Getting: Missing AmplifyAppId in amplify-meta.json error when trying to "amplify console api"

I created a new react-app
Modified its schema (its a simple blog app)
did amplify add api followed by amplify push
Now when I am trying to open this api using amplify console api, I am getting this error " Missing AmplifyAppId in amplify-meta.json".
Also, in my account I had created another api(s) and dynamodb table(s) in past, but there is literally nothing in my account! Why did this happened and how can I rectify this situation and the error?
Please provide your suggestions.
Thanks,

Hey @spharsh :wave: can you share the steps you took to set up the Amplify project?

@spharsh Can you check if you have >= 25 app created on the Amplify Console in your AWS account?

Hi,
so I started with npx create-react-app app-name
amplify init
amplify add api (changed my graphql schema and it compiled successfully)
amplify push
Now when I am doing this amplify console api, I am getting this error.

@ammarkarachi so this is weird too. I am pretty sure I had, if not 25, atleast 20 apps (I am in learning phase) but now there is not a single app!!!
Where did they go?

@ammarkarachi okay my bad, I was in a different region and yes there are exactly 25 apps.

Yes, there is an app limit on Amplify Console and it's always good practice to clean up test app so as not to incur any charges.

Okay, I am doing this now, and hopefully, after this, I won't be getting that error.
Thank you so much!

I will close this issue for now let me know if you need any additional help


Use type-safe 'union type' trick

To model <input> element value-related attributes.

This is working, here's an example type error:
  We've found a bug for you!
  /Users/yawar/src/t2/src/Elem.re 3:40-41

  1 │ module Input = ReactDOMRe.Input;
  2 │
  3 │ let elem = <input type_="number" min={0->Input.int} max={""->Input.stri
      ng} />;

  This has type:
    Input.t(int) (defined as ReactDOMRe.Input.t(int))
  But somewhere wanted:
    ReactDOMRe.Input.t(string)

  The incompatible parts:
    int
    vs
    string

You can convert a int to a string with string_of_int.


support for example pipeline

Codecov Report

Merging #210 (eed575d) into main (ca8da18) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #210   +/-   ##
=======================================
  Coverage   25.13%   25.13%
=======================================
  Files           1        1
  Lines         187      187
=======================================
  Hits           47       47
  Misses        134      134
  Partials        6        6

Continue to review full report at Codecov.

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

/e2e


instructions to reproduce the dataset generation and fine-tuning steps

the current readme has instructions for reproducing the evaluation results and how to run inference.
I cannot find instructions to reproduce the dataset generation and fine-tuning steps.  Please add them when you are ready.
Another thing is to make sure all the steps can be done on NERSC's perlmutter. I need to run experiments on that machine.
Please let me know when you have something for me to try on perlmutter.
Thanks.

OKOK.

@bin123apple a reminder for this ticket.  The way we generate the training dataset is a key contribution of the paper. This repos should let people reproduce the dataset generation process.

OKOK, I am modifying some dataset cleaning code, after that is finished, I will upload the all the things.

Just uploading the dataset generation code and the dataset. The detailed steps are in README/Dataset Generation.

I can now run the data generation step, after fixing various minor things in the code.


install_dependencies hangs while installing python-pip

This is @robertecurtin posting from a friend's laptop
It hangs with
troy@Carol:~/git/mtg-life-tracker-esp8266$ espeon install_dependencies
E: Package 'python-pip' has no installation candidate

This is on ubuntu 20.04.4
Running sudo apt-get install python-pip || sudo apt-get install python3-pip manually seems to work just fine, and it started working after we manually installed it

Is there a chance it's waiting for you to enter your password?

No, it had already done the sudo prompt

Realistically I should probably just remove the python2 path.

Can you give v1.12-0 (the latest on Luarocks) a try?


[Bug] On my terramaster nas I have to delete container, image and config directory

Current Behavior
Hi of all your docker apps I tried, they work only until I reboot the nas. I can also start/stop them and it's working but after a full reboot  I have to delete the container, image and config directory and recreate. I tought about permissions but everything I tried didn't work. I attach the container log after a full system reboot.
Expected Behavior
No response
Steps To Reproduce
No response
Environment

OS: linux/amd64

Container creation
standard -v flags. Tried different uid/gid (also as root) and umask (000). Same behaviour.

No response

Looks like the image gets modified.  At least, permissions on files have changed.
Can you provide more details about the file system on which the image is stored ?

@LiskoFINAL, do you have any update on this ?
Closing this issue for now.  Please re-open if needed.


parseBody() replaces Session parameters with form parameters in method POST

When serving a POST from such a form (enctype being the default application/x-www-form-urlencoded):
<form method="post" action="dopost?file=afile_somewhere">
    <input type="text" name="file" value="/tmp/foo.txt" />
    <input type="submit" />
</form>

public Response serve(IHTTPSession session) {
    System.out.println("Before: "+session.getParms());
    if (session.getMethod() == Method.POST) {
        Map<String,String> fics = new HashMap<>();
        parseBody(fics);
        System.out.println("After: "+session.getParms());
    }
}

will show:

Before: {file=afile_somewhere}
After: {file=/tmp/foo.txt}

That is because in parseBody(), we call decodeParms(postLine, this.parms); if content type is application/x-www-form-urlencoded (which is the default for <form> elements, see NanoHTTPD.java:1179) which overwrites URL parameters.
I suggest passing an extra Map<String,String> to parseBody(), which would receive those parameters. I can provide a pull-request.
It is not critical as the workaround is easy: create a local copy of session.getParms() before calling parseBody().

That explains #363 I'll be marking as duplicate and closing as this one explains everything better.

Marked as in-progress because of #366


wrap k3s with slirp4netns ?

Describe the bug
This is my first try with k3s and I hit:
❯ k3s server --rootless
WARN[0000] Cannot set cgroup2 evacuation, make sure to run k3s as a systemd unit
FATA[0000] exec: "slirp4netns": executable file not found in $PATH

I will try the module but it doesn't seem to wrap it either.
This is on unstable
cc @euank @yajo

I never used it rootless, but indeed the request makes sense.


Type class for probe results

To unify results.
Should contain:

probe name
results as they are
function to serialize the results*

* - optional, res.toString() as default

Naming the package, some options

detail (noun)
feature (noun)
trait (noun)

characteristic

quirk (noun)

an individual peculiarity of character; mannerism or foible

Follow #23


Don't include the gz/math.hh header from library code

🦟 Bug fix
Summary
Don't include the gz/math.hh header from library code. Using overly-broad include statements leads to slower builds and bloated object code. This commit swaps it out the gz/math.hh "everything" header for more targets files, instead.
Checklist

[x] Signed all commits for DCO
[x] Added tests (n/a)
[x] Updated documentation (n/a)
[x] Updated migration guide (n/a)
[x] Consider updating Python bindings (n/a)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

(There are some build errors; I'll work on resolving those locally now.)


Fixing redundant match alternative.

Got a build error which seems to be due to an error in translation from French to English.
This change seems to fix it, but as I am new to Lean, I am not fully sure I am doing the right thing, apologies if this is creating noise.

Sorry I did’t see this before Pierre Bousquet draw my attention to his PR who was conflicting this. So I fixed the issue on master. Thanks for your help!

No problem, and I see that Pierre did make the whole thing compatible
with the latest version, that's great!
On Tue, Mar 12, 2024 at 4:30 PM Patrick Massot @.***> wrote:

Sorry I did’t see this before Pierre Bousquet draw my attention to his PR who was conflicting this. So I fixed the issue on master. Thanks for your help!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Space comsumption?

The benchmark of Oxygraph looks promising, but there is no information about
space consumption.
Is it possible to report the space consumption between blazegraph, graphdb, jena and
Virrtuoso??

Thank you for having a look at Oxigraph! Indeed having such a benchmark would be interesting. I have not done any work to optimize the disk usage and it's quite bad at the moment. I plan to tackle that in the next few releases.


500/503 HttpException subclasses

@danielfinke which APIs return a 500 not_found?  I suspect those are bugs :)

@k-anderson it looks like the only API to behave that way was GET to phone_numbers when the number didn't exist. I compared the response from our 3.22 cluster and our 4.1 cluster. The issue must have been patched at some point. 3.22 gives a 500 not_found, 4.1 as expected returns a 404.
I guess the decision here is whether to bother supporting the 3.22 response. If not, let me know, I'll remove that part of the PR.

We don't care about the 3.22 compatibility so you can remove that part from this PR and I will merge this. Also note, I merged the patch change PR and made a tag 2.0.1 which includes this non-backwards compatible change.

@swysor Alright, I have removed the 3.22 compatibility code. Thanks for tackling these PRs!

Thanks for all the great contributions. Keep em coming!


Where can I upload the PDF files for knowledge?

i wanna help please.

Please us the Discussions or Discord channel for this as it is not a bug.
documentation : https://docs.openwebui.com/features/workspace/knowledge
you can go in the Workspace tab, and then in "Konwledge" section and create a knowledge to upload your files

Thanks so much bro🌹


ParseUser not supporting custom property ParseGeoPoint

Sample code:
var user = await ParseUser.currentUser();
if (user != null) {
    var location = ParseGeoPoint(latitude: 48.858372, longitude: 2.294481);
    user.set<ParseGeoPoint>('location', location);
    var response = await user.save();
}

.save() throws exception:
Exception has occurred.
JsonUnsupportedObjectError (Converting object to an encodable object failed: Instance of 'ParseGeoPoint')

Edit: as of v1.0.16

Very strange. for me it's working.
dependencies:
  flutter:
    sdk: flutter
  parse_server_sdk: ^1.0.16

My code:
  var parseObject = ParseObject("TestAPI", debug: true);
  parseObject.set<String>("stringName", "Name");
  parseObject.set<double>("doubleNumber", 1.5);
  parseObject.set<int>("intNumber", 0);
  parseObject.set<bool>("boolFound", true);
  parseObject.set<List<String>>("listString", ["a", "b", "c", "d"]);
  parseObject.set<List<int>>("listNumber", [0, 1]);
  parseObject.set<DateTime>("dateTest", DateTime.now());
  parseObject.set<Map<String, dynamic>>(
      "jsonTest", {"field1": "value1", "field2": "value2"});
  parseObject.setIncrement("intNumber2", 2);
  parseObject.setDecrement("intNumber3", 2);
  parseObject.set<ParseGeoPoint>(
      "location", ParseGeoPoint(latitude: -20.2523818, longitude: -40.2665611));
  parseObject.set<ParseUser>("user", user);
  parseObject.set<ParseObject>(
      "produto", ParseObject("Produto")..set("objectId", "E7o3gkZD2T"));
  parseObject.set<List<ParseUser>>("users", [user, user]);
  parseObject.set<ParseFile>("fileImage", parseFile);
  parseObject.set<List<ParseFile>>("fileImages", [parseFile, parseFile]);

  apiResponse = await parseObject.save();

Response:
API Response (TestAPI : ParseApiRQ.create) :
Status Code: 201
Payload: {"className":"TestAPI","objectId":"h0Q91oPnIX","createdAt":"2019-03-29T17:51:08.028Z","stringName":"Name","doubleNumber":1.5,"intNumber":0,"boolFound":true,"listString":["a","b","c","d"],"listNumber":[0,1],"dateTest":{"__type":"Date","iso":"2019-03-29T17:51:07.393Z"},"jsonTest":{"field1":"value1","field2":"value2"},"intNumber2":2,"intNumber3":-2,"location":{"__type":"GeoPoint","latitude":-20.2523818,"longitude":-40.2665611},"user":{"__type":"Pointer","className":"_User","objectId":"0C6ptX39c8"},"produto":{"__type":"Pointer","className":"Produto","objectId":"E7o3gkZD2T"},"users":[{"__type":"Pointer","className":"_User","objectId":"0C6ptX39c8"},{"__type":"Pointer","className":"_User","objectId":"0C6ptX39c8"}],"fileImage":{"__type":"File","name":"6fb8ec5b4f0e2cc48a060b95f677126a_image.png","url":"https://api.feitoemcasaapp.com/1/files/HIn4bvCmAYvwpDmPTmRjfoSwpTPPmGsPUMKYU36Q/6fb8ec5b4f0e2cc48a060b95f677126a_imag<…>

Sure, but you don’t add GeoPoint to a User object in your test case. 😉
Works fine on ParseInstallation class, and on “regular” ParseObject (and subclassed) here too.

@danibjor
OK. then the problem only occurs with class _User?

@danibjor
I found the problem, I'm going to do a PR.
@phillwiggins
Should I use which branch?

Cheers.
Please use the release/1.0.17 branch.
Thank you!
On Fri, Mar 29, 2019, 19:54 Rodrigo de Souza Marques <
<EMAIL_ADDRESS>wrote:

@danibjor https://github.com/danibjor
I found the problem, I'm going to do a PR.
@phillwiggins https://github.com/phillwiggins
Should I use which branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phillwiggins/flutter_parse_sdk/issues/142#issuecomment-478129288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHgn3pBq-3EltML6e1d50whYrQZm8LNKks5vbm9YgaJpZM4cSrxp
.

@phillwiggins
I did not have time to change the code and submit a PR.
The problem is in the save method on the line containing json.encode.
Just remove toEncodable.
Parse data types are already being handled in toJson and calling toEncodable causes error.
...
final Uri url = getSanitisedUri(_client, '$_path/$objectId');
        final String body =
            json.encode(toJson(forApiRQ: true), toEncodable: dateTimeEncoder);
...

...
final Uri url = getSanitisedUri(_client, '$_path/$objectId');
        final String body =
            json.encode(toJson(forApiRQ: true));
..

@rodrigosmarques
Good spotting. Due to ParseUser extending ParseObject, we should be fine just to use super.save(). Thank you
@danibjor
This looks to be working on branch release/1.0.17. If you have a chance and want to test this as well you can, or if you want, you can wait until the next release is created. Please let me know if you have a chance and this fixes your issue.

@phillwiggins just tested, but my app breaks on ParseInstallation if I'm switching to 1.0.17.
parse_installation.dart line 129
128: if (installationMap != null) {
129:        return ParseInstallation()..fromJson(installationMap);

Exception has occurred.
_TypeError (type 'ParseObject' is not a subtype of type 'Map<String, dynamic>')

@phillwiggins tried changing the sources manually (adding the fix pointed out) and commenting out stuff related to ParseInstallation.
Still no go - it saves, but the data is not showing up on the server.
Been digging and it seems like the data is not persisted on the GeoPoint object. I make a new GeoPoint, set it on the user and save().
ParseGeoPoint seems to be broken on 1.0.17

Created a pull request that fixes the ParseGeoPoint. Data (location prop of type GeoPoint) on the User object is now persisted on the server. https://github.com/phillwiggins/flutter_parse_sdk/pull/143

Strange that I had already hit Geopoint in branch v1.0.16.
I tested the branch 1.0.17 and ParseFile is in error.
The strange thing is that the Master code is OK and works correctly in branch v1.0.16 (last).
I think it gave some trouble in the merge.
[VERBOSE-2: ui_dart_state.cc (148)] Unhandled Exception: Stack Overflow
# 0 ParseFile.toString
../.../Objects/parse_file.dart:44
# 1 ParseFile.toString
../.../Objects/parse_file.dart:45
# 2 ParseFile.toString
../.../Objects/parse_file.dart:45
# 3 ParseFile.toString
../.../Objects/parse_file.dart:45
# 4 ParseFile.toString
../.../Objects/parse_file.dart:45
# 5 Pair <...>

There's not been much movement on this recently. Are we safe to close?

There's not been much movement on this recently. Are we safe to close?

Yes, the GeoPoint is working perfectly well, even with the _User class now!


Restrucutre /src

So the /src folder is getting a bit unwieldy. I propose we create a sub-directory called extras or something to store the non-core functionality scripts.
The idea would be the scripts recently moved into /src such as bayes.py, helpers.py, plotting.py would live in /extras as a collection of scripts that are designed to work with ∂lux but are not core and therefore not documented or tested.
Over time some of this functionality would be lifted to /src, such as a subset of the helpers.py functions as they are widely applicable to the usage of the package.
This could also be a good place to put a development.py script to place layers in development (ie not documented and tested) so that we can all have access and use consistent versions. This would be very useful for the development of the JWST models so we can put code to share without while still being flexible.

I agree, we should implement some set of sub-modules. Personally I quite like the following structure:
src/
    optics/
        wavefronts.py
        layers.py
        base.py
    statistics/
        bayes.py
        helpers.py?
    graphics/
        plotting.py

As this groups things by the functionality that they add. We would have to change the init file to:
from . import optics
from . import statistics
from . import graphics

So the import in scripts would becomes from dLux.optics import *

So I have implemented the structure I described above on the HexagonsAndHexikes branch as a demo/example. I added a src/dev/development.py as well based on @LouisDesdoigts's suggestion. I think having a dev directory even might be good because then you can have multiple files.

To keep everyone in the loop this was actually much harder than expected but I have it working on the HexagonsAndHexikes branch. The way it works is src now looks like this:
src/
    dLux/
        __init__.py
        optics/
            __init__.py
            base.py
            wavefronts.py
            propagators.py
            layers.py
        graphics/
            __init__.py
            plotting.py
        statistics/
            __init__.py
            zernike.py
            hexikes.py
            bayes.py
        utilities/
            __init__.py
            helpers.py
            models.py
        dev/
            development.py

I'm not particularly attached to this exact structure and there are many that work. The important thing is we know how to implement this. I think other structures like dLux.optics and dLux.utils been simpler and easier to use. Please respond @LouisDesdoigts and @atras2 if there are particular configurations that you want to trial. For now I will leave it as is.

As a reference for any who are interested the relevant websites is:
https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
which had a very useful guide once I took the time to read it thoroughly

Yeah so really there is a lot of overlap with all of these scripts and directories, I think any structure will ultimately be somewhat arbitrary. I think it might be work keeping the 'core' functionality directly in the /src (or /dLux) folders, and only having a /utils and /dev directories, maybe with a /models too.
dLux/
    __init__.py
    base.py
    wavefronts.py
    propagators.py
    layers.py
    coordinates.py # For paraxial coordinate grids
    transforms.py # For arcsec_to_radians, cart_to_polar, etc
    utilities/
        __init__.py
        helpers.py
        models.py
        zernike.py
        bayes.py
        plotting.py
    dev/
        development.py
        hexikes.py

This structure makes sense to me, letting us add any specific directories once there is enough of a code base to warrant it (ie splitting off into /models once we have integrated the code for making the JWST models). Let me know what you think.

That looks perfect. I will change the structure on the HexagonsAndHexikes branch. A little bit of warning, this mixes namespace packages and normal packages. I think I know how to deal with it but it might become:
src/
    __init__.py
    dLux/
        __init__.py
        base.py
        wavefronts.py
        propagators.py
        layers.py
        coordinates.py # For paraxial coordinate grids
        transforms.py # For arcsec_to_radians, cart_to_polar, etc
    utilities/
        __init__.py
        helpers.py
        models.py
        zernike.py
        bayes.py
        plotting.py
    dev/
        development.py
        hexikes.py

where the top level __ init __ file will let us import it in the same structure @LouisDesdoigts described. I will have a fiddle and hopefully it just works out of the box though.

So the extra dLux directory seems to be a requirement for setuptools. As an informal reference checkout (this)[https://stackoverflow.com/questions/59543313/pip-install-error-package-directory-does-not-exist] stack post.

This is now resolved. To clarify the changes:

src -> dLux to avoid pip calling the package src. poppy has a similar structure.
packages=["dLux", "dLux/utils"]; the packages are manually entered.
__init__.py; all functions are manually imported e.g. from .wavefronts import GaussianWavefront. This means if you add a function or class it also needs to be added to the __init__.py.

Cheers Jordan, this is great stuff.

init.py; all functions are manually imported e.g. from .wavefronts import GaussianWavefront. This means if you add a function or class it also needs to be added to the init.py.

Just curious, is this a necessary change to allow the new structure or just a 'best practice' sort of this?


helm chart: Invalid volumeTypestandard is set by default

In Kubernetes: v1.9.1
Perhaps this became a problem since a certain version of Kubernetes?
Anyway, all the statefulsets seem to fail saying:
Events:
  Type     Reason              Age               From                         Message
  ----     ------              ----              ----                         -------
  Warning  ProvisioningFailed  12s (x8 over 1m)  persistentvolume-controller  Failed to provision volume with StorageClass "ap-northeast-1a": invalid AWS VolumeType "standard"

Indeed there is no such a volume type named standard as of today in k8s aws cloudprovider.
Probably we'd better set the default to e.g. gp2?

I guess perhaps in other cloudprovider like GCE there is a volume type named such?
However, given we already have AWS AZ names in the zones property of values.yaml by default, I guess we can just default to an volume type which exists in AWS here, too.


how to override shouldOverrideUrlLoading to limit webView to single domain?

Hi,
In the default webView we can override shouldOverrideUrlLoading like this
`    @Override
public boolean shouldOverrideUrlLoading(WebView view, String url) {
if (Uri.parse(url).getHost().endsWith("doblist.com")) {
return false;
}
    Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(url));
    view.getContext().startActivity(intent);
    return true;
}

`
to open external links in the default browser.
I tried this with addPermittedHostname{"my-site.com") but it handles my site's sub folders as external links.
it opens my-site.com/forum in a new tab or browser.
How to solve this?

Thanks for your report!
Can you try
compile 'com.github.delight-im:Android-AdvancedWebView:2bd3e0534c36c5c046e5af6c039ce35eeb2addfb'

instead of
compile 'com.github.delight-im:Android-AdvancedWebView:v2.1.0'

please? Does this help?

@mwaclawek  This solved the problem but is it save to use this version and publish the app on the store?

Thanks, great to hear that it works!
Yes, that should be safe. Nevertheless, there's now a new release that you can use:
compile 'com.github.delight-im:Android-AdvancedWebView:v2.1.1'

By the way, once you compiled your app and created the APK, it's always safe. At that point, the dependency is "baked in" to your app.


Allow for scoping of the VO property

Summary
Support the "egi.VO" as default property name, fallback to "VO" if not
available. See fedcloud-tf meeting notes for 2023-10-24 at https://docs.google.com/document/d/1PlTXexteaMz7Qw8gYuou0WpTxlsz-kHS_fbgGZrwR7Y/edit#heading=h.rrn6n11rq6zt

Related issue :

Manually tested at TUBITAK, seems to work fine


US171Task202 Test HODForm w/ basic pattern for form testing.

This establishes a pattern for the testing of forms & does a little more setup for the testing environment as a whole.
The HODForm contains 5 tests --

a check to ensure that, when mounted, the form has the correct default model
a check to ensure that whenever the selected model changes, the parameters also change
a check to ensure that whenever the selected model changes, the correct fields are rendered
a check to ensure that whenever the selected model changes, the 'onChange' event is emitted
a check to ensure that whenever the value of the model parameters change, the 'onChange' event is emitted

Includes:
client/jest.config.js update
client/_tests_/HODForm.spec.js
client/_tests_/setup.js
Developer Checklist:

[X] The code follows the Quality Policy file on Google Drive
[X] My code has been developer-tested and includes unit tests
[X] I have considered proper use of exceptions
[X] I have eliminated IDE warnings

This looks great! The only question that seems worth asking is about the code coverage. Whenever checking out the code coverage it shows the below:

Does it show something different on another person's machine?

Running it again I had the same issue. Resolved it in recent commit, though!

This looks great! The only question that seems worth asking is about the code coverage. Whenever checking out the code coverage it shows the below:

Does it show something different on another person's machine?

Running it again I had the same issue. Resolved it in recent commit, though!

It looks like it is failing some linting tests on the front-end.

It looks like it is failing some linting tests on the front-end.

Going ahead and merging because linting has been resolved and it has two approvals.

Going ahead and merging because linting has been resolved and it has two approvals.


[ingester] Add metrics& healthcheck, rename Kafka cli flags

Which problem is this PR solving?
Resolves https://github.com/jaegertracing/jaeger/issues/1014
Resolves https://github.com/jaegertracing/jaeger/issues/1013
Resolves https://github.com/jaegertracing/jaeger/issues/1093
Short description of the changes

Add default healthcheck port (14270)
Add a configurable metrics HTTP handler (default port is 14271)
Make Kafka flags the same as in the Collector (prefix is kafka instead of ingester)

Comments:
I wasn't sure if I should have refactor the following:

Move the various Kafka flags under /pkg
I left it as is mainly because there's a mix of consumer vs producer flags and because the producer flags are under plugins

Also, should the Parallelism be under Kafka prefix? I felt it was more a ingester flags than a kafka one, but I don't have any strong opinion about it

I'm not sure what would be the best way to fix that problem in the CI. The flags is indeed redefined, but they usually run in different Go applications
--- FAIL: TestKafkaStorage (0.00s)
panic: flag redefined: kafka.brokers [recovered]
	panic: flag redefined: kafka.brokers

I've also fixed the Ingester flag tests and moved ingester.encoding to kafka.encoding because it's like that in Collector

The flags is indeed redefined, but they usually run in different Go applications

This sounds like an issue with the tests. We should be able to create a new instance of the FlagSet in the unit test instead of depending on the global one.

@ledor473 do you still have anything to work here, or can I merge it ?

@jpkrohling It's ready to merge! I'll rebase it real quick

Once codecov turns green, this will be merged.

I restarted test coverage job

@ledor473 could you please fix DCO of the last commit? I will merge afterwards.

thanks @ledor473

@yurishkuro @pavolloffay @objectiser I've just realized that if you run the Ingester with SPAN_STORAGE_TYPE=elasticsearch,kafka, the Ingester crash with the following:
WARNING: multiple span storage types have been specified. Only the first type (elasticsearch) will be used for reading and archiving.

flag redefined: kafka.brokers
panic: flag redefined: kafka.brokers

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc000080d80, 0xefd9a0, 0xc00018d080, 0xe04f6e, 0xd, 0xe2cb58, 0x4b)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/flag/flag.go:805 +0x529
flag.(*FlagSet).StringVar(0xc000080d80, 0xc00018d080, 0xe04f6e, 0xd, 0xe05426, 0xe, 0xe2cb58, 0x4b)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/flag/flag.go:708 +0x8a
flag.(*FlagSet).String(0xc000080d80, 0xe04f6e, 0xd, 0xe05426, 0xe, 0xe2cb58, 0x4b, 0xe00e66)
	/home/travis/.gimme/versions/go1.11.1.linux.amd64/src/flag/flag.go:721 +0x8b
github.com/jaegertracing/jaeger/cmd/ingester/app.AddFlags(0xc000080d80)
	/home/travis/gopath/src/github.com/jaegertracing/jaeger/cmd/ingester/app/flags.go:84 +0x6e
github.com/jaegertracing/jaeger/pkg/config.AddFlags(0xc00015a0f0, 0xc000186240, 0xc000159f28, 0x5, 0x5, 0xc00003a042, 0xd)
	/home/travis/gopath/src/github.com/jaegertracing/jaeger/pkg/config/config.go:36 +0x56
main.main()
	/home/travis/gopath/src/github.com/jaegertracing/jaeger/cmd/ingester/main.go:138 +0x59f


use inside of a function / impl block doesn't highlight imported items

If you write use some::module::or::member; inside of an impl block, or a function block, VSCode won't highlight imported items, won't provide documentation on hover, and won't provide auto-complete suggestions.
Screenshot:

Example code:
pub enum FileExtensions {
	PNG,
	APNG,
	WEBP,
	WEBM,
	MP4,
	M4A,
	JPEG,
	WAVE,
	MP3,
	GIF,
	OGG,
	SWF,
	Torrent,
	MatroskaVideo,
}

impl TryFrom<&str> for FileExtensions {
	type Error = ();
	fn try_from(extension: &str) -> Result<FileExtensions, ()> {
		use FileExtensions::*;
		Ok(match extension {
			"png"     => PNG,
			"apng"    => APNG,
			"webp"    => WEBP,
			"webm"    => WEBM,
			"mp4"     => MP4,
			"m4a"     => M4A,
			"ogg"     => OGG,
			"swf"     => SWF,
			"torrent" => Torrent,
			"jpeg"    => JPEG,
			"jpg"     => JPEG,
			"gif"     => GIF,
			"wav"     => WAVE,
			"wave"    => WAVE,
			"mp3"     => MP3,
			"mkv"     => MatroskaVideo,
			_ => return Err(()),
		})
	}
}

Duplicate of #1165.


openssl-cmp.pod.in and apps/cmp.c: Various minor doc improvements

This fixes various minor issues I found when proof-reading the CMP app man page.
The only more bulky (but trivial) change included is
moving the -recipient option to a different group of options where it fits better.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged - thanks @t8m


Add fog

A good fog creates a better sense of distance for the player when they see far away mountains and helps to hide LOD artefacts.
In order to implement fog the current custom Material (used for texture arrays) needs to be replaced by a bevy ExtensionMaterial, but I haven't figured out how to do that yet.
Contribute to this bevy issue if you want to help me and others figure out how to use fog with texture arrays in bevy:
https://github.com/bevyengine/bevy/issues/12591

done !


Add icon and link to our linkedin page

Above the footer, add a social links section with the linkedin icon linking to https://www.linkedin.com/company/wejustdevelop/

okay


Support deployment without cluster admin permissions

In some cases, users may want to deploy the operator in a single namespace and without cluster-wide permissions. Explore how the operator can support this.

This feature would be very useful for big orgs with different teams, for example if you have one team managing kubernetes and another one managing Apicurio. It would allow the second one to be independent and make changes quicker.
It could also help with engineers doing development or PoC of the product. They typically don't have cluster-wide permissions but a namespace to do this type of work.
Based in the article With Kubernetes Operators comes great responsibility, it seems also a more secure operator.
It would be interesting to know what global resources this operator needs to create and it could be avoided or separated in a previous step so the rest of the installation is independent of the specific actions with cluster-wide permissions.

After a brief review, we only found one thing which requires cluster-wide privileges:
https://github.com/Apicurio/apicurio-registry-operator/blob/be91f2b38134f1d44ad90e70fbf9f1ad550fbe5e/pkg/controller/apicurioregistry/clients.go#L94-L118
So it's checking the openshift version (object clusterversions from the Api Group config.openshift.io) , we guess to assure compatibility between the operator and openshift. If it isn't Openshift, then just ignore the validation:
if api_errors.IsNotFound(err) {
			// default to OpenShift 3 as ClusterVersion API was introduced in OpenShift 4
			ocpSemVer, _ = semver.NewVersion("3")
		} else {
			log.Error(err, "Failed to get OCP cluster version")
			return nil
		}

We understand if the user doesn't have privileges, it fails because it's a different error, right?
In any case, allow bypass this validation or provide the Openshift version as argument to the operator would solve the issue. Does it make sense?

Hi, thank you for the feedback and review. I think this would be a good solution, I'll prepare a PR for the next release.

@jsenko note the cluster_role and cluster_role_binding included in the yaml's we release, we'll need to remove those to address this as well. Btw, here an example of how to detect the openshift cluster without requiring admin permissions https://github.com/EnMasseProject/enmasse/blob/master/pkg/util/openshift.go


FIX Capture duplicate suggestion exception

Captures any validation exception thrown and rather than failing the full request, logs the error and returns.
Not sure on the underlying conditions of the duplicate detection occurring, but this prevents that failure causing white-screen-of-death

It seems the problem here is that two search suggestions are being created at the exact same time (to the second), which is quite possibly a race condition. I want to look into this one a little more before actioning.

I've now resolved this here https://github.com/nglasl/silverstripe-extensible-search/commit/8722a557e7abf6c44c32b9135752ebfed4255d22. Basically, while it's mostly an edge case, and that ignoring the validation error isn't going to break anything, this is going to cause the analytics to display a different frequency to the suggestion frequency. I've basically implemented a fallback so the frequency is updated should this race condition occur.


updating banner

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation, VERSION, and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

Summary of Changes:

Banner updated
Test action sync'd with other plugin repos, since the pre-release trigger was broken
Pre-commit hooks were updated
covalent added as an explicit requirement; will be updated to the stable release when available
tests were fixed since conda is not supported in BaseAsyncExecutor

Note to @cjao and @santoshkumarradha since BaseAsyncExecutor does not support Conda, that functionality has effectively been broken in this plugin.  Moving forward we want to move Conda support outside of core Covalent and implement it directly within each plugin when appropriate.  We can re-enable Conda in the appropriate plugins in the next release.


Suggest details should use link hover color

Similar to #121536, #121521, #125956, #126752
"workbench.colorCustomizations": {
	"textLink.foreground": "#ffae00",
	"textLink.activeForeground": "#00a2ff",
}

Links on hover in suggest details are not using textLink.activeForeground.

Created a PR #130966 fixing this


Fixed typo on lines 270,271

Changed normal strings to f strings, issue 8.

Thanks for noticing this!


Upgrade version + some minor edits

@mairaw : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mairaw : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

#sign-off


Trying to add JS Function to ID

Hey, I'm very new to Javascript and I've been trying to create an animated drop-down with bodymovin. I added id's (#) to my layers in after effects and I want to add hyperlinks and anim.playSegments to some of those ids but I can't seem to make it work. Any ideas? They are all in the same json.
EDIT: I managed to do it but it only works on Chrome, it doesn't work on Firefox nor Opera and probably the others too, this is the code I used, please help out if you know what is the problem.
Code:
// Open Drop Down //
var jsonData = { "name": "hamburger" };
$(document).ready(function () {
    $("#hamburger").on("click", function () {
        anim.playSegments([[0,20]],true);
    });
});

// Close Drop-Down //
var jsonData = { "name": "closemenu" };
$(document).ready(function () {
    $("#closemenu").on("click", function () {
        anim.playSegments([[20,0]],true);
    });
});

EDIT 2: In Mozilla the code seems to work sometimes but when I refresh it doesnt work again, it's confusing. It works fine in Opera and Chrome.
EDIT 3: It seems it's because the files are too heavy but the gzipped version of bodymovin doesnt work for some reason.

Hi Madrise,
Can you share the link to your full code (either a link to your site or a pen on https://codepen.io)? This will help troubleshoot where things are going wrong. I can imagine a couple of problematic things that might be occurring.
First, the playSegments() method is attached to a loaded Bodymovin animation; not to individual layers within the animation. Therefore, I don't believe you can call the playSegments() method from a layer within the loaded animation. Adding IDs to layers within the animation allow you to directly manipulate values of that layer via JavaScript, which is more advanced than what you're trying to do.
Are you able to get the animations to load and playback all of the way through? What does your JavaScript code look like for loading your Bodymovin animations?
Second, you might be attempting to play an animation before it is loaded by Bodymovin. The document might report that it is "ready", but Bodymovin animations still can be loading after the document ready state. This is why there's a DOMLoaded event listener in Bodymovin (NOTE: This is not the same as DOMContentLoaded). DOMLoaded is an event listener that is specific to Bodymovin. Here is a function that I wrote that initializes mouse events only after the Bodymovin animation has loaded:
function initEvents (anim) {     // DOMLoaded event listener that waits for the Bodymovin animation to load before I perform any actions on it     anim.addEventListener('DOMLoaded', function () {       // Define the element to add mouse and touch event listeners to, which is typically a parent element of the SVG; not the SVG itself. Note: "element" is the parent container of the SVG. I use "parentNode" to travel up the DOM.       var parent = element.parentNode.parentNode;       // Mouseover event listener       parent.addEventListener("mouseover", function () {         if (thisAnim.isPaused) {           thisAnim.goToAndPlay(0);         } // if isPaused conditional block       }); // Mouseover event listener     }); // DOMLoaded event listener   };

Hey, here's a link of the website.
This is the version that only works when you refresh.
http://futurize.gr/test/
And this is the temporary fix that I was talking about
http://futurize.gr/test/2

Hi @Madrise , as @Jeremy-Knudsen says, you need to attach your click events to the DOMLoaded event of the animation.
When the jquery document ready event is fired, the animation is not loaded yet so your element with id "hamburguer" does not exist.
After your code
anim = bodymovin.loadAnimation(animData);

You should do something in the lines of:
anim.addEventListener('DOMLoaded', function(){

$("#hamburger").on("click", function () {
  anim.playSegments([[0,20]],true);
  $("#bodymovin").css("z-index", "4");
  $("#bodymovin").css("transition", "z-index 0s step-end, opacity 0s linear");
  $("#hamburger").css("display", "none");
  $("#hamburger").css("cursor", "default");
  });

})

Thank you bodymovin this worked perfectly! I understand my mistake now.

Hello @bodymovin
I am actually having the same problem.
I have created some animation in after effects and then named the layers as per the class name I want.
I am totally new to coding and all I know is HTML and CSS, no javascript knowledge.
I also want to add hyperlinks to my SVG elements, basically want them to work as buttons for some external links.
Is there any reference material on how to do it or can you help me out with the code?
Any help would be appreciated.


[BUG] When me launch roblox me have loaded only friends

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[X] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.0
What problem did you encounter?
when me load roblox this happened how fix me try redownload roblox but this dont helped (Sorry for bad english)

Bloxstrap Log
N/A

Update to latest version and make sure that the drive your bloxstrap is installed in has no special characters, and is from A to Z in latin alphabet.

dont helped :(

dont helped :(

and now new roblox menu :(

To solve this issue i recommand you to open "Roblox Player" (in right click), go to root folder, find "RobloxPlayerlauncher", and clicking file as an administrator (by right click) and it should work because i had that issue before and i solved that, It's easy to fix.

Duplicate of #3691

me dont have admin 😢
but roblox fix this


fix: errors should no longer throw on intial render

This PR fixes an error that was introduced in #505, which I did not catch prior to merging. Sorry y'all!

Codecov Report
Attention: 31 lines in your changes are missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

packages/form-core/src/utils.ts
89.13% <ø> (ø)

packages/react-form/src/createFormFactory.ts
100.00% <100.00%> (ø)

packages/react-form/src/formContext.ts
83.33% <ø> (ø)

packages/react-form/src/useForm.tsx
100.00% <100.00%> (+11.11%)
:arrow_up:

...ckages/react-form/src/useIsomorphicLayoutEffect.ts
100.00% <100.00%> (ø)

packages/solid-form/src/createFormFactory.ts
100.00% <100.00%> (ø)

packages/solid-form/src/tests/utils.ts
100.00% <100.00%> (ø)

packages/yup-form-adapter/src/tests/utils.ts
100.00% <100.00%> (ø)

packages/yup-form-adapter/src/validator.ts
100.00% <100.00%> (ø)

packages/zod-form-adapter/src/tests/utils.ts
100.00% <100.00%> (ø)

... and 7 more

:loudspeaker: Thoughts on this report? Let us know!.


Shibboleth request timestamp format

Rancher versions:
rancher/server: v1.6.5
rancher/agent: v1.2.5
Infrastructure Stack versions:
healthcheck: v0.3.0
ipsec: v0.1.0
network-services: v0.2.0
scheduler: v0.5.1
Docker version: (docker version,docker info preferred)
Version: 1.12.5
API version: 1.24
Go version: go1.6.4
Git commit: 7392c3b
Built: Fri Dec 16 02:23:59 2016
OS/Arch: linux/amd64
Server:
Version: 1.12.5
API version: 1.24
Go version: go1.6.4
Git commit: 7392c3b
Built: Fri Dec 16 02:23:59 2016
OS/Arch: linux/amd64
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Red Hat Enterprise Linux Server release 7.3 (Maipo), 3.10.0-693.1.1.el7.x86_64
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node with external MariaDB.
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Issue
Microsoft SAML server refuses to accept the request sent by Rancher:
MSIS0018: The SAML protocol message cannot be read because it contains data that is not valid. --> System.FormatException: String was not recognized as a valid DateTime.
Seems that Rancher writes timestamp in more detail than Microsoft can handle. It looks like the reason may lay within the very nature of the DateTime-structure in .NET which is based on 100-nanosecond vs. nanoseconds in Go (7 floating points vs 9 floating points).
Would it be possible to add configuration field to change/alter the precision of the timestamp?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


(dropbox) update for stable version

Update to dropbox  to always have the correct stable version, and to allow for the dropbox-beta package in the future
@AdmiringWorm
I might have at least lowered the time to 2 min 52 sec

I almost thought something went wrong when I was seeing the install of 29.3.18. It wasn't until I checked the latest beta is 29.3.19. So should I add in this PR a reset of the nuspec file?

I almost thought something went wrong when I was seeing the install of 29.3.18. It wasn't until I checked the latest beta is 29.3.19. So should I add in this PR a reset of the nuspec file?

You don't need to do that, because the update inside update.ps1 wasn't uncommented, the package didn't actually update itself. Therefore you still see the previous beta version in the appveyor logs.

Changes made. Enjoy the PR

@AdmiringWorm
Updated update.ps1  to have a update_helper.ps1. This will keep update smaller. Should be ready for your approval 😄


Limit use of WebGL contexts

https://registry.khronos.org/webgl/extensions/WEBGL_lose_context/ - does this actually release the context, or merely 'simulate' it?

Fixed in fbb962af40f659759654f29927dcb2b035c7ee1d


Empty commit to rebuild/publish docker image

failed in: https://ci.balena-dev.com/teams/main/pipelines/github-events-balena-io/jobs/publish/builds/2219

Change-type: patch

@balena-ci I self-certify!


Ansible agent fails create daemonset on k8s 1.16

Ansible agent fails create daemonset on k8s 1.16
Expected Behavior

ansible agent should succeed
Current Behavior

fails
Possible Solution

Ansible agent uses v1beta for daemonset which has been removed in k8s 1.16
Steps to Reproduce

Context (Environment)

OS:
Architecture:
Docker version:
Docker compose version:
Kubernetes version:

Detailed Description and log

Possible Implementation

Fixed by PR #81


search: Set base font-size on search input.

Additional work can (and eventually will) better shore up the twisted inheritance chains for font-sizing on input elements such as the search input box, but the fix in this PR gets the highly visible search box in line with the rest of the always-visible UI.
Fixes part of #30359

Screenshots and screen captures:

Before
After
After, expanded

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Screenshots look good to me!

Merged, thanks @karlstolley!


cmd/cue: define UX for validating JSON with JSON Schema that includes "additionalProperties": false

What version of CUE are you using (cue version)?

$ cue version
cue version 0.3.0-beta.4 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
I have an existing JSON Schema (schema.json), that includes "additionalProperties": false like this:
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "test",
  "type": "object",
  "required": ["mandatory"],
  "additionalProperties": false,
  "properties": {
    "mandatory": {
      "description": "mandatory field",
      "type": "string"
    },
    "optional": {
      "description": "optional field",
      "type": "string"
    }
  }
}

I imported this with cue:
$ cue import schema.json

Then I tried to validate a JSON file (data.json) with the following content
{
  "mandatory": "foo",
  "optional": "bar",
  "invalid": true
}

with
$ cue vet data.json schema.cue

What did you expect to see?
I expect this command to fail, because the JSON file does include an additional field (invalid) and this is not allowed with "additionalProperties": false.
What did you see instead?
cue did not complain.

Might be related to #267.

The issue here is that by default cue import by default imports the schema as follows:
// schema.cue
// test
@jsonschema(schema="http://json-schema.org/draft-07/schema#")
// mandatory field
mandatory: string
// optional field
optional?: string

Then via cue vet the root of the loaded CUE files (i.e. the value {mandatory: string, optional?: string}) is used to validate data.json.
Notice however the root value is not closed. Hence, regardless of whether additionalProperties is supplied or not, additional fields will be allowed.
@mpvl and I discussed this in the context of imports of package values the other day. This is another interesting data point in the question of whether package values should be closed or not.
On a related note the following also "fails":
cue vet jsonschema: schema.json json: data.json

I suspect for the same reason. However from a user's perspective, this workflow should probably work without any further effort (independent of how/whether we address the package closedness question)

@myitcv: there is more going on here, in fact.
The conversion also doesn't close structs that are not at the root. The reason is that closeness in CUE means something different from closeness in JSON schema (additionalProperties: false).
The purpose of closeness in CUE is 1) represent proto-like oneofs, 2) catch typos, or basically validation within a single version. The belief is though, that an API should not close the door for future expansion and has no means of representing this. So closeness it to detect types in a closed environment, but unknown fields of incoming messages should be ignored. A very close analogy is how Proto definitions are closed when generated for, say, a Go program, but that unknown fields in a received message within that same program are ignored.
It is quite unclear to me how JSON Schema should be interpreted in this context. There seems to be about as little guidance around it and it seems about as vague as the concept of null in JSON. There is a reason its use is restricted in structural form OpenAPI for CRDs.
But open to suggestions on how this should be translated. There seems to be at least something amiss. If there is an additionalProperties: false in the input schema, at the very least the schema in CUE should be closed. But arguably it should always be closed regardless. Or it should be a command line option. See also discussion in #267.

This issue has been migrated to https://github.com/cue-lang/cue/issues/750.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Inquiry

I have send Inquiry on https://www.panicbyte.xyz/about
looking forward hearing from you ;-)

How can I contact you directly?


Added aot compatibility

Followed this guide
<EMAIL_ADDRESS>Your library works now with my new angular-cli generated project.
If you want to do this yourself as you've said you have some plans, at least here's an idea of the steps to take.
I will be using my fork internally until your npm package has AOT support.

Thnx @TrevorBroderick1 looks good, I pulled in the changes and republised as 0.5.5


Update 0000-01-02-smakhanya.md

I created a branch; made a commit and first pull request

made mistake?


why aren't the PTModel topic distributions equal for documents of the same pseudodocument?

When working with the PTModel, i noticed that the topic distributions obtained via doc.get_topic_dist() would return different distributions for documents that had been assigned to the same pseudodocument. If i read the original paper correctly, the topic distributions for each document should be the same as the topic distribution for the pseudodocument it is part of. Is this a bug or am I missing something?

Hi @RutgerEttes ,
Thank you for asking a good question.
As you said, currently doc.get_topic_dist() of PTModel return the distribution based on topic allocation for the real document's words, so it may be different from the pseudo document's one.
I'll add an optional argument from_pseudo_doc to get_topic_dist() in the next update so that we can choose whether to get the distribution from a pseudo document or a real document.


Issue while Creating keys and certificates

Describe the bug
I am getting this warning : generating random key material may take a long time
if the system has a poor entropy source
No OpenSSL randomness retrieved. DRBG available?
while I run this command from the terminal : openssl req -x509 -new -newkey dilithium2 -keyout dilithium3_CA.key -out dilithium3_CA.crt -nodes -subj "/CN=test CA" -days 365 -config /home/amit/softwares/openssl-1.1.1w/apps/openssl.cnf
also, any file is not generated in the directory, can anyone please help me on how to solve this issue?

Please read USAGE.md:

Note: Be sure to always activate either the "default" or "fips" provider as these deliver functionality also needed by oqsprovider (e.g., for hashing or high quality random data during key generation).


Update AWS Braket Executor to use AWSExecutor

Acceptance Criteria

[ ] Pass any required attributes from credentials_file, region, s3_bucket_name, profile, execution_role, and log_group_name to AWSExecutor super class
[ ] Re-structure executor in order to accord with abstract class methods as defined in RemoteExecutor, namely _upload_task, submit_task, get_status, _poll_task, _query_result, and cancel when appropriate
[ ] Update unit tests for executor
[ ] Update doc strings for executor

Closed as duplicate of https://github.com/AgnostiqHQ/covalent-braket-plugin/issues/16


The final solution for the user undefined error.

I was over complicating my reasoning and somehow missed this detail. Please close my old PR as it's useless and doesn't fix the problem. This should.

close it yourself? :lmao:


Move implicit and hybrid flow to separate document/chapter

Is it possible to change this part of the documentation

After fixing #104958 implicit and hybrid are not mentioned in the send the sign-in request section correctly.
But these changes are not captured in the Protocol flow: Sign-in and Enable ID tokens. In both sections OpenID Connect implicit and hybrid flow are still mentioned. That is misleading!
In OpenID Connect Auth Code Flow the ID Token is delivered to the Relying Party (RP) and not to the user agent like shown in the sign in flow which would be correct for OIDC implict/OIDC hybrid flow.
Enable ID tokens only enables ID Token delivery to the user agent. That is not the case for the RP.
I would suggest to rename the exisiting link "OpenID Connect"

to "OpenID Connect auth code flow with PKCE" and move implcit and hybrid to their own corresponding chapters/documents
"OpenID Connect implicit flow" and "OpenID Connect hybrid flow"
so the sidebar would look like:

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0d3746e5-5147-d996-ba4f-350fd1d086ef
Version Independent ID: afff03f1-16c3-9866-39b0-bdddd0e55d7d
Content: OpenID Connect (OIDC) on the Microsoft identity platform - Microsoft Entra
Content Source: articles/active-directory/develop/v2-protocols-oidc.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@krantic
Thanks for your feedback! We will investigate and update as appropriate.

@krantic
I'm going to assign this to the document author so they can take a look at it accordingly.
@OwenRichards1
Please review it.

@krantic Thanks for your feedback - this repo is currently undergoing a migration. I am required to close this issue, although it has been assigned in product backlog and will be addressed when migration is complete.

#please-close


Fix/firebase config

Removed firebaseConfig and fixed path in .gitignore

Thank you very much! I will merge this!


Leader-follower in icerpc accept loop?

I am wondering if we could/should switch to a leader-follower model in the icerpc AcceptRequestsAsync loop:
https://github.com/icerpc/icerpc-csharp/blob/6036d786a0ad5ee1f81bc6b5c0ae469db7c12125/src/IceRpc/Internal/IceRpcProtocolConnection.cs#L892
Currently, we have a task that accepts new requests (= multiplexed streams) and then schedules their dispatch in a separate thread:
https://github.com/icerpc/icerpc-csharp/blob/6036d786a0ad5ee1f81bc6b5c0ae469db7c12125/src/IceRpc/Internal/IceRpcProtocolConnection.cs#L953
The alternative would be for the thread that accepted the stream to perform this dispatch. And before dispatching, it would schedule (Task.Run) another AcceptRequestAsync (singular).
The potential advantage here is better latency since there is one fewer context switch.
If you look at Slic, the implementation of AcceptStreamAsync already performs a context switch: the Slic reader thread/task pushes the new stream into a Channel (_acceptStreamChannel), and AcceptStreamAsync pulls from this channel not inline. (I think this Slic logic is fine).

leader-follower is not a good idea. The current setup (with a single read flow) is much simpler.


API question: should we implement encode_x(), etc.?

Currently we have two ways of specifying configurations, which are equivalent:
Chart().configure(cell=CellConfig(**kwargs)) and
Chart().configure_cell(**kwargs).
On the other hand, for encodings we have
Chart().encode(x=X('name', **kwds)) or Chart().encode(x='name'), where in the second shorthand there is no way to specify additional keywords.
I wonder if it wouldn't be convenient to have, by analogy with the configure methods, Chart().encode_x('name', **kwds)?
On the one hand, there are situations where it would be very useful – especially for tab-completion of arguments within the function. It also creates some symmetry with the configure_* methods, and users might expect to be able to do this. On the other hand, it would add yet another way of solving the same probelm, and is not particularly convenient for the most common case of defining several encodings at once.
Thoughts?

The issue with encode is that it accepts multiple different objects, each
with its own keywords arguments. Because of this, my thought is to keep as
is.
On Wed, Jun 15, 2016 at 10:38 PM, Jake Vanderplas<EMAIL_ADDRESS>wrote:

Currently we have two ways of specifying configurations, which are
equivalent:
Chart().configure(cell=CellConfig(**kwargs)) and
Chart().configure_cell(**kwargs).
On the other hand, for encodings we have
Chart().encode(x=X('name', **kwds)) or Chart().encode(x='name'), where in
the second shorthand there is no way to specify additional keywords.
I wonder if it wouldn't be convenient to have, by analogy with the
configure methods, Chart().encode_x('name', **kwds)?
On the one hand, there are situations where it would be very useful –
especially for tab-completion of arguments within the function. It also
creates some symmetry with the configure_* methods, and users might
expect to be able to do this. On the other hand, it would add yet another
way of solving the same probelm, and is not particularly convenient for the
most common case of defining several encodings at once.
Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ellisonbg/altair/issues/132, or mute the thread
https://github.com/notifications/unsubscribe/AABr0BSPti6H2jsDMb-YSQv6k3OkH_g-ks5qMOFMgaJpZM4I3CrR
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Sounds good


[FIPS] build operator in fips mode

This change modifies how the operator is built to use
the ubi9 base image and golang tool chain.
A new GO_BUILD_EXTRA_ENV_ARGS build arg is added to the dockerfile
to enable the build system to inject addtional parmaters.
the default value enable dynmaic linking of glibc which is required
for FIPS
The prow_ci.env file is extended to enable fips checkign in the
prow image build job to validate this change.
The Makefile is extened to allow passing build args to docker-build
Closes: OSPRH-3110

/test placement-operator-build-deploy-kuttl

/test placement-operator-build-deploy-kuttl

As discussed pointed in chat earlier, pin-bundle-images.sh is failing because the fork has a different repo name, and the script's regex does not expect that.

oh right i have 2 forks ...
the first one https://github.com/SeanMooney/placement-operator was one i created whne the placement operator was acidnetally deleted i created it before i setup my gitea mirrors
https://gitea.seanmooney.info/openstack-k8s-operators/placement-operator
i can delete my first fork and then rename the new one since that is the one git thinks is the correct fork.

/test placement-operator-build-deploy-kuttl


[Exploratory] Finding handles in 1) applications, 2) systems

Greg's commit is an early prototype (with outstanding to do's) for getting handles from an application.  We need to develop this further.
Is getting handles from a system similar?

Superseded by current work.


Add a way to revoke multiple approvals one after the other

Many people have requested whether we can let them revoke multiple approvals in a single click. I don't want to blindly send like 20 sendTransaction requests to the wallet since that encourages users to just click "accept" without looking at their transaction popups.
But perhaps what we can do is set up a process where a user selects approvals they want to revoke and then clicks "batch revoke". This then opens a modal that shows the approvals one by one, so that the MetaMask popups get triggered one at a time and there is a clear overview of the progress through spinners / checkmarks / progress bars.

We've added a "batch revoke" functionality that queues up all transactions.


--sources does not work with IPv6

Hello,
on IPv6 only networks, --source [ipv6] does not work:
Could not retrieve speedtest.net configuration: <urlopen error [Errno -9] Address family for hostname not supported>

speedtest.net does not support IPv6.
https://support.speedtest.net/hc/en-us/articles/203845430-Does-Speedtest-net-support-IPv6-


Onboarding instruction improvements

Link to the Page
https://www.skeleton.dev/guides/install
Describe the Issue

Add a warning about mixing third party plugins with Skeleton, such as Flowbite or Daisy
The CLI will no longer use Svelte-Add for Tailwind - manual instructions will
Simplify the Styling section to only recommend all.css. No more individual imports.

Are you able to create a Pull Request with the fix?
Yes

Side note: add a quick origin story for Skeleton and the theme in an "about" section

These changes have been implemented and will be merged into dev branch shortly.


tensorflow/python/ops/init_ops.py line 466 - initialization scaling incorrect?

System information : NOT APPLICABLE
Have I written custom code: No and N/A
OS Platform and Distribution: GNU/Linux Gentoo and N/A
TensorFlow installed from: https://www.tensorflow.org/install/install_sources
TensorFlow version:  1.6.0 but relevant to stable version on GitHub
Bazel version: 0.11.1 and N/A
CUDA/cuDNN version: 9.1/7.1 and N/A
GPU model and memory: Titan XP x2 - 12GB x2 and N/A
Exact command to reproduce: N/A
Source code / logs:
tensorflow/python/ops/init_ops.py - lines 465-469:
    if self.distribution == "normal":
      stddev = math.sqrt(scale)
      return random_ops.truncated_normal(
          shape, 0.0, stddev, dtype, seed=self.seed)

Describe the problem:
According to He et al (2015) [http://arxiv.org/abs/1502.0185] (Eq. 10) the correct scaling for the standard deviation for kernel initialization is sqrt(2/n). However line 466 of tensorflow/python/ops/init_ops.py reads:
stddev = math.sqrt(scale)
where the default scale is 1/n (n depending on fan mode), corresponding to sqrt(1/n) rather than sqrt(2/n) - therefore giving half the correct scaling.
Also - since a truncated (-2SD to +2SD) normal distribution is used rather than a full distribution, shouldn't the scale be multiplied by 1.137? Perhaps the simplest fix is therefore:
stddev = math.sqrt(2.274*scale)

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Apologies, and thanks for the template. I have amended the post to include the details.

/CC @fchollet, can you take a look?

There's a PR awaiting merge that fixes this issue: https://github.com/tensorflow/tensorflow/pull/18854

Thanks. It looks like the issue was first raised at https://github.com/tensorflow/tensorflow/issues/18706 nearly a month ago. It seems a peculiarly long-winded procedure to correct 'stddev = math.sqrt(scale)' to 'stddev = math.sqrt(2.274*scale)' but never mind!

Nagging Assignee @fchollet: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Pull request has been merged, so this issue could probably be closed.


Documenting how to get button information from MouseEvent

📚 Documentation
The information of how to get which button generated the event can be found here
And here is an example using napari:
import napari

viewer = napari.Viewer()
pt_layer = viewer.add_points()

@pt_layer.mouse_drag_callbacks.append
def _click_callback(layer, event):
    if event.button == 1:
        print('left')
    elif event.button == 2:
        print('right')
    elif event.button == 3:
        print('middle')

napari.run()

We might also want to consider using our own napari mouse event that would give us additional control over what aspects of this event are available

This information is found in the vispy docs here https://vispy.org/api/vispy.app.canvas.html?highlight=mouseevent#vispy.app.canvas.MouseEvent along with some additional properties added here https://github.com/napari/napari/blob/ea3fadcfbc54d630271e0e32f151371dfb499a8b/napari/_qt/qt_viewer.py#L900-L919
I think it would be good to get this stuff added here too https://napari.org/howtos/connecting_events.html#listening-for-mouse-events - maybe @kevinyamauchi and @alisterburt can help with some of the details here as they've used this API a lot


Update npm package?

Hey there, thanks for creating this!  Just a heads up that the npm module seems to be lagging slightly behind the github repo:
https://www.npmjs.com/package/react-native-fabric-twitterkit
Possible to update?

Hey Jason, thanks for letting me know. Going to update it and release as version 0.1.0!

No worries.  Also, I can't remember specifically, but I actually had to roll back my version because the updates in this pull (https://github.com/tkporter/react-native-fabric-twitterkit/commit/f89c80b4c7f7d052be3813248e85f77535d6ae09) conflicted with the setup instructions in your README.  Might be worth triple checking the two align, and apologies for not logging the conflict.

I'll fix that too, seems to be just a matter of changing FabricTwitterKitPackage.getInstance().onActivityResult(requestCode, resultCode, data); to FabricTwitterKitPackage.getInstance().onActivityResult(this, requestCode, resultCode, data);. Thanks for the heads up.


chore(deps): update docker:25.0.4 docker digest to 0cbb848

This PR contains the following updates:

Package
Type
Update
Change

docker
image
digest
0b0e8ca -> 0cbb848

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Create a docker image for all components

For learning and illustrating purposes it;s a good idea to have a single Docker image via single Dockerfile.
Then executing/implementing issues #1 to #10 will become easier.
Here are two examples to follow to create the docker config file(s) and shell scripts to achieve it:

https://github.com/neomatrix369/awesome-ai-ml-dl/tree/master/examples/deepnetts
https://github.com/neomatrix369/awesome-ai-ml-dl/tree/master/examples/tribuo

(also check the docker-image folder)

@yugoccp let's do this together, I'll help you here, if we do it the above way there are multiple benefits

If there are any branches or PRs you wish reviewing feel free to push them to Github and I can share my comments on there.

You are also a collaborator to this project which also means we can work on the same branch or PR if necessary @yugoccp

Just enabled the https://github.com/neomatrix369/chatbot-conversations/projects/1 project management interface so that we can keep track of issues and PRs

You are also a collaborator to this project which also means we can work on the same branch or PR if necessary @yugoccp

Thanks @neomatrix369 ! I'll push some changes soon!

Created branch to address this issue
https://github.com/neomatrix369/chatbot-conversations/tree/feature/add-single-dockerfile
@neomatrix369 could you help me fix run container command?

@neomatrix369 in the end I make it run with helidon and quarkus worlds, will be happy to review it together, and moving forward to also run roberta-world :)

I'll test it out on my machine and try to push something for python/roberta-world

@neomatrix369 in the end I make it run with helidon and quarkus worlds, will be happy to review it together, and moving forward to also run roberta-world :)

Its fixed now, there was an issue with torch==1.3.1 in the requirements.txt file, this version does not exist - check the commits you can see other changes as well.
I'll briefly test it and push the changes and let you continue

There are some python related errors, try to debug and see why its failing - there is fun in this investigation.

@neomatrix369 I've updated README.md file with instructions and fixed roberta-world dependency to work. Will open PR for review 😄


Adding support for WebRDP

Hi. Do you have a plan to adding support for a WebRDP? Does it possible?
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin
Thank you for your work!

This have nothing with RDP Wrapper.


HTTP: formParamSeq/formParamMap - EL resolving issue

Version: 3.9.3
Methods: formParamMap and formParamSeq
These methods can't resolve simultaneously map/seq AND values inside.
Here you are example when myMap will be resolved, and someValue not:
Session("someValue" -> "foo", "myMap" -> Map("key" -> "#{someValue}"))

formParamMap("#{myMap}")

Sorry, I way on my phone and didn't properly understand your issue.
Sadly, that's a path I don't want to follow.
I don't want to support recursive EL nor have EL works inside functions:

this harms performance as EL parsing must then be performed at runtime on every resolution
you want 1 level of recursivity, but why not 2, 3, 4, etc?
we would have to support this across the whole codebase

Oh, I see the point! Got it.


Modify GRPC support version

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] Bug fix
[ ] New feature provided
[x] Improve performance

Coverage remained the same at 21.842% when pulling c7c190165fcb611853a8be251f584e12dd69e475 on ascrutae:feature/update-docs into 63eec4bd217d0151c05ebe1750c1f2de4d7d481f on apache:master.