Cleanup sandcastle and docs for ground atmosphere

What I did
I think the current Sandcastle names of "Atmosphere" and "Atmosphere color" are confusing, because it implies they're different aspects of the same thing. But "Atmosphere color" only changes the color of the sky as seen from the ground or the atmosphere around the ellipsoid. Whereas "Atmosphere" is specifically about the ground atmosphere.
I renamed them to "Ground Atmosphere" and "Sky Atmosphere" respectively. Both will show up when a user searches for "Atmosphere" so it will be obvious there are two different ways of affecting the atmosphere.
I also updated some things that were copied from the Sky Atmosphere example to the Ground one, and added links to the Sandcastle in the docs.
One problem left
I updated the showGroundAtmosphere doc to say that it's only visible when the camera is at a distance between lightingFadeOutDistance and lightingFadeInDistance but the doc for those say:

The distance where everything becomes lit. This only takes effect when enableLighting is true.

Which seems to contradict this, since you can see it does affect the ground atmosphere whether or not lighting is enabled:
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=Atmosphere.html
So I'm not sure whether this is expected behavior that lightingFadeInDistance controls both lighting and ground atmosphere and if the doc just needs to be updated, or if there's supposed to be a separate control for ground atmosphere?
@bagnell @lilleyse

Thanks for the pull request @OmarShehata!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

So I'm not sure whether this is expected behavior that lightingFadeInDistance controls both lighting and ground atmosphere and if the doc just needs to be updated, or if there's supposed to be a separate control for ground atmosphere?

I think it's expected that it controls both, and the doc just needs to be updated to say it takes effect when enableLighting or showGroundAtmosphere are true.

@lilleyse I removed the Sandcastle renames from breaking changes, both for this and for the 1.50 release from CHANGES.md.

@lilleyse this should be good to merge.

Ah thanks for the reminder!


Ghost empty when used in a table

See this fiddle: http://jsfiddle.net/qjdunLnu/
When you drag the numbers, they are just empty. Couldn't figure out if it is an issue with the library or with the browser.

Guess this project is dead.

Guess this project is dead.

Hey, support for tables was never really a goal. If you want to send a PR to fix this, I would be very happy to merge it.

This seems to be a browser issue: works well with firefox. In webkit browsers, some table cells are displayed and some aren't. Trying to figure out how webkit decides what to display/hide.

Hmm, interesting. Please feel free to submit a PR if you figure out how ti solve it. Thank you.

Safari will display contents of the TD cell as long as there are no inline elements inside the TD. For example text	 will be displayed, but not text	.
Chrome will not display anything in either case.
The problem seems to be with the display: table-row value. If we set display of UL to table, and display of LI to table-row, and inner divs as table-cell, then the same behavior happens as with regular tables. Omitting table-row seems to fix the problem.
I have looked through the code and I don't think there is anything wrong with it, at least the part where the ghost is being created and set. In my case I was able to replace the traditional table with table layout not using display: table-row.

Ahh, nice. So maybe could you send a PR adding this info as a step by step part to the readme? This would probably help others who have similar problems. Thanks.


unit test created

----------|---------|----------|---------|---------|-------------------

File
% Stmts
% Branch
% Funcs
% Lines
Uncovered Line #s

All files
50
0
50
50

data.js
50
0
50
50
5-7

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

Test Suites: 1 passed, 1 total

Tests:       1 passed, 1 total

Snapshots:   0 total

Time:        0.249 s, estimated 1 s

Also change the target branch be to be "main", but a branch with your name. If it doesn't exist tell me that I will create it.

Also change the target branch be to be "main", but a branch with your name. If it doesn't exist tell me that I will create it.

It doesn't exist, please create it.
https://github.com/flaviostutz/onboarding-nodejs-users/branches/all


cpp, Simplified Chinese garbled

cpp, Simplified Chinese garbled
As shown in the following figure when there is Simplified Chinese in the code, the relevant characters cannot be displayed normally

Looks like the font doesn't support Chinese glyphs and the font renderer doesn't fallback. Does it work if you change to a font with Chinese glyphs in it?

Thank you, to pass this method to solve the font display problem, but found that the code file in the first line more than an unknown character (not caused by the font file, you can refer to the previous picture, not set the body of the code file at the beginning of the contents of the content compared to the source code more than some of the content.)

Yes, it means what you understand it to mean (the code file is generated by the vs 2022 default settings)

Feature request: It would be nice if there were some way to set the font via the UI, and preferably choose from the standard list of installed fonts on Windows. Having to find a config file and copy the .ttf there manually was not easy to discover.


Workaround for updating hashes

Temporary workaround for #25
This PR will modify hashes of entry chunks based on the current date during build.
https://user-images.githubusercontent.com/5134470/204069233-01019f75-5336-4f36-9a99-f8c33de7d9ec.mp4

@montalvomiguelo sorry for the delayed review here, but vite 4.0 was released last week so it looks like we may have successfully waited this out 😅
would you be able to test with the new vite release and verify if the entry file hashes are now updated when the content of imported chunks is modified?

@ScottPolhemus The [hash] issue persists when using Vite 4

@montalvomiguelo Rather than merging this, I ended up implementing a version of @slavamak's proposed solution from #25 in this commit. I prefer that approach because it only updates the hashes when necessary, allowing unchanged modules to retain their prior hashes (and thus allowing browsers to retain and re-use the client-side cache for those modules until they are actually modified). It works because the vite metadata for each chunk contains the hashed filenames for each imported module, so using those filenames to invalidate the entry module's hash effectively gives us exactly the behavior that we're looking for. (I would still consider this a temporary solution until https://github.com/vitejs/vite/issues/9583 is resolved, but a more robust one that doesn't have the drawback of invalidating the hashes for all files on each build regardless of changes.)


Add display_version to antora.yml

Looks cleaner :)
We can get rid of the neo4j versions here?

I haven't seen any usage for those here. Do you know why were they added in the first place? Are you using them in the main GDS docs?

yes we do have them in the main docs. Although with the same outdated values.
    neo4j-version: '4.1'
    neo4j-version-exact: '4.1.1'
    neo4j-buildnumber: '4.1'

So we can remove them there too?

yes we do have them in the main docs. Although with the same outdated values.
    neo4j-version: '4.1'
    neo4j-version-exact: '4.1.1'
    neo4j-buildnumber: '4.1'

So we can remove them there too?

I guess so. Just make sure by running a search before and building the docs after removing them.


Missing libgvplugin_pango

I get the following error when using the dot command:
Warning: Could not load "/home/johannes/.local/opt/miniconda3/envs/snakemake-tutorial/lib/graphviz/libgvplugin_pango.so.6" - file not found
Warning: Could not load "/home/johannes/.local/opt/miniconda3/envs/snakemake-tutorial/lib/graphviz/libgvplugin_pango.so.6" - file not found
Format: "jpg" not recognized. Use one of: bmp canon cmap cmapx cmapx_np dot eps fig gv ico imap imap_np ismap jpe jpeg jpg pdf pic plain plain-ext png pov ps ps2 svg svgz tif tiff tk vml vmlz xdot xdot1.2 xdot1.4

This is on fedora linux 26.

@ocefpaf, since you are one of the maintainers, any insight on this?

No idea. I kind don't really use graphviz a lot. Ping @conda-forge/graphviz team.

BTW, if you can create a test and send it as a PR we can check if a re-build fixes this.

@johanneskoester, what were you doing when you got that error?

I have the same error on Ubuntu. Here is a Dockerfile to reproduce it.
FROM ubuntu:latest

RUN apt-get update && apt-get -y dist-upgrade
RUN apt-get install -y --no-install-recommends bzip2 wget

RUN wget --no-check-certificate https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh && \
    bash Miniconda3-latest-Linux-x86_64.sh -bf && \
    rm Miniconda3-latest-Linux-x86_64.sh
ENV PATH="/root/miniconda3/bin:${PATH}"

RUN conda install -c conda-forge graphviz=2.38.0

CMD dot

This gives:
$ docker run --rm docker_graphviz
Warning: Could not load "/root/miniconda3/lib/graphviz/libgvplugin_pango.so.6" - file not found

Seems like an X libraries thing..
root@e87e82132286:/home# ldd /root/miniconda3/lib/graphviz/libgvplugin_pango.so.6
        linux-vdso.so.1 =>  (0x00007ffec4fe2000)
        libgvc.so.6 => /root/miniconda3/lib/graphviz/../libgvc.so.6 (0x00007fba3fcc6000)
        libltdl.so.7 => /root/miniconda3/lib/graphviz/../libltdl.so.7 (0x00007fba3fabd000)
        libxdot.so.4 => /root/miniconda3/lib/graphviz/../libxdot.so.4 (0x00007fba3f8b8000)
        libcgraph.so.6 => /root/miniconda3/lib/graphviz/../libcgraph.so.6 (0x00007fba3f6a2000)
        libcdt.so.5 => /root/miniconda3/lib/graphviz/../libcdt.so.5 (0x00007fba3f49c000)
        libpathplan.so.4 => /root/miniconda3/lib/graphviz/../libpathplan.so.4 (0x00007fba3f294000)
        libexpat.so.1 => /root/miniconda3/lib/graphviz/../libexpat.so.1 (0x00007fba3f06a000)
        libpangocairo-1.0.so.0 => /root/miniconda3/lib/graphviz/../libpangocairo-1.0.so.0 (0x00007fba3ee5e000)
        libcairo.so.2 => /root/miniconda3/lib/graphviz/../libcairo.so.2 (0x00007fba3eb19000)
        libpixman-1.so.0 => /root/miniconda3/lib/graphviz/../libpixman-1.so.0 (0x00007fba3e873000)
        libXrender.so.1 => not found
        libSM.so.6 => not found
        libICE.so.6 => not found
        libX11.so.6 => not found
        libXext.so.6 => not found
        libpangoft2-1.0.so.0 => /root/miniconda3/lib/graphviz/../libpangoft2-1.0.so.0 (0x00007fba3e65e000)
        libharfbuzz.so.0 => /root/miniconda3/lib/graphviz/../libharfbuzz.so.0 (0x00007fba3e3d0000)
        libgraphite2.so.3 => /root/miniconda3/lib/graphviz/../libgraphite2.so.3 (0x00007fba3e19c000)
        libpango-1.0.so.0 => /root/miniconda3/lib/graphviz/../libpango-1.0.so.0 (0x00007fba3df52000)
        libgthread-2.0.so.0 => /root/miniconda3/lib/graphviz/../libgthread-2.0.so.0 (0x00007fba3dd51000)
        libfontconfig.so.1 => /root/miniconda3/lib/graphviz/../libfontconfig.so.1 (0x00007fba3db0f000)
        libxml2.so.2 => /root/miniconda3/lib/graphviz/../libxml2.so.2 (0x00007fba3d7a9000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fba3d5a5000)
        libicui18n.so.58 => /root/miniconda3/lib/graphviz/../libicui18n.so.58 (0x00007fba3d0a5000)
        libicuuc.so.58 => /root/miniconda3/lib/graphviz/../libicuuc.so.58 (0x00007fba3cca6000)
        libicudata.so.58 => /root/miniconda3/lib/graphviz/../libicudata.so.58 (0x00007fba3b1a6000)
        liblzma.so.5 => /root/miniconda3/lib/graphviz/../liblzma.so.5 (0x00007fba3af80000)
        libgobject-2.0.so.0 => /root/miniconda3/lib/graphviz/../libgobject-2.0.so.0 (0x00007fba3ad2b000)
        libffi.so.6 => /root/miniconda3/lib/graphviz/../libffi.so.6 (0x00007fba3ab22000)
        libglib-2.0.so.0 => /root/miniconda3/lib/graphviz/../libglib-2.0.so.0 (0x00007fba3a7f7000)
        libiconv.so.2 => /root/miniconda3/lib/graphviz/../libiconv.so.2 (0x00007fba3a509000)
        libpcre.so.1 => /root/miniconda3/lib/graphviz/../libpcre.so.1 (0x00007fba3a2c7000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fba3a0aa000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fba39ea2000)
        libfreetype.so.6 => /root/miniconda3/lib/graphviz/../libfreetype.so.6 (0x00007fba39c0a000)
        libpng16.so.16 => /root/miniconda3/lib/graphviz/../libpng16.so.16 (0x00007fba399ca000)
        libz.so.1 => /root/miniconda3/lib/graphviz/../libz.so.1 (0x00007fba397b3000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fba394aa000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fba390e0000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fba4016c000)
        libXrender.so.1 => not found
        libSM.so.6 => not found
        libICE.so.6 => not found
        libX11.so.6 => not found
        libXext.so.6 => not found
        libXrender.so.1 => not found
        libSM.so.6 => not found
        libICE.so.6 => not found
        libX11.so.6 => not found
        libXext.so.6 => not found
        libstdc++.so.6 => /root/miniconda3/lib/graphviz/.././libstdc++.so.6 (0x00007fba38da6000)
        libgcc_s.so.1 => /root/miniconda3/lib/graphviz/.././libgcc_s.so.1 (0x00007fba38b94000)

If I install them from conda-forge it works.
FROM ubuntu:latest

RUN apt-get update && apt-get -y dist-upgrade
RUN apt-get install -y --no-install-recommends bzip2 wget

RUN wget --no-check-certificate https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh && \
    bash Miniconda3-latest-Linux-x86_64.sh -bf && \
    rm Miniconda3-latest-Linux-x86_64.sh
ENV PATH="/root/miniconda3/bin:${PATH}"

RUN conda install -c conda-forge graphviz=2.38.0 xorg-libxrender xorg-libxpm

CMD dot

I don't know if they should be added as dependencies or if a fancier solution is required?

Did you install the yum requirements from the recipe? Note the names may be different for apt-get.

Just install everything listed in yum_requirements.txt. There is currently no gtk2 package. Using X11 condapackages as dependencies is an ongoing discussion.

I understand. May I ask why you're reluctant to add it as a dependency? Is it because conda-forge doesn't want large dependencies that the majority of the users would already have installed? If so, is there a list somewhere of these programs that are considered "outside of conda"? Thanks!

@rasmusagren, the simplest way for you to solve this for now is to install an X server in your server.

Thanks, but the solution with xorg-libxrender xorg-libxpm works for me right now. I still think that all dependencies should be included in the recipes, in particular as docker and singularity are becoming so popular and there people often use slimmed down distributions.

Should add put up PR ( https://github.com/conda-forge/staged-recipes/pull/3920 ) for gtk2 some time ago, which is the only package we are getting from yum here. Not sure if that is enough to make this installable from conda alone or if there are more issues hidden.

So, no gtk needed.

Ha! No wonder. :)

Fixed by #23.


Question: Server-side authentication

Hi there,
I was wondering if it would be possible to have a route protected by some server-side authentication.
Simplest example:

Auth page (public)
Secret page (loaded only if authenticated)

Most importantly, the data (including layout / content of the page) cannot be transmitted unless the client has successfully authenticated. I was hoping to use import and have the server only return the component if the user is authenticated but don't know how to hook into this tool (or if it is possible).
Thanks in advance!

Yes, here's how I handle this (going to mainly copy and paste some code I'm using)
I create a Router component with all my routes and a getInitialProps method that refreshes the session (the example below uses apollo)
const routable = (Layout, Page) => props => <Layout {...props}><Page {...props} /></Layout>

export default class Router extends React.Component {
  static async getInitialProps (ctx) {
    await Router.refreshSession(ctx)
  }

  static async refreshSession (ctx) {
    const token = getTokenFromReq(ctx.req)
    if (!ctx.store.getState().session.user && token) {
      try {
        const res = await ctx.apollo.query({ query: authUserQuery })
        ctx.store.dispatch(setSession({ user: res.data.authUser }))
      } catch (err) { // invalid or expired token
        ctx.apollo.resetStore()
        ctx.store.dispatch(removeSession())
      }
    }
  }

  render () {
    return (
      <Switch>
        <Route exact path="/welcome" render={routable(Landing, Welcome)} />
        <Route exact path="/register" render={routable(Auth, Register)} />
        <Route exact path="/login" render={routable(Auth, Login)} />
        <Route path="/" render={routable(App, Dashboard)} />
      </Switch>
    )
  }
}

Then I create some middleware for handling authentication
const isSessionUser = (ctx) => ctx.store.getState().session.user

export const loggedInOrRedirect = (ctx) => {
  if (!isSessionUser(ctx)) {
    ctx.redirect('/welcome')
  }
}

export const loggedOutOrRedirect = (ctx) => {
  if (isSessionUser(ctx)) {
    ctx.redirect('/')
  }
}

and I use this middleware inside my AppLayout and AuthLayout etc. getInitialProps method
export default class AuthLayout extends React.Component {
  static async getInitialProps (ctx) {
    await loggedOutOrRedirect(ctx)
  }
}

Your Router will be the top most component and be called first, so session will be refreshed prior to running middleware inside Layout/Page to check whether user is authenticated
I plan on adding an example of this, and maybe even including this by default in starter template since everyone needs authentication for an app
But I hope it helps for now! Closing this

Thanks so much for the quick reply! I'll try this out.


addIndex on reduceWhile, provide index to both predicate and iterator?

Hi, beginner question here.
I find myself in a situation where I want to wrap reduceWhile in addIndex. I want to access the index in both the predicate and iterator function.
I know I can flip() reduceWhile to choose the other one if I so please, but I need it in both.
Can this be solved with some existing ramda function I've missed?
If you're curious, I'm doing advent of code 2019, day 2 part 1. That's the scenario where I need this to work.
Contrived example, perhaps, but my challenge is to solve it as ramda-functional as possible.

No, I don't think Ramda has anything particularly helpful here.  I certainly have never thought about that before.
I'd be interested to see how that would help you with the problem.  I solved it recursively, and it seemed fairly simple, straightforward code.

Actually I had an extra self imposed restriction on that challenge - don't use recursion. Overly complicating it most likely.

@karlmacklin  it might help to zip the indexes and values together then reduceWhile over the pairs.
If you run into more issues it might help to look into the Ramda chat room which might get you help a bit faster, or get you more input.

Here is an only-slightly tested version:
const addIndices = (fn) => (...args) => fn (... [
  ... init (args) .map (
    arg => is (Function, arg)
      ? (...args) => arg (...[...args.slice(0, -1), ...args[args.length - 1]])
      : arg
  ),
  zip (last (args), range(0, args .length))
])

addIndices (reduceWhile) (
  (a, x, i) => x <= i,
  (a, x, i) => `${a} (${x}:${i})`,
  'start',
  [0, 0, 1, 2, 9, 4]
)
//=> "start (0:0) (0:1) (1:2) (2:3)"

It might also be cleaner to abstract something like
const spreadLast = (fn) => (...args) =>
  fn (...[...args.slice(0, -1), ...args[args.length - 1]])

and replace
    arg => is (Function, arg)
      ? (...args) => arg (...[...args.slice(0, -1), ...args[args.length - 1]])
      : arg

with
      arg => is (Function, arg)
        ? spreadLast (arg)
        : arg

This assumes that all function parameters need to be updated.  I can't think of a better alternative, but as with R.addIdx, that is problematic in the general case.


restoreSnapshot trouble

Hi, I'm having a hard time restoring a machine from a snapshot. This is one of the many things that I've tried, and this has gotten me the closest:
`import virtualbox
vm = virtualbox.VirtualBox().find_machine('test')
vm.restoreSnapshot()`
but then I get the error: AttributeError: 'IMachine' object has no attribute 'restoreSnapshot'
and by reading this page on the documentation (https://www.virtualbox.org/sdkref/interface_i_machine.html#a5b696740ceccb14750718e2648d6928c) it seems as though iMachine does have an attribute of restoreSnapshot. Any ideas?

You can't use it directly on a machine, you have to use it from a session.
Check out MachinePool in pool.py for an example.


is not a map for `map-has-key' error

Hi,
I use breakpoint, but when my sass file should be compiled I get this error:
Line 5 of C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/breakpoint-2.7.0/stylesheets/breakpoint/_settings.scss: $map: ((48.0625em 51.8125em), (27em 39.125em)) is not a map for map-has-key'`
This error is in place where I want to import breakpoint.
What is wrong?

I'm also having this issue and haven't solved this yet.


Explore Helm Go-Client to replace helm as dependency on CLI

Overview

[ ] explore tools like https://github.com/mittwald/go-helm-client to replace helm binary by golang calls.

notes

tiller is not needed anymore on newer versions of helm.

We no longer use the Helm binary and downloading it has been removed.


Typescript issue with includes in tsconfig

🔎 Search Terms
tsconfig includes
🕗 Version & Regression Information
Version: 5.2.2/ 5.1.6
⏯ Playground Link
No response
💻 Code

🙁 Actual behavior
I created a new file that is included in the includes in tsconfig, but it keeps on nagging me that the file
File '/home/path/to/file/resources/js/views/TestNewView.vue' is not listed within the file list of project '/home/path/to/file/tsconfig.app.json'. Projects must list all files or use an 'include' pattern
🙂 Expected behavior
there shouldn't be any error since the pattern is included already
Additional information about the issue
restarting vscode seems to fix the issue, but will occur again for other new files

Does this happen for .ts files or just for .vue files?

it seems to only happen with .vue files only

Can you please share tsserver verbose log for the same.
You can upload logs by following these steps:

Set "typescript.tsserver.log": "verbose"
Restart vscode or vscode insiders
Reproduce the problem
In vscode or vscode insiders, run the TypeScript: Open TS Server log command
This should open a large file called tsserver.log. Please share this file.

here you go. thanks
tsserver.log


Set c++14 as standard

Attempting an install on Ubuntu 22.04, with gcc 8.4.0 and cmake 3.22.1.
Within project's root folder, created a build directory, moved into it, and ran cmake ../ (no libtiff location, I just wanted to test if it was possible installing the library without first installing libtiff and providing its location).
That returned:
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/msalinas/Documents/standalone-installations/EerReaderLib/build

So far so good, but then, I ran make, which returned the following error:
[ 10%] Building CXX object CMakeFiles/EERReaderLib.dir/Bitmap.cpp.o
[ 20%] Building CXX object CMakeFiles/EERReaderLib.dir/DefectMaskingEER.cpp.o
[ 30%] Building CXX object CMakeFiles/EERReaderLib.dir/EerFile.cpp.o
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp: In function ‘void Fei::Acquisition::EerReader::{anonymous}::TagExtender(TIFF*)’:
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
         };
         ^
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp: In member function ‘std::unique_ptr<Fei::Acquisition::EerReader::EerFrame> Fei::Acquisition::EerReader::EerFile::GetNextEerFrame()’:
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:89:29: error: ‘make_unique’ is not a member of ‘std’
             eerFrame = std::make_unique<EerFrame>(m_tiff.get());
                             ^~~~~~~~~~~
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:89:29: note: ‘std::make_unique’ is only available from C++14 onwards
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:89:49: error: expected primary-expression before ‘>’ token
             eerFrame = std::make_unique<EerFrame>(m_tiff.get());
                                                 ^
make[2]: *** [CMakeFiles/EERReaderLib.dir/build.make:104: CMakeFiles/EERReaderLib.dir/EerFile.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:100: CMakeFiles/EERReaderLib.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

There are also some warnings, but, what is really concerning is the error: 'make_unique' is not a member of 'std'
After a quick search, I found out that such function is included in c++14, and that it can be used from gcc / g++ >= 5 if c++14 is enabled.
After the proposed change, compilation now returns a different error (but completes a greater percentage of the compilation, so there was some progress):
[ 10%] Building CXX object CMakeFiles/EERReaderLib.dir/Bitmap.cpp.o
[ 20%] Building CXX object CMakeFiles/EERReaderLib.dir/DefectMaskingEER.cpp.o
[ 30%] Building CXX object CMakeFiles/EERReaderLib.dir/EerFile.cpp.o
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp: In function ‘void Fei::Acquisition::EerReader::{anonymous}::TagExtender(TIFF*)’:
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
         };
         ^
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
/home/msalinas/Documents/standalone-installations/EerReaderLib/EerFile.cpp:53:9: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
[ 40%] Building CXX object CMakeFiles/EERReaderLib.dir/EerFrame.cpp.o
[ 50%] Building CXX object CMakeFiles/EERReaderLib.dir/ElectronCountedFramesDecompressor.cpp.o
[ 60%] Building CXX object CMakeFiles/EERReaderLib.dir/GainDefectCorrect.cpp.o
[ 70%] Building CXX object CMakeFiles/EERReaderLib.dir/stdafx.cpp.o
In file included from /home/msalinas/Documents/standalone-installations/EerReaderLib/stdafx.h:10,
                 from /home/msalinas/Documents/standalone-installations/EerReaderLib/stdafx.cpp:7:
/home/msalinas/Documents/standalone-installations/EerReaderLib/targetver.h:10:10: fatal error: SDKDDKVer.h: No such file or directory
 #include <SDKDDKVer.h>
          ^~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/EERReaderLib.dir/build.make:160: CMakeFiles/EERReaderLib.dir/stdafx.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:100: CMakeFiles/EERReaderLib.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

So, my idea is to merge this change, and then maybe open an issue to try to figure out what else is missing to complete the installation.

I appreciate your suggested fix, which I will merge.
However, please note that this library currently relies on Windows-specific include dependencies, like targetver.
Therefore, I recommend that you create an issue to help ensure compatibility with Linux, as building it on Linux is not currently possible.
Thank you for your contribution and support.


When embedding web fonts, fonts need to be minimized to ensure svg+xml parsing performance

embed-web-font.ts

(。・＿・。)ﾉI’m sorry~
This part of the feature is currently not available for open source


Timeout reported by broadcastTxCommit

When executing transfer with demoappd, I see following errors:
ERR Error on broadcastTxCommit err="timed out waiting for tx to be included in a block" module=events

Error is also returned to the client:
Error: RPC error -32000 - timed out waiting for tx to be included in a block

Transfer is successful (can confirm balance change), but reported as timeout. This may be related to custom block time, or some issues with event bus.

related:

https://github.com/celestiaorg/celestia-core/blob/1609bde2a41604fff1ebcb202e0e9cce1048fb3b/config/config.go#L479-L483
https://github.com/celestiaorg/celestia-core/blob/0ed8dba99189e3dfd960a8945192c6146c47dc9d/rpc/core/mempool.go#L123

So could just try to make this roughly the block time instead.

Duplicate of https://github.com/rollkit/rollkit/issues/1036


BGD-5201 - Ocean spark fix double submit

Jira Ticket
BGD-5201
Demo
before
each time a sparkapp is created, the spark-operator receive 2 times the event with newstate.
-> the spark-operator will try to submit 2 times for each spark app
fortunately, the second one is skip because it is able to know if it was already submitted.
But if the first submission failed, and then the second one works,
the CRD state will be FailedSubmission even if the second one success, that's because the submission should not be retry.
W0604 11:29:29.276145      12 submission.go:75] trying to resubmit an already submitted SparkApplication spark-apps/dma-simple-pi-with-optim-a1f5a-flits
W0604 14:37:10.693116      12 submission.go:75] trying to resubmit an already submitted SparkApplication spark-apps/dma-pi-test-sel-optim-20ec0-goofy
W0604 16:30:38.682624      12 submission.go:75] trying to resubmit an already submitted SparkApplication spark-apps/dma-thread-stages-transition-336aa-cheep

With the fix
on the log, this time the spark-operator will not try to skip it
I0604 17:25:34.742185      11 controller.go:579] submission attempt already done for: "spark-apps/dma-pi-double-submit-59b94-farad", skip it

Note
I can't test the situation when the first attempt failed, and the second one success, too complicated to simulate it on real case.
But I create a unit test for that.

trying to resubmit an already

After up to date the PR to the upstream branch ocean-spark, the previous approval was discard.
Can someone re-approve? @crezvoy @alextarasov-spot @epignot  🙏
current PR was re-tested on DP
I0821 12:05:58.486497 10 controller.go:579] submission attempt already done for: "spark-apps/dma-pi-test-dbf11-ibsen", skip it


fix: pod name with invalid character

pkg["name"] resolves to a scoped package name: @vforvasile/react-native-photos-framework, which is not valid pod name AFAIK. Changing it to the same name as the podspec file is named, which is an established practice.

You could also do: pkg["name"].split('/')[1..-1].join('/')
Just encountered your PR to fix my own package :) thanks


Fix for build script on internal branch with gmock

Need to add additional defines for gmock flags

Not needed anymore


Start of ACM identification

Pull Request Overview

Implementing commit for a real detection config
mocked up for now, depends on IA config work
something wrong with the message to Sage, it's rejecting it and I don't know why

/rebase

/rebase

/rebase

looks good, give or take the bits we are still ironing out (ia config, sage/wbia to-be-developed).
i do wanna ask drew about something, so going to dump that in #devhouston right now.

one-or-many detection config seems resolved via discussion in devhouston.  1 detection for mvp, more later.


Hide masthead from splash page

Hi, is there a parameter I missed that could hide the masthead on a specific page?
I would like to do that on my home page (a spash-page).
Thank you!

Add some CSS to the page you want to hide masthead from. It could be as simple as
body.layout--splash .masthead {
  display: none;
}

https://mmistakes.github.io/minimal-mistakes/docs/stylesheets/

Thank you very much for the quick answer! It worked fine.
OMG it is so easy, I love it.


@xtina-starr: Clarify how to deploy

          1 Warning

:warning:
Please include a PR summary

  Generated by :no_entry_sign: Danger

Nice!! Thanks 😄


wip: ci: add step to push to aws ecr too

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This PR adds a job to build and publish a container image to AWS public ECR registry.
Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
We try to make OCI artifacts highly available by hosting them on different public registries like Docker Hub and AWS ECR.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: maxgio92
To complete the pull request process, please assign cpanato after the PR has been reviewed.
You can assign the PR to them by writing /assign @cpanato in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This is a work in progress, as the AWS ECR repositories need to be in place before trying to push images to them.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, maxgio92
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for merging this, will tagged images also get pushed here (instead of latest)?
I would like to use it in the falcosidekick helm chart like so:
image:
  registry: public.ecr.aws


Shareable config for the strict security rules?

I think it would be nice to have a sharable config that turns on all of the new security rules, so teams can turn off just the ones they don't want and automatically get new ones turned on as they're included (as a way to keep abreast of new best practices)

@beaugunderson if you simply specify"plugins: ["security"] in your soliumrc, then by default ALL non-deprecated rules inside that plugin will be enabled (all security rules are by default specified as error).
Any new rule that we add to the plugin WILL be automatically enabled when the user updates solium (provided that they have the "plugins" property set).
To turn off or change a specific security rule to warning, user needs to separately modify the rule like "security/no-throw": "off".
Is this^ what you wanted to achieve? If yes, then its already covered. If no, could you point out the diff.?

@beaugunderson does the above resolve your issue or did I miss something?

@duaraghav8 i think 'everything on' works for Augur, but not sure if it should be default behavior of specifying the plugin, since some of the rules are more draconian (like no-user-defined-modifiers)

you're right. I think we can write a sharable config solium-config-augur which augur can use since not all the security are desirable to all devs.
How this will work is

If you just use solium with default settings, it will apply some security rules and turn off some (especially the [Optional] ones)
If you apply augur sharable config on top, it applies all security rules. Otherwise you can choose to enable whatever rules you like inside soliumrc.json

I can publish this config, but I believe it is better suited for augur to keep it in their organisation?


I will fix the responsiveness of all the pages

Category

[ ] Documentation
[ ] Resource Addition
[ ] Codebase
[x] User Interface
[ ] Feature Request

Description

I will fix the responsiveness of all the pages, please assign me this issue under JWOC '24

You're assigned.


Refactor kubeadmin renewal code

Mostly code movement to group most of the renewal code in cluster/kubeadmin.go
This should not have any user-visible change, apart from an added log line when
the kubeadmin password is renewed.

/lgtm


Remove Preview as Feature is GA already

The feature is already GA - Azure Update but the docs still indicate that it is in preview.

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

ID: 3de54e65-8484-42e4-0193-0caa0d5e7d94
Version Independent ID: 8c968dfa-e851-e832-e9bf-8115930fbcc8
Content: Audit queries in Azure Monitor log queries - Azure Monitor
Content Source: articles/azure-monitor/logs/query-audit.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@mikhailalmeida Thanks for your comment! We will review and provide an update as appropriate.

@mikhailalmeida I have verified and updated the document as required. The update should go live soon i.e., in less than 24 hours. Thanks again!


Track stdout and stderr of child processes

In util.py we need to get the output ofstderr and print it in case of exit code other than 0 and also output the stdout in case of verbose builds.

This is done in more recent bockbuilds; exit codes are now never ignored.


Pyroscope forwarding through Alloy

Request
Currently, Alloy only supports forwarding pyroscope profiles scraped from pprof endpoints, eBPF, and Java. It would be great if Allow could act as a general Pyroscope proxy, exposing an HTTP endpoint sink that can accept submitted profiles and forward them to a deployed Pryroscope instance or Grafana Cloud.
Use case
The pyroscope SDKs offer support for many languages. However, using the SDK to push profiles to Grafana Cloud in certain environments can be problematic or difficult due to network restrictions and secrets management.
Many other solutions (Vector, Grafana Agent, etc), support models where metrics, logs, traces, etc can be pushed to a private (or even local) endpoint that then forwards to a hosted service.
Having Alloy act as a Pyroscope forwarder / proxy allows for secure and scalable deployment models where applications can push profiles to a local Alloy agent (e.g. k8s Daemonset), which then further route profiles to an Alloy agent with public internet access and Grafana Cloud credentials configured.

Hi @jalaziz! Thank you for raising an issue. I'm going to close this one, because it seems to be a duplicate of #270.


undescriptive installation guide

the guide is reasonably friendly to people already used to more "programmy" endeavours and don't really know minecraft extremely well, but not the other way around. as someone who loves the game and is a huge ai enthusiast, but doesn't actually get their hands dirty often, it is very frustrating and demotivating to get this close to getting this incredible project running, only to be met with strange errors, not knowing if it assumes you've installed something already, or if i missed a step, or if i'm not using the right command prompt. "well, cmd worked this far, but now it's just not working anymore. this bit of code looks different from the rest. should i have put it somewhere else? i should probaby be using the python one, but that failed at step 1, so what am i doing wrong?" i get that casual minecraft players don't often go to github pages to run AI projects locally, but this is such a fantastic thing i was so happy to find out you could just run by yourself, that i couldn't help but try. i got really worried when i saw "Python Install: (BOX OF CODE)", and heartbroken when even after over an hour of trying to fix it, a handful of stackoverflow threads and tutorial posts on developer websites, i couldn't get past a single error that didn't even get a passing mention in the installation guide. there's not even a discord server or overall group where you can talk to people and ask for support, which is what led to me writing in the github issues page instead. i would deeply, truly love to make a world and play with this, but i simply don't know how. i hope we can get a more beginner-friendly guide soon, or at least a tutorial video or a discord server or something.
just in case, if anyone's willing to help, i'm aedenuniverse on discord. i would be thrilled if someone helped me with this. thanks

Hi, I would like to know what problems did you encounter? Could you please put the errors here?

it became too confusing for me to follow with all the azure stuff; i had tried skipping it but it gave me a "from is not recognized as an internal command" error. i'd love to be helped on discord if you'd like, but i also find it important to make a clearer guide in general for other folks who might run into the same troubles as me

it became too confusing for me to follow with all the azure stuff; i had tried skipping it but it gave me a "from is not recognized as an internal command" error. i'd love to be helped on discord if you'd like, but i also find it important to make a clearer guide in general for other folks who might run into the same troubles as me

Now, running the code in Azure login mode is not available. Using the mc_port mode.

Using the mc_port mode.

You should add instructions on how to do that.

Using the mc_port mode.

You should add instructions on how to do that @GoingMyWay

Using the mc_port mode.

You should add instructions on how to do that @GoingMyWay
azure_login = { ... }
voyager = Voyager(
    azure_login=azure_login,
    openai_api_key=openai_api_key,
)

or
mc_port = <port provided by minecraft>
voyager = Voyager(
    mc_port=mc_port
    openai_api_key=openai_api_key,
)

Right. The example code in README is the code for the Azure login mode.


if upstream is down, authentication JWT is not cached

What happened?
If a destination TCP upstream is down, Pomerium serves HTTP 503 and JWT auth token would not be persisted by the CLI.
That causes two issues:

the need to open auth URL next time an authentication attempt is made, which, in case it is done by some software that auto-retries connections, will keep opening user's browser over and over again.
there is no indication to the user of the underlying root cause (destination upstream down).

What did you expect to happen?

JWT auth token persisted by the CLI
have a better user error message

I think it's reasonable to cache (TOFU) the JWKS.

have a better user error message

Is probably not possible. We intentionally don't provide detailed error messages. It's considered a security leak.


Support for -var on Terraform plan

Any plans to support the command line option -var on the plan command?
Regards, Lars

Hi @Lars-Kolsaker. You can supply -var or -var-file in the commandOptions field. E.g.
- task: TerraformCLI@1
  displayName: 'terraform plan')
  inputs:
    command: plan
    environmentServiceName: 'My Azure Service Connection'
    commandOptions: '-var "my_variable=testing123" -var "my_other_variable=123456"'

Example usage here: https://github.com/Azure-Samples/azure-devops-terraform-oidc-ci-cd/blob/e1d267c3baa370516a7614f978ff0c1080868c91/pipelines/oidc.yml#L102

Thanks


ci(labels.yaml): add labels to test-ui-ci when touching code there

Description
Add test-ci-ui label when we're touching files under ui/

@iranzo just a question...Have you tried manually the label in a PR at least?

The label is assigned on all Marek PR's and have got the CI executed there, and the autolabelling is in all the PR's in the repo since long ago

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


Request access to apex organization

If you'd like access to the org to help contribute or help create Apex runtimes, leave a comment!

:hand:

Test

@tj Could you share your short-term and long-term goals and vision for apex with the community so we know where the project is heading? What helps do you need to most?

Hmm yea I've been meaning to do some sort of roadmap, as far as help goes pretty much anything in the issue queue! I've been focusing on nailing the function/overall experience before moving on to other things like bootstrapping resources. Ideally someone can figure up functions with a brand new AWS account and no other work.

If you want to add me I'll help out with some docs as I learn it and maybe write a few generic modules that could at worst serve as examples.

Great project! I'd like to contribute to add Scala support!

@tj I would love to help with this project. I can work on the "contrib (easy)" tags such as adding self-upgrading and implementing CI. I have experience working with Go.

awesome! everyone should have an invite

I would like to help some easy features first. Hopefully contribute more.

I'd love to help out. There's some interesting things I've been messing with in my own projects for Node on Lambda that I'd love to see if they fit with the project (using Webpack, Babel, etc.) and I can also help with the contrib (easy) ones as I'm still learning Go.

I'm interested of helping with the project.

added everyone!

i'm interested in contributing as well probably #150 initially.

I'm interested too!

Hi, what about if apex deploy would work with different cloud providers ? or perhaps some sort of docker integration. I'm thinking in providers like iron.io, maybe Google cloud, and others.  I love the whole idea of lambda but it worries me to be locked in AWS platform.
I'm asking here, because somehow is related to possible future contributions let me know if there is a better issue to discuss it, if you are interested.

@alfonsodev http://apex.run/#faq's "Can I test functions locally?" is my typical answer to lock-in. I have for example ~20 functions in my first app, but maybe ~40 lines dedicated to Lambda, I could easily move providers as long as they provide similar features.
I have mixed feelings about supporting many providers, it would certainly make things more confusing, and you could potentially miss out on provider-specific features. Personally that's not something I'm interested in right now, since I'm happy with Lambda, but possibly in the future

I'd like to move Apex forward.
I will fill missing docs, work on issue which is tagged contrib (easy) and Apex website, trying to implement local invoke feature, and yes. i'll do my best to contribute.

@mooyoul sent an invite :D. Local invoking is something we probably won't add though actually, it would be very hard to replicate the entire AWS environment so it would have limited use. I generally recommend just placing most logic in packages and test those


feat: edit/delete concept + error handling

Fixes https://github.com/Informasjonsforvaltning/catalog-frontend/issues/152

deploy feilet


[FLINK-19441][network] Avoid loading of ResultPartition wrapper class for consumable notifications when possible.

What is the purpose of the change
A small code optimization attempting to reduce the virtual method call overhead on the per-record methods in ResultPartition.
It does that by making the class wrapping the ResultPartition (formerly ConsumableNotifyingResultPartitionWriterDecorator) a different class than the one with the factory method. That way, if the factory method never needs a wrapper class (under normal configuration, it never needs one) the wrapping class is never loaded, and the JIT can find out (through CHA) that only one implementation for the per-record methods on ResultPartition exists.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): yes
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Adjusted the code to make the role of the utility class more clear.


Update vscode

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Every time I update this package, I have to do the exact same steps every single time. So I wrote a script to automate most of this (it just prints out the various bits of the derivation that need to change), and checked it in as part of this PR.
Is this OK?

The license should remain unfree as the binary version is distributed under EULA.

Hey, I don't know much about licenses, so more than happy to back out the change, but would really appreciate some more detail.
When I go to the GitHub page it says MIT, what exactly makes this package unfree?

The source is MIT licensed but the pre-built binary from Microsoft that we are using falls under the "MICROSOFT SOFTWARE LICENSE TERMS". It specifically states that "You may not [..] share, publish, or lend the software [..] to any third party", thus making it unfree.
We would have to compile it from source ourselves to create a binary we can distribute freely.

VS Code is currently at 1.10.2 so this PR would be downgrading. Can it be closed?


failed to collect metrics: error Tag at: 32  Configured ebgp ECMP multipath: Currently set at 32

Hello,
Thank you for publishing such great exporter!!!
Unfortunately, when I tried to execute it, I encountered the following difficulties.
I would be happy if you could solve it.
root@edgerouter-x:~# [2022-01-28T09:14:20Z ERROR] failed to collect metrics: error Tag at: 32  Configured ebgp ECMP multipath: Currently set at 32
    1  Configured ibgp ECMP multipath: Currently set at 1

    Neighbor                 V   AS   MsgRcv    MsgSen TblVer   InQ   OutQ    Up/Down   State/PfxRcd
    <IP_ADDRESS>           4 65002 7990       8014     159      0      0  1d19h46m               5
    <IP_ADDRESS>           4 65002 7988       8010     159      0      0  1d19h45m               5
    <IP_ADDRESS>           4 65002 7989       8012     159      0      0  1d19h45m               5
    <IP_ADDRESS>           4 65002 8029       8041     159      0      0  1d19h45m               5
    <IP_ADDRESS>           4 65002 8029       8043     159      0      0  1d19h45m               5
    <IP_ADDRESS>           4 65002 8029       8040     159      0      0  1d19h45m               5
    <IP_ADDRESS>           4 65002 8028       8046     159      0      0  1d19h44m               5
    <IP_ADDRESS>           4 65002 8143       8126     159      0      0  1d19h21m               5

    Total number of neighbors 8

    Total number of Established sessions 8

Hi!
Thanks for raising this issue. It turns out that the current parser implementation does not correctly handle BGP configuration with maximum paths enabled. I've just pushed the fix to add support for this setting that should do the trick!

Please try v2.0.1 and let me know if you could find something to feedback!

Hi,
v2.0.1 had solved this issue!
Thank you for your quick bug fix!!!


Test that UI indicates terminal activation when activating using environment variables

Refs: #21793

[ ] windows @amunger
[ ] linux @lramos15
[ ] macOS @aiday-mar

Complexity: 5
Create Issue

Requirements
Similar to https://github.com/microsoft/vscode-python/issues/21102 hence preassigning.

Python extension pre-release
Latest VSCode Insiders
Ability to create virtual environment

Use python -m venv <name> to create virtual envs.

Ability to create conda environment

Install conda via: https://conda.io/projects/conda/en/latest/user-guide/install/index.html. Make sure it's on PATH during installation.
Run conda init --all & restart the shell.
Create conda env using conda create -n <name> python -y.

Basic terminal shell types, please tick whatever is available in your OS:

Windows:

[ ] cmd
[ ] powershell
[ ] powershellcore

Linux:

[ ] bash
[ ] zsh
[ ] fish

macOS :

[x] bash
[x] zsh

Nice to have:

[ ] sh
[ ] ksh
[x] csh
[x] tcsh
[ ] nushell
[ ] xonsh

Verification

Add following to user settings and reload window:

"python.experiments.optInto": ["pythonTerminalEnvVarActivation"]

Run conda config --set auto_activate_base True.

Open a workspace folder and activate Python extension by opening a Python file.

Select a virtual environment using Python: Select Interpreter command.

Loop -> Do the following for all terminal shell types:

Open a new terminal.
Ensure we indicate the env is activated in at least one of the following ways:

Terminal prompt carrying selected environment's name is present:

Notification appears, simply close it for now:

Make sure terminal is activated using the selected environment. Run the following in terminal:python -c"import sys;print(sys.executable)"

Output should contain the path to interpreter selected. For eg. for .venv created via python -m venv .venv it looks something like:C:\Users\karraj\OneDrive - Microsoft\Desktop\folders\crap\.venv\Scripts\python.exe

Change the default shell in your OS using Terminal: Select Default Profile, say bash->fish

Select a conda environment using Python: Select Interpreter command and repeat the above loop.

If the notification was visible at some point:

Verify clicking "learn more" opens this wiki.
Verify that opening a new terminal after clicking "Don't show again" does not show the notification.

Not ready this iteration.

Not ready this iteration.

This isn't working for me at all:
After running conda config --set auto_activate_base True, it always just activates the base conda environment, not the interpreter I have selected.
Before I ran that, the environment never activated, but I get the notification: https://github.com/microsoft/vscode-python/issues/21887

Yes you can ignore that for now. Please run the Python command specified to see which environment is actually activated.

This isn't working for me at all:

Me and Aaron discussed here that it actually works: https://github.com/microsoft/vscode-python/issues/21887#issuecomment-1697866886, but it was the same confusion that @eleanorjboyd has, which is that it always shows (base) regardless of which env is actually activated.

@lramos15 Were you able to test for zsh and fish on Linux?

@lramos15 Were you able to test for zsh and fish on Linux?

Oh I do not have those installed, do I need to install them for the TPI. I got confused by the wording please tick whatever is available in your OS which made me think it was test what you have.

Sorry, if you could install them that would be great. Our codespaces already has it pre-installed so you can also use that, thanks!

Sorry, if you could install them that would be great. Our codespaces already has it pre-installed so you can also use that, thanks!

Done 👍


nixos/i18n: add extraLocales option

This adds a new i18n.extraLocales setting for installing additional locales not specified in i18n.defaultLocale or i18n.extraLocaleSettings. This is useful when you need to run isolated applications that requires a specific locale not used by the rest of the system, for example when running certain Japanese games in a wine prefix.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4948

supportedLocales = lib.mkDefault [ "...." ] is not working for this usecase?

Not exactly sure what you mean, can you elaborate?


Allow for multiple sizes as an option / make it easier to see larger groups of people

I'm only able to see at most 4 people from any given timezone. It would be great if we could have the option of hiding the image or make it possible to have a smaller image shown. For example, if the image was ~1/4 the size with the username + full name to the right of it. Or if the image could be 1/8 the size with either the username or the full name shown.
Neat tool. :)

Oh! It should be worth noting that there are at least two people missing from that right column.  Still, it would be nice to use this for larger teams that have their timezones spread out more.

I don't want to add options, but I would accept a PR which uses max

Sorry, misclick :cold_sweat:
I'm working on a fix now to add vertically responsive user images using max-height. Thanks for the issue report!

Hope this helps. In production now.

Yes, this is an interesting start. It is funny though because for me in my environment at browser full screen I get the exact same view. I only get smaller icons if I make my browser window shorter.
https://www.dropbox.com/s/11go97x5kkx7bds/teamtimezone.mp4?dl=0

Either way, I appreciate that you don't want to make options. :) It's still awesome and I'll still probably use it for now even as-is! Thanks for the quick feedback!


⚠ Jurnal has degraded performance

In e445d68, Jurnal (https://jurnal.unmer.ac.id) experienced degraded performance:

HTTP code: 200
Response time: 8406 ms

Resolved: Jurnal performance has improved in 60895ee.


Diagram should auto-save with the keyword it was loaded with

From<EMAIL_ADDRESS>on May 24, 2009 16:07:55
With the latest checkout, I have to

Click on "Save / Load"
Click On "Save"
Type keyword
Confirm (Ok/Enter)

to save the drawing. If the drawing was previously loaded, perhaps it could
be auto-saved. Even a one-click option to save it with the current keyword
would be very helpful indeed.
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=19

From ondrej.zara on May 25, 2009 23:42:59
Status: Accepted
Owner: ondrej.zara
Labels: -Type-Defect Type-Enhancement

From ondrej.zara on November 04, 2009 01:29:15
The "load" and "save" prompts now have a default value, equal to the latest keyword used.
Status: Fixed


How to prevent rogue tasks

Lets say I set up PAC for a repo with associated Kubernetes namespace. Aside from careful PR review policies, what's to stop someone modifying the PipelineRun in .tekton to include a taskSpec to egress the service account token (probably pipeline with edit role) - giving persistent access to that namespace?
Should there be a mode to only allow pre-approved tasks rather than allowing inline taskSpec? Or at least include a security section in the docs warning about this?

@jimmyjones2 users are supposed to be "trusted" and already have an access to the cluster to be able to run "CI". We don't let any CI run unless the users is an "owner/collaborator" on the repo or explicitely approved with the /ok-to-test on or inside the OWNERS files.
If you don't trust those users you probably are looking to run an open policy agent https://www.openpolicyagent.org/docs/latest/policy-language/, I am not an expert on this but i know some teams at Red Hat runs this to only have an "allowed list" of tekton bundles to be allowed to be run on tekton/PAC.


ROS2 Update

Just opening up this issue since I couldn't find anything regarding Astrobee and ROS2. Are there plans for the port? At KTH we are starting a new lab in which we plan to use Astrobee-analogues and we are planning to go for ROS2 from the start, so we would be interested in contributing to this effort (tagging @marinagmoreira @bcoltin @trey0 ).

Hi, Pedro!
We are very interested in eventually migrating to ROS2, but there are a lot of complicated issues tied up with it.
A piece of good news is the Astrobee flight software team will have a small stream of new funding to study platform modernization, which can include considering both ROS2 and its Space ROS extensions. But I wouldn't expect to get to a fully supported ROS2 build for a while.
For one thing, our team is already burdened with supporting the software sim in Ubuntu 16.04, 18.04, and 20.04 (with their respective different ROS1 versions and third party library versions), so multiplying that sounds painful. There is an active effort preparing to migrate the Astrobee hardware units from 16.04 to 20.04, which should allow us to deprecate the older versions and simplify the code base a lot. It would be great if we could complete that simplification before investing seriously in ROS2 support.
There are also lots of open questions about how to do the migration. From my perspective, the theme of the migration should be to improve software quality by moving to the new framework whose core has a higher level of QA, and keeping the software stack as simple as possible for robustness and maintainability. I would probably advocate for moving to the most recent ROS2 version that runs on Ubuntu 22.04, due to its better maturity, even though that would make our overall ROS1-to-ROS2 jump bigger, and also against pursuing a hybrid build where ROS1 and ROS2 modules run side-by-side and communicate via a bridge, because I expect that might even be a step backward in terms of having more ways for things to go wrong. But these are all questions that need more study.
I think a realistic hope is to have a clear plan for this by say the end of February 2023. And it's great that you're raising the question now leading up to the next Astrobee Working Group meeting in October. We should probably use the AWG as an opportunity to ask about stakeholder needs and concerns relating to a possible migration. There's a lot of legacy code out there and we can't strand users who still have ISS activities left to run.
Something we hadn't considered is that outside developers might be able to provide a significant force multiplier for our team to help with the transition. That could make a big difference! So that's another place for more discussion. Thanks for raising this issue!

Hi @trey0!
I see a very close alignment between your thoughts and ours here. We also do not believe that a good way forward is to still be tied to ROS1 since that is deprecated, and bridges would be another failure point that we wish to avoid. SpaceROS is on our minds too, but since there is no clear release yet (at least for public/academic users), we think that might go to the second plane. Right now the priority would be to go to ROS2+Ubuntu 22 (and perhaps even think about a way to make the dependence of Ubuntu 22 away - ROS2 on Arch, as then we could use lighter OSs both on the platforms and on our dev systems, but this is also second plane thought).
Indeed, having outside developers running the platform can have a significant contribution to the Astrobee - afterall, isn't that the benefit of Open-sourcing it? 😃 Since there exist already important guidelines in place (cpp format / PEP compliance , documentation standards), this shouldn't be a big hurdle.
On our side, we are 4 PhD's that will be using the software, and I believe across the Astrobee WG there are many more. Let's talk at the AWG, but probably until then we might start working on a tentative migration of a few modules. We will bring some ideas/points to see how to go forward.
Cheers!

While we don't have anywhere better to put this, here are some notes from a meeting we had:
Migrating to ROS2 Recommendations:

Use rolling version to get latest features (seems that a specific release might not be complete enough). rolling can be compiled for arm in 20.04 (rolling is advertised as for 22.04), so no OS upgrade necessary for now.
Use docker to release to robot, less setup.
Use lifecycle nodes from the start
Use abstraction with rclcpp_lifecycle for things like: wrap up callbacks, scope time, diagnostics
Pipelines CPU sets (apparently you can assign CPU's to certain pipelines such that nodes in a pipeline formation don't interfere with each other), measure latency
Build system powerful but commands not intuitive, able to do things like linting/testing
Comms use fastrtps for users (Apache 2) keep using rti for robot (better), ROS2 looks for which one is available, so possibly no more separate set of instructions.

Things to try

data visualization: foxglove/webviz
development env: vscode + ssh + docker images

Others

Check what packages/libs are missing from ROS2/SpaceROS

Awesome Marina, will use these as well for the meeting ahead, thanks!

@marinagmoreira I uploaded a VS Code template we can maybe start from (unless you got something already working out), here it goes: https://github.com/DISCOWER/ros2_rollingbee_ws

There is a lot of discussion about how to potentially support multiple ROS versions in one repo branch at #562 . Perhaps we can bring the discussion back to this main thread if that experimental PR is likely to be closed.

I found this thread that mentions agnostic .xml files https://github.com/ros-infrastructure/rosdep/issues/653
and I tested it using the same xml in ros1 and ros2 and works flawlessly, all we have to do is bump the package to format 3.
Tested example: https://github.com/marinagmoreira/astrobee/blob/ros2/astrobee/package.xml

That's awesome, I looked for such an option but didn't come across that - that fixes the issue for XMLs, and we can keep what we had for CMakeLists. I also think regular meetings and dividing tasks would be good since we have overlapped @marinagmoreira (I had a devcontainer already hehe).

Tested example: https://github.com/marinagmoreira/astrobee/blob/ros2/astrobee/package.xml

Tested in ROS1 kinetic? :)
If so, it sounds great! The approach could be (1) rename package.xml to ros1-package.xml until the ROS2 coverage expands to that package, then (2) rename back to package.xml and use package format 3 with conditionals after that.

Wow, REP-149 is a great find, too. It sketches the idea of "universal packages" that compile under both ROS1 and ROS2. I had been looking for those but couldn't find them among all the migration tutorials. I just realized the conditional syntax in package.xml is something perfect to search on to find examples (see below).
I think these could be very useful to help us find the right patterns that enable universal support with minimum pain.

https://github.com/luxonis/depthai-ros - Claims to support ROS1 Melodic up to ROS2 Galaxy
https://github.com/mrpt-ros-pkg/pose_cov_ops - Found from useful discussion at https://discourse.ros.org/t/why-not-exposing-ros-version-in-the-ros-1-2-build-farms/25476
https://gepgitlab.laas.fr/gepetto/example-robot-data/-/blob/master/package.xml

Tested example: https://github.com/marinagmoreira/astrobee/blob/ros2/astrobee/package.xml

Tested in ROS1 kinetic? :)
If so, it sounds great! The approach could be (1) rename package.xml to ros1-package.xml until the ROS2 coverage expands to that package, then (2) rename back to package.xml and use package format 3 with conditionals after that.

It works for kinetic, yes.
However, I don't think we should worry about ROS1 kinetic for this migration. We're not in a rush to merge with develop and supporting 4 platforms is too much for such a small team (even 3 now is time consuming -- e.g. I spent a few hours last week fixing a build error that only happened in melodic even though we prob don't have many users on it). My suggestion is to coincide this migration with the noetic robot migration and make a "last kinetic release".

I agree that we should try not to support too many platforms at once.
In particular, let's discuss dropping melodic support again. The only reason I'm aware of that we keep support for it is that it's the native install on the NASA-internal astrobeast server. What's blocking us from upgrading astrobeast and dropping melodic support? (The last time I suggested this, the response was that melodic support was not a big time sink, but maybe that's not the case?)
Unfortunately, I think kinetic support may be needed longer than any of us would like. It's not very well-defined when the facility team can end-of-life it. There may be important legacy users (e.g., Kibo-RPC) who especially value stability and want to hold off on upgrades for a while.
There is a proposed roadmap of ROS2 migration phases on the NASA-internal FFFSW wiki (same as in some PPTX slides we shared) https://babelfish.arc.nasa.gov/confluence/display/FFFSW/ROS1+To+ROS2+Migration . That roadmap calls for merging ros2 into develop when transitioning from "Experimental" phase to "Work-in-progress" phase. However, and this is important, that comes well before the transition to "Dual-support" phase. In other words, merging into develop would not signal that ROS2 is a supported platform. The objective of merging would be to make sure that ongoing improvements to the ROS1 version flow to the ROS2 version as well by default.

o do not believe that a good way forward is to still be tied to ROS1 since that is deprecated, and bridges would be another failure point that we wish to avoid. SpaceROS is on our minds too, but since there is no clear release yet (at least for public/academic user

Yeah I used the repo you created as a base :) but worked on simplifying the Docker image so it's not 14Gb just for the base ROS install. Also that image doesn't include gazebo :(
What time would it be good for you? I'm thinking either 8AM or 9AM PST that translates to 4PM or 5PM in Sweden, depending on your nominal workday schedule. (My calendar is free any day of the week for that time.)

That works well for me, Wednesday would be a good day if that works for you?
I was about to add the Gazebo stuff in since but I started checking how to migrate the code from the old Gazebo and then I never did 🫣 If you have that PR somewhere / you are goingf to PR to that repo, I'd be in to check it out!

That works well for me, Wednesday would be a good day if that works for you?
I was about to add the Gazebo stuff in since but I started checking how to migrate the code from the old Gazebo and then I never did 🫣 If you have that PR somewhere / you are goingf to PR to that repo, I'd be in to check it out!

Great, that works for me :)
Let me get the PR in today, I'm a little late on that

Here's the simplest approach yet for disabling colcon build of packages that will eventually become universal packages (ROS1+ROS2), but that don't yet compile under ROS2: if you place a COLCON_IGNORE file in a folder, it will be ignored by colcon package discovery.
Here's one place the feature is mentioned: https://colcon.readthedocs.io/en/released/reference/discovery-arguments.html

Another note relevant to enabling a universal package to condition on ROS version: You can add <depends>ros_environment</depends> in your package.xml and it will define some standard ROS variables like $ROS_VERSION in your environment.
It seems like it defines the variables in your shell environment when you source setup.bash (you would only need to add it to one package.xml file in the workspace to get this effect). I'm not sure if it defines them in other contexts as well, like during build, or when executing files with rosrun or ros2 run.
Anyway, this might be convenient for keeping our environment management approach more standard.
Looks like it does the same thing under ROS1 and ROS2:
https://github.com/ros/ros_environment/tree/noetic/env-hooks
https://github.com/ros/ros_environment/tree/rolling/env-hooks

if you place a COLCON_IGNORE file in a folder, it will be ignored by colcon package discovery.

I just learned to my surprise that the noetic version of catkin "helpfully" respects COLCON_IGNORE markers as well, so it turns out this is not a good way to mark packages as ROS1-only.
However, given we have the autogen symlink script, an alternative approach that is arguably just as easy is to rename any ROS1-only package.xml file to package.ros1.xml. Then the autogen script will skip symlinking it when ROS_VERSION=2, colcon package discovery won't find the package, and colcon won't try to build it.
If there are no objections, I could easily submit a PR that removes the COLCON_IGNORE marker files and renames the corresponding package.xml files.

Use Marina's link above for the future. Closing this issue.


InvalidArgumentError: indices[15,28] = 22105 is not in [0, 22015) [[node encoder/embedding/embedding_lookup

I am using tf 2.4.1, keras 2.4.3, and python 3.8.10 on CPU.
I have downloaded pretrained GloVe word embeddings to train an Encoder-Decoder Model for abstractive summarization.
I have created two embedding matrices, one to represent the vocabulary of the source input documents and one to represent the summary vocabulary. I am a little unsure if this is the correct practice but the model is able to train on 100 batches until the bug in the title stops training.
Currently, the embedding matrix is of size 22015, 200. The first dimension represents the indices of the word embeddings and the second dimension represents the embedding dimension size for each word. The size of the encoder (source documents) vocabulary is taken directly from the embedding matrix = 22015. The summary vocabulary size is 7932 which is also the size of the first dimension of the summary embedding matrix. I should note that the original vocabulary sizes taken directly from dictionaries are different though come before the implementation of glove.
The Decoder model is expected to output a probability distribution over the summary vocabulary (7932 "classes"). It seems that the decoder output head is functioning as intended but the error occurs when the encoder starts to work on its word embeddings
CODE to SIMULATE issue
from keras.layers import Embedding

encoder_vocab_size = 22015
emb_dim = 200
input_dim = encoder_vocab_size
output_dim = emb_dim
Setting the weights of the Embedding layer to pretrained GloVe matrix (22015x200)
weights = [embmatrix]

The Encoder uses this embedding layer with exact configuration
embedding = Embedding(input_dim, output_dim, input_length=200, weights=weights, is_trainable=False)
Training the Encoder-Decoder Model
for epoch in range(25):
for batch, (encoder_inp_batch, decoder_input_batch, target_input_batch) in enumerate(generator):

encoder_inp_batch is shape (batch_size, 200)

decoder_input_batch is shape (batch_size, 49)

target_input_batch is shape (batch_size, 49)
with tf.GradientTape() as tape:
- Code breaks here AFTER successfully training over 100 batches of data
encoder_output, encoder_hidden_states = encoder(encoder_inp_batch)

The loss used is sparse_categorical_crossentropy as targets are not one-hot encoded. Data is passed to the model in batches of 16. Number of data points used for training ~ 5,000.
Still trying to pinpoint where exactly the embedding index out of bounds error might lie. Is it an issue arising from indices in the encoder embedding matrix or does the index out of bounds occur when feeding sequences of encoder training data where indices might be greater than the allowable range up to 22015

@EthanIrby8 ,
Can you please take a look at issue and this comment from a similar StackOverflow issue and let us know if it helps. Thanks!

@tilakrayal Sorry I should have closed this issue a few days ago. I was able to fix the bug! Thanks


Create "AmandaNP's recommendation" for proxy blocking

Using http://proxycheck.io/v2/{ip}?risk=1&asn=1&vpn=3&cur=0
Provide a recommendation on whether or not to block

<30 - No block
30-50 Use caution
>50 block
Use VPN or proxy flags as a requirement
Provide the City, Area, Location fields
Provide the Company "via" provider
Do not provide the VPN/proxy/risk flags directly to the user - only color-coded recommendations
Standard disclaimers for Nepal, Nigeria, likely Ghana, and Bangledesh until they can be tested more thoroughly
Direct warning about Russian IPs
Using the following disclaimer: "[[m:User:AmandaNP's]] recommendations are to keep you out of trouble for blocking or requesting blocks. Do not expect that this tool covers your accountability. There will be times that this recommendation will fail to recommend a block for a proxy out of pure caution. There may be times a false positive exists. This is not a substitute for a proxy expert, just like any other detection tool. This is simply meant for people who are without the skills, those unwilling to do the legwork, or those too busy to do the legwork."

Bump

Moved to https://phabricator.wikimedia.org/T382528


Simplify categorization

The current categorization is great for finding libraries.
But many PRs are put into the "wrong" category.
I've an idea for improving the situation. I'll post it here once it's more fleshed out. (It doesn't involve any third party tool.)

@brillout I am ready to consider your proposal if it is and is still relevant

Hi Ivan, I'm super busy with other things and I won't have time to further work on Awesome Vue. Unfortunately :-(.
Feel free to close this ticket.


Cast map_features energy to int16

Potential solution to #18 - question: is there any reason for state.map_features.energy to be float32?

this should save a decent amount of memory (and cut down the number of decimals in the replay files haha).


Fix to restructured text syntax

Quick small change to docstring.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Horanp seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


skin.js not found

Hi,
I'm on symfony 2.8.15 and installed IvoryCKEditorBundle 5.0.1
I'm using the office2013 skin:
configs: ck_editor_config: skin: "office2013,/bundles/{bundlename}/js/ckeditor/skins/office2013/"
And everythings works well but for unknown reasons it makes a request on a none existing resource when loading the ckeditor:
GET http://domain.lo/bundles/{bundlename}/js/ckeditor/skins/office2013/skin.js?t=H0CG 404 (Not Found)
skin.js does not exist at this location and doesn't seem to be needed since everthing works fine. But I'd like to get rid of this error..
Any idea?
Thank you

@placid2000 I have give  a look to its homepage: http://ckeditor.com/addon/office2013 and it seems it is really compatible with CKEditor 4.4 only (or at least it guarantees compatibility with this version only) whereas the bundle relies on the very last version of CKEditor (the most up to date one). Maybe related?...
Futhermore, after some more search, http://docs.ckeditor.com/#!/guide/skin_sdk_intro specifies that the skin.js file should be there... Then, IMO, you should probably report your issue directly to the office2013 plugin.

@egeloen Actually I didn't see that that version compatibility discrepancy. Thanks for the help!


Graphical walkthrough

it would be great to show a walk through using the UI for this #enable-local-git-with-kudu!

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

ID: 8e94f3fb-7da7-3ddf-bf38-32e4fea00699
Version Independent ID: 59222ad8-9930-b889-f0a9-c9bc3c642e38
Content: Deploy from local Git repo - Azure App Service
Content Source: articles/app-service/deploy-local-git.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @jsandersrocks, thanks for the feedback! I have assigned the issue to the content author to evaluate and update the doc as appropriate.

@jsandersrocks Thank for this feedback. However we need to minimize steps that depend on the portal UI in order to reduce maintenance cost on our docs, so the docs will stay put for now. Thanks for your understanding. #please-close


Update Color Picker download link to 1.3.2

I just noticed that while you updated the signal txt on this one but not the download, on the Bluetooth one you have updated neither, so maybe this is on purpose and will be done later as part of your process? If so, feel free to close at will.

Thanks, in a hurry I just forgot to commit and push some changes.


Enable strict mode with transform-strict-mode

I enable strict mode with  transform-strict-mode instead of writing it on each file. I think we don't have to add it each file. What do you think ?
Thanks in advance. 😄

Why? I've always added "use strict" to header for machine readability.
It means that editor softwares are able to know "the file is strict mode".
For example, WebStorm recognize "use strict".

@azu I misunderstood about strict mode. I appreciate your polite response.

No problem :)


Default Agent is too basic

The default agent only says "Hello, world" and does not reply to any interaction with the terminal
We can easily make it more interactive by simply uncommenting these lines:
https://github.com/nearai/nearai/blob/3fc906f0c6d4e115a64f0bc5ad986dbe102462fe/nearai/cli.py#L722-L728
This will drastically reduce the "time to first wow"

closed by #631


Type problems in tqt/function/number.py

Hello,
I tried to use a script QuantizationPool/examples/tqt/resnet20/qunat_tqt.py from your other repository, QuantizationPool, that also utilizes this TQT repository. Unfortunately, I got errors as below:
Traceback (most recent call last):
  File "quant_tqt.py", line 198, in <module>
    train(net, loss_function, optimizer, train_loader, i)
  File "quant_tqt.py", line 135, in train
    loss.backward()
  File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/tensor.py", line 118, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/autograd/__init__.py", line 93, in backward
    allow_unreachable=True)  # allow_unreachable flag
  File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/autograd/function.py", line 77, in apply
    return self._forward_cls.backward(self, *args)
  File "/home/ninnart/github/TQT/tqt/function/number.py", line 99, in backward
    grad_s = (rounded - x_div_s) * cmp0 + n * cmp1 + p * cmp2
RuntimeError: expected device cuda:0 and dtype Float but got device cuda:0 and dtype Bool

There are type errors from mismatch operations between float and bool. I was able to detect them in the following lines of code in tqt/function/number.py.
https://github.com/PannenetsF/TQT/blob/6397a57225f83e2075900678c60ffed35f64f20b/tqt/function/number.py#L58-L60
and
https://github.com/PannenetsF/TQT/blob/6397a57225f83e2075900678c60ffed35f64f20b/tqt/function/number.py#L89-L91
In general, these lines of code produce tensors with dtype bool. I was able to fix these errors by converting them to float as shown below:
cmp0 = ((n <= rounded) & (rounded <= p)).to(torch.float32)
cmp1 = (rounded < n).to(torch.float32)
cmp2 = (rounded > p).to(torch.float32)

I guess it is a version compatibility issue, and the quant-dequant functions have been test under my own conda environment.
I will finish my vacation in a week, and response of version/environment will arrive then.
Thx! :)
---Original---
From: "Ninnart @.>
Date: Mon, Oct 4, 2021 15:14 PM
To: @.>;
Cc: @.***>;
Subject: [PannenetsF/TQT] Type problems in tqt/function/number.py (#2)
Hello,
I tried to use a script QuantizationPool/examples/tqt/resnet20/qunat_tqt.py from your other repository, QuantizationPool, that also utilizes this TQT repository. Unfortunately, I got errors as below:
Traceback (most recent call last):                                                                                File "quant_tqt.py", line 198, in <module>                                                                               train(net, loss_function, optimizer, train_loader, i)                                                                File "quant_tqt.py", line 135, in train                                                                                loss.backward()                                                                                File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/tensor.py", line 118, in backward           torch.autograd.backward(self, gradient, retain_graph, create_graph)                                                  File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/autograd/init.py", line 93, in backward     allow_unreachable=True)  # allow_unreachable flag                                                                    File "/home/ninnart/.conda/envs/torch/lib/python3.6/site-packages/torch/autograd/function.py", line 77, in apply     return self._forward_cls.backward(self, *args)                                                                       File "/home/ninnart/github/TQT/tqt/function/number.py", line 99, in backward                                        grad_s = (rounded - x_div_s) * cmp0 + n * cmp1 + p * cmp2                                                          RuntimeError: expected device cuda:0 and dtype Float but got device cuda:0 and dtype Bool
There are type errors from mismatch operations between float and bool. I was able to detect them in the following lines of code in tqt/function/number.py.
https://github.com/PannenetsF/TQT/blob/6397a57225f83e2075900678c60ffed35f64f20b/tqt/function/number.py#L58-L60
and
https://github.com/PannenetsF/TQT/blob/6397a57225f83e2075900678c60ffed35f64f20b/tqt/function/number.py#L89-L91
In general, these lines of code produce tensors with dtype bool. I was able to fix these errors by converting them to float as shown below:
cmp0 = ((n <= rounded) & (rounded <= p)).to(torch.float32) cmp1 = (rounded < n).to(torch.float32) cmp2 = (rounded > p).to(torch.float32)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think so. Just to note, I used torch=1.2.0 and ppc64le.

I have just checked the torch version 1.7.1 of our x86_64 servers. Torch after 1.6.x should work with this repo. By the way, the nondifferentiable operations like floor, round have built-in backward functions in torch now. So some of the quant functions could be removed.

That is interesting. I think you can include a torch version requirement into your README.md or maybe use an if-cause statement with the torch version and support both new and old versions.

Yes, I am working on this.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_dc12c878-2be2-457a-9714-32406bebc904/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_dc12c878-2be2-457a-9714-32406bebc904.git

Docs Build status updates of commit 6f6111b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Compiler error with swift 5.8

I have a compiler error when using xCode 14.3, swift 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)):
failed to verify module interface of 'SDWebImageSwiftUI' due to the errors above; the textual interface may be broken by project issues or a compiler bug.

thanks

What build system did you use ?

CocoaPods
SwiftPM
Carthage (prebuilt-binary framework)

@dreampiggy
encountered same issue here.
I used CocoaPods + Static setting like this.
build using Xcode 14.3
Podfile
platform :ios, '14.0'

target 'some-target-name' do
  # use_frameworks!

  pod 'SDWebImage', '5.12.1', :modular_headers => true
  pod 'SDWebImageSwiftUI', '2.2.2'

end

same here !

Will fix in later. These months have no time in iOS development, focus on LLVM/Swift toolchain.

(Workaround, CocoaPods + Xcode 14.3)
Setting Project: Pods > Target: SDWebImageSwift > Settings > Build Libraries for Distribution to "No" and I was able to build the app.

Is this the same issue as #261 ? See comments there

@niccari Oh. You're using CocoaPods with Library Evolution on. The SPM does not enable Library Evolution, maybe this cause problem.

@Willicious-k @higekick @Niccari  Got the reason. It because of your SDWebImage version.
If you upgrade to 5.15.0+, it does not contains any issue at all

Can you use the Static Framework integration to test ?
use_frameworks! :linkage => :static

Seems because of that Static Lib + Library Evolution YES cause the issue

Agreed, I'm using Static Framework(not setting use_frameworks!) and Library Evolution YES in the project.
in Pods/Pods.xcodeproj/project.pbxproj, there was no "BUILD_LIBRARY_FOR_DISTRIBUTION" key and somehow "YES" used as defaults so I'll investigate why it happens.
Checked below situations.

❌ Build Failed: (Current settings) Static Libs + BUILD_LIBRARY_FOR_DISTRIBUTION = Yes
✅ Build Succeeded: Dynamic Libs for SDWebImage and SDWebImageSwiftUI + BUILD_LIBRARY_FOR_DISTRIBUTION = Yes
✅ Build Succeeded: Static Libs + BUILD_LIBRARY_FOR_DISTRIBUTION = No
✅ Build Succeeded: Dynamic Libs for SDWebImage and SDWebImageSwiftUI + BUILD_LIBRARY_FOR_DISTRIBUTION = No

And, what cause CocoaPods use Library Evolution on ? I try that :modular_headers => true it does not enable this by default.

In SDWebImageSwiftUI.podspec, it seems that swift interface needs to be generated and BUILD_LIBRARY_FOR_DISTRIBUTION is set to "yes".
https://github.com/SDWebImage/SDWebImageSwiftUI/commit/056cc697131cc71946cd0b4bf25628e4cc43d25a

@dreampiggy

And, what cause CocoaPods use Library Evolution on ? I try that :modular_headers => true it does not enable this by default.

In SDWebImageSwiftUI.podspec, it seems that swift interface needs to be generated and BUILD_LIBRARY_FOR_DISTRIBUTION is set to "yes".
https://github.com/SDWebImage/SDWebImageSwiftUI/commit/056cc697131cc71946cd0b4bf25628e4cc43d25a

Thanks! @Niccari
Seems that Podspec hack for BUILD_LIBRARY_FOR_DISTRIBUTION should be removed. I doubt what issue cause me to add this at that time (Xcode 12, 2 years agao....)
But seems this is the correcy way to go, since whether or not to enable Library Evolution is controlled by user who integrate, not the lib author


feat: adding accent and negative background color

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

:tada: This PR is included in version 12.0.0-beta.13 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:


html: select: refactor API

This PR refactors the lona.html.Select API to be more concise and convenient.

RFC: I added a patch that removes the vast majority of magic i added before. The more i think about this i think less is more here, and it is least surprising to just emulate what the browser does here.
Option.selected just sets or unsets selected in Option.attributes now and does not interact with the surrounding Select. If you decide to use a non-multiple select, but select multiple options, you can do that, but Select.value will return the value of the first selected option.
@maratori, @SmithChart, @grigolet: Which approach do you like better?

I created #329, on top of master, that contains all feedback up to this point, and using my second implementation as base. This way we make the new implementation usable before Lona 2, making the transition easier.


Be able to monitor specific domains, routes and even files for changes.

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
New Monitor
🔖 Feature description
Be able to monitor specific domains and routes for changes.
A check that runs every few hours and creates a hash fingerprint and a screenshot of a specific target domain.
Alerts if anything changed. Maybe even for specific files.
Configurable with xpath, regex, css selectors.
✔ Solution
Be able to monitor specific domains and routes for changes.
❓ Alternatives
There are alternatives but coupled with Kuma would be better :-)
📝 Additional Context
https://github.com/edgi-govdata-archiving/awesome-website-change-monitoring
https://github.com/dgtlmoon/changedetection.io

I'm not sure how that's meant to be helpfull on an uptime monitor?

I suppose you need something like this?
https://github.com/dgtlmoon/changedetection.io


Obfuscated Meshes are broken

This is what the original mesh looks like

And this is what the obfuscated mesh looks like

Only seems to happen in some meshes but its annoiyng nonetheless never knowing if i'll be able to obfuscate my avatar or not

If we could please talk about ways that this could be fixed i would appreciate it very much since i've noticed this issue for a few months now

No idea what causes this but i would really thank you for helping me fix this

Thanks for reporting! Fixed in v2.1.3.


Remove reactome-data index

We should evaluate usage of this index, and move to generating a file that can be read within data_pipeline and separately loaded into elasticsearch if necessary for rest_api

This is used by the API

Decision taken to close based on low priority and value at this point in platform refactor.

For future reference, the API uses this only to map IDs to friendly names when rendering facets. This could be removed from the API, and therefore this index could then be removed entirely.


New package: VIDA v0.1.0

Registering package: VIDA
Repository: https://github.com/ptiede/VIDA.jl
Created by: @ptiede
Version: v0.1.0
Commit: 2642ae45302bee3e3b2c7c8226976e01f1103a23
Git reference: master

[noblock] Renamed LaVIDA back to VIDA after I was told the original name was fine. I am really sorry for the confusion!

I was just wondering whats the timescale for this to be merged?